Configuring Storage Arrays

This section contains the procedures about how to configure a storage array in a Sun Cluster environment. The following table lists these procedures. For configuration tasks that are not cluster-specific, see the documentation that shipped with your 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.

How to Add a Logical Volume

Use this procedure to add a logical volume to a cluster. This procedure assumes that your service provider created your logical volume. This procedure also assumes that all nodes are booted and are attached to the storage array.

Steps

1. On all nodes, update the /devices and /dev entries.

   # devfsadm

2. On each node connected to the storage array, verify that the same set of LUNs is visible to the expected controllers.

   # format

   See the format command man page for more information about how to use the command.

3. Determine if you are running VERITAS Volume Manager.

   • If not, proceed to Step 4

   • If you are running VERITAS Volume Manager, update the list of devices on all nodes that are attached to the logical volume that you created in Step 2.

     See your VERITAS Volume Manager documentation for information about how to use the vxdctl enable command. Use this command to update new devices (volumes) in your VERITAS Volume Manager list of devices.

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

   # scgdevs

   If a volume management daemon such as vold is running on your node, and you have a CD-ROM drive that is connected to the node, a device busy error might be returned even if no disk is in the drive. This error is expected behavior.

See Also

To create a new resource or reconfigure a running resource to use the new logical volume, see your Sun Cluster data services collection.

How to Remove a Logical Volume

Use this procedure to remove a logical volume. This procedure assumes all nodes are booted and are connected to the storage array. This storage array hosts the logical volume that you are removing.

This procedure defines Node A as the node with which you begin working. Node B is the remaining node.

If you need to remove a storage array from more than two nodes, repeat Step 9 through Step 11 for each additional node. Each node connects to the logical volume.

This procedure destroys all data on the logical volume that you are removing.

Steps

1. If necessary, back up all data. Migrate all resource groups and disk device groups to another node.

2. Is the logical volume that you plan to remove configured as a quorum device?

   # scstat -q

   • If no, proceed to Step 3.

   • If yes, choose and configure another device to be the new quorum device. Then remove the old quorum device.

     For procedures about how to add and remove quorum devices, see your Sun Cluster system administration documentation.

3. Run the appropriate Solstice DiskSuite/Solaris Volume Manager commands or VERITAS Volume Manager commands to remove the reference to the logical volume from any diskset or disk group.

   For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.

4. If the cluster is running VERITAS Volume Manager, update the list of devices on all nodes. These nodes are attached to the logical volume that you are removing.

   See your VERITAS Volume Manager documentation for information about how to use the vxdisk rm command to remove devices (volumes) in your VERITAS Volume Manager device list.

5. Remove the logical volume.

   Contact your service provider to remove the logical volume.

6. Determine the resource groups and device groups that are running on Node A and Node B.

   Record this information because you use this information in Step 11 of this procedure to return resource groups and device groups to these nodes.

   # scstat

7. Shut down and reboot Node A by using the shutdown command with the -i6 option.

   For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.

8. On Node A, update the /devices and /dev entries.

   # devfsadm -C # scdidadm -C

9. Shut down and reboot Node B by using the shutdown command with the -i6 option.

   For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.

10. On Node B, update the /devices and /dev entries.

    # devfsadm -C # scdidadm -C

11. Return the resource groups and device groups that you identified in Step 6 to Node B.

    # scswitch -z -g resource-group -h nodename # scswitch -z -D device-group-name -h nodename

    For more information, see your Sun Cluster system administration documentation.

12. Repeat Step 9 through Step 11 for each additional node that connects to the logical volume.

See Also

To create a logical volume, see How to Add a Logical Volume.