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

Binding of LUN path 0/1/1/0.0x1.0x0 with new LUN validated successfully
The advantage of this method is that it directly specifies the lunpath class and instance provided in the
logging message. This is also sufficient when the replaced disk only has one lunpath, or if only a few
lunpaths are affected by the SAN reconfiguration.
Validating disk replacement for all lunpaths of a replaced LUN
If disk15 had multiple lunpaths, it would be cumbersome to repeat the ‘scsimgr replace_wwid’
command for each lunpath. It is more convenient to validate the replacement for all lunpaths of the
disk at once by specifying the replaced LUN as shown in the command below.
# scsimgr -f replace_wwid -D /dev/rdisk/disk15
scsimgr: Successfully validated binding of LUN paths with new LUN.
Note: To be able to validate the replacement by specifying the replaced LUN, either write down its
identifier (device file name, hardware path, or class and instance number of the replaced LUN) before
proceeding with the replacement, or determine the replace LUN hardware path by running the
following commands after the authentication failure is logged:
1. Determine the hardware path of the lunpath:
# scsimgr -p get_attr -C lunpath -I 0 -a hw_path
0/1/1/0.0x0.0x0
2. Determine the hardware path of the replaced LUN
# ioscan -m hwpath -H 0/1/1/0.0x0.0x0
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0x0
0/1/1/0.0x0.0x0 0/1/1/0.0.0
3. Validate the replacement using the hardware path of the replaced LUN
# scsimgr -f replace_wwid -H 64000/0xfa00/0x0
scsimgr: Successfully validated binding of LUN paths with new LUN.
Once the replacement is validated, data transfer to the new disk can be performed through the
lunpaths. Since the new disk has a different WWID, the system assigns it a new instance and creates
new DSFs. To avoid reconfiguring applications and upper layer modules (Volume Managers, file
systems, etc.) using disk15, assign disk15 DSFs and instance to the new disk by specifying the ‘dsf’
keyword at the command line as shown below.
# scsimgr -f replace_wwid -D /dev/rdisk/disk15 dsf
scsimgr: Successfully validated binding of LUN paths with new LUN.
Device special file of replaced LUN successfully re-assigned to replacing LUN
Notes:
• scsimgr calls the io_redirect_dsf script to re-assign the device files of the replaced
disk to the new disk. For more information about this script, see the io_redirect_dsf (1M) man
page.
• If the device is used by the Logical Volume Manager (LVM), you must use the ‘dsf’ keyword or
use the io_redirect_dsf script during the LVM online disk replacement procedure.
Validating disk replacement for all lunpaths under a target path
When a LUN is replaced or the SAN is reconfigured, several lunpaths under a given target can be
put in “authentication failure” state. This is true when for instance a reconfiguration of a disk array
result to different WWIDs being assigned to all LUNs of the disk array seen by the system. The disk
array can have thousand of LUNs, but only a few target ports. All lunpaths of the affected LUNs will
31