Hardware and Software Installation Procedure
Step 8: Verify the fibre channel installation
Step 8: Verify the fibre channel installation
•To verify that the fc driver appears for each installed card, enter: ioscan
The ioscan output might look like the following:
Class I H/W Path Driver S/W State | H/W Type Description | ||||
fc | 4 | 1/0/8/1/0/4/0 fcd CLAIMED | INTERFACE HP | ||
1) | |||||
fc | 5 | 1/0/8/1/0/4/1 fcd CLAIMED | INTERFACE HP | ||
2) | |||||
The last two digits of the hardware path (third column) reflect the path of each port. Both ports need to show as CLAIMED here.
•Verify that all devices you attached to the fibre channel card are listed in the ioscan output. For example, if you have a direct attach fibre channel device attached to the system, the ioscan output might look like:
8/12.8.0.255.0.1.0 sdisk CLAIMED DEVICE DGC C3400WDR5
The example above is the hardware path of LUN0 of a directly attached fibre channel mass storage device with loop ID of 1. If all attached devices are not listed, or for details on interpreting hardware paths, see the HP Fibre Channel Mass Storage Adapters Support Guide. HP fibre channel installation is verified if the ioscan output lists all mass storage devices attached to the card.
If the correct driver is installed, but the card does not show in the ioscan output, the driver is not recognizing the card. Make sure the card is seated and connectors are attached tightly, then if the problem persists, contact HP for assistance.
Step 9: Verify the LAN installation
•Verify that the LAN connector’s Link LED is steadily on (this means the card and driver are installed successfully).
•Obtain the PPA number and the station address of each card by using the lanscan command. The MAC address labelled on each card refers to LAN port A (the right port). Add 1 to obtain the MAC address for LAN port B.
•To verify
Note: when you use linkloop, ensure that the remote system is on the same subnet and is an
•To verify
$ping Remote_IP_Address and
netstat -in
When you use netstat
6