User Manual

Rev 2.1-1.0.6
Mellanox Technologies
139
bound to 1 port at a time.
If GUID given is 0, OpenSM displays a list
of possible port GUIDs and waits for user input.
Without -g, OpenSM tries to use the default port.
--lmc, -l <LMC>
This option specifies the subnet's LMC value.
The number of LIDs assigned to each port is 2^LMC.
The LMC value must be in the range 0-7.
LMC values > 0 allow multiple paths between ports.
LMC values > 0 should only be used if the subnet
topology actually provides multiple paths between
ports, i.e. multiple interconnects between switches.
Without -l, OpenSM defaults to LMC = 0, which allows
one path between any two ports.
--priority, -p <PRIORITY>
This option specifies the SM's PRIORITY.
This will effect the handover cases, where master
is chosen by priority and GUID. Range goes
from 0 (lowest priority) to 15 (highest).
--smkey, -k <SM_Key>
This option specifies the SM's SM_Key (64 bits).
This will effect SM authentication.
Note that OpenSM version 3.2.1 and below used the
default value '1' in a host byte order, it is fixed
now but you may need this option to interoperate
with old OpenSM running on a little endian machine.
--reassign_lids, -r
This option causes OpenSM to reassign LIDs to all
end nodes. Specifying -r on a running subnet
may disrupt subnet traffic.
Without -r, OpenSM attempts to preserve existing
LID assignments resolving multiple use of same LID.
--routing_engine, -R <engine name>
This option chooses routing engine(s) to use instead of default
Min Hop algorithm. Multiple routing engines can be specified
separated by commas so that specific ordering of routing
algorithms will be tried if earlier routing engines fail.
If all configured routing engines fail, OpenSM will always
attempt to route with Min Hop unless 'no_fallback' is
included in the list of routing engines.
Supported engines: updn, file, ftree, lash, dor, torus-2QoS