IBM 8668 Hardware Maintenance Manual - Page 21

Diagnostics, Diagnostic tools overview, POST

Get IBM 8668 - Eserver xSeries 232 PDF manuals and user guides
UPC - 087944723158
View all IBM 8668 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Diagnostics This section provides basic troubleshooting information to help you resolve some common problems that might occur with the server. If you cannot locate and correct the problem using the information in this section, refer to "Symptom-to-FRU index" on page 107 for more information. Diagnostic tools overview The following tools are available to help you identify and resolve hardware-related problems: v POST beep codes, error messages, and error logs The power-on self-test (POST) generates beep codes and messages to indicate successful test completion or the detection of a problem. See "POST" for more information. v Light Path Diagnostics The server has light-emitting diodes (LEDs) to help you identify problems with server components. These LEDs are part of the Light Path Diagnostics feature that is built into the server. By following the path of lights, you can quickly identify the type of system error. See "Identifying problems using status LEDs" on page 18 for more information. v Diagnostic programs and error messages The server diagnostic programs are stored in upgradable read-only memory (ROM) on the system board. These programs are the primary method of testing the major components of the server. See "Diagnostic programs and error messages" on page 15 for more information. POST When you turn on the server, it performs a series of tests to check the operation of server components and some of the options installed in the server. This series of tests is called the power-on self-test, or POST. If POST finishes without detecting any problems, a single beep sounds, the first screen of your operating system or application program appears, and the System POST Complete (OK) light is illuminated on the operator information panel. If POST detects a problem, more than one beep sounds and an error message appears on your screen. See "Beep Symptoms" on page 107 and "POST error codes" on page 117 for more information. Notes: 1. If you have a power-on password or administrator password set, you must type the password and press Enter, when prompted, before POST will continue. 2. A single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After you correct the cause of the first error message, the other error messages usually will not occur the next time you run the test. © Copyright IBM Corp. 2000, 2001 13

  • 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
Diagnostics
This section provides basic troubleshooting information to help you resolve some
common problems that might occur with the server.
If you cannot locate and correct the problem using the information in this section,
refer to “Symptom-to-FRU index” on page 107 for more information.
Diagnostic tools overview
The following tools are available to help you identify and resolve hardware-related
problems:
v
POST beep codes, error messages, and error logs
The power-on self-test (POST) generates beep codes and messages to indicate
successful test completion or the detection of a problem. See “POST” for more
information.
v
Light Path Diagnostics
The server has light-emitting diodes (LEDs) to help you identify problems with
server components. These LEDs are part of the Light Path Diagnostics feature
that is built into the server. By following the path of lights, you can quickly
identify the type of system error. See “Identifying problems using status LEDs”
on page 18 for more information.
v
Diagnostic programs and error messages
The server diagnostic programs are stored in upgradable read-only memory
(ROM) on the system board. These programs are the primary method of testing
the major components of the server. See “Diagnostic programs and error
messages” on page 15 for more information.
POST
When you turn on the server, it performs a series of tests to check the operation of
server components and some of the options installed in the server. This series of
tests is called the power-on self-test, or POST.
If POST finishes without detecting any problems, a single beep sounds, the first
screen of your operating system or application program appears, and the System
POST Complete (OK) light is illuminated on the operator information panel.
If POST detects a problem, more than one beep sounds and an error message
appears on your screen. See “Beep Symptoms” on page 107 and “POST error
codes” on page 117 for more information.
Notes:
1.
If you have a power-on password or administrator password set, you must
type the password and press Enter, when prompted, before POST will continue.
2.
A single problem might cause several error messages. When this occurs, work
to correct the cause of the first error message. After you correct the cause of the
first error message, the other error messages usually will not occur the next
time you run the test.
© Copyright IBM Corp. 2000, 2001
13