User Manual

Rev 2.2-1.0.1
Mellanox Technologies
197
Dump Files per Routing Engine
Each routing engine on the chain will dump its own data files if the appropriate log_flags
is set (for instance 0x43).
The files that are dumped by each engine are:
• opensm-lid-matrix.dump
• opensm-lfts.dump
• opensm.fdbs
• opensm-subnet.lst
These files should contain the relevant data for each engine topology.
topology Define the topology that this engine uses.
• Legal value – id of an existing topology that is
defined in topologies policy (or zero that repre
-
sents the entire fabric and not a specific topol-
ogy).
• Default value – If unspecified, a routing engine
will relate to the entire fabric (as if topology
zero was defined).
• Notice: The first routing engine (the engine
with the lowest id) MUST be configured with
topology: 0 (entire fabric) or else, the routing
chain parser will fail.
topology: 1
fallback-to This is an optional qualifier that enables one
to define the current unicast step as a fallback
to another unicast step. This can be done by
defining the id of the unicast step that this step
is a fallback to.
• If undefined, the current unicast step is not a
fallback.
• If the value of this qualifier is a non-existent
engine id, this step will be ignored.
• A fallback step is meaningless if the step it is a
fallback to did not fail.
• It is impossible to define a fallback to a fall-
back step (such definition will be ignored)
-
path-bit This is an optional qualifier that enables one
to define a specific lid offset to be used by the
current unicast step. Setting lmc > 0 in main
opensm configuration file is a prerequisite for
assigning specific path-bit for the routing
engine.
Default value is 0 (if path-bit is not specified)
Path-bit: 1
Table 22 - Routing Engine Qualifiers
Parameter Description Example