| Solaris Fibre Channel and Storage Multipathing Administration Guide |    
|
| Solaris Fibre Channel and Storage Multipathing Administration Guide |
|
| A P P E N D I X A |
|
Manual Configuration for Fabric Connected Devices |
This appendix explains about configuring and unconfiguring the fabric devices in Solaris 10. It explains how the visible fabric devices on a host are detected and configured without enabling the multipathing feature and enabling the multipathing software.
This appendix contains the following sections:
In Solaris 10, fabric-connected devices are made available to the Solaris host. This differs from previous versions of the Solaris FC and Storage Multipathing 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 on the Solaris 10 host. If you want to manually configure the fabric-connected devices, use the following steps to change the default behavior on the Solaris 10 host. Note that changing the default behavior makes all of your fabric-connected devices unavailable. This can cause problem for fabric-connected devices that are required to be available at boot time.
1. Edit the file /kernel/drv/fp.conf and uncomment the line.
Please refer to the fp(7D) man page and the cfgadm_fp(1M) man page for further information on this setting.
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 dependent upon whether you are using the Solaris FC and Storage Multipathing Software for multipathing.
If the original default behavior for fabric-connected devices is desired, use the following steps:
4. Edit the file "/kernel/drv/fp.conf" and comment the line
Please refer to the fp(7D) man page and the cfgadm_fp(1M) man page for further information on this setting.
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, you need to 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 10 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.
You need to follow the steps mentioned below to ensure the visibility of LUN level information.
1. Use the cfgadm -al -o show_SCSI_LUN <controller_id> 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.
|
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. |
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 10 OS.
3. Display information about the host ports and their attached devices.
This section describes fabric device configuration tasks on a host that does not have multipathing enabled.
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 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 10 OS.
The device information that you supply and that is displayed by the cfgadm(1M) command depends on your system configuration.
|
This sample procedure describes how to configure a fabric device that is attached to the fabric-connected host port c0.
2. Identify the device to be configured.
3. Configure the fabric device.
4. Verify that the selected fabric device is configured.
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.
The device is now available on the host using the Solaris 10 OS. The paths represent each SCSI LUN in the physical device represented by c0::50020f2300006077.
|
Make sure you first identify the devices visible to the host with the procedure To Detect Fabric Devices Visible on a Host. 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.
2. Identify the devices to be configured.
3. Configure all of the unconfigured devices on the selected port.
|
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.
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.
This section describes how to perform fabric device configuration steps on a host that has the Solaris 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 10 OS. Use the cfgadm(1M) configure and 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 10 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.
|
This sample procedure uses fabric-connected host ports c0 and c2 to configure fabric devices as multipath devices on a host that has the Solaris FC and Storage Multipathing software enabled.
The cfgadm -c configure command for fabric devices is the same regardless of whether or not multipathing is enabled.
2. Identify the port WWN of the device to be configured as the Solaris FC and Storage Multipathing software device.
Look for devices on a fabric-connected host port, marked as fc-fabric. These are the devices you can configure with the cfgadm -c configure command.
In Code example A-3, 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 Solaris FC and Storage Multipathing software.
3. Configure the fabric device and make the Solaris FC and Storage Multipathing software devices available to the host.
4. Verify that the selected devices are configured.
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 Solaris FC and Storage Multipathing software device. Code example A-4, shows that two LUNs are configured through c0::50020f2300006077 and c2::50020f2300006107. Each Ap_Id is associated with a path to those Solaris FC and Storage Multipathing software devices.
In code example A-4, notice that the following two multipathing-enabled devices are created for the device represented by c0::50020f2300006077 and c2::50020f2300006107:
|
Before you configure or remove device nodes, be sure to first identify the fabric devices by using the procedure To Detect Fabric Devices Visible on a Host.
In this example, an Ap_Id on a fabric-connected host port is a path to the Solaris FC and Storage Multipathing 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 Solaris FC and Storage Multipathing software device that has already been configured through another Ap_Id results in an additional path to the previously configured device. Note that 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 Solaris FC and Storage Multipathing device is configured.
2. Identify the fabric-connected host port to be configured.
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.
3. Verify that all devices on c2 are configured.
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. Code example A-5, shows that the physical devices connected through by c2::50020f2300006107 and c2::50020f2300005f24 each have two LUNs configured.
This section provides information about unconfiguring the Solaris FC and Storage Multipathing software.
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 10 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.
|
This procedure describes how to unconfigure a fabric device that is attached to the fabric-connected host port c0.
2. Identify the device to be unconfigured.
Only devices on a fabric-connected host port can be unconfigured.
3. Unconfigure the fabric device.
4. Verify that the selected fabric device is unconfigured.
|
This procedure describes how to unconfigure all configured fabric devices that are attached to a fabric-connected host port.
2. Identify the fabric devices to be unconfigured.
Only devices on a fabric-connected host port can be unconfigured.
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.
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 can be time-consuming if the number of devices on c0 is large. |
5. Verify that all the devices on c0 are unconfigured.
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 Solaris FC and Storage Multipathing software devices.
2. Identify the port WWN of the fabric device to be unconfigured.
In this example, the c0::50020f2300006077 and c2::50020f2300006107 Ap_Ids represent different port WWNs for the same device associated with a Solaris FC and Storage Multipathing software device. The c0 and c2 host ports are enabled for use by the Solaris FC and Storage Multipathing 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 Solaris FC and Storage Multipathing software device.
Only devices on a fabric-connected host port can be unconfigured through the cfgadm -c unconfigure command.
5. Verify that the selected devices are unconfigured.
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 Solaris FC and Storage Multipathing software devices associated with the Ap_Ids c0::50020f2300006077 and c2::50020f2300006107 are no longer available to the host using the Solaris 10 OS. The following two Solaris FC and Storage Multipathing devices are removed from the host:
/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.
2. Identify the Ap_Id of the Solaris FC and Storage Multipathing software device to be unconfigured.
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 Solaris FC Storage Multipathing software 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.
4. Verify that the selected path c2::50020f2300006107 is unconfigured.
The Solaris FC and Storage Multipathing software devices associated with that Ap_Id are still available to a host using the Solaris 10 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 |
|
An Ap_Id on a fabric-connected host port is a path to the Solaris FC and Storage Multipathing software device.
When a Solaris FC and Storage Multipathing software device has multiple Ap_Ids connected to it, the device is still available to the host using the Solaris 10 OS after you unconfigure an Ap_Id. After you unconfigure the last Ap_Id, no additional paths remain and the Solaris FC and Storage Multipathing software device is unavailable to the host using the Solaris 10 OS. Only devices on a fabric-connected host port can be unconfigured.
2. Identify the devices to be unconfigured.
3. Unconfigure all of the configured devices on the selected port.
|
Note - This operation repeats the unconfigure command of an individual device for all devices on c2. This can be time-consuming if the number of devices on c2 is large. |
4. Verify that all devices on c2 are unconfigured.
Notice that the Occupant column lists c2 and all the devices attached to c2 as unconfigured.
| Solaris Fibre Channel and Storage Multipathing Administration Guide | 819-0139-12 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Detect Fabric Devices Visible on a Host