Configuring Storage Arrays in a Running Cluster

This section contains the procedures for configuring a storage array in a running cluster. Table 1-2 lists these procedures.

device id for nodename:/dev/rdsk/cXtYdZsN does not match physical 
device's id for ddecimalnumber, device may have been replaced.

Table 1-2 Task Map: Configuring a Fibre-Channel Storage Array 

How to Create and Map a LUN

Use this procedure to create a LUN from unassigned storage capacity.

Before You Begin

This procedure relies on the following prerequisites and assumptions.

• All nodes are booted in cluster mode and attached to the storage device.

• The storage device is installed and configured If you are using multipathing, it is configured as described in the installation procedure.

• If you are using Solaris I/O multipathing (MPxIO) for the Oracle Solaris 10 OS, previously called Sun StorEdge Traffic Manager in the Solaris 9 OS, verify that the paths to the storage device are functioning. To configure multipathing for the Oracle Solaris 10 OS, see the Solaris Fibre Channel Storage Configuration and Multipathing Support Guide.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.

To perform this procedure, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

1. Follow the instructions in your storage device's documentation to create and map the LUN.

   To allow multiple clusters and nonclustered systems to access the storage device, create initiator groups by using LUN filtering or masking.

2. If you are using multipathing, and if any devices that are associated with the LUN you created are at an unconfigured state, configure the STMS paths on each node that is connected to the storage device.

   To determine if any devices are at an unconfigured state, use the following command:

   # cfgadm -al | grep disk

   To configure the STMS paths on each node, use the following command:

   cfgadm -o force_update -c configure controllerinstance

   See the Solaris Fibre Channel Storage Configuration and Multipathing Support Guide for information on Solaris I/O multipathing.

3. On one node that is connected to the storage device, use the format command to label the new LUN.
4. From any node in the cluster, update the global device namespace.

   # cldevice populate

   ---

   Note - You might have a volume management daemon such as vold running on your node, and have a CD-ROM drive connected to the node. Under these conditions, a device busy error might be returned even if no disk is in the drive. This error is expected behavior. You can safely ignore this error message.

   ---

5. If you will manage this LUN with volume management software, use the appropriate Solaris Volume Manager or Veritas Volume Manager commands to update the list of devices on all nodes that are attached to the new volume that you created.

   For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.

See Also

• To configure a LUN as a quorum device, see Chapter 6, Administering Quorum, in Oracle Solaris Cluster System Administration Guide.

• To create a new resource or configure a running resource to use the new LUN, see Chapter 2, Administering Data Service Resources, in Oracle Solaris Cluster Data Services Planning and Administration Guide.

How to Unmap and Remove a LUN

Use this procedure to remove one or more LUNs. See the Sun StorEdge 3000 Family RAID Firmware 3.25 and 3.27 User's Guide for the latest information about LUN administration.

This procedure assumes that all nodes are booted in cluster mode and attached to the storage device.

---

Caution - When you delete a LUN, you remove all data on the LUN that you delete.

---

Before You Begin

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.

To perform this procedure, become superuser or assume a role that provides solaris.cluster.read and solaris.cluster.modify RBAC authorization.

1. Identify the LUN or LUNs that you will remove.

   Refer to your Solaris Volume Manager or Veritas Volume Manager documentation for the appropriate commands.

   Use the following pairs of commands.

   # luxadm probe
   # cldevice show 

2. If the LUN that you will remove is configured as a quorum device, choose and configure another device as the quorum device. Then remove the old quorum device.

   To determine whether the LUN is configured as a quorum device, use the following command.

   # clquorum show 

   For procedures about how to add and remove quorum devices, see Chapter 6, Administering Quorum, in Oracle Solaris Cluster System Administration Guide.

3. Remove the LUN from disksets or disk groups.

   Run the appropriate Solaris Volume Manager or Veritas Volume Manager commands to remove the LUN from any diskset or disk group. For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation for more information. See the following note for additional Veritas Volume Manager commands that are required.

   ---

   Note - LUNs that were managed by Veritas Volume Manager must be completely removed from Veritas Volume Manager control before you can delete them from the Oracle Solaris Cluster environment. After you delete the LUN from any disk group, use the following commands on both nodes to remove the LUN from Veritas Volume Manager control.

   # vxdisk offline cNtXdY
   # vxdisk rm cNtXdY

   ---

4. Unmap the LUN from both host channels.

   For the procedure on unmapping a LUN, see the Sun StorEdge 3000 Family RAID Firmware 3.25 and 3.27 User's Guide.

5. (Optional) Delete the logical drive.

   For more information, see Sun StorEdge 3000 Family RAID Firmware 3.25 and 3.27 User's Guide.

6. On both nodes, remove the paths to the LUN that you are deleting.

   # devfsadm -C

7. On both nodes, remove all obsolete device IDs.

   # cldevice clear