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.

Before installing or configuring your cluster, see “Known Problems” in the Sun Cluster 3.0-3.1 Release Notes Supplement for important information about the StorEdge 3510 and 3511 FC storage array.

When you upgrade firmware on a storage device or on an enclosure, redefine the stripe size of a LUN, or perform other LUN operations, a device ID might change unexpectedly. When you perform a check of the device ID configuration by running the scdidadm -c command, the following error message appears on your console if the device ID changed unexpectedly.

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

To fix device IDs that report this error, run the scdidadm -R command for each affected device.

Logical volumes are not supported in a Sun Cluster environment. Use logical drives as an alternative.

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 Sun StorEdge Traffic Manager, it is installed and configured and the path between Traffic Manager and the storage device is functioning.

Steps

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. Are you using multipathing?

   • If yes, proceed to Step 3.

   • If no, skip to Step 4.

3. Are any devices that are associated with the LUN you created at an unconfigured state?

   # cfgadm -al | grep disk

   • If no, proceed to Step 4.

   • If yes, configure the STMS paths on each node that is connected to the storage device.

     cfgadm -o force_update -c configure controllerinstance

     For the procedure about how to configure STMS paths, see the Sun StorEdge Traffic Manager Installation and Configuration Guide.

4. On one node that is connected to the storage device, use the format command to label the new LUN.

5. From any node in the cluster, update the global device namespace.

   # scgdevs

   ---

   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.

   ---

6. If you will manage this LUN with volume management software, use the appropriate Solstice DiskSuite/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 Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.

See Also

• To configure a LUN as a quorum device, see Chapter 5, Administering Quorum, in Sun Cluster System Administration Guide for Solaris OS.

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

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.

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

Steps

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

   Refer to your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation for the appropriate commands. For example:

   # luxadm probe # scdidadm -L pathname

2. Is the LUN that you will remove a quorum device?

   # scstat -q

   • If no, proceed to Step 3.

   • If yes, choose and configure another device as the quorum device. Then remove the old quorum device.

     For procedures about how to add and remove quorum devices, see Chapter 5, Administering Quorum, in Sun Cluster System Administration Guide for Solaris OS.

3. Remove the LUN from disksets or disk groups.

   Run the appropriate Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager commands to remove the LUN from any diskset or disk group. For more information, see your Solstice DiskSuite/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 Sun 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.

   # scdidadm -C