5 Troubleshooting
The purpose of this chapter is to provide a preferred methodology (strategies and procedures) and
tools for troubleshooting complex error and fault conditions.
Methodology
General troubleshooting methodology
The system provides several sources of information for troubleshooting:
LED status information
Front door display/insight display
The OA CLI
The OA GUI
LED status information
The LEDs provide initial status and health information. LED information should be verified by the
other sources of status information.
See
"Superdome 2 LEDs and components" (page 55)
TIP:
The CLI is the most efficient way to verify the information provided from LEDs.
OA access
You can access the Superdome 2 OA by using either a telnet session or a ssh connection. This
can be done by connecting a laptop to the eSwitch using a standard LAN cable using telnet.
IMPORTANT:
the OA should be always be accessed using telnet or ssh.
CLI
Superdome 2 troubleshooting tools differ from both Superdome and other IA64 blade systems.
The central point of communication for gaining system status is the active OA.
HP recommends checking the system status information using show complex status before
continuing with troubleshooting:
sd-oa1> show complex status
Status: OK
Enclosure ID: OK
Enclosure: OK
Robust Store: OK
CAMNET: OK
Product ID: OK
Xfabric: OK
Diagnostic Status:
If no issues are seen in the command output, then more troubleshooting information is required.
Only use the OA serial port for initial system setup. Once the network is configured,
Thermal Danger
Cooling
Device Failure
Device Degraded
Firmware Mismatch
for more information.
OK
OK
OK
OK
OK
Methodology
49