IBM JS20 Hardware Maintenance Manual - Page 162

Software, problems, Startup, Service, processor, error, codes

Page 162 highlights

Software problems Symptom Suspected software problem. FRU/action 1. To determine if problems are caused by the software, verify that: v The server has the minimum memory needed to use the software. For memory requirements, see the information that comes with the software. Note: If you have just installed an adapter or memory, you might have a memory address conflict. v The software is designed to operate on the server. v Other software works on the server. v The software that you are using works on another system. If you received any error messages when using the software program, see the information that comes with the software for a description of the messages and suggested solutions to the problem. 2. If you have verified these items and the problem remains, contact the place of purchase. Startup problems Symptom FRU/action System reboots or hangs 1. Verify in lscfg that all resources, such as DIMMs and hard disk drives, are present and correctly configured. 2. Check BladeCenter management-module event log. System reboots and there is no login prompt 1. Follow action for any POST error code and location code displayed. 2. Check BladeCenter management module event log and follow action for that entry. System stops and message v See "Firmware checkpoint (progress) codes" on page 94 and "Firmware error Starting Software Please Wait is codes" on page 102. displayed on the blade server console. All four-digit POST indicators are displayed on the system v Go to "Boot problem resolution" on page 153. console, and the system pauses and restarts. No codes are displayed on the 1. Verify that the system console is selected for the system you are trying to system console within a few power on. seconds of turning on the system, and the system console 2. System board. was blank before the system was powered on, or the system reboots continuously. Service processor error codes Service processor error codes are viewed in the BladeCenter management-module event log; see the Hardware Maintenance Manual and Troubleshooting Guide for your BladeCenter unit. 152 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide

  • 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

Software
problems
Symptom
FRU/action
Suspected
software
problem.
1.
To
determine
if
problems
are
caused
by
the
software,
verify
that:
v
The
server
has
the
minimum
memory
needed
to
use
the
software.
For
memory
requirements,
see
the
information
that
comes
with
the
software.
Note:
If
you
have
just
installed
an
adapter
or
memory,
you
might
have
a
memory
address
conflict.
v
The
software
is
designed
to
operate
on
the
server.
v
Other
software
works
on
the
server.
v
The
software
that
you
are
using
works
on
another
system.
If
you
received
any
error
messages
when
using
the
software
program,
see
the
information
that
comes
with
the
software
for
a
description
of
the
messages
and
suggested
solutions
to
the
problem.
2.
If
you
have
verified
these
items
and
the
problem
remains,
contact
the
place
of
purchase.
Startup
problems
Symptom
FRU/action
System
reboots
or
hangs
1.
Verify
in
lscfg
that
all
resources,
such
as
DIMMs
and
hard
disk
drives,
are
present
and
correctly
configured.
2.
Check
BladeCenter
management-module
event
log.
System
reboots
and
there
is
no
login
prompt
1.
Follow
action
for
any
POST
error
code
and
location
code
displayed.
2.
Check
BladeCenter
management
module
event
log
and
follow
action
for
that
entry.
System
stops
and
message
Starting
Software
Please
Wait
is
displayed
on
the
blade
server
console.
v
See
“Firmware
checkpoint
(progress)
codes”
on
page
94
and
“Firmware
error
codes”
on
page
102.
All
four-digit
POST
indicators
are
displayed
on
the
system
console,
and
the
system
pauses
and
restarts.
v
Go
to
“Boot
problem
resolution”
on
page
153.
No
codes
are
displayed
on
the
system
console
within
a
few
seconds
of
turning
on
the
system,
and
the
system
console
was
blank
before
the
system
was
powered
on,
or
the
system
reboots
continuously.
1.
Verify
that
the
system
console
is
selected
for
the
system
you
are
trying
to
power
on.
2.
System
board.
Service
processor
error
codes
Service
processor
error
codes
are
viewed
in
the
BladeCenter
management-module
event
log;
see
the
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
for
your
BladeCenter
unit.
152
BladeCenter
JS20
Type
8842:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide