Managing SAN Devices and Multipathing in Oracle^® Solaris 11.3

How to Unconfigure a Multipathed FC Device

This procedure shows fabric-connected host ports c0 and c2 to illustrate how to unconfigure fabric devices associated with multipathed devices.

1. Become an administrator.

   For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.3.

2. Identify the port WWN of the fabric 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, the c0::50020f2300006077 and c2::50020f2300006107 Ap_Ids represent different port WWNs for the same device associated with a multipathed device. The c0 and c2 host ports are enabled for use.

3. Stop all device activity to each fabric device on the selected port and unmount any file systems on each fabric device.

   If the device is under any volume manager's control, see your volume manager documentation for maintaining the fabric device.

4. Unconfigure fabric devices associated with the device.

   Only devices on a fabric-connected host port can be unconfigured through the cfgadm -c unconfigure command.

   # cfgadm -c unconfigure c0::50020f2300006077 c2::50020f2300006107

   ---

   Note -  You can remove a device from up to eight paths individually, as in the example command cfgadm -c unconfigure c0::1111, c1::2222, c3::3333, and so on. As an alternative, you can remove an entire set of paths from the host, as in the example cfgadm -c unconfigure c0.

   ---

5. Verify that the selected devices are unconfigured.

   # cfgadm -al
   Ap_Id                Type       Receptacle   Occupant     Condition
   c0                 fc-fabric    connected    configured   unknown
   c0::50020f2300006077 disk       connected    unconfigured 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

   Notice that the Ap_Ids c0::50020f2300006077 and c2::50020f2300006107 are unconfigured. The Occupant column of c0 and c2 still displays those ports as configured because they have other configured occupants.

   Multipathed devices associated with the Ap_Ids c0::50020f2300006077 and c2::50020f2300006107 are no longer available to the system. The following two devices are removed from the system:

   /dev/rdsk/c6t60020F20000061073AC8B52D000B74A3d0s2

   /dev/rdsk/c6t60020F20000061073AC8B4C50004ED3Ad0s2