Appendix A Manual Configuration for Fabric-Connected Devices

This appendix explains about configuring and unconfiguring the fabric devices in the Solaris Express Developer's Edition OS. It explains how the visible fabric devices on a host are detected and configured with and without enabling the Sun StorageTek Traffic Manager software.

This appendix contains the following sections:

• Manual Configuration

• Fabric Device Node Configuration

• Configuring Device Nodes Without Multipathing Enabled

• Configuring Device Nodes With Solaris Multipathing Software Enabled

• Unconfiguring Fabric Devices

Manual Configuration

In the Solaris Express Developer's Edition OS, fabric-connected devices are made available to the Solaris host. This differs from previous versions of the Sun StorageTek Traffic Manager software running on the Solaris 8 or the Solaris 9 OS. In those versions, manual configuration steps were required to achieve fabric-connected device availability.

If you want to manually configure the fabric-connected devices, use the following steps to change the default behavior on the Solaris Express Developer's Edition OS.

---

Note –

Changing the default behavior makes all of your fabric-connected devices unavailable, which can cause problems for fabric-connected devices that are required to be available at boot time.

---

To Configure Manually

1. To enable manual configuration, make sure that the following line in the/kernel/drv/fp.conf file does not start with an initial # character:

   manual_configuration_only=1;

   Refer to the fp(7D) man page and the cfgadm_fp(1M) man page for further information on this setting.

2. Reboot the host.

3. For each fabric-connected device that will need to be made available, follow the steps in Configuring Device Nodes Without Multipathing Enabled or Configuring Device Nodes With Solaris Multipathing Software Enabled, depending on whether you are using the Sun StorageTek Traffic Manager software for multipathing.

   If the original default behavior for fabric-connected devices is desired, use the following steps:

4. To disable manual configuration, make sure that the following line in the/kernel/drv/fp.conf file starts with an initial # character:

   # manual_configuration_only=1;

   Refer to the fp(7D) man page and the cfgadm_fp(1M) man page for further information on this setting.

5. Reboot the host.

Fabric Device Node Configuration

After you configure the hardware in your direct-attach system or SAN, you must ensure that the hosts recognize the devices. This section explains host recognition of fabric devices, also known as 24-bit FC addressing devices on the SAN. After configuring the devices, ports, and zones in your SAN, make sure that the host is aware of the devices. You can have up to 16 million fabric devices connected together on a SAN with FC support.

This section is limited to the operations required from the perspective of the Solaris Express Developer's Edition OS. It does not cover other aspects, such as device availability and device-specific management. If devices are managed by other software, such as a volume manager, refer to the volume manager product documentation for additional instructions.

Ensuring That LUN Level Information Is Visible

To Ensure LUN Level Information is Visible

1. Use the cfgadm command to identify LUN level information.

   If you issue the cfgadm -al -o show_SCSI_LUN controller-ID command immediately after a system boots up, the output might not show the Fibre Channel Protocol (FCP) SCSI LUN level information. The information does not appear because the storage device drivers, such as the ssd and st driver, are not loaded on the running system.

2. Use the modinfo command to check whether the drivers are loaded. After the drivers are loaded, the LUN level information is visible in the cfgadm output.

To Detect Fabric Devices Visible on a Host

This section provides an example of the procedure for detecting fabric devices using FC host ports c0 and c1. This procedure also shows the device configuration information that is displayed with the cfgadm(1M) command.

---

Note –

In the following examples, only failover path attachment point IDs (Ap_Ids) are listed. The Ap_Ids displayed on your system depend on your system configuration.

---

1. Log in as root (su - root)..

2. Display the information about the attachment points on the system.

   # cfgadm -l Ap_Id Type Receptacle Occupant Condition c0 fc-fabric connected unconfigured unknown c1 fc-private connected configured unknown

   In this example, c0 represents a fabric-connected host port, and c1 represents a private, loop-connected host port. Use the cfgadm(1M) command to manage the device configuration on fabric-connected host ports.

   By default, the device configuration on private, loop-connected host ports is managed by a host using the Solaris Express Developer's Edition OS.

3. Display information about the host ports and their attached devices.

   # 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 c0::50020f2300005f24 disk connected unconfigured unknown c0::50020f2300006107 disk connected unconfigured 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

   ---

   Note –

   The cfgadm -l command displays information about FC host ports. You can also use the cfgadm -al command to display information about FC devices. The lines that include a port world wide name (WWN) in the Ap_Id field associated with c0 represent a fabric device. Use the cfgadm configure and unconfigure commands to manage those devices and make them available to hosts using the Solaris Express Developer's Edition OS. The Ap_Id devices with port WWNs under c1 represent private-loop devices that are configured through the c1 host port.

   ---

Configuring Device Nodes Without Multipathing Enabled

This section describes fabric device configuration tasks on a host that does not have multipathing enabled.

The procedures in this section show how to detect fabric devices that are visible on a host and to configure and make them available to a host using the Solaris Express Developer's Edition OS. The procedures in this section use specific devices as examples to illustrate how to use the cfgadm(1M) command to detect and configure fabric devices.

The device information that you supply and that is displayed by the cfgadm(1M) command depends on your system configuration.

To Configure an Individual Device Without Multipathing

This sample procedure describes how to configure a fabric device that is attached to the fabric-connected host port c0.

1. Log in as root (su - root).

2. Identify the device to be configured.

   # 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 c0::50020f2300005f24 disk connected unconfigured unknown c0::50020f2300006107 disk connected unconfigured 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

3. Configure the fabric device.

   # cfgadm -c configure c0::50020f2300006077

4. Verify that the selected fabric 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 unconfigured unknown c0::50020f2300005f24 disk connected unconfigured unknown c0::50020f2300006107 disk connected unconfigured 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

   Notice that the Occupant column for both c0 and c0::50020f2300006077 displays as configured, indicating that the c0 port has a configured occupant and that the c0::50020f2300006077 device is configured.

5. Use the show_SCSI_LUN option to display FCP SCSI LUN information for multi-LUN SCSI devices.

   The following code example shows that the physical devices connected through Ap_Id c0:50020f2300006077 have four LUNs configured.

   # cfgadm -al -o show_SCSI_LUN c0 Ap_Id Type Receptacle Occupant Condition c0 fc-fabric connected configured unknown c0::50020f2300006077,0 disk connected configured unknown c0::50020f2300006077,1 disk connected configured unknown c0::50020f2300006077,2 disk connected configured unknown c0::50020f2300006077,3 disk connected configured unknown

   The device is now available on the host using the Solaris Express Developer's Edition OS. The paths represent each SCSI LUN in the physical device represented by c0::50020f2300006077.

To Configure Multiple Devices Without Multipathing

Make sure you first identify the devices visible to the host with the procedure Ensuring That LUN Level Information Is Visible. This procedure describes how to configure all unconfigured fabric devices that are attached to a fabric-connected host port. The port used as an example is c0.

1. Log in as root (su - root).

2. Identify the devices to be configured.

   # 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 c0::50020f2300005f24 disk connected unconfigured unknown c0::50020f2300006107 disk connected unconfigured 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

3. Configure all of the unconfigured devices on the selected port.

   # cfgadm -c configure c0

   ---

   Note –

   This operation repeats the configure operation of an individual device for all the devices on c0. This can be time consuming if the number of devices on c0 is large.

   ---

4. Verify that all devices on c0 are 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 c0::50020f2300005f24 disk connected configured unknown c0::50020f2300006107 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

5. Use the show_SCSI_LUN command to display FCP SCSI LUN information for multi-LUN SCSI devices.

   The following code example shows that the physical devices represented by c0::50020f2300006077 and c0::50020f2300006107 each have four LUNs configured. The physical devices represented by c0::50020f23000063a9 and c0::50020f2300005f24 each have two LUNs configured.

   # cfgadm -al -o show_SCSI_LUN c0 Ap_Id Type Receptacle Occupant Condition c0 fc-fabric connected configured unknown c0::50020f2300006077,0 disk connected configured unknown c0::50020f2300006077,1 disk connected configured unknown c0::50020f2300006077,2 disk connected configured unknown c0::50020f2300006077,3 disk connected configured unknown c0::50020f23000063a9,0 disk connected configured unknown c0::50020f23000063a9,1 disk connected configured unknown c0::50020f2300005f24,0 disk connected configured unknown c0::50020f2300005f24,1 disk connected configured unknown c0::50020f2300006107,0 disk connected configured unknown c0::50020f2300006107,1 disk connected configured unknown c0::50020f2300006107,2 disk connected configured unknown c0::50020f2300006107,3 disk connected configured unknown

Configuring Device Nodes With Solaris Multipathing Software Enabled

This section describes how to perform fabric device configuration steps on a host that has the multipathing software enabled.

The devices attached to the fabric-connected host port are not configured by default and so are not available to the host using the Solaris Express Developer's Edition OS. Use the cfgadm configure and cfgadm unconfigure commands to manage device node creation for fabric devices. See the cfgadm_fp(1M) man page for additional information. The procedures in this section illustrate steps to detect fabric devices that are visible on a host and to configure them as multipathing devices to make them available to the host using the Solaris Express Developer's Edition OS.

The device information that you supply, and that is displayed by the cfgadm(1M) command, depends on your system configuration. For more information on the cfgadm command, see the cfgadm_fp(1M) and cfgadm(1M) man pages.

To Configure Individual Devices With Sun StorageTek Traffic Manager Software

This sample procedure uses fabric-connected host ports c0 and c2 to configure fabric devices as multipath devices on a host that has the Sun StorageTek Traffic Manager software enabled.

The cfgadm -c configure command for fabric devices is the same regardless of whether multipathing is enabled.

1. Log in as root (su - root)..

2. Identify the port WWN of the device to be configured as the Sun StorageTek Traffic Manager software device.

   Look for devices on a fabric-connected host port marked as fc-fabric. These devices are the devices you can configure with the cfgadm -c configure command.

   # 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 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

   In the above example, the c0::50020f2300006077 and c2::50020f2300006107 Ap_Ids represent the same storage device with different port WWNs for the storage device controllers. The c0 and c2 host ports are enabled for use by the Sun StorageTek Traffic Manager software.

3. Configure the fabric device and make the devices available to the host.

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

4. Verify that the selected devices are 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 unconfigured 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 unconfigured unknown c2::50020f2300006107 disk connected configured unknown

   Notice that the Occupant column of c0 and c0::50020f2300006077 specifies configured, which indicates that the c0 port has at least one configured occupant and that the c0::50020f2300006077 device is configured. The same change has been made in c2 and c2::50020f2300006107.

   When the configure operation has been completed without an error, multipathing-enabled devices are created on the host. If the physical device represented by c0::50020f2300006077 and c2::50020f2300006107 has multiple SCSI LUNs configured, each LUN is configured as a Sun StorageTek Traffic Manager software device. The example below shows that two LUNs are configured through c0::50020f2300006077 and c2::50020f2300006107. Each Ap_Id is associated with a path to those Sun StorageTek Traffic Manager software devices.

   # cfgadm -al -o show_SCSI_LUN c0::50020f2300006077\ c2::50020f2300006107 Ap_Id Type Receptacle Occupant Condition c0::50020f2300006077,0 disk connected configured unknown c0::50020f2300006077,1 disk connected configured unknown c2::50020f2300006107,0 disk connected configured unknown c2::50020f2300006107,1 disk connected configured unknown

   The example above shows that the following two multipathing-enabled devices are created for the device represented by c0::50020f2300006077 and c2::50020f2300006107:

To Configure Multiple Devices With Multipathing

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 the Sun StorageTek Traffic Manager software 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 host to the fabric, whereas c2::50020f2300006107 is an attachment point from the storage to the fabric. A host 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.

1. Log in as root (su - root)..

2. Identify the fabric-connected host port to be 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

3. Verify that all devices on c2 are 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 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

Unconfiguring Fabric Devices

This section provides information about unconfiguring the Sun StorageTek Traffic Manager software.

Unconfiguring a Fabric Device

Before you unconfigure a fabric device, stop all activity to the device and unmount any file systems on the fabric device. See the administration documentation for the Solaris Express Developer's Edition OS for unmounting instructions. If the device is under any volume manager’s control, see the documentation for your volume manager before unconfiguring the device.

To Unconfigure a Fabric Device

This procedure describes how to unconfigure a fabric device that is attached to the fabric-connected host port c0.

1. Log in as root (su - root)..

2. Identify the device to be unconfigured.

   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

3. Unconfigure the fabric device.

   # cfgadm -c unconfigure c0::50020f2300006077

4. Verify that the selected fabric device is 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

To Unconfigure All Fabric Devices on a Fabric-Connected Host Port

This procedure describes how to unconfigure all configured fabric devices that are attached to a fabric-connected host port.

1. Log in as root (su - root)..

2. Identify the fabric devices to be unconfigured.

   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

3. Stop all 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 the documentation for your volume manager before unconfiguring the device.

   # cfgadm -c unconfigure c0

4. Unconfigure all of the configured fabric devices on a selected port.

   ---

   Note –

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

   ---

5. Verify that all the devices on c0 are unconfigured.

   # 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.

To Unconfigure a Fabric Device Associated With Sun StorageTek Traffic Manager Multipathing-Enabled Devices

This procedure shows fabric-connected host ports c0 and c2 to illustrate how to unconfigure fabric devices associated with Sun StorageTek Traffic Manager software devices.

1. Log in as root (su - root)..

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 Sun StorageTek Traffic Manager software device. The c0 and c2 host ports are enabled for use by the Sun StorageTek Traffic Manager software.

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 the documentation for your volume manager 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.

   The Sun StorageTek Traffic Manager software devices associated with the Ap_Ids c0::50020f2300006077 and c2::50020f2300006107 are no longer available to the host using the Solaris Express Developer's Edition OS. The following two devices are removed from the host:

   /dev/rdsk/c6t60020F20000061073AC8B52D000B74A3d0s2

   /dev/rdsk/c6t60020F20000061073AC8B4C50004ED3Ad0s2

To Unconfigure One Path to a Multipathing 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. Log in as root (su - root)..

2. Identify the Ap_Id of the Sun StorageTek Traffic Manager software 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 host using the Solaris Express Developer's Edition OS 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

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 Express Developer's Edition 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 Express Developer's Edition 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.