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 (Continued)<br />

Parameter<br />

Default<br />

Value<br />

Description<br />

TrapLogSuppressTriggerInterval<br />

30 If traps are received from the same port within the<br />

interval (in seconds), logging of traps from that<br />

port will be suppressed.<br />

Log suppression is disabled if set to 0.<br />

CS_LogMask<br />

MAI_LogMask<br />

CAL_LogMask<br />

DVR_LogMask<br />

IF3_LogMask<br />

SM_LogMask<br />

SA_LogMask<br />

PM_LogMask<br />

PA_LogMask<br />

BM_LogMask<br />

FE_LogMask<br />

APP_LogMask<br />

0x000000<br />

00<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

0x000001f<br />

f<br />

Alternative to use of LogLevel. For advanced<br />

users, these parameters can provide more precise<br />

control over per subsystem logging. For typical<br />

configurations these should be omitted and the<br />

LogLevel parameter should be used instead.<br />

For each subsystem there can be a LogMask. The<br />

mask selects severities of log messages to enable<br />

and is a sum of the following values:<br />

0x1=fatal<br />

0x2=actionable error<br />

0x4=actionable warning<br />

0x8=actionable notice<br />

0x10=actionable info<br />

0x20=error<br />

0x40=warn<br />

0x80=notice<br />

0x100=progress<br />

0x200=info<br />

0x400=verbose<br />

0x800=data<br />

0x1000=debug1<br />

0x2000=debug2<br />

0x4000=debug3<br />

0x8000=debug4<br />

0x10000=func call<br />

0x20000=func args<br />

0x40000=func exit<br />

For embedded FM corresponding Chassis Logging<br />

must also be enabled and Sm configuration<br />

applies to all managers<br />

For Host FM, the linux syslog service will need to<br />

have an appropriate level of logging enabled.<br />

3-52 IB0054608-01 B

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

Saved successfully!

Ooh no, something went wrong!