JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: SAN Configuration and Multipathing     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

Preface

1.  Solaris I/0 Multipathing Overview

2.  Fibre Channel Multipathing Configuration Overview

3.  Configuring Solaris I/O Multipathing Features

4.  Administering Multipathing Devices (mpathadm)

5.  Configuring SAN Devices

6.  Configuring Virtual Fibre Channel Ports

7.  Configuring FCoE Ports

8.  Configuring SAS Domains

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

Manually Configuring FC Devices

How to Manually Configure a FC Device

Configuring Fabric Device Nodes

Ensuring That LUN Level Information Is Visible

How to Ensure LUN Level Information is Visible

How to Detect Visible Fabric Devices on a System

Configuring Device Nodes Without Multipathing Enabled

How to Manually Configure an FC Device Without Multipathing

How to Configure Multiple FC Devices Without Multipathing

Configuring Device Nodes With Solaris Multipathing Enabled

How to Configure Individual Multipathed FC Devices

How to Configure Multiple Multipathed FC Devices

Unconfiguring Fabric Devices

Unconfiguring a Fabric Device

How to Manually Unconfigure a FC Device

How to Unconfigure All FC Devices on a FC Host Port

How to Unconfigure a Multipathed FC Device

How to Unconfigure One Path to a Multipathed FC Device

How to Unconfigure All Multipathed FC Devices

B.  Supported FC-HBA API

C.  Troubleshooting Multipathed Device Problems

Index

How to Unconfigure All Multipathed FC Devices

An Ap_Id on a fabric-connected host port is a path to a multipathed device.

When a multipathed device has multiple Ap_Ids connected to it, the device is still available to the system after you unconfigure an Ap_Id. After you unconfigure the last Ap_Id, no additional paths remain and the device is unavailable to the system. Only devices on a fabric-connected host port can be unconfigured.

  1. Become an administrator
  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.