User Manual

Rev 2.3-1.0.1

Mellanox Technologies

Table 4 - Topology Qualifiers

Parameter Description Example

id Topology ID.

Legal Values – any positive value.

Must be unique.

id: 1

sw-grp Name of the port group that includes all

switches and switch ports to be used in

this topology.

sw-grp: ys_switches

hca-grp Name of the port group that includes all

HCA’s to be used in this topology.

hca-grp: ys_hosts

Configuration File per Routing Engine

Each engine in the routing chain can be provided by its own configuration file. Routing engine

configuration file is the fraction of parameters defined in the main opensm configuration file.

Some rules should be applied when defining a particular configuration file for a routing engine:

• Parameters that are not specified in specific routing engine configuration file are inher-

ited from the main opensm configuration file.

• The following configuration parameters are taking effect only in the main opensm con-

figuration file:

• qos and qos_* settings like (vl_arb, sl2vl, etc.)

• lmc

• routing_engine

Defining a Routing Chain Policy File

In order to define a port group policy file, set the parameter 'rch_policy_file' in the opensm con-

figuration file.

rch_policy_file /etc/opensm/conf/chains_policy_file

First Routing Engine in the Chain

The first unicast engine in a routing chain must include all switches and HCA's in the fabric

(topology id must be 0). The path-bit parameter value is path-bit 0 and it cannot be changed.

Configuring a Routing Chains Policy

The routing chains policy file details the routing engines (and their fallback engines) used for the

fabric's routing. The policy file should be composed of one or more paragraphs which defines an

engine (or a fallback engine). Each paragraph should begin with the line 'unicast-step' and end

with the line 'end-unicast-step'.

For example

unicast-step

…routing engine qualifiers…

end-unicast-step