HP Integrity Superdome 2 16-socket HP Integrity Superdome 2 User Service Guide - Page 49

Troubleshooting, Methodology, General troubleshooting methodology, LED status information, OA access

Get HP Integrity Superdome 2 16-socket PDF manuals and user guides View all HP Integrity Superdome 2 16-socket manuals
Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

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) for more information. 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: Only use the OA serial port for initial system setup. Once the network is configured, 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: Thermal Danger OK Cooling OK Device Failure OK Device Degraded OK Firmware Mismatch OK If no issues are seen in the command output, then more troubleshooting information is required. Methodology 49

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
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)
for more information.
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:
Only use the OA serial port for initial system setup. Once the network is configured,
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:
Thermal Danger
OK
Cooling
OK
Device Failure
OK
Device Degraded
OK
Firmware Mismatch
OK
If no issues are seen in the command output, then more troubleshooting information is required.
Methodology
49