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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1–Overview of the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong> Suite<br />

SM Algorithms & Features<br />

SM Algorithms & Features<br />

Routing Algorithms in the SM<br />

The primary routing algorithm selects, for every pair of nodes in the fabric, the<br />

quickest path available. In the case where there is more than one path available,<br />

load-balancing of the paths occurs over the available ports at each switch to get<br />

an even distribution of traffic over the fabric. Refer to “Routing Algorithm” on<br />

page 2-3 for detailed information.<br />

Spine-first routing is an optional feature that, when enabled, will favor paths that<br />

route through a chassis, rather than a path that exits and then re-enters a chassis.<br />

This helps eliminate cycles (for example, credit loops) on fabrics where such<br />

routes are possible. Refer to “Shortest Path” on page 2-3 for more information.<br />

LID Mask Control (LMC)<br />

The LMC feature provides a method for assigning multiple addresses, local<br />

identifiers (LIDs) to a single physical port. This allows for multiple paths through<br />

the fabric to be configured between a single pair of nodes. When enabled, the<br />

routing algorithm will attempt to ensure that these paths are placed on unique<br />

hardware when possible in order to reduce disruption in the case of switch failure.<br />

Each end-node port will have 2 LMC address LIDs. Refer to “LMC, Dispersive<br />

Routing and <strong>Fabric</strong> Resiliency” on page 2-8 for detailed information.<br />

Multicast Group Support<br />

Multicast groups are used to direct one-to-many and many-to-many traffic. Nodes<br />

subscribe to multicast groups by issuing requests to the SM. The user may use<br />

SM CLI commands to manage multicast groups. Refer to “<strong>Fabric</strong> Multicast<br />

Routing” on page 2-16 for detailed information.<br />

<strong>Fabric</strong> <strong>Manager</strong>’s InfiniBand Subnet <strong>Manager</strong><br />

The <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong> implemented a complete InfiniBand Subnet <strong>Manager</strong><br />

(SM). The SM is responsible for monitoring, initializing and configuring the fabric.<br />

One of the critical roles of the SM is the initialization and configuration of routing<br />

tables in all the switches. The <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong>’s SM supports a variety of<br />

routing algorithms which will be discussed in detail later in this guide. Among the<br />

capabilities are:<br />

• Support for a wide range of fabric topologies, including Fat Tree, Clos<br />

network, Mesh/Torus and various irregular topologies<br />

• Support for assigning multiple LIDs to end nodes and the carefully balanced<br />

programming of alternate routes through the fabric for use by dispersive<br />

routing, load balancing and failover techniques by various upper level<br />

protocols (ULP).<br />

1-12 IB0054608-01 B

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

Saved successfully!

Ooh no, something went wrong!