Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: SAN Configuration and Multipathing Oracle Solaris 11 Information Library |
1. Solaris I/0 Multipathing Overview
2. Fibre Channel Multipathing Configuration Overview
3. Configuring Solaris I/O Multipathing Features
Enabling and Disabling 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)
6. Configuring Virtual Fibre Channel Ports
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
The multipathing features for FC devices can be configured to control all supported FC HBAs. Multipathing is disabled by default for FC devices on SPARC based systems, but is enabled by default on x86 based systems. Configuration of the multipathing features depends on how you intend to use your system.
Note - The multipathing feature is not available for parallel SCSI devices, but is available for FC, SAS, and iSCSI devices. Multipathing is also supported for tape drives and libraries.
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.
Device specific and device name change considerations
In the /dev and /devices trees, multipathed 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:
/dev/dsk/c1t1d0s0
Device name with multipath enabled:
/dev/dsk/c0t60003BA27D5170003E5D2A7A0007F3D2d0s0
Therefore, applications that use device names directly must be configured to use the new names whenever you change a multipath configuration from disabled to enabled or vice-versa.
Updates to /etc/vfstab entries and dump configuration
The system’s /etc/vfstab file and the dump configuration also contain references to device names. On both SPARC and x86-based systems the stmsboot 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 the devfsadm -C or performed a reconfiguration boot, the old device paths will not exist and the stmsboot -L command will fail to provide this information. |