IBM HS12 Service Guide - Page 125

About the checkout procedure, Performing the checkout procedure

Get IBM HS12 - BladeCenter - 8028 PDF manuals and user guides
UPC - 883436037129
View all IBM HS12 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 125 highlights

About the checkout procedure Use this information to run diagnostics, locate error codes, and identify device errors for the blade server. Before you perform the checkout procedure for diagnosing hardware problems, review the following information: v Read "Safety" on page v. v The diagnostic programs provide the primary methods of testing the major components of the blade server. If you are not sure whether a problem is caused by the hardware or by the software, you can use the diagnostic programs to confirm that the hardware is working correctly. v When you run the diagnostic programs, a single problem might cause more than one error message. When this happens, correct the cause of the first error message. The other error messages usually will not occur the next time you run the diagnostic programs. Exception: If multiple error codes or light path diagnostics LEDs indicate a microprocessor error, the error might be in a microprocessor or in a microprocessor socket. See "Microprocessor problems" on page 117 for information about diagnosing microprocessor problems. v If the blade server is halted and a POST error code is displayed, see "POST error codes" on page 86. If the blade server is halted and no error message is displayed, see "Troubleshooting tables" on page 114 and "Solving undetermined problems" on page 171. v For intermittent problems, check the error log; see "Error logs" on page 76 and "Dynamic system analysis diagnostic programs and messages" on page 132. v If no LEDs are lit on the blade server front panel, verify the blade server status and errors in the management-module Web interface; also see "Solving undetermined problems" on page 171. v If device errors occur, see "Troubleshooting tables" on page 114. Performing the checkout procedure Use this information to perform the checkout procedure for the blade server. To perform the checkout procedure, complete the following steps: 1. If the blade server is running, turn off the blade server. 2. Turn on the blade server. Make sure that the blade server has control of the video (the LED on the keyboard/video/mouse button is lit). If the blade server does not start, see "Troubleshooting tables" on page 114. 3. Record any POST beep codes that sound or POST error messages that are displayed on the monitor. If an error is displayed, look up the first error in the "POST error codes" on page 86. 4. Check the control panel blade-error LED; if it is lit, check the light path diagnostics LEDs (see "Light path diagnostics" on page 127). 5. Check for the following results: v Successful completion of POST, indicated by a single beep. v Successful completion of startup, indicated by a readable display of the operating-system desktop. 6. Did a single beep sound and are there readable instructions on the main menu? v No: Find the failure symptom in "Troubleshooting tables" on page 114; if necessary, see "Solving undetermined problems" on page 171. Chapter 6. Diagnostics 113

  • 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
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
About the checkout procedure
Use this information to run diagnostics, locate error codes, and identify device
errors for the blade server.
Before you perform the checkout procedure for diagnosing hardware problems,
review the following information:
v
Read “Safety” on page v.
v
The diagnostic programs provide the primary methods of testing the major
components of the blade server. If you are not sure whether a problem is caused
by the hardware or by the software, you can use the diagnostic programs to
confirm that the hardware is working correctly.
v
When you run the diagnostic programs, a single problem might cause more than
one error message. When this happens, correct the cause of the first error
message. The other error messages usually will not occur the next time you run
the diagnostic programs.
Exception:
If multiple error codes or light path diagnostics LEDs indicate a
microprocessor error, the error might be in a microprocessor or in a
microprocessor socket. See “Microprocessor problems” on page 117 for
information about diagnosing microprocessor problems.
v
If the blade server is halted and a POST error code is displayed, see “POST error
codes” on page 86. If the blade server is halted and no error message is
displayed, see “Troubleshooting tables” on page 114 and “Solving undetermined
problems” on page 171.
v
For intermittent problems, check the error log; see “Error logs” on page 76 and
“Dynamic system analysis diagnostic programs and messages” on page 132.
v
If no LEDs are lit on the blade server front panel, verify the blade server status
and errors in the management-module Web interface; also see “Solving
undetermined problems” on page 171.
v
If device errors occur, see “Troubleshooting tables” on page 114.
Performing the checkout procedure
Use this information to perform the checkout procedure for the blade server.
To perform the checkout procedure, complete the following steps:
1.
If the blade server is running, turn off the blade server.
2.
Turn on the blade server. Make sure that the blade server has control of the
video (the LED on the keyboard/video/mouse button is lit). If the blade server
does not start, see “Troubleshooting tables” on page 114.
3.
Record any POST beep codes that sound or POST error messages that are
displayed on the monitor. If an error is displayed, look up the first error in the
“POST error codes” on page 86.
4.
Check the control panel blade-error LED; if it is lit, check the light path
diagnostics LEDs (see “Light path diagnostics” on page 127).
5.
Check for the following results:
v
Successful completion of POST, indicated by a single beep.
v
Successful completion of startup, indicated by a readable display of the
operating-system desktop.
6.
Did a single beep sound and are there readable instructions on the main menu?
v
No:
Find the failure symptom in “Troubleshooting tables” on page 114; if
necessary, see “Solving undetermined problems” on page 171.
Chapter 6. Diagnostics
113