IBM JS20 Hardware Maintenance Manual - Page 80

operation.

Get IBM JS20 - BladeCenter - 8842 PDF manuals and user guides
UPC - 000435230263
View all IBM JS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 80 highlights

4. If the system is running in a full-machine partition, turn on the system unit power. Restart the AIX operating system in the system you wish to run online diagnostics. 5. Enter any requested passwords. 6. Select Utilities. 7. Depending on the console type, select [was ″RIPL or Remote Initial Program Load Setup″]. 8. Depending on the console type, select [″Set Address or IP Parameters″]. 9. Enter the client address, server address, gateway address (if applicable), and subnet mask into the Remote Initial Program Load (RIPL). If there is no gateway between the NIM server and the client, set the gateway address to 0.0.0.0. To determine if there is a gateway, either ask the system network administrator or compare the first 3 octets of the NIM server address and the client address. If they are the same, (for example, if the NIM server address is 9.3.126.16 and the client address is 9.3.126.42, the first 3 octets (9.3.126) are the same), then set the gateway address in the RIPL field to 0.0.0.0. 10. If the NIM server is setup to allow the pinging of the client system, use the ping option in the RIPL utility to verify that the client system can ping the NIM server. Under the Ping utility, choose the network adapter that provides the attachment to the NIM server to do the ping operation. If the ping comes back with an OK prompt, the client is prepared to boot from the NIM server. If ping returns with a FAILED prompt, the client does not proceed with the boot. Note: If the ping fails, refer to "Boot problem resolution" on page 153; then, follow the steps for network boot problems. Use the following procedure to temporarily change the system boot list so that the network adapter attached to the NIM server network, is first in the boot list. The system should start loading packets while doing a bootp from the network. Follow the instructions on the screen to select the system console. If Diagnostics Operating Instructions Version x.x.x is displayed, standalone diagnostics has loaded successfully. If the AIX login prompt displays, standalone diagnostics did not load. Check the following items: v The boot list on the client might be incorrect. v Cstate on the NIM server might be incorrect. v There might be network problems preventing you from connecting to the NIM server. Verify the settings and the status of the network. If you continue to have problems, refer to"Boot problem resolution" on page 153; then, follow the steps for network boot problems. After running diagnostics, reboot the system and use BladeCenter management screens to change the boot list sequence back to the original settings. Verify the settings and the status of the network. If you continue to have problems, refer to"Boot problem resolution" on page 153. After running diagnostics from NIM server, change the boot list to the original boot list. 70 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
4.
If
the
system
is
running
in
a
full-machine
partition,
turn
on
the
system
unit
power.
Restart
the
AIX
operating
system
in
the
system
you
wish
to
run
online
diagnostics.
5.
Enter
any
requested
passwords.
6.
Select
Utilities.
7.
Depending
on
the
console
type,
select
[was
″
RIPL
or
Remote
Initial
Program
Load
Setup
″
].
8.
Depending
on
the
console
type,
select
[
″
Set
Address
or
IP
Parameters
″
].
9.
Enter
the
client
address,
server
address,
gateway
address
(if
applicable),
and
subnet
mask
into
the
Remote
Initial
Program
Load
(RIPL).
If
there
is
no
gateway
between
the
NIM
server
and
the
client,
set
the
gateway
address
to
0.0.0.0.
To
determine
if
there
is
a
gateway,
either
ask
the
system
network
administrator
or
compare
the
first
3
octets
of
the
NIM
server
address
and
the
client
address.
If
they
are
the
same,
(for
example,
if
the
NIM
server
address
is
9.3.126.16
and
the
client
address
is
9.3.126.42,
the
first
3
octets
(9.3.126)
are
the
same),
then
set
the
gateway
address
in
the
RIPL
field
to
0.0.0.0.
10.
If
the
NIM
server
is
setup
to
allow
the
pinging
of
the
client
system,
use
the
ping
option
in
the
RIPL
utility
to
verify
that
the
client
system
can
ping
the
NIM
server.
Under
the
Ping
utility,
choose
the
network
adapter
that
provides
the
attachment
to
the
NIM
server
to
do
the
ping
operation.
If
the
ping
comes
back
with
an
OK
prompt,
the
client
is
prepared
to
boot
from
the
NIM
server.
If
ping
returns
with
a
FAILED
prompt,
the
client
does
not
proceed
with
the
boot.
Note:
If
the
ping
fails,
refer
to
“Boot
problem
resolution”
on
page
153;
then,
follow
the
steps
for
network
boot
problems.
Use
the
following
procedure
to
temporarily
change
the
system
boot
list
so
that
the
network
adapter
attached
to
the
NIM
server
network,
is
first
in
the
boot
list.
The
system
should
start
loading
packets
while
doing
a
bootp
from
the
network.
Follow
the
instructions
on
the
screen
to
select
the
system
console.
If
Diagnostics
Operating
Instructions
Version
x.x.x
is
displayed,
standalone
diagnostics
has
loaded
successfully.
If
the
AIX
login
prompt
displays,
standalone
diagnostics
did
not
load.
Check
the
following
items:
v
The
boot
list
on
the
client
might
be
incorrect.
v
Cstate
on
the
NIM
server
might
be
incorrect.
v
There
might
be
network
problems
preventing
you
from
connecting
to
the
NIM
server.
Verify
the
settings
and
the
status
of
the
network.
If
you
continue
to
have
problems,
refer
to“Boot
problem
resolution”
on
page
153;
then,
follow
the
steps
for
network
boot
problems.
After
running
diagnostics,
reboot
the
system
and
use
BladeCenter
management
screens
to
change
the
boot
list
sequence
back
to
the
original
settings.
Verify
the
settings
and
the
status
of
the
network.
If
you
continue
to
have
problems,
refer
to“Boot
problem
resolution”
on
page
153.
After
running
diagnostics
from
NIM
server,
change
the
boot
list
to
the
original
boot
list.
70
BladeCenter
JS20
Type
8842:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide