Advertisements

The legacy lun path (b 32 – t 13 – l 0) registration failed because it has been re-mapped from its original LUN (default dev 0xb000018) to a different LUN (default dev 0xc0000bd).

Checking /var/adm/syslog/syslog.log I see that lunpath, instance 81 is showing an error message

root@hp-ux:~ # grep vmunix /var/adm/syslog/syslog.log | grep “Nov 9”
Nov 9 04:37:14 hp-ux vmunix: class : lunpath, instance 81
Nov 9 04:37:14 hp-ux vmunix: The legacy lun path (b 32 – t 13 – l 0)
Nov 9 04:37:14 hp-ux vmunix: registration failed because it has been
Nov 9 04:37:14 hp-ux vmunix: re-mapped from its original LUN (default dev 0xb000018)
Nov 9 04:37:14 hp-ux vmunix: to a different LUN (default dev 0xc0000bd).
Nov 9 04:37:14 hp-ux vmunix: The administrator has to close the original LUN and
Nov 9 04:37:14 hp-ux vmunix: then validate this LUN re-mapping using the scsimgr
Nov 9 04:37:14 hp-ux vmunix: command:
Nov 9 04:37:14 hp-ux vmunix: scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz

(b 32 – t 13 – l 0)
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/c32t13d0

Let’s discover the hardware path for this instance

root@hp-ux:~ # scsimgr -p get_attr -C lunpath -I 81 -a hw_path
0/2/0/0/0/1.0x5001438017928fe6.0x0

Pick the LUN H/W Path

root@hp-ux:~ # ioscan -m hwpath -H 0/2/0/0/0/1.0x5001438017928fe6.0x0
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0xbd
0/2/0/0/0/1.0x5001438017928fe6.0x0

And run the following command

root@hp-ux:~ # scsimgr -f replace_wwid -H 64000/0xfa00/0xbd
scsimgr: Successfully validated binding of LUN paths with new LUN.

Advertisements
%d bloggers like this: