Volume stipulations

[Sam_120]

Do HP volumes using PVlinks have to start with a certain LUN # when using EMC Symm's? What are the known volume stipulations/limitations when connecting multiple HP hosts (DUAL Pathed via FC-HBA's) to an EMC Symm with two FA ports?

[James A. Donovan]

Not sure I entirely understand the question, but to give you a little info; the LUN for an EMC device is assigned by the Symmetrix's bin file. Under HP-UX the LUN # can range between 00 and FF. The first digit will correspond to the "t", and the second digit will be the "d". The controller number is dependent on what slot you place the HBA in on your server.

Using,

# sympd show /dev/rdsk/cXtYdZ

will show you what LUN number a particular device has on each path (FA) to the device.

There are no restrictions as to how you build your volume groups.

[Sam_120]

Well, my problem is that one hosts first lun does not start with a zero. In digging around more I've found that /cXtYd0 has to be true for the first LUN or otherwise it will not continue to scan the bus.

Is this true and if so do you know why HP does this?

[James R. Ferguson]

Hi Sam:

I have encountered this before, too. EMC engineering warned me of this, and the Knowledge Base (document #A4839313) notes the requirement for contiguous, sequentially numeric LUNs on 10.20.

It appears that patch PHKL_22224 (rolled into PHKL_23259) fixes the problem.

I am not sure if the same problems exist in 11.x.

Hopefully this helps.

...JRF...

[James A. Donovan]

I was not aware of the need for the first "d" to be a 0, and it sounds like the EMC engineer who created your bin file didn't know this either. You'll need to go back to EMC and get the bin file for your Symmetrix modified, so that your one host sees what it needs to see.