Hardware and Software Installation Procedure
Step 10: Verify the LAN installation
9
------------------------------------------------------------------------------
#
NOTE
When the system boots after installation, the
insf
command creates the proper device
files for the “ctl” interfaces (which would include the AB290A adapter) as well as the
SCSI devices attached to the AB290A adapter. Sometimes, however, the
insf
command
does not create all of the device files that are needed. For example, this happens when
you attach SCSI disks to the adapter after the system boots, but the adapter is already
installed in the system.
If you see a SCSI device listed in the
ioscan
output, but there is no device file in the
second line of the ioscan output for that device, the device file is missing. To solve this
problem, issue the
insf -e
command, which will create
all
of the device files.
For more information about the
ioscan
command, see the
ioscan(1M)
man page.
For more information about the
insf
command, see the
insf (1M)
man page.
Refer to your system documentation for information about verifying system operation.
Step 10: 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.
•
To verify link-level connectivity with a remote system, enter:
$
linkloop -i
PPA_number remote_station_address
Note: when you use
linkloop
, ensure that the remote system is on the same subnet and is an
HP-UX-based system.
•
To verify IP-level connectivity with a remote system, enter:
$
ping
Remote_IP_Address
and
netstat -in
When you use
netstat -in
, the output values
Ipkts
and
Opkts
should be incrementing.
•
Installation is complete when you have successfully run
linkloop
,
ping
, and
netstat
. To configure
remote systems, see the
Ethernet Support Guide
available on the web at
http://docs.hp.com
. Do this
step only if remote systems have not been previously configured.
•
Optionally, if you want to verify that the iether driver appears for each installed card, enter:
ioscan
-fknClan
The ioscan output for each port would look something like the following:
Class I H/W Path Driver S/W State H/W Type Description
lan
3 1/10/0/1
iether
CLAIMED
INTERFACE HPAB290A PCI-X 2port U320 SCSI/2port 1000Base-T
