Installing and Administering HP FDDI/9000 Software

68 Chapter 4

Troubleshooting HP FDDI/9000

Diagnostic Flowcharts

Flowchart 5 Procedures

A. /usr/sbin/ifconﬁg not found. The command has been

relocated on the system or deleted. Go to E.

B. Bad system call; core dumped. Networking is not

conﬁgured into the HP-UX kernel. Go to F.

C. No such interface name. The interface name passed

to ifconﬁg does not exist on the system. Check spelling

and names of interfaces on the system using netstat -i.

If you have more than one FDDI adapter, make sure

the number of FDDI adapters has been conﬁgured into

the kernel and that an ifconﬁg command has been

executed for each. Go to G.

D. Any other error message. If you received an error

message not listed on this ﬂowchart, interpret the

message and take the appropriate action. See

“Contacting Your HP Representative” and call HP.

E. Restore /usr/sbin/ifconﬁg from tape and

reconﬁgure kernel. You can restore ifconﬁg from the

last good backup tape or your install/update tape. Go to

F. Reconﬁgure HP-UX kernel to include HP

FDDI/9000 software. See the Installing and

AdministeringLAN/9000 manual for information on

how to create a new kernel. Go to Flowchart 2.

G. More than 1 FDDI adapter installed? If you

installed more than one FDDI adapter, go to Flowchart

10. If not, go to I.

H. Problem resolved? If so, stop. If not, re-install the

entire HP FDDI/9000 software product. Start again

with Flowchart 2, as necessary.

I. Find correct interface name. Using the correct

interface name, start again with Flowchart 2.

J. Reinstall HP FDDI/9000 software. Re-install the

entire HP FDDI/9000 software product. If necessary,

start again with Flowchart 2.