User Manual

Features Overview and ConfigurationRev 2.3-1.0.1
Mellanox Technologies
98
Routing Engine Qualifiers
Unlike unicast-step and end-unicast-step 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 colon in the qualifier values will result in the policy's
failure.
Parameter Description Example
id ‘id’ is mandatory. Without an id qualifier
for each engine, the policy fails.
• Legal values – size_t value (0 is illegal).
• The engines in the policy chain are set accord-
ing to an ascending id order, so it is highly cru-
cial to verify that the id that is given to the
engines match the order in which you would
like the engines to be set.
is: 1
engine This is a mandatory qualifier that
describes the routing algorithm used
within this unicast step.
Currently, on the first phase of routing
chains, legal values are minhop/ftree/
updn.
engine: minhop
use This is an optional qualifier that enables
one to describe the usage of this unicast
step. If undefined, an empty string is used
as a default.
use: ftree routing for
for yellow stone
nodes
config This is an optional qualifier that enables
one to define a separate opensm config
file for a specific unicast step. If unde
-
fined, all parameters are taken from main
opensm configuration file.
config: /etc/config/
opensm2.cfg
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