JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: SAN Configuration and Multipathing     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

Preface

1.  Solaris I/0 Multipathing Overview

2.  Fibre Channel Multipathing Configuration Overview

3.  Configuring Solaris I/O Multipathing Features

Configuring Multipathing I/O Features

Multipathing Considerations

Enabling and Disabling Multipathing

How to Enable Multipathing

How to Disable Multipathing

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 o Configure Third-Party Devices

Configuring Third-Party Storage Devices: Disabling Devices

How to Disable Third-Party Devices

Displaying Device Name Changes

Configuring Automatic Failback

How to Configure Automatic Failback

4.  Administering Multipathing Devices (mpathadm)

5.  Configuring SAN Devices

6.  Configuring Virtual Fibre Channel Ports

7.  Configuring FCoE Ports

8.  Configuring SAS Domains

9.  Configuring IPFC SAN Devices

10.  Booting the Solaris OS From Fibre Channel Devices on x86 Systems

11.  Persistent Binding for Tape Devices

A.  Manual Configuration for Fabric-Connected Devices

B.  Supported FC-HBA API

C.  Troubleshooting Multipathed Device Problems

Index

Configuring Automatic Failback

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 keeps 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).

How to Configure Automatic Failback

  1. Become an administrator.
  2. Copy the /kernel/drv/scsi_vhci.conf file to the /etc/driver/drv/scsi_vhci.conf file.
  3. Edit the /etc/driver/drv/scsi_vhci.conf file.
  4. Disable automatic failback capability by changing the auto-failback entry to:
    auto-failback="disable";

    Enable automatic failback capability (if you disabled it before), by changing the auto-failback entry to:

    auto-failback="enable";
  5. Save and exit the file.
  6. Reboot the system.
    # shutdown -g0 -y -i6