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

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

Manual Configuration

To Configure Manually

Fabric Device Node Configuration

Ensuring That LUN Level Information Is Visible

To Ensure LUN Level Information is Visible

To Detect Fabric Devices Visible on a Host

Configuring Device Nodes Without Multipathing Enabled

To Configure an Individual Device Without Multipathing

To Configure Multiple Devices Without Multipathing

Configuring Device Nodes With Solaris Multipathing Software Enabled

To Configure Individual Devices With Sun StorageTek Traffic Manager Software

To Configure Multiple Devices With Multipathing

Unconfiguring Fabric Devices

Unconfiguring a Fabric Device

To Unconfigure a Fabric Device

To Unconfigure All Fabric Devices on a Fabric-Connected Host Port

To Unconfigure a Fabric Device Associated With Sun StorageTek Traffic Manager Multipathing-Enabled Devices

To Unconfigure One Path to a Multipathing Device

To Unconfigure All Fabric-Connected Devices With Multipathing Enabled

B.  Supported FC-HBA API

C.  Multipathing Troubleshooting

Index

To Configure Multiple Devices With Multipathing

Before you configure or remove device nodes, be sure to first identify the fabric devices by using the procedure Ensuring That LUN Level Information Is Visible.

In this example, an Ap_Id on a fabric-connected host port is a path to the Sun StorageTek Traffic Manager software device. For example, all devices with a path through c2 are to be configured, but none through c0 are to be configured. c2 is an attachment point from the host to the fabric, whereas c2::50020f2300006107 is an attachment point from the storage to the fabric. A host detects all the storage devices in a fabric for which it is configured.

Configuring an Ap_Id on the device that has already been configured through another Ap_Id results in an additional path to the previously configured device. A new device node is not created in this case. The device node is created only the first time an Ap_Id to the corresponding device is configured.

  1. Log in as root (su - root)..
  2. Identify the fabric-connected host port to be configured.
    # cfgadm -al
    Ap_Id                Type        Receptacle  Occupant     Condition
    c0                   fc-fabric   connected   configured   unknown
    c0::50020f2300006077 disk        connected   configured   unknown
    c0::50020f23000063a9 disk        connected   configured   unknown
    c1                   fc-private  connected   configured   unknown
    c1::220203708b69c32b disk        connected   configured   unknown
    c1::220203708ba7d832 disk        connected   configured   unknown
    c1::220203708b8d45f2 disk        connected   configured   unknown
    c1::220203708b9b20b2 disk        connected   configured   unknown
    c2                   fc-fabric   connected   unconfigured unknown
    c2::50020f2300005f24 disk        connected   unconfigured unknown
    c2::50020f2300006107 disk        connected   unconfigured unknown

    Devices represented by Ap_Ids c0::50020f2300006077 and c2::50020f2300006107 are two paths to the same physical device, with c0::50020f2300006077 already configured. Configure the unconfigured devices on the selected port. This operation repeats the configure command of an individual device for all the devices on c2. This can be time-consuming if the number of devices on c2 is large.

    # cfgadm -c configure c2
  3. Verify that all devices on c2 are configured.
    # cfgadm -al
    Ap_Id                Type       Receptacle   Occupant     Condition
    c0                   fc-fabric  connected    configured   unknown
    c0::50020f2300006077 disk       connected    configured   unknown
    c0::50020f23000063a9 disk       connected    configured   unknown
    c1                   fc-private connected    configured   unknown
    c1::220203708b69c32b disk       connected    configured   unknown
    c1::220203708ba7d832 disk       connected    configured   unknown
    c1::220203708b8d45f2 disk       connected    configured   unknown
    c1::220203708b9b20b2 disk       connected    configured   unknown
    c2                   fc-fabric  connected    configured   unknown
    c2::50020f2300005f24 disk       connected    configured   unknown
    c2::50020f2300006107 disk       connected    configured   unknown

    Notice that the Occupant column of c2 and all of the devices under c2 is marked as configured.

    The show_SCSI_LUN command displays FCP SCSI LUN information for multiple LUN SCSI devices. The following code example shows that the physical devices connected through by c2::50020f2300006107 and c2::50020f2300005f24 each have two LUNs configured.

    # cfgadm -al -o show_SCSI_LUN c2
    Ap_Id                 Type     Receptacle   Occupant     Condition
    c2                   fc-fabric connected    configured   unknown
    c2::50020f2300005f24,0 disk    connected    configured   unknown
    c2::50020f2300005f24,1 disk    connected    configured   unknown
    c2::50020f2300006107,0 disk    connected    configured   unknown
    c2::50020f2300006107,1 disk    connected    configured   unknown