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


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


Multipathing Considerations

Before you change multipathing configuration note the following considerations. Then follow the instructions for your machine architecture (SPARC or x86) described in the subsequent sections. Some devices need to be properly configured to work with the multipathing software. Refer to your storage array documentation for details on the device specific configuration for your device.

In the /dev and /devices trees, multipath-enabled devices receive new names that indicate that they are under multipath control. A device therefore will have a different name from its original name when it is under multipath control.

Device name with multipath disabled:


Device name with multipath enabled:


Therefore, applications that use device names directly must be configured to use the new names whenever you change multipath configuration from disabled to enabled or vice-versa.

The system’s /etc/vfstab file and the dump configuration also contain references to device names. On both SPARC and x86/x64-based systems the stmsboot(1m) command described in the following sections automatically updates the /etc/vfstab file dump configuration with the new device names. If you have application-dependent file systems which are not listed in the file /etc/vfstab, you can use the stmsboot command to determine the mapping between the old and new device paths.


Caution - if you have run devfsadm -C or performed a reconfiguration reboot then the old device paths will not exist and the stmsboot -L command will fail to provide this information.