AB291A Fabric Clustering System Support Guide (12-port Switch), April 2004

Chapter 6
Monitoring and Troubleshooting
Monitoring and Troubleshooting the Switch
121
• Trace-Level
•Flow
Application The number of applications may change between releases. The numbers assigned to
applications may also change. Check application and module number assignments using CLI help (i.e.,?)
before setting a trace level.
Module "Module" is used to specify what module of code (library), in the selected application tracing should
be configured for.
The number of modules may change between releases. The numbers assigned to modules may also change.
Check module number assignments using CLI help (i.e.,?) before setting trace levels.
Trace-Level "Trace-Level" is used to specify the verbosity of the output. You can specify different levels of
verbosity to control the amount of the tracing information that is generated.
Trace levels are described in the following table:
The information at the specified level and below is shown. For example, if you are only interested in seeing
information that belongs to the VERBOSE category, you can dynamically set the control to VERBOSE. The
trace software will then display information in the VERBOSE, TERSE and VERY_TERSE categories.
Flow "Flow" is used to specify a particular flow in the code. How flows are specified varies, depending on the
module.
• 0x1: This flow shows all the Subnet Management (SM) discovery, assignment routing and routing
processing.
• 0x2: This flow shows all the Subnet Management Agent (SA) related processing.
• 0x4: This flow shows the trap related processing.
• 0x8: This flow shows the redundancy related processing.
Table 6-5 Trace Level Descriptions
Trace Level Description
NO_DISPLAY No tracing information will be generated. This is the default setting to ensure the best
SM performance.
VERY_TERSE Not currently used.
TERSE This level is used to generate the basic flow of MAD packet as it goes through the
Subnet Manager state machine. Verbose description will be made to the success or
failure of the MAD packet. For example, a PathRecord lookup failure will include
description on the cause of the failure (SGID is not found in database, DGID is not
found in database, no component is specified in the component mask…) instead of
simple success or failure code.
VERBOSE This level shows the MAD management class header information.
VERY_VERBOS
E
This level shows the MAD in a decoded format according to HP Fabric Clustering
System Switch decoding algorithm.
SCREAM This level shows the MAD in its raw format.