The Effect of Device Replacement on Agile Device Files

Figure 5 shows FRU replacement with no spoofing.
Figure 5: FRU Replacement (No spoofing)
If spoofing of the target World Wide Name and LUN WWID is not supported, replacement results in
the detection of a new device (a new tape has a new WWID); a new LU and a new target are
presented to HP-UX. Because neither the LU nor the mapping of LUN to LU is known, HP-UX creates a
new device special file. No authentication failure is flagged in this case.
To minimize the effect of tape replacement on applications already configured to use the device
special file associated with the old tape, use the io_redirect_dsf command to redirect I/O
requests from the old DSF to the new DSF. For example, in Figure 5, tape1 points to the replaced
device and tape2 is the DSF for the new device. To redirect I/O requests from the old DSF to the
new DSF, enter the following command:
1131:/>io_redirect_dsf /dev/rtape/tape1 /dev/rtape/tape2
For more information, see io_redirect_dsf(1M).
If the application is reconfigured to use the new device file (I/O redirection not required), HP
recommends you use the rmsf command to clean up the old device special files.
8