26.12.2014 Views

Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3–<strong>Fabric</strong> <strong>Manager</strong> Configuration<br />

Configuring the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong><br />

Sm Parameters<br />

SM Redundancy<br />

The following tables describe parameters that can be used in the Sm subsection of<br />

either the Common or Fm sections.<br />

Any parameter which can be used in the Common.Shared section may also be<br />

used in the Common.Sm or Fm.Sm sections.<br />

The parameters in Table 3-3 control SM Failover, they complement the Priority<br />

and ElevatedPriority parameters that are used in the Shared section and can<br />

also be used in the Sm section if needed.<br />

Table 3-3. Sm Redundancy Parameters<br />

Parameter<br />

Default<br />

Value<br />

Description<br />

MasterPingInterval 5 MasterPingInterval is the interval in seconds<br />

at which the secondary SM pings<br />

the master (the ping occurs using an<br />

inband SM packet).<br />

MasterPingMaxFail 3 Number of times a secondary’s ping of<br />

the master must fail before renegotiation<br />

of a new master occurs.<br />

DbSyncInterval 15 Secondary SMs will synchronize their<br />

fabric database with the master at<br />

DbSyncInterval minutes. If set to 0, Db<br />

synchronization is disabled.<br />

<strong>Fabric</strong> Routing<br />

The following Routing Algorithms are supported<br />

• shortestpath - pick shortest path and balance lids on ISLs<br />

• fattree — shortest path with better balancing for fat tree topology<br />

• SpineFirstRouting - option to avoid credit loops in complex fabrics with<br />

<strong>QLogic</strong> Switches. Given equal length routes, routes through chassis spine<br />

first. Hence avoids loops caused by routing via edge/leaf switches instead of<br />

spines.<br />

• dor-updown - Direction Ordered routing with updown. This routing algorithm<br />

is for mesh and torus topologies. For torus topologies, dor-updown requires<br />

2 VLs on Inter Switch Links and uses 2 dimensions SLs (limit of 4 dimensions).<br />

When a fabric disruption occurs, an additional VL and SL is used for an<br />

Up/Down style non-optimal routing around the failure (therefore, limited to 3<br />

dimensions).<br />

3-14 IB0054608-01 B

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!