HP XP20000/XP24000 HP StorageWorks XP Disk Array Configuration Guide (T5278-96 - Page 21

Verifying the device files and drivers, Creating the device files, array device.

Get HP XP20000/XP24000 PDF manuals and user guides View all HP XP20000/XP24000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Verifying the device files and drivers The device files for new devices are usually created automatically during HP-UX startup. Each device must have a block-type device file in the /dev/dsk directory and a character-type device file in the /dev/rdsk directory. 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 "Creating the device files" (page 21). 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 -fn command. Example # ioscan -fn Class I H/W Path Driver S/W State H/W Type Desc bc 0 root CLAIMED BUS_NEXUS... bc 1 8 bc CLAIMED BUS_NEXUS... fc 0 8/12 fcT1 CLAIMED INTERFACE... fcp 0 8/12.8 fcp CLAIMED INTERFACE... ext_bus 2 8/12.8.0.255.0 fcpdev CLAIMED INTERFACE... disk 3 8/12.8.8.255.0.6.0 sdisk CLAIMED DEVICE... /dev/dsk/c2t6d0 /dev/rdsk/c2t6d0 disk 4 8/12.8.8.255.0.6.1 sdisk CLAIMED DEVICE... /dev/dsk/c2t6d1 /dev/rdsk/c2t6d1 disk 5 8/12.8.8.255.0.8.0 sdisk CLAIMED DEVICE... /dev/dsk/c2t8d0 /dev/rdsk/c2t8d0 Creating the device files If the device files were not created automatically when the system was restarted, use the insf -e command in the /dev directory to create the device files. After this command is executed, Configuring disk array devices 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
Verifying the device files and drivers
The device files for new devices are usually created automatically during HP-UX startup. Each
device must have a block-type device file in the
/dev/dsk
directory and a character-type device
file in the
/dev/rdsk
directory.
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
“Creating the device files”
(page 21)
.
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
–
fn
command.
Example
# ioscan -fn
Class
I H/W Path
Driver S/W State H/W Type
Desc
------------------------------------------------------------
bc
0
root
CLAIMED
BUS_NEXUS...
bc
1 8
bc
CLAIMED
BUS_NEXUS...
fc
0 8/12
fcT1
CLAIMED
INTERFACE...
fcp
0 8/12.8
fcp
CLAIMED
INTERFACE...
ext_bus 2 8/12.8.0.255.0
fcpdev CLAIMED
INTERFACE...
disk
3 8/12.8.8.255.0.6.0 sdisk
CLAIMED
DEVICE...
/dev/dsk/c2t6d0
/dev/rdsk/c2t6d0
disk
4 8/12.8.8.255.0.6.1 sdisk
CLAIMED
DEVICE...
/dev/dsk/c2t6d1
/dev/rdsk/c2t6d1
disk
5 8/12.8.8.255.0.8.0 sdisk
CLAIMED
DEVICE...
/dev/dsk/c2t8d0
/dev/rdsk/c2t8d0
Creating the device files
If the device files were not created automatically when the system was restarted, use the
insf
–
e
command in the
/dev
directory to create the device files. After this command is executed,
Configuring disk array devices
21