>8 LUNs from an external storage array

[Corey Boyer]

Hello -

We've presented an external storage array to an HP-UX 11iv2 IA64 system. This is connected through a Brocade switch, to a 4GB FC HBA on the host.

The device only supports peripheral device addressing, so my understanding is that after the 8th LUN, the OS should automatically increment the target. However, that's not happening - we're only seeing 8 LUNs through ioscan (insf, etc. has already been done):

disk 182 0/4/0/0/0/0.10.6.255.0.0.0 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d0 /dev/rdsk/c38t0d0
disk 183 0/4/0/0/0/0.10.6.255.0.0.1 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d1 /dev/rdsk/c38t0d1
disk 184 0/4/0/0/0/0.10.6.255.0.0.2 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d2 /dev/rdsk/c38t0d2
disk 185 0/4/0/0/0/0.10.6.255.0.0.3 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d3 /dev/rdsk/c38t0d3
disk 186 0/4/0/0/0/0.10.6.255.0.0.4 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d4 /dev/rdsk/c38t0d4
disk 187 0/4/0/0/0/0.10.6.255.0.0.5 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d5 /dev/rdsk/c38t0d5
disk 188 0/4/0/0/0/0.10.6.255.0.0.6 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d6 /dev/rdsk/c38t0d6
disk 189 0/4/0/0/0/0.10.6.255.0.0.7 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c38t0d7 /dev/rdsk/c38t0d7

Any advice on how to force increment the target would be appreciated!

Thanks in advance,
- Corey

[Tim Nelson]

Typically the 8th lun and greater would be
Lun8 0/4/0/0/0/0.10.6.255.0.1.0
Lun9 0/4/0/0/0/0.10.6.255.0.1.11
and so on..

What type of array ??

If EMC then you need to set the lun to 10, 11 ( or was it a, b, c)etc.. Not sure about other arrays. Try using 10 or 0A and see what happens.

[Tim Nelson]

Typically the 8th lun and greater would be
Lun8 0/4/0/0/0/0.10.6.255.0.1.0
Lun9 0/4/0/0/0/0.10.6.255.0.1.1
and so on..

What type of array ??

If EMC then you need to set the lun to 10, 11 ( or was it a, b, c)etc.. Not sure about other arrays. Try using 10 or 0A and see what happens.