IBM SA38-0512-03 manual F5B

Ÿ For

network

boot

attempts:

–

Are

the IP parameters correct?

–

Attempt

to

“Ping”

the

target

server

using

the

SMS “Ping”

utility.

2. If

the

checkpoint

F05

or

F5B

is

displayed for

an

extended

time, there may

problem with

the

integrity

of

the boot

image.

ŸTry to boot and run standalone diagnostics against the system, particularly against the intended boot device. If the diagnostics are successful, it necessary to perform an operating system specific recovery process, or

reinstall

the

operating

system.

3. If

attempting

to

boot

from

a Harddisk, CDROM, or Tape drive:

a. Try

a

different

CD/Tape

(unless

booting

from

Harddisk)

b. Verify

proper

SCSI

bus

termination

c. Replace

SCSI

cable

d. It

is

possible that another attached SCSI device is causing the problem.

Disconnect

any

other

SCSI

devices

attached

to

the

same

controller

as

the

one the boot device is attached to and retry the boot operation. If th

successful,

one

of

the devices

removed

is

causing

the problem, re-attach

devices

one

by

one

and

retry the boot operation until the problem recurs

replace

the

device that caused the problem.

e. Replace

SCSI

adapter

(if

drive

is

attached

to

a

card

rather

than

the

board)

f. Replace

SCSI

drive

g. It

is

possible

that another installed adapter is causing

the

problem.

Remove

all

installed

adapters

except

the

one

the

boot

device

is

attached

try

to

boot

the

standalone

diagnostics

from

a

CDROM

drive

attached

to

the

scsi controller on the system board, and run

the

diagnostics against

the

system.

If

this

is

successful,

re-install adapters (and attached

devices

as

appli

that were removed, one at a time, and

run

the

standalone

diagnostics

against

the

system.

h. Replace

riser

card

i. Replace

system

board

4. If

attempting

to

boot

from

a

Network

controller:

a. Power

Off

then

On and retry the boot operation

b. Verify

the

network

connection

(network

could

be

down)

c. Verify

that IP parameters are correct

d. Try

to

“Ping”

the

target

server

e. Have network

administrator

verify

the

server

configuration

for

this

client

f. Replace

network

cable

g. Replace

network

adapter

(unless

trying

to

boot

using

the

ethernet

controller

on

the

system

board)

h. It

is

possible

that

another

installed

adapter

is

causing

the

problem.

Chapter 3. Error Code to FRU Index for Model 1403-19and Model 240