No-beep
symptoms
The
following
table
describes
situations
in
which
no
beep
code
sounds
when
POST
is
completed.
v
Follow
the
suggested
actions
in
the
order
in
which
they
are
listed
in
the
Action
column
until
the
problem
is
solved.
v
See
Chapter
3,
“Parts
listing,
Type
7981
and
1884,”
on
page
53
to
determine
which
components
are
customer
replaceable
units
(CRU)
and
which
components
are
field
replaceable
units
(FRU).
v
If
an
action
step
is
preceded
by
“(Trained
service
technician
only),”
that
step
must
be
performed
only
by
a
trained
service
technician.
No-beep
symptom
Action
No
beep
and
the
blade
server
operates
correctly
(Trained
service
technician
only)
Replace
the
system
board
assembly.
No
beep
and
no
video
(system-error
LED
is
off)
See
“Solving
undetermined
problems”
on
page
49.
No
beep
and
no
video
(system
attention
LED
is
lit)
See
“Light
path
diagnostics”
on
page
38.
Error
logs
The
BMC
log
contains
all
system
status
messages
from
the
blade
server
service
processor.
The
management-module
event
log
in
your
BladeCenter
unit
contains
messages
that
were
generated
on
each
blade
server
during
POST
and
status
messages
from
the
BladeCenter
service
processor.
(See
the
documentation
for
your
management-module
for
more
information.)
The
following
illustration
shows
an
example
of
a
BMC
log
entry.
BMC
System
Event
Log
----------------------------------------------------------
Get
Next
Entry
Get
Previous
Entry
Clear
BMC
SEL
Entry
Number=
00005
/
00011
Record
ID=
0005
Record
Type=
02
Timestamp=
2005/01/25
16:15:17
Entry
Details:
Generator
ID=
0020
Sensor
Type=
04
Assertion
Event
Fan
Threshold
Lower
Non-critical
-
going
high
Sensor
Number=
40
Event
Direction/Type=
01
Event
Data=
52
00
1A
Important:
v
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.
v
The
management-module
event
log
in
your
BladeCenter
unit
lists
messages
according
to
the
position
of
the
blade
server
in
the
blade
bays.
If
a
blade
server
is
moved
from
one
bay
to
another,
the
management-module
event
log
will
report
16
BladeCenter
HS20
Type
7981
and
1884:
Problem
Determination
and
Service
Guide
Summary of Contents for eServer BladeCenter HS20 Type 8832
Page 1: ...BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 2: ......
Page 3: ...BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 8: ...vi BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 16: ...xiv BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 68: ...52 BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 98: ...82 BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 110: ...94 BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 111: ......
Page 112: ... Part Number 31R1716 Printed in USA 1P P N 31R1716 ...