I have four LUNs masked to a particular HP-UX(11.11) host and 'symdev -sid xxx show abcx" shows the following where abcx is diffrent LUN numbers. As you can see the first one is showing visble while rest three are not.. While loking at the GUI all those luns showing "granted".
Any sugetions.. I am planning to umask&umap & and try again..
Also here the status for the paths.
150 0/0/10/0/0.97.10.19.0 000190101854 FA 14dA 18 0
235 0/0/8/0/0.98.10.19.1 000190101854 FA 3dA 93 0
Front Director Paths (2):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
/dev/rdsk/c235t15d7 PARENT FA 03D:0 RW 001 0F 007 007
/dev/rdsk/c234t15d7 CHILD FA 14D:0 RW 001 0F 007 007
}
Front Director Paths (2):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 03D:0 RW 002 00 000 N/A
Not Visible N/A FA 14D:0 RW 002 00 000 N/A
}
Front Director Paths (2):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 03D:0 RW 002 00 001 N/A
Not Visible N/A FA 14D:0 RW 002 00 001 N/A
}
Front Director Paths (2):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 03D:0 RW 002 00 002 N/A
Not Visible N/A FA 14D:0 RW 002 00 002 N/A
}
I am still not clear abou the Controller/X number. I am not sure why it is picking Vbus2 and would that cause to this problem.
it would be due to the mapping done on symmetrix. while mapping devices on cli, you can, rather need to, specify the vbus tid parameters and those are visible to host.
HPUX have a very complex behaviour when it comes to disks .. The target and lun part of the special file name is almost self explanatory. The controller part is a little more complex since HPUX will create a different cX (controller instance = ext_bus in ioscan) for every different vbus seen from every different FCID where it can see some kind of storage device.
The same complex behaviour is the root cause for the strange behaviour that HPUX shows if you unplug the storage from the switch and plug it again in a different port. If you change the port on the switch where the STORAGE is connected, the host will LOOSE the "moved" path to the storage. You have to issue ioscan and insf to re-create brand new devices and -since the controller is a combination of FCID and VBUS- you'll find brand new controllers with the same targets and luns as before.
If you look at the rightmost part of ioscan output for a "disk" instance, you'll find (from right to left) the lun(zz), the target (yy), the vbus (xx), three numbers (ww.kk.hh) that form the FCID of the port where the storage is connected and if you keep on moving left you'll find the FC controller itself (ioscan -fnkC td i suppose). If you merge in a single blob (ww.kk.hh.xx) you'll have the so-called ext_bus. If you change any value in the "blob" HPUX will allocate a brand new ext_bus = a brand new controller. That's why you have different controllers when devices have different vbusses
When you map symdevs for your hpux hosts, you have to assign three different nibbles .. the first one (VBUS) is a mysterious one and will be explained better later. The values you choose for Target and Lun are exactly what you'll see in your /dev/dsk/cXtYdZ The value you choose for Target will be the Y while the value choosen for Lun is the Z in the above template.
HP choose the so called Volume Set addressing (that maps to the V-bit when configuring a FA port) so when you configure your storage, it will show up on your host like a complex infrastructure of different controllers, targets and luns .. We already talked about luns and targets .. I must only add that legal values for Lun are from 0 to 7 (so even if it's a full hex nibble you can't use the upper bit) and for Target are from 0 to 15 (a full nibble). The third value you configure when you map devices on the frontend of a FA configured for HPUX (the mysterious vbus) becomes part of the controller (the X in cXtYdZ) with the FCID of the port where the storage is connected.
/dev/rdsk/c235t15d7 PARENT FA 03D:0 RW 001 0F 007 007 /dev/rdsk/c234t15d7 CHILD FA 14D:0 RW 001 0F 007 007
Not Visible N/A FA 03D:0 RW 002 00 000 N/A Not Visible N/A FA 14D:0 RW 002 00 000 N/A
The first strange thing I can notice is that you have a lot of controllers The second thing that I can notice is that the last volume you can see have a VBUS=1 while the first one that's giving you PITA have a VBUS=2 .. This means that HPUX have to allocate another virtual bus controller for the volumes with vbus=2. Maybe you are out of virtual controllers
Forgive the silly question .. Did you run insf -e ??
I am still not clear abou the Controller/X number.I am not sure why it is picking Vbus2 and would that cause to this problem.
it would be due to the mapping done on symmetrix. while mapping devices on cli, you can, rather need to, specify the vbus tid parameters and those are visible to host.
Can you run and post output of symcfg -sid XXX -dir YY -p Z list -address where XXX is your symmetrix ID, YY is FA port and Z is port number
I am still not clear abou the Controller/X number.I am not sure why it is picking Vbus2 and would that cause to this problem.
Please have a look at a different thread named " mapping ctd's to lun number to symm device number on HPUX" in the Software area of the forums "EMC Support Forums » Host Software" .. Enjoy !!
HP have 2 different drivers for FC cards .. they are called FC ant TD .. I never used option "u" with ioscan .. but I can tell you a secret .. option "k" will save you time and pain
xe2sdc
6 Operator
•
2831 Posts
1155
0
Posted February 15th, 2008 00:00
I am not sure why it is picking Vbus2 and would that
cause to this problem.
while mapping devices on cli, you can, rather need
to, specify the vbus tid parameters and those are
visible to host.
HPUX have a very complex behaviour when it comes to disks .. The target and lun part of the special file name is almost self explanatory. The controller part is a little more complex since HPUX will create a different cX (controller instance = ext_bus in ioscan) for every different vbus seen from every different FCID where it can see some kind of storage device.
The same complex behaviour is the root cause for the strange behaviour that HPUX shows if you unplug the storage from the switch and plug it again in a different port. If you change the port on the switch where the STORAGE is connected, the host will LOOSE the "moved" path to the storage. You have to issue ioscan and insf to re-create brand new devices and -since the controller is a combination of FCID and VBUS- you'll find brand new controllers with the same targets and luns as before.
Look at the following fake hardware path:
root/of.host/path.to.fc-controller.ww.kk.hh.xx.yy.zz
If you look at the rightmost part of ioscan output for a "disk" instance, you'll find (from right to left) the lun(zz), the target (yy), the vbus (xx), three numbers (ww.kk.hh) that form the FCID of the port where the storage is connected and if you keep on moving left you'll find the FC controller itself (ioscan -fnkC td i suppose). If you merge in a single blob (ww.kk.hh.xx) you'll have the so-called ext_bus. If you change any value in the "blob" HPUX will allocate a brand new ext_bus = a brand new controller. That's why you have different controllers when devices have different vbusses