JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris SAN Configuration and Multipathing Guide
search filter icon
search icon

Document Information

Preface

1.  Product Overview

2.  Fibre Channel Configuration Overview

3.  Administering Multipathing Devices Through mpathadm Commands

4.  Configuring Multipathing Software

Configuring Multipathing

Multipathing Considerations

Enabling and Disabling Multipathing

To Enable Multipathing

To Disable Multipathing

Enabling or Disabling Multipathing on a Per-Port Basis

Port Configuration Considerations

To Configure Multipathing by Port

Configuring Third-Party Storage Devices

Third-Party Device Configuration Considerations

Configuring Third-Party Storage Devices: New Devices

To Configure New Third-Party Devices

Configuring Third-Party Storage Devices: Disabling Devices

To Disable Third-Party Devices

Displaying Device Name Changes

Configuring Automatic Failback

To Configure Automatic Failback

5.  Configuring SAN Devices

6.  Configuring SAS Domains

7.  Configuring IPFC SAN Devices

8.  Solaris 10 10/08 x86/x64 Fibre Channel Operating System Booting Procedure

9.  Persistent Binding for Tape Devices

A.  Manual Configuration for Fabric-Connected Devices

B.  Supported FC-HBA API

C.  Multipathing Troubleshooting

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(1M) command.

To Configure Automatic Failback

  1. Open the /kernel/drv/scsi_vhci.conf file in a text editor.
  2. To disable automatic failback capability, change the auto-failback entry to:
    auto-failback="disable";

    To enable automatic failback capability (if you disabled it before), change the auto-failback entry to:

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