hardware path translation

[gdemers]

EMS Event Notification identified a disk at path 64000_0xfa00_0x0. How can I translate that to either a cntndn or an H/W path as given by ioscan n/n/n/n/n.n.n?

[Mel Burslan]

I have not seen a device path like this from EMS. Is this a VPAR or something ?

But this might help :

cd /dev/dsk
ls -l | grep -i 0xfa00

you might find it this way. Not that I know for sure but this is something I used in the past, translating minor device numbers to their cxtxdx device files.

[gdemers]

Looks like The agile LUN H/W path vs the Legacy H/W path:

LUN H/W Path 64000/0xfa00/0x2dc

Persistent Device File /dev/disk/disk7225

Legacy Device File(s) /dev/dsk/c153t0d3;/dev/dsk/c158t0d3;/dev/dsk/c163t0d3;/dev/dsk/

Legacy H/W Path(s) 0/0/6/1/0.20.68.0.0.0.3;0/0/14/1/0.10.68.0.0.0.3;1/0/4/1/0.20.6

[Ismail Azad · Accepted solution]

Hi gdemers,

This is the virtualized hardware address in terms of the agile view where you speak in the language of a "virutal root node" and a "vitual bus" and that is why the 64000 and 0xfa00 are always the same and the only thing that differs is the last field termed as the virtual_lun_id.

Execute ioscan -m hwpath and this should map all the different "views" of hardware addressing.

From there the command ioscan -funNC disk can be executed and the corresponding persistent DSF (/dev/disk/diskx) will be found.

After which you can execute an ioscan -m dsf which can actually tell you the device file in the form cxtxdx. Hopefully you can skip one of these steps but this works fine for me.

Regards
Ismail Azad

[gdemers]

This is a rather strange situation where an internal drive failed, we replaced it and removed only the legacy device file. Now the agile name shows up in both the sam disk display regardless of whether we toggle to legacy or agile view. Any thoughts as to how best to get the hpux meta information back in sync to support the newly added disk?