IBM 887022X Maintenance Manual - Page 75

Error, Light, diagnostics

Page 75 highlights

Error logs An overall status message will then appear. Partition merge successful If the merge was not successful, the message will indicate the failure (see "Verifying scalability and RXE cabling" on page 72). For example: Partition merge failed: No secondary SMP Exp. Modules merged The message above indicates that the secondary chassis was not seen. Partition mismatch: Expected partition 8-8, Actual partition 8-4 The message above indicates that one of the SMP Expansion Modules was not enabled. The POST error log contains the three most recent error codes and messages that the system generated during POST. The System Error log contains all messages issued during POST and all system status messages from the service processor. You can view the contents of the System Error log from the Configuration/Setup Utility program or from the diagnostic programs. Note: When troubleshooting problems with PCI-X slots, you will notice that the error logs report the PCI-X buses numerically. The numerical assignment will change depending on your configuration. Viewing error logs from the Configuration/Setup Utility program Start the Configuration/Setup Utility program; then, select Error Logs from the main menu. See "Using the Configuration/Setup Utility program" on page 14 for more information. Viewing error logs from the diagnostic programs Start the diagnostic programs; select Hardware Info from the top of the diagnostic programs screen; select System Error Log from the list that appears; then, follow the instructions on the screen. See "Starting the diagnostic programs" on page 70 for more information for more information. Light path diagnostics The server's light path diagnostics feature provides a path that can be followed in four phases to help identify the source of an error. The lights are designed to be followed in an orderly progression, depending on the error. The lights are viewed in the following order: 1. Begin on the front panel (see "Server controls and indicators" on page 4). 2. Proceed to the light path diagnostics panel (see Figure 27 on page 66). 3. Check the lights on the top of the server (see Figure 28 on page 67). 4. Look inside the server, if required. Many errors are first indicated by the illumination of the system-error light in the operator information panel on the front of the server (see "Server controls and indicators" on page 4). If the system-error light is on, one or more lights on top of and/or inside the server might also be on that can direct you to the source of the error. This section will describe how to follow this light path. Chapter 3. Diagnostics 65

  • 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
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324

An
overall
status
message
will
then
appear.
Partition
merge
successful
If
the
merge
was
not
successful,
the
message
will
indicate
the
failure
(see
“Verifying
scalability
and
RXE
cabling”
on
page
72).
For
example:
Partition
merge
failed:
No
secondary
SMP
Exp.
Modules
merged
The
message
above
indicates
that
the
secondary
chassis
was
not
seen.
Partition
mismatch:
Expected
partition
8-8,
Actual
partition
8-4
The
message
above
indicates
that
one
of
the
SMP
Expansion
Modules
was
not
enabled.
Error
logs
The
POST
error
log
contains
the
three
most
recent
error
codes
and
messages
that
the
system
generated
during
POST.
The
System
Error
log
contains
all
messages
issued
during
POST
and
all
system
status
messages
from
the
service
processor.
You
can
view
the
contents
of
the
System
Error
log
from
the
Configuration/Setup
Utility
program
or
from
the
diagnostic
programs.
Note:
When
troubleshooting
problems
with
PCI-X
slots,
you
will
notice
that
the
error
logs
report
the
PCI-X
buses
numerically.
The
numerical
assignment
will
change
depending
on
your
configuration.
Viewing
error
logs
from
the
Configuration/Setup
Utility
program
Start
the
Configuration/Setup
Utility
program;
then,
select
Error
Logs
from
the
main
menu.
See
“Using
the
Configuration/Setup
Utility
program”
on
page
14
for
more
information.
Viewing
error
logs
from
the
diagnostic
programs
Start
the
diagnostic
programs;
select
Hardware
Info
from
the
top
of
the
diagnostic
programs
screen;
select
System
Error
Log
from
the
list
that
appears;
then,
follow
the
instructions
on
the
screen.
See
“Starting
the
diagnostic
programs”
on
page
70
for
more
information
for
more
information.
Light
path
diagnostics
The
server’s
light
path
diagnostics
feature
provides
a
path
that
can
be
followed
in
four
phases
to
help
identify
the
source
of
an
error.
The
lights
are
designed
to
be
followed
in
an
orderly
progression,
depending
on
the
error.
The
lights
are
viewed
in
the
following
order:
1.
Begin
on
the
front
panel
(see
“Server
controls
and
indicators”
on
page
4).
2.
Proceed
to
the
light
path
diagnostics
panel
(see
Figure
27
on
page
66).
3.
Check
the
lights
on
the
top
of
the
server
(see
Figure
28
on
page
67).
4.
Look
inside
the
server,
if
required.
Many
errors
are
first
indicated
by
the
illumination
of
the
system-error
light
in
the
operator
information
panel
on
the
front
of
the
server
(see
“Server
controls
and
indicators”
on
page
4).
If
the
system-error
light
is
on,
one
or
more
lights
on
top
of
and/or
inside
the
server
might
also
be
on
that
can
direct
you
to
the
source
of
the
error.
This
section
will
describe
how
to
follow
this
light
path.
Chapter
3.
Diagnostics
65