2.
Reset
the
service
processor
by
activating
the
pinhole
reset
switch
on
the
operator
panel.
3.
Call
service
support.
Error
Code
B1xx
8FF0
The
following
error
code
was
moved
out
of
the
Common
Firmware
Error
Code
table
because
of
the
size
of
the
description
column.
Error
Code
Description:
Action/
Possible
Failing
FRU:
B1xx
8FF0
Informational
message
No
action
required.
(The
data
in
these
informational
log
entries
may
be
used
by
support
personnel
to
gather
additional
debug
information.)
For
complete
information
regarding
this
error
code,
read
through
this
entire
section.
If
the
managed
server
is
down,
go
to
the
service
processor
error
log
and
find
the
error
log
entry
containing
B1xx
8FF0.
Examine
the
first
two
bytes
of
word
13
of
the
detailed
entry
information.
If
the
managed
server
is
running,
do
the
following:
v
Examine
the
AIX
error
log
entry
containing
B1xx
8FF0.
This
is
a
FIRMWARE_EVENT
error
with
an
identifier
of
A6D1BD62.
v
In
the
detail
data,
find
the
string
B1xx
8FF0.
(If
present,
it
will
be
at
byte
60
of
the
detail
data.)
v
Move
forward
8
bytes
to
bytes
68
and
69;
this
is
the
value
of
word
13
in
the
service
processor
error
log
entry.
If
the
system
is
running
Linux,
examine
the
Linux
system
log.
The
line(s)
in
the
extended
data
that
begin
with
<4>RTAS:
Log
Debug:
04
contain
the
error
code
in
the
next
8
hex
characters.
(This
error
code
is
also
known
as
word
11).
Each
4
bytes
after
the
error
code
in
the
Linux
extended
data
are
another
word.
The
4
bytes
after
the
error
code
are
word
12
and
the
next
four
bytes
are
word
13.
An
example
of
the
Linux
extended
data,
and
finding
words
11,
12,
and
13,
is
shown
in
MAP
1321,
step
1321-28,
and
step
1321-29,
in
this
service
guide.
CoD
Transactions
If
the
value
of
the
first
two
bytes
of
word
13
in
the
detailed
service
processor
error
log
entry,
or
the
value
of
bytes
68
and
69
in
the
AIX
error
log
entry
is
C1A4,
this
indicates
a
capacity
on
demand
(CoD)
transaction
has
taken
place.
For
more
detail
about
CUoD
and
CoD
transactions,
see
the
IBM
Hardware
Management
Console
for
pSeries
Installation
and
Operations
Guide
,
order
number
SA38-0590.
If
a
CoD
transaction
has
taken
place,
and
more
detail
about
the
transaction
is
required,
do
the
following:
v
Record
the
36
bytes
in
the
AIX
error
log
entry
starting
with
B1xx
8FF0,
grouping
4
bytes
at
a
time
so
that
the
resulting
words
match
the
service
processor
error
log’s
detail
data.
For
example,
B1xx
8FF0
is
the
value
of
word
11,
the
next
4
bytes
are
word
12,
the
next
4
are
word
13,
etc,
until
word
19
has
a
value.
There
are
five
parameters
of
interest
in
the
CoD
log
entry:
1.
Word
16
value
(first
2
bytes):
the
type
of
transaction
2.
Word
17
value
(first
2
bytes):
the
change
in
number
of
processors
due
to
this
transaction
3.
Word
17
value
(second
2
bytes):
the
resulting
number
of
processor
due
to
this
transaction
4.
Word
18
value
(first
2
bytes):
the
on/off
CoD
processor
days
remaining
5.
Word
18
value
(second
2
bytes):
the
hours
remaining
in
the
current
on/off
CoD
resource
period
To
find
these
values
in
the
service
processor
error
log
entry,
or
in
the
AIX
error
log
entry,
do
the
following:
Chapter
5.
Error
Code
to
FRU
Index
765
Содержание eserver pSeries 690
Страница 1: ...pSeries 690 Service Guide SA38 0589 05 ERserver...
Страница 2: ......
Страница 3: ...pSeries 690 Service Guide SA38 0589 05 ERserver...
Страница 12: ...x Eserver pSeries 690 Service Guide...
Страница 14: ...xii Eserver pSeries 690 Service Guide...
Страница 228: ...Step 1527 5 Call your next level of support 212 Eserver pSeries 690 Service Guide...
Страница 357: ...Step 1543 15 Call for support This ends the procedure Chapter 3 Maintenance Analysis Procedures 341...
Страница 362: ...Step 1545 15 Call for support This ends the procedure 346 Eserver pSeries 690 Service Guide...
Страница 365: ...Step 1546 15 Call for support This ends the procedure Chapter 3 Maintenance Analysis Procedures 349...
Страница 381: ...Step 154A 14 Turn off the power Chapter 3 Maintenance Analysis Procedures 365...
Страница 430: ...414 Eserver pSeries 690 Service Guide...
Страница 798: ...782 Eserver pSeries 690 Service Guide...
Страница 868: ...Media Subsystem Internal Cables 1021 p690 Cable Installation and Management 1022 852 Eserver pSeries 690 Service Guide...
Страница 910: ...MCM Installation Shorts Test Step 3 See L3 Cache Modules on page 898 894 Eserver pSeries 690 Service Guide...
Страница 923: ...L3 Cache Shorts Test Step 4 Chapter 9 Removal and Replacement Procedures 907...
Страница 924: ...L3 Cache Shorts Test Step 5 908 Eserver pSeries 690 Service Guide...
Страница 926: ...L3 Cache Shorts Test Step 2 910 Eserver pSeries 690 Service Guide...
Страница 928: ...L3 Cache Shorts Test Step 4 912 Eserver pSeries 690 Service Guide...
Страница 929: ...L3 Cache Shorts Test Step 5 Chapter 9 Removal and Replacement Procedures 913...
Страница 1055: ...7040 Model 681 Media Subsystem 1 2 3 4 5 6 7 8 9 10 Chapter 10 Parts Information 1039...
Страница 1057: ...Power and SCSI Cables to the Media Subsystem 1 2 3 5 4 6 Chapter 10 Parts Information 1041...
Страница 1061: ...Power Cabling Chapter 10 Parts Information 1045...
Страница 1090: ...1074 Eserver pSeries 690 Service Guide...
Страница 1094: ...1078 Eserver pSeries 690 Service Guide...
Страница 1109: ...error Handle unexpected modem responses expect 8 r or 7 r or 6 r or 4 r or 3 r delay 2 done Appendix D Modem Configurations 1093...
Страница 1122: ...1106 Eserver pSeries 690 Service Guide...
Страница 1123: ...Appendix E Ground Path The ground path for the pSeries 690 is shown in the following figure 1107...
Страница 1124: ...1108 Eserver pSeries 690 Service Guide...
Страница 1132: ...1116 Eserver pSeries 690 Service Guide...
Страница 1133: ......
Страница 1134: ...Printed in U S A February 2004 SA38 0589 05...