Skip to main content

Cornelis Technical Documentation

5.2.5. Using Configuration Files

To configure virtual fabrics, you can use either opafm.xml or opafm_pp.xml, depending on your use case.

If you are using multi-tenancy (refer to Virtual Fabrics for Multi-Tenancy), use opafm_pp.xml; if not, use opafm.xml.

5.2.5.1. Fabric Manager Configuration File (opafm.xml)

opafm.xml is the Fabric Manager (FM) configuration file. Modify this file directly when you want to configure or update the FM's core settings.

Note

  • The opafm.xml configuration file is located under the /etc/opa-fm directory and is self-documented.

  • In case of corruption, a copy of the opafm.xml file can be found under /usr/share/opa-fm/.

The configuration file, opafm.xml, defines the following:

  • FM management entities are to be run on this FM host or chassis for each subnet to which the host is attached (by definition a chassis is only connected to one subnet).

  • Operational parameters for the fabric, such as routing and time-outs.

  • vFabrics to be configured.

  • Configuration for each FM component, such as sweep rates, logging options, and retries.

To make a change to an FM’s configuration, edit the opafm.xml configuration file and restart the FM.

The configuration of vFabrics consists of the following sections in the Fabric Manager configuration file opafm.xml:

  • Applications - Describes applications that can run on one or more end nodes.

  • DeviceGroups - Describes a set of end nodes in the fabric.

  • QOSGroups - Defines various levels of quality of service (QoS) supported in dynamic virtual fabric configurations with multiple virtual fabrics (refer to Multiple Virtual Fabrics).

  • VirtualFabrics - Defines a vFabric consisting of a group of applications, a set of devices, and the operating parameters for the vFabric.

Note

To configure multi-tenant virtual fabrics, the preferred method is to use the opafmvf command (refer to opafmvf).

To configure QOSGroups, you modify the opafm_pp.xml.

Each section must be given a unique name that is used to reference it.

Applications, DeviceGroups, and VirtualFabrics may be defined in the Common or Fm sections.

  • The Common section applies to all Fm Instances.

  • The Fm section describes additional Applications, DeviceGroups, or VirtualFabrics that are specific to the given Fm instance.

5.2.5.2. Fabric Manager vFabric Configuration File (opafm_pp.xml)

This file is the vFabric configuration file that allows you to include fragmentary changes to the opafm.xml file. Use this file to configure multiple vFabrics and set up QOSGroups.

To simplify creating configurations with multiple virtual fabrics, an XML file is provided at /etc/opa-fm/opafm_pp.xml. This contains sample QOSGroups and the Admin VirtualFabric.

  • QOSGroups are defined in the opafm_pp.xml file to ensure that no vFabric can be added or removed that would change QoS policies or VL assignments, which would create fabric disruption.

    QOSGroups define QoS parameters that can be used when configuring vFabrics. Every enabled vFabric must specify a QOSGroup.

  • The Admin vFabric is included in the opafm_pp.xml file to ensure that it will not be removed during reconfiguration.

Along with these settings, the vFabric XML contains the following comment lines under DeviceGroups and VirtualFabrics, respectively:

<!-- INCLUDE:DG_DIR=/etc/opa-fm/dgs -->
<!-- INCLUDE:VF_DIR=/etc/opa-fm/vfs -->

In each INCLUDE directory, individual files containing a specific DeviceGroup or VirtualFabric can be added or removed.

Refer to Modifying the vFabric Configuration File for Multiple vFabrics for more information on how the file is used.

Fabric Manager - This is an OPX Software component responsible for managing the fabric using management packets over a dedicated virtual lane (VL15).

Virtual Lane - This feature allows multiple, multiplexed, independent data to stream onto a single physical link.