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


Enabling or Disabling Multipathing on a Per-Port Basis

Multipathing can be enabled or disabled on specific Fibre Channel Host Bus Adapter (HBA) controller ports. If you enable multipathing on a specific HBA port controller port, all supported devices connected to that controller port will be enabled for multipath operation.

The following procedure applies to both SPARC and x86 based machines.

Port Configuration Considerations

Before you start configuring the software by port, consider the following:

To Configure Multipathing by Port

Depending on how many ports you want the multipathing software to control, you can enable or disable multipathing globally or for specified ports.

  1. Log in as root (su - root).
  2. Determine the HBA controller ports that you want the multipathing software to control.

    For example, to select the desired device, perform an ls -l command on /dev/cfg directory. The following example shows the ls -l command output.

    lrwxrwxrwx  1 root  root  50 Jan 29 21:33 c0 -> 
    lrwxrwxrwx  1 root  root  61 Jan 29 21:33 c1 ->
    lrwxrwxrwx  1 root  root  61 Jan 29 21:33 c2 -> 
    lrwxrwxrwx  1 root  root  53 Jan 29 21:33 c3 -> 
    lrwxrwxrwx  1 root  root  54 Apr 16 20:28 c5 ->
    lrwxrwxrwx  1 root  root  56 Apr 16 20:28 c6 -> 

    Note - Controllers c5 and c6 are ports A and B on a dual-port FC HBA. Controllers c1 and c3 are single port SAS HBA ports. Controller c2 is the internal SAS controller in a Sun Fire T2000 server.

    Once you have determined the port, or ports, you want to explicitly enable or disable multipathing for, go to the next step.

  3. Enable or disable specific ports as follows:
    • FC HBA ports
      1. Edit file /kernel/drv/fp.conf
      2. Add the following line for each FC HBA port that is to be enabled:
        name="fp" parent="parent name" port=port-number mpxio-disable="no";

        where parent name is the port device name, and port-number is the FC HBA port number.

        For example, the following entries disable multipathing on all FC HBA controller ports except for the two specified ports:

        name="fp" parent="/pci@6,2000/SUNW,qlc@2" port=0 mpxio-disable="no";
        name="fp" parent="/pci@13,2000/pci@2/SUNW,qlc@5" port=0 mpxio-disable="no";
      3. Add the following line for each FC HBA port that is to be disabled:
        name="fp" parent="parent name" port=port-number mpxio-disable="yes";

        For example:

        name="fp" parent="/pci@6,2000/SUNW,qlc@2" port=0 mpxio-disable="yes";
  4. Type stmsboot -u to start the reboot and configuration process.

    You are prompted to reboot. During the reboot, the /etc/vfstab file and your dump device configuration are updated to reflect any device name changes.

  5. (Optional) After the reboot, if necessary, configure your applications to use new device names as described in Multipathing Considerations.