JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Administration: SAN Configuration and Multipathing     Oracle Solaris 11.1 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

5.  Configuring Fabric-Connected Devices

6.  Configuring Solaris iSCSI Initiators

7.  Configuring Virtual Fibre Channel Ports

8.  Configuring FCoE Ports

9.  Configuring SAS Domains

10.  Configuring IPFC SAN Devices

11.  Booting the Oracle Solaris OS From Fibre Channel Devices on x86 Based Systems

12.  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 One Path to a Multipathed FC Device

In contrast to the procedure in the preceding section, this procedure shows how to unconfigure one device associated with c2::50020f2300006107 and leave the other device, 50020f2300006077, configured. Only devices on a fabric-connected host port can be unconfigured through the cfgadm unconfigure command.

  1. Become an administrator.
  2. Identify the Ap_Id of the multipathed device 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::220203708ba7d832 disk        connected    configured   unknown
    c2                   fc-fabric   connected    configured   unknown
    c2::50020f2300005f24 disk        connected    configured   unknown
    c2::50020f2300006107 disk        connected    configured   unknown

    In this example, c0::50020f2300006077 and c2::50020f2300006107 Ap_Ids represent different port WWNs for the same device.

  3. Unconfigure the Ap_Id associated with the device.

    Note - If the Ap_Id represents the last configured path to the device, stop all activity to the path and unmount any file systems on it. If the multipathing device is under any volume manager’s control, see the documentation for your volume manager for maintaining the fabric device.


    In the example that follows, the path represented as c2::50020f2300006107 is unconfigured, and c0::50020f2300006077 remains configured to show how you can unconfigure just one of multiple paths for a multipathing device.

    # cfgadm -c unconfigure c2::50020f2300006107
  4. Verify that the selected path c2::50020f2300006107 is 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::220203708ba7d832 disk       connected    configured   unknown
    c2                   fc-fabric  connected    configured   unknown
    c2::50020f2300005f24 disk       connected    configured   unknown
    c2::50020f2300006107 disk       connected    unconfigured unknown

    The devices associated with that Ap_Id are still available to a system through the other path, represented by c0::50020f2300006077. A device can be connected to multiple Ap_Ids and an Ap_Id can be connected to multiple devices.

    /dev/rdsk/c6t60020F20000061073AC8B52D000B74A3d0s2
    and
    /dev/rdsk/c6t60020F20000061073AC8B4C50004ED3Ad0s2