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 a multipathed 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 system to the fabric, whereas c2::50020f2300006107 is an attachment point from the storage to the fabric. A system 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.
# 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
# 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
This section provides information about unconfiguring the multipathing features for fabric devices.
Before you unconfigure a fabric device, stop all activity to the device and unmount any file systems on the fabric device. See the Oracle Solaris administration documentation for unmounting instructions. If the device is under any volume manager’s control, see your volume manager documentation before unconfiguring the device.
This procedure describes how to unconfigure a fabric device that is attached to the fabric-connected host port c0.
Only devices on a fabric-connected host port can 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
# cfgadm -c unconfigure c0::50020f2300006077
# 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
This procedure describes how to unconfigure all configured fabric devices that are attached to a fabric-connected host port.
Only devices on a fabric-connected host port can 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
If the device is under any volume manager’s control, see your volume manager documentation before unconfiguring the device.
# cfgadm -c unconfigure c0
# cfgadm -al Ap_Id Type Receptacle Occupant Condition c0 fc-fabric connected unconfigured unknown c0::50020f2300006077 disk connected unconfigured unknown c0::50020f23000063a9 disk connected unconfigured unknown c1 fc-private connected configured unknown c1::220203708b69c32b disk connected configured unknown c1::220203708ba7d832 disk connected configured unknown
Notice that the Occupant column of c0 and all the fabric devices attached to it are displayed as unconfigured.
This procedure shows fabric-connected host ports c0 and c2 to illustrate how to unconfigure fabric devices associated with multipathed devices.
# 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.
If the device is under any volume manager’s control, see your volume manager documentation for maintaining the fabric 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
# 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
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.
# 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.
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
# 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
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.
# 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
# cfgadm -c unconfigure c2
# 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.