scsimgr SCSI Management and Diagnostics utility on HP-UX 11i v3 (March 2008)

The SCSI stack detects the change of the disk seen through the legacy lunpaths (legacy DSFs) with
hardware path starting with: 0/4/1/0/4/0.1.4. It logs the following message for the legacy
lunpaths impacted; One message for each legacy lunpath.
The legacy lun path (b 17 - t 0 - l 1) registration failed because it has been re-mapped
from its original LUN (default dev 0x0C000005) to a different LUN (default dev 0xC0000006).
The administrator has to close the original LUN and then validate this LUN re-mapping using
the scsimgr:
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz
The legacy lun path (b 17 - t 0 - l 2) registration failed because it has been re-mapped
from its original LUN (default dev 0x0C000005) to a different LUN (default dev 0xC0000006).
The administrator has to close the original LUN and then validate this LUN re-mapping using
the scsimgr:
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz
The legacy lun path (b 17 - t 0 - l 3) registration failed because it has been re-mapped
from its original LUN (default dev 0x0C000005) to a different LUN (default dev 0xC0000006).
The administrator has to close the original LUN and then validate this LUN re-mapping using
the scsimgr:
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz
The legacy lun path (b 17 - t 0 - l 4) registration failed because it has been re-mapped
from its original LUN (default dev 0x0C000005) to a different LUN (default dev 0xC0000006).
The administrator has to close the original LUN and then validate this LUN re-mapping using
the scsimgr:
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz
The legacy lun path (b 17 - t 0 - l 5) registration failed because it has been re-mapped
from its original LUN (default dev 0x0C000005) to a different LUN (default dev 0xC0000006).
The administrator has to close the original LUN and then validate this LUN re-mapping using
the scsimgr:
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz
In these messages, the legacy lunpath is identified by the legacy bus instance (b), the legacy target
identifier (t), and the legacy LUN identifier (l). The impacted legacy DSFs can be derived from these
identifiers by following the legacy DSF naming convention (see intro(7)). The legacy DSFs impacted
are:
• Raw legacy DSFs:
/dev/rdsk/c17t0d1
/dev/rdsk/c17t0d2
/dev/rdsk/c17t0d3
/dev/rdsk/c17t0d4
/dev/rdsk/c17t0d5
• Block legacy DSFs:
/dev/rdsk/c17t0d1
/dev/rdsk/c17t0d2
/dev/rdsk/c17t0d3
/dev/rdsk/c17t0d4
/dev/rdsk/c17t0d5
The disk86 of the disk array DA1 is still accessible through the lunpath:
0/4/1/0/4/0.0x50001fe150006e69.0x4001000000000000, and the multi-pathing is enabled
by default on legacy DSFs. The application ‘A’ I/O transfers to disk86 through the legacy DSF
/dev/rdsk/c17t0d1 are not interrupted. Another application can even open /dev/rdsk/c17t0d1 to
access disk86 even if the corresponding lunpath is no longer available. The following example shows
the dd command opening /dev/rdsk/c17t0d1 and transferring data successfully.
37