1 REPLY
Re: Volume Set Addressing
VSA mode is used for disk arrays. Driver bound should be 'fcparray' (not 'fcpdev'). It's responsibility of disk array to tell hpux host that it should use VSA (there's special request made by hpux OS to check what the device is - disk array [VSA] or target device [TAM - target addressing mode]).
You need to check with your disk arrays' documentation if they're certified for hpux and how to set their 'hpux' behavior.
Also please remember that in hpux FC LUN number is coded in three last numbers separated by dot, i.e.
0/8/0/0.8.0.4.0.3.5
LUN number is 0.3.5, 5+3*8+0*128=29 (LUN #29). To make hpux see newly create LUN run 'ioscan -fn' and 'insf -e' or simply reboot the host
Eugeny
Honored Contributor
![Michael_556]()
![krusty]()
![Honored Contributor]()
HONORED CONTRIBUTOR
You need to check with your disk arrays' documentation if they're certified for hpux and how to set their 'hpux' behavior.
Also please remember that in hpux FC LUN number is coded in three last numbers separated by dot, i.e.
0/8/0/0.8.0.4.0.3.5
LUN number is 0.3.5, 5+3*8+0*128=29 (LUN #29). To make hpux see newly create LUN run 'ioscan -fn' and 'insf -e' or simply reboot the host
Eugeny
===========================================================================================
3 REPLIES
Honored Contributor
Re: VSA in HPUX
Michael,
I'm not sure what storage device you are using, but it sounds like it is not using VSA. VSA is used by all HP disk arrays, to the best of my knowledge.
HPUX is based on the SCSI standard using Bus/Target/LUN. The device files are created based on this. You will note if you map sequential LUNs on you storage device, HPUX will create the devices as shown here:
LUN 0 cXt0d0
LUN 1 cXt0d1
LUN 2 cXt0d2
'
LUN 7 cXt0d7
LUN 8 cXt1d0
LUN 9 cXt1d1
'
LUN 15 cXt1d7
LUN 16 cXt2d0
'
and so forth. X is the instance of the controller, but is not pertinent here anyway.
I have seen some storage arrays whereas they will increment the target, rather than the LUN as shown above. This would give the results you are seeing. I believe the device is using Peripheral Device Addressing. I'm not sure what are are trying to do here. Do you have an ioscan and type of storage device?
Curt
I'm not sure what storage device you are using, but it sounds like it is not using VSA. VSA is used by all HP disk arrays, to the best of my knowledge.
HPUX is based on the SCSI standard using Bus/Target/LUN. The device files are created based on this. You will note if you map sequential LUNs on you storage device, HPUX will create the devices as shown here:
LUN 0 cXt0d0
LUN 1 cXt0d1
LUN 2 cXt0d2
'
LUN 7 cXt0d7
LUN 8 cXt1d0
LUN 9 cXt1d1
'
LUN 15 cXt1d7
LUN 16 cXt2d0
'
and so forth. X is the instance of the controller, but is not pertinent here anyway.
I have seen some storage arrays whereas they will increment the target, rather than the LUN as shown above. This would give the results you are seeing. I believe the device is using Peripheral Device Addressing. I'm not sure what are are trying to do here. Do you have an ioscan and type of storage device?
Curt
"In Vino Veritas"
============================================================================
VSA in HPUX
VSA in HPUX
Hi
We have a target with some LUNs that we want to work with an HPUX host which has HPUX HBA.
We want to work in VSA (Volume Set Addressing ) mode.
In this mode we can work with larger LU numbers (16k) by setting bit 6 in the first byte of the LUN. This will cause for example LUN 1 to appear as LUN 4001h in the Finisar (FC) trace.
The problem is that sometimes our LU number are not sequential - not 4000h,4001h,4002h but
4000h,4007h,4010h for example.
However i could see that HPUX searches LUNs not sequntial but it is jumping 8 numbers
(4000h,4008h,4010h).
I also saw that if the HPUX found for example an active LUN in 4008h then it will inquiry LUNs 4009h-400fh, however if no active LUN is found in 4008h then it will skip to LUN 4010h.
And that means that if i do not have a LUN whose number is 4008h that means that HPUX will not see any LUNs in 4009h-400fh.
Is there a way to solve it?
Is there something special i should return in inquiry commands (regular and page 80h) to the HPUX?
Thanks,
Michael
We have a target with some LUNs that we want to work with an HPUX host which has HPUX HBA.
We want to work in VSA (Volume Set Addressing ) mode.
In this mode we can work with larger LU numbers (16k) by setting bit 6 in the first byte of the LUN. This will cause for example LUN 1 to appear as LUN 4001h in the Finisar (FC) trace.
The problem is that sometimes our LU number are not sequential - not 4000h,4001h,4002h but
4000h,4007h,4010h for example.
However i could see that HPUX searches LUNs not sequntial but it is jumping 8 numbers
(4000h,4008h,4010h).
I also saw that if the HPUX found for example an active LUN in 4008h then it will inquiry LUNs 4009h-400fh, however if no active LUN is found in 4008h then it will skip to LUN 4010h.
And that means that if i do not have a LUN whose number is 4008h that means that HPUX will not see any LUNs in 4009h-400fh.
Is there a way to solve it?
Is there something special i should return in inquiry commands (regular and page 80h) to the HPUX?
Thanks,
Michael
3 REPLIES
Re: VSA in HPUX
Michael,
I'm not sure what storage device you are using, but it sounds like it is not using VSA. VSA is used by all HP disk arrays, to the best of my knowledge.
HPUX is based on the SCSI standard using Bus/Target/LUN. The device files are created based on this. You will note if you map sequential LUNs on you storage device, HPUX will create the devices as shown here:
LUN 0 cXt0d0
LUN 1 cXt0d1
LUN 2 cXt0d2
'
LUN 7 cXt0d7
LUN 8 cXt1d0
LUN 9 cXt1d1
'
LUN 15 cXt1d7
LUN 16 cXt2d0
'
and so forth. X is the instance of the controller, but is not pertinent here anyway.
I have seen some storage arrays whereas they will increment the target, rather than the LUN as shown above. This would give the results you are seeing. I believe the device is using Peripheral Device Addressing. I'm not sure what are are trying to do here. Do you have an ioscan and type of storage device?
Curt
I'm not sure what storage device you are using, but it sounds like it is not using VSA. VSA is used by all HP disk arrays, to the best of my knowledge.
HPUX is based on the SCSI standard using Bus/Target/LUN. The device files are created based on this. You will note if you map sequential LUNs on you storage device, HPUX will create the devices as shown here:
LUN 0 cXt0d0
LUN 1 cXt0d1
LUN 2 cXt0d2
'
LUN 7 cXt0d7
LUN 8 cXt1d0
LUN 9 cXt1d1
'
LUN 15 cXt1d7
LUN 16 cXt2d0
'
and so forth. X is the instance of the controller, but is not pertinent here anyway.
I have seen some storage arrays whereas they will increment the target, rather than the LUN as shown above. This would give the results you are seeing. I believe the device is using Peripheral Device Addressing. I'm not sure what are are trying to do here. Do you have an ioscan and type of storage device?
Curt
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
