Ignite-UX and SAS white paper

4
- Swapping two or more SAS devices
- Permanently removing
4
- Moving a SAS device from one SAS HBA to another.
a SAS device when there are still devices in higher numbered bays
- Creating or deleting SAS RAID volumes post-installation
5
Once installed, if a SAS device must be replaced, you must use the sasmgr(1m) option
replace_tgt to re-associate a SAS device with the hardware path of the device it replaces (it will
be assigned a new hardware path since it has a different WWN).
As of release C.7.5 of Ignite-UX, the WWN (or WWID) is also used to identify a device during a
recovery. This allows Ignite-UX to restore the system to the same SAS disks as before. However,
the hardware paths and legacy device file names will still change when configuration changes are
made.
As of release C.7.10, Ignite-UX attempts to remap legacy hardware paths so it can restore legacy
device file names for SAS devices under the sasd driver. For this to work correctly, a recovery
archive must be made after each hardware configuration change.
In the next few sections we will discuss exactly what happens when you place a SAS device in a
lower bay number or remove a SAS device when there are some in higher bay numbers, and then
cold-install or recover a system.
4
This does not include replacing a SAS device as long as the replacement is performed before doing a cold-install or recovery using Ignite-
UX.
5
Performing either of these actions may change the hardware path of other RAID volumes. These actions will not affect the hardware paths of
SAS devices. See the previous section for more information.