User Manual

Rev 2.2-1.0.1
Mellanox Technologies
195
For example:
topology
…topology qualifiers…
end-topology
Topology Qualifiers
Unlike topology and end-topology which do not require a colon, all qualifiers must end
with a colon (':'). Also - a colon is a predefined mark that must not be used inside qualifier
values. An inclusion of a column in the qualifier values will result in the policy's failure.
All topology qualifiers are mandatory. Absence of any of the below qualifiers will cause the pol-
icy parsing to fail.
Table 21 - 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
8.5.8.3 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