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 Unconfigure All Fabric-Connected Devices With Multipathing Enabled

An Ap_Id on a fabric-connected host port is a path to the Sun StorageTek Traffic Manager software device.

When a Sun StorageTek Traffic Manager software device has multiple Ap_Ids connected to it, the device is still available to the host using the Solaris 10 OS after you unconfigure an Ap_Id. After you unconfigure the last Ap_Id, no additional paths remain and the device is unavailable to the host using the Solaris 10 OS. Only devices on a fabric-connected host port can be unconfigured.

  1. Log in as root (su - root)..
  2. Identify the devices to be unconfigured.
    # 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::220203708b9b20b2 disk       connected    configured   unknown
    c2                   fc-fabric  connected    configured   unknown
    c2::50020f2300005f24 disk       connected    configured   unknown
  3. Unconfigure all of the configured devices on the selected port.
    # cfgadm -c unconfigure c2

    Note - This operation repeats the unconfigure command of an individual device for all devices on c2. This process can be time-consuming if the number of devices on c2 is large.


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

    Notice that the Occupant column lists c2 and all the devices attached to c2 as unconfigured.