Ethernet Support Guide (for HP-UX 11i v1, 11i v2)

Troubleshooting
Diagnostic Flowcharts
Chapter 4
66
Flowchart 9 Procedures
The procedures in Figure 4-10 (Flowchart 9) are:
• Enter ioscan(1M) as follows:
ioscan -kfd drivername
In this command, drivername is either btlan, gelan or igelan.
Verify that the output from ioscan shows that the card is “CLAIMED” by the
system.
IMPORTANT Do not proceed to the next step until this step has been done! It is possible for a
card’s bulkhead LED to indicate that the card is “present” when, in fact, ioscan will
show that it is not. The cause is a poorly seated PCI-X slot assembly that allows
power to the LED, but there is a poor, or nonexistent, connection to the PCI-X bus.
The fix is to remove and re seat the appropriate portion of the I/O cage, and then
reboot.
• If the card is claimed, enter lanscan(1M) and check to see if the hardware state
display shows UP. If so, go to Cable and LED Test (Flowchart 1). If not, continue to
the logging function of the netfmt and lanadmin Test (Flowchart 10).
• If the card is not claimed, enter: what /stand/vmunix | grep drivername
In this command, drivername is one of the previous drives. Verify that the output is
similar to the output documented in the latest Release Notes for your Gigabit
Ethernet product. Use the name of the running kernel image file in place of
/stand/vmunix as appropriate.
• If the driver is displayed, check to see if the dmesg/syslog output shows error
messages pertaining to btlan/gelan/igelan. Also, check nettl log messages. If
there are errors, check the card installation and reset or re seat the card, and repeat
this test. Otherwise, call your HP representative.
Note that NetTL creates the following log files:
— For releases prior to HP-UX 11i: nettl.LOG-00 and nettl.LOG-01
— For release HP-UX 11i and later: nettl.LOG000 and nettl.LOG001
• If the driver is not displayed, install it using swinstall(1M) and:
— For pre-11.23 systems:
Regenerate the kernel, reboot the system, and repeat this test.
— For 11.23 systems:
Use the appropriate kernel configuration commands.