No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

After VIS take over array, HP-UX cannot find hardware identification of array

Publication Date:  2012-10-09 Views:  61 Downloads:  0
Issue Description
Initialize LUN of array on VIS, create volume and mirror it to host. Execute ioscan -fnC disk on host, the output is:
#ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
====================================================================================
disk 3 0/0/2/1.0.16.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-V
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
/dev/dsk/disk_query
disk 15 0/3/1/0.1.0.179.0.0.1 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d1 /dev/rdsk/c16t0d1
disk 23 0/3/1/0.1.0.179.0.0.2 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d2 /dev/rdsk/c16t0d2
disk 24 0/3/1/0.1.0.179.0.0.3 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d3 /dev/rdsk/c16t0d3
disk 26 0/3/1/0.1.0.179.0.0.4 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d4 /dev/rdsk/c16t0d4
disk 31 0/3/1/0.1.0.179.0.0.5 sdisk CLAIMED DEVICE HUAWEI VIS6000

The last line is new-added LUN mirrored from VIS to host, but it does not generate hardware identification CxTxDx, so it cannot manage hardware device. 
Alarm Information
Na
Handling Process
Execute insf -C disk –e in HP-UX, like below:
# insf -C disk -e
insf: Installing special files for sdisk instance 3 address 0/0/2/1.0.16.0.0
insf: Installing special files for sdisk instance 15 address 0/3/1/0.1.0.179.0.0.1
insf: Installing special files for sdisk instance 23 address 0/3/1/0.1.0.179.0.0.2
insf: Installing special files for sdisk instance 24 address 0/3/1/0.1.0.179.0.0.3
insf: Installing special files for sdisk instance 26 address 0/3/1/0.1.0.179.0.0.4
insf: Installing special files for sdisk instance 31 address 0/3/1/0.1.0.179.0.0.5
Then execute ioscan -funC disk, like this:
#ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
====================================================================================
disk 3 0/0/2/1.0.16.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-V
/dev/dsk/c0t0d0 /dev/dsk/disk_query /dev/rdsk/c0t0d0
disk 15 0/3/1/0.1.0.179.0.0.1 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d1 /dev/rdsk/c16t0d1
disk 23 0/3/1/0.1.0.179.0.0.2 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d2 /dev/rdsk/c16t0d2
disk 24 0/3/1/0.1.0.179.0.0.3 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d3 /dev/rdsk/c16t0d3
disk 26 0/3/1/0.1.0.179.0.0.4 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d4 /dev/rdsk/c16t0d4
disk 31 0/3/1/0.1.0.179.0.0.5 sdisk CLAIMED DEVICE HUAWEI VIS6000
/dev/dsk/c16t0d5 /dev/rdsk/c16t0d5
The last line is new-generated hardware identification c16t0d5, so we can operate on this hard disk.
Root Cause
HP-UX can discover this LUN, but it does not generate hardware identification.
Suggestions

After VIS mirror LUN to HP-UX host, if HP-UX host discover this LUN through ioscan command, it need generate hardware identification through insf command.

END