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.

2–Advanced <strong>Fabric</strong> <strong>Manager</strong> Capabilities<br />

Mesh/Torus Topology Support<br />

It is important to understand that the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong>’s shortestpath<br />

algorithm can be used to temporarily route a Mesh/Torus for low bandwidth basic<br />

operations such as fabric topology verification and the configuration of externally<br />

managed switches. The shortestpath algorithm will be able to route the fabric in a<br />

usable manner for such operations, however it will have credit loops. Such credit<br />

loops will not cause issues for low bandwidth operations nor for operations where<br />

only two nodes in the fabric are using high bandwidth (such as loading firmware<br />

on a externally managed switch). However attempts to run real MPI jobs with<br />

multiple nodes or collectives or even Fast<strong>Fabric</strong> MPI Performance verification<br />

tools while using shortestpath are likely to induce credit loops and cause<br />

extremely poor performance.<br />

Topology Configuration in the <strong>Fabric</strong> <strong>Manager</strong><br />

When using the dor-updown algorithm, the Mesh/Torus topology information must<br />

be configured in the <strong>Fabric</strong> <strong>Manager</strong> configuration file. Only the ISLs that<br />

constitute the different dimensions of the Mesh or Torus must be defined. All ISLs<br />

in the fabric which have not been configured in this section will be considered<br />

invalid and ignored when the dor-updown algorithm is selected as the routing<br />

algorithm.<br />

The <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong> only needs the “ISL pattern” to be defined. It merely<br />

needs to know which pairs of ports will be connected to form each dimension. It<br />

does not need to know any specific details about the switches. Replacement of<br />

switches will not require any configuration changes.<br />

This is necessary so that the <strong>Fabric</strong> <strong>Manager</strong> can be aware of the intended<br />

topology and therefore properly configure SLs and VLs. This approach allows the<br />

<strong>Fabric</strong> <strong>Manager</strong> to minimize impacts when large fabric changes occur, such as the<br />

loss/reappearance of toroidal links or loss/reappearance of an entire dimension.<br />

The SM will ignore the invalid links and proceed ahead with the sweep and will<br />

make the best case effort to finish the sweep, so that other tools (like Fast<strong>Fabric</strong>)<br />

can be used to verify the condition of the fabric. If there are warnings related to<br />

invalid links, it is highly recommended to verify the cable connections in the fabric.<br />

At the end of the sweep, the SM will show all the invalid ISL port pairs it found<br />

during the sweep.<br />

In Mesh fabrics, the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong> will allow Channel Adapters to be<br />

connected to unused switch ports at the edges of each mesh dimension. For<br />

example, in the picture below, when using 36 port switches. There could be<br />

additional servers on edge and corner switches, such as:<br />

• Switch E: 32 servers<br />

• Switch B, D, F, H: 33 servers<br />

• Switch A, C, G, I: 34 servers<br />

IB0054608-01 B 2-15

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

Saved successfully!

Ooh no, something went wrong!