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

# dd if=/dev/rdsk/c17t0d1 of=/dev/null count=100
100+0 records in
100+0 records out
Validating the change of LUN binding for a single legacy DSF
You can choose to immediately validate the binding of some of the legacy DSFs with new LUNs and
deferred it for others for example to let applications using these legacy DSFs complete. In this case,
run the ‘scsimgr replace_leg_dsf’ command for each legacy DSF for which you want to
validate the change in binding. The example below validates the change in binding of the legacy
DSF: c17t0d2.
# scsimgr -f replace_leg_dsf -D /dev/rdsk/c17t0d2
scsimgr: Legacy device file '/dev/rdsk/c17t0d2' binding to LUN changed successfully
Validating the change of LUN binding for all legacy DSFs corresponding to lunpaths beneath a target
path
You can choose to validate at once the change of the binding for all legacy DSFs impacted, by
specifying the target path to the ‘scsimgr replace_leg_dsf’ command. This is convenient if
there are several lunpaths beneath each target path as in our example. You should make sure that all
affected legacy DSFs are closed, then run ‘scsimgr replace_leg_dsf’ for each target path
beneath which legacy DSFs are impacted. For this example of reconfiguration, only one target path is
affected: 0/4/1/0/4/0.0x50002fe250006e6c. You can validate the change in binding for all
legacy DSFs by running the command below.
# scsimgr -fv replace_leg_dsf -H 0/4/1/0/4/0.0x50002fe250006e6c
scsimgr: Legacy device file '/dev/rdsk/c17t0d1' binding to LUN changed successfully
scsimgr: Legacy device file '/dev/rdsk/c17t0d2' binding to LUN changed successfully
scsimgr: Legacy device file '/dev/rdsk/c17t0d3' binding to LUN changed successfully
scsimgr: Legacy device file '/dev/rdsk/c17t0d4' binding to LUN changed successfully
scsimgr: Legacy device file '/dev/rdsk/c17t0d5' binding to LUN changed successfully
Note: if you invoke ‘scsimgr replace_leg_dsf’ while the legacy DSF is still opened, the SCSI
stack fails the validation of change in binding for the legacy DSF, and scsimgr displays an error
message as shown below.
# scsimgr -f replace_leg_dsf -D /dev/rdsk/c17t0d1
scsimgr: ERROR: The Legacy device file is opened. replace_leg_dsf cannot proceed
# scsimgr -fv replace_leg_dsf -H 0/4/1/0/4/0.0x50002fe250006e6c
scsimgr: ERROR: The Legacy device file '/dev/rdsk/c17t0d1' is opened. replace_leg_dsf
operation cannot proceed on it.
scsimgr: Legacy device file '/dev/rdsk/c17t0d2' binding to LUN changed successfully
scsimgr: Legacy device file '/dev/rdsk/c17t0d3' binding to LUN changed successfully
scsimgr: Legacy device file '/dev/rdsk/c17t0d4' binding to LUN changed successfully
scsimgr: Legacy device file '/dev/rdsk/c17t0d5' binding to LUN changed successfully
Note: In case the SAN reconfiguration affects both legacy DSFs binding and lunpath authentication, if
you run ‘scsimgr replace_wwid’ while the legacy DSF is closed, the SCSI stack automatically
binds the legacy DSF to the new disk. However, if the legacy DSF is
opened when ‘scsimgr
replace_wwid’ is run, it remains bound to the original disk. The SCSI stack then logs a message
similar to the one below:
38