Table 7-7 Trace Level Descriptions (continued)

Trace Level

Description

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_VERBOSE

This level shows the MAD in a decoded format according to HP Fabric Switch decoding

 

algorithm.

 

 

SCREAM

This level shows the MAD in its raw format.

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.

•0x10: This flow shows the Related Multipack Protocol (RMPP) related processing.

•0x20: This flow shows the partition management related processing.

•0x1000: This flow shows the internal state machine (may create more flow for more granularity for path, mcast, …).

•0x2000: This flow shows the user configuration management related processing.

•0x4000: This flow triggers the HP Fabric Switch Subnet Manager to take a snap shot of the current logging information for the trace.

For example, use:

•0x4001 to take a snapshot of the SM logging information.

•0x4002 to take a snapshot of the SA information.

•0x8000: This flow triggers the MAD packet to be displayed.

For example, use:

•0x8002 to display MAD packets and SA related processing.

•0x8001 to display SM MAD packets and SM related processing.

Troubleshooting the HP Fabric Network

Ping

As on any IP network, you can use the UNIX ping command to test connectivity between IPoIB HP Fabric-attached hosts. For more information, see “Verifying Connectivity” in Chapter 3.

126 Monitoring and Troubleshooting