HP StorageWorks XP24000 Configuration Manual page 22

However, some HP-compatible systems do not create the device files automatically. If verification
shows that the device files were not created, follow the instructions in
The following procedure verifies both types of device files:
1.
Display the block-type device files in the /dev/dsk directory using the ls –l command with
the output piped to more. Verify there is one block-type device file for each disk array device.
Example
# ls –l /dev/dsk | more
Total 0
brw-r - - - - - 1 bin sys 28 0x006000 Dec 6 15:08 c6t0d0
brw-r - - - - - 1 bin sys 280 0x06100 Dec 6 15:08 c6t0d1
2.
Verify that the block-type device file name for each device is correct.
3. Display the character-type device files in the /dev/rdsk directory using the ls –l command
with the output piped to more. Verify that there is one character-type device file for each disk
array device.
Example
# ls –l /dev/rdsk | more
Total 0
crw-r - - - - - 1 bin sys 177 0x006000 Dec 6 15:08 c6t0d0
crw-r - - - - - 1 bin sys 177 0x006100 Dec 6 15:08 c6t0d1
4.
Use the device data table you created to verify that the character-type device file name for each
device is correct.
This task can also be accomplished with the lssf command.
5. After verifying the block-type and character-type device files, verify the HP-UX driver for the disk
array using the ioscan –fncommand.
Example
# ioscan -fn
Class I H/W Path
------------------------------------------------------------
bc 0
bc 1 8
fc 0 8/12
fcp 0 8/12.8
ext_bus 2 8/12.8.0.255.0
disk 3 8/12.8.8.255.0.6.0 sdisk
/dev/dsk/c2t6d0
disk 4 8/12.8.8.255.0.6.1 sdisk
/dev/dsk/c2t6d1
disk 5 8/12.8.8.255.0.8.0 sdisk
/dev/dsk/c2t8d0
22 Installing and configuring HP-UX for the XP disk array
Driver S/W State H/W Type
root CLAIMED
bc CLAIMED
fcT1 CLAIMED
fcp CLAIMED
fcpdev CLAIMED
CLAIMED
/dev/rdsk/c2t6d0
CLAIMED
/dev/rdsk/c2t6d1
CLAIMED
/dev/rdsk/c2t8d0
Creating the device
Desc
BUS_NEXUS...
BUS_NEXUS...
INTERFACE...
INTERFACE...
INTERFACE...
DEVICE...
DEVICE...
DEVICE...
files.