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.

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

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

Table 3-20. Sm Debug Parameters<br />

Parameter<br />

Default<br />

Value<br />

Description<br />

LoopTestOn 0 Cable loop test enable.<br />

When SM starts, if LoopTestOn is set to 1 a loop<br />

test will be started in normal mode. The LoopTest-<br />

Packets setting will specify how many packets will<br />

be injected into the loop test when started.<br />

LoopTest is a good way to validate ISL's between<br />

switches in a cluster.<br />

By default Loop test runs in default mode. In the<br />

default mode, the SM uses an exhaustive<br />

approach to setup loop routes and will include<br />

each ISL in as many loops as possible. This<br />

ensures that each ISL is exactly in the same number<br />

of loops and hence will see the same amount<br />

of utilization. But finding all possible loops is computationally<br />

intensive and can take a long amount<br />

of time.<br />

LoopTestFastMode 0 Puts LoopTest in fast mode when set to 1, when<br />

started based on LoopTestOn setting.<br />

Under this mode, loop test doesn't attempt to<br />

include each ISL in all possible loops, but includes<br />

it in at least the specified number of loops (this<br />

value is controlled via the MinISLRedundancy<br />

parameter).<br />

In typical fast mode operations (with the default<br />

MinISLRedundancy of 4), injecting four packets<br />

into each loop is sufficient to get a high utilization<br />

on the ISLs.<br />

LoopTestPackets 0 Number of packets to inject. If the XML tag is not<br />

set or commented out in the XML configuration file<br />

but loop test has been enabled in the configuration<br />

file, then a loop test will start but since the packet<br />

count is zero, no packets will be injected into the<br />

loops for testing. Using one of the inject CLI commands<br />

the user can manually inject packets.<br />

LIDSpacing 0 Spacing of LIDs to test LFT<br />

SaRmppChecksum 0 RMPP internal checksum<br />

DynamicPortAlloc 1 This parameter is for development use only.<br />

IB0054608-01 B 3-51

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

Saved successfully!

Ooh no, something went wrong!