Predicting new FC HBA instance number

[ASOEASTGEOGRAPHY]

We will be changing the FC connection between our XP1024 and our core switches. Keeping the FC cable attached to the XP port we will move the other ens (SAN connection) to another port (different number) on another switch (different domain id). This will change two fields of the FC hardware path. We are keeping the same LUN number, so I can predict the target and LUN id that will result, but I don't know how ioinit (if that's the responsible process) will deternmine the 'new' HBA instance number. Is there a way to reliably predict this?

[Sanjay_6]

Hi,

This link from itrc might help,

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000073838415

The doc id is KBRC00004879.

you can also check the doc KBAN00000795 along the same lines.

Hope this helps.

Regds

[Steven E. Protter]

You can actually accurately predict the isntance number every time.

The full scoop is in the HP-UX CSA guide by Charles Keenan: Chapter 4

Here is an example:

Hardware path is

0/2/0/0.3.3.0.4.6.0

HBA is 0/2/0/0
PortID=3.3.0(3=domain switch closest to the disk array, 3 equal port number on the switch,0=loop id in the switched fabric SAN
SCSI Address is 4.6.0(4=VSB:each VSP ccan handle 128 LUNS hence 560/128=4 remainder 48, 6-target id 48/6,)=SCSI LUN, remainder of the last division 48/6 remainder 0.

device file


/dev/dsk/c14t6d0 6 is from targed it above.
This is based in a diagram on page 230.

Or:
thread:
http://search.hp.com/redirect.html?url=http%3A//forums1.itrc.hp.com/service/forums/questionanswer.do%3FthreadId%3D318251&qt=predict+%2Bscsi+%2Binstance+%2Bnumber&hit=1

Manual:
http://docs.hp.com/hpux/pdf/B2355-90841docs.pdf

SEP

[ASOEASTGEOGRAPHY]

Steve,

Thanks for the reply. Your example holds a lot of promise, but I can't tell how the instance number (c14) is derived.
On the XP we are using Volume Set Addressing, so the LUN value assigned at the XP to the 'disk' can be translated to a target and LUN id. When we change the hardware path, we'll go from
0/12/0/0.10.15.0.0.X.Y
0/12/0/0.20.4.0.0.X.Y
Again, the domain id and the port number should be the only things changing in the hardware address. These should change the card instance number right?
How was the "c14" value caluculated in your example?