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-16. Sm <strong>Fabric</strong> Sweep Parameters<br />

Parameter<br />

Default<br />

Value<br />

Description<br />

SweepInterval 300 The SM sweeps immediately upon fabric<br />

changes based on traps from the switches. Since<br />

traps can be lost, the SM also has a slow periodic<br />

sweep at a maximum of SweepInterval seconds<br />

to verify fabric config.<br />

IgnoreTraps 0 Do not sweep or log when traps occur when<br />

enabled (1)<br />

MaxAttempts<br />

RespTimeout<br />

MinRespTimeout<br />

SweepErrorsThreshold<br />

SweepAbandonThreshold<br />

3<br />

250<br />

35<br />

0<br />

3<br />

The SM will spend up to RespTimeout multiplied<br />

by MaxAttempts per packet. These allow<br />

two modes of operation.<br />

When MinRespTimeout is non-zero: the SM<br />

will start with MinRespTimeout as the time-out<br />

value for requests and use multiples of this value<br />

for subsequent attempts if there is a time-out in<br />

the previous attempt. SM will keep retrying until<br />

the cumulative sum of time-outs for retries is less<br />

than RespTimeout multiplied by MaxAttempts.<br />

This approach is recommended and<br />

will react quickly to lost packets while still allowing<br />

adequate time for slower SMAs to respond.<br />

When MinRespTimeout is zero: upon a<br />

time-out, up to MaxAttempts are attempted<br />

with each attempt having a time-out of Resp-<br />

Timeout. This approach is provided for backward<br />

compatibility with previous SM versions.<br />

When there are a large number of fabric changes<br />

at once, the SM could have lots of errors while<br />

attempting to access/program devices which disappeared<br />

mid-sweep. If the SM receives more<br />

than the set SweepErrorsThreshold parameter of<br />

errors in a given sweep, it will give up and start<br />

the sweep over. When the SM abandons more<br />

than the set SweepAbandonThreshold parameter<br />

of sweeps in a row the SM will do its best to<br />

complete the sweep.<br />

TrapThreshold 0 If a given port issues more than the Trap-<br />

Threshold traps/minute value it will be disabled<br />

as an unstable port. 0 disables this feature.<br />

IB0054608-01 B 3-45

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

Saved successfully!

Ooh no, something went wrong!