Installing and Administering HP FDDI/9000 Software

66 Chapter 4
Troubleshooting HP FDDI/9000
Diagnostic Flowcharts
Flowchart 4 Procedures
A. Execute: ifconfig <interface>. Execute ifconfig
without the up parameter on the interface you want to
test, to check the flag setting for the up parameter. For
example, to check FDDI interface lan1, type:
/usr/sbin/ifconfig lan1
B. Is ifconfig up? Check the results of the ifconfig
command to see if the interface is up. If it is, go to G. If
not, go to C.
C. Execute: ifconfig <interface> <IP address> up.
Check to see if ifconfig is up. If not, execute ifconfig on
the interface you want to test. For example, to check
FDDI interface lan1, enter:
/usr/sbin/ifconfig lan1 ip_address up
Type ifconfig <interface> again to see if the interface is
up, then go to D.
D. ifconfig successful? ifconfig is successful if the output
shows the correct Internet address and the flags: <UP,
BROADCAST, ROUTE, NOTRAILERS, RUNNING>.
Note: Make sure the UP flag is displayed. Also, ROUTE
may or may not be present. If yes, go to G. If not, go to
E.
E. Any error message returned? If ifconfig is not
successful, and an error message appears, go to
Flowchart 5. Flowchart 5 shows common error
messages and what to do for each. If no error messages
appear, go to F.
F. Correct ifconfig flag settings. If ifconfig returns an
incorrect flag setting, re-execute the command with the
proper setting. Go to Flowchart 6.
G. Check configuration in SAM. Check that the FDDI
in SAM is correct. See chapter 3 for the configuration
steps.
H. Is SAM configuration correct? If yes, the problem is
outside your domain. If not, correct the configuration in
SAM and start over with Flowchart 1.