User Manual

Rev 2.3-1.0.1

Mellanox Technologies

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.

sl2vl and mcfdbs files are dumped only once for the entire fabric and NOT by every rout-

ing engine.

• Each engine concatenates its ID and routing algorithm name in its dump files names, as

follows:

• opensm-lid-matrix.2.minhop.dump

• opensm.fdbs.3.ftree

• opensm-subnet.4.updn.lst

• In case that a fallback routing engine is used, both the routing engine that failed and the

fallback engine that replaces it, dump their data.

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 of

fset 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 speci-

fied)

Path-bit: 1

Parameter Description Example