IBM HS20 User Guide - Page 75

Troubleshooting, charts, Memory, problems, Microprocessor, Monitor

Page 75 highlights

Troubleshooting charts The following tables list problem symptoms and suggested solutions. See the blade server Hardware Maintenance Manual and Troubleshooting Guide on the IBM BladeCenter Documentation CD or the IBM BladeCenter T Documentation CD for more detailed troubleshooting charts. If you cannot find the problem in these charts, run the diagnostic programs. If you have run the diagnostic test programs, or if running the tests does not reveal the problem, call for service. Memory problems Symptom The amount of system memory displayed is less than the amount of physical memory installed. Suggested action Make sure that: v The memory modules are seated correctly. v You have installed the correct type of memory. v If you changed the memory, you updated the memory configuration in the Configuration/Setup Utility program. v All banks of memory are enabled. The blade server might have automatically disabled a memory bank when it detected a problem, or a memory bank might have been manually disabled. Check the POST error log for error message 289: v If the DIMM was disabled by a system-management interrupt (SMI), replace the DIMM. v If the DIMM was disabled by the user or by POST, run the Configuration/Setup Utility program and enable the DIMM. v If this error remains, replace the DIMM. If the problem remains, call for service. Microprocessor problems Symptom Suggested action The blade server emits a The startup (boot) microprocessor is not working properly. continuous tone during POST. make sure that the startup microprocessor is seated correctly. If it is, replace the startup microprocessor. If the problem remains, call for service. Monitor problems Note: The monitor screen remains blank until it is directed to a blade server that is powered on; this is normal behavior. Chapter 6. Solving problems 61

  • 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

Troubleshooting
charts
The
following
tables
list
problem
symptoms
and
suggested
solutions.
See
the
blade
server
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
on
the
IBM
BladeCenter
Documentation
CD
or
the
IBM
BladeCenter
T
Documentation
CD
for
more
detailed
troubleshooting
charts.
If
you
cannot
find
the
problem
in
these
charts,
run
the
diagnostic
programs.
If
you
have
run
the
diagnostic
test
programs,
or
if
running
the
tests
does
not
reveal
the
problem,
call
for
service.
Memory
problems
Symptom
Suggested
action
The
amount
of
system
memory
displayed
is
less
than
the
amount
of
physical
memory
installed.
Make
sure
that:
v
The
memory
modules
are
seated
correctly.
v
You
have
installed
the
correct
type
of
memory.
v
If
you
changed
the
memory,
you
updated
the
memory
configuration
in
the
Configuration/Setup
Utility
program.
v
All
banks
of
memory
are
enabled.
The
blade
server
might
have
automatically
disabled
a
memory
bank
when
it
detected
a
problem,
or
a
memory
bank
might
have
been
manually
disabled.
Check
the
POST
error
log
for
error
message
289:
v
If
the
DIMM
was
disabled
by
a
system-management
interrupt
(SMI),
replace
the
DIMM.
v
If
the
DIMM
was
disabled
by
the
user
or
by
POST,
run
the
Configuration/Setup
Utility
program
and
enable
the
DIMM.
v
If
this
error
remains,
replace
the
DIMM.
If
the
problem
remains,
call
for
service.
Microprocessor
problems
Symptom
Suggested
action
The
blade
server
emits
a
continuous
tone
during
POST.
The
startup
(boot)
microprocessor
is
not
working
properly.
make
sure
that
the
startup
microprocessor
is
seated
correctly.
If
it
is,
replace
the
startup
microprocessor.
If
the
problem
remains,
call
for
service.
Monitor
problems
Note:
The
monitor
screen
remains
blank
until
it
is
directed
to
a
blade
server
that
is
powered
on;
this
is
normal
behavior.
Chapter
6.
Solving
problems
61