Skip Navigation Links | |
Exit Print View | |
Oracle Solaris SAN Configuration and Multipathing Guide Oracle Solaris 10 1/13 Information Library |
1. Solaris I/0 Multipathing Overview
2. Configuring Solaris I/O Multipathing Features
Configuring Multipathing I/O Features
Enabling and Disabling Multipathing
How to Determine if Multipathing is Enabled or Disabled
Enabling or Disabling Multipathing on a Per-Port Basis
Port Configuration Considerations
How to Configure Multipathing by Port
Configuring Third-Party Storage Devices
Third-Party Device Configuration Considerations
Configuring Third-Party Storage Devices: New Devices
How to Configure Third-Party Devices
Configuring Third-Party Storage Devices: Disabling Devices
How to Disable Third-Party Devices
Displaying Device Name Changes
Administering Solaris I/O Multipathing
Displaying Multipathing Support Information
How to Display Multipathing Support Information
How to Display Properties of a Specific Initiator Port
How to Display Specific LU Information
How to Display All LUs Associated With a Specific Target Port
How to Display a LU With a Specific Name
Configuring Automatic Failback for Multipathing Support
How to Configure Automatic Failback for Specific Multipathing Support
3. Configuring Fabric-Connected Devices
4. Configuring Oracle Solaris iSCSI Initiators
6. Configuring IPFC SAN Devices
7. Booting the Oracle Solaris OS From Fibre Channel Devices on x86 Based Systems
8. Persistent Binding for Tape Devices
A. Manual Configuration for Fabric-Connected Devices
Some storage devices have controllers configured as PRIMARY and SECONDARY as part of the array configuration. The secondary paths may operate at a lower performance level than the primary paths. The multipathing software uses the primary path to talk to the storage device and to keep the secondary path on standby.
In the event of a primary path failure, the multipathing software automatically directs all I/O traffic over the secondary path, with the primary path taken offline. This process is called a “failover” operation. When the failure associated with the primary path has been repaired, the multipathing software automatically directs all I/O traffic over the primary path and keeps the secondary path standby as before. This process is called a failback operation.
You can disable the automatic failback operation so the multipathing software does not automatically failback to the primary path. Later, after the failure associated with the primary path has been repaired, you can do a manual failback operation using the luxadm command. For more information, see luxadm(1M).
auto-failback="enable";
auto-failback="disable";
# shutdown -g0 -y -i6