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

Chapter 6
Monitoring and Troubleshooting
Monitoring and Troubleshooting the Switch
120
Monitoring and Troubleshooting the Switch
The CLI can also be used to monitor the system.
Health Monitoring
The system is a robust product with fail-over protection. In the event a physical component fails, a similar one
automatically assumes the load of the failed component.
The physical components should be checked on occasion, particularly if there are problems with the initial
setup and configuration.
The HP Fabric Clustering System Switch, and controller may be monitored in several ways. Switch cluster
connections and controller cards include a general system LED to indicate the physical health of the card.
Card status information may be displayed in the CLI that indicates the success or failure of the boot process.
Ports may be monitored in several ways. You may check a port physically by looking at the port LEDs. You
may also open various graph and statistics windows to notice network traffic across the port. If there is no
traffic going across what should otherwise be a busy port, refer to status LEDs next to the port or check the
physical connections.
Traffic can be analyzed across individual ports or aggregated total across interface cards.
About Logging and Tracing
In general, two types of messages are generated: Events and Traces.
About HP Fabric Clustering System Events
Event messages are generated whenever a significant event occurs in the system, and cannot be turned-off or
configured by the user.
The following types of scenarios fall into the Events category.
• A Subnet Manager has been started (created)
• A new Fabric node is in-service
• An existing Fabric node is out-of-service
• A new Fabric multicast group is created
• A new multicast member is added to an existing multicast group
• An existing multicast group is deleted
About Tracing
Trace messages are only generated when the user has explicitly enabling tracing for
debugging/trouble-shooting purposes. By default, tracing is disabled.
The trace feature has different levels of control to allow the user to dynamically select the amount and/or type
of tracing information to be generated.
• Application
Levels of Traces
• Module