Chapter 3 Maintaining a StorageTek Array

This chapter contains the procedures about how to maintain a StorageTek array. These procedures are specific to a Sun^TM Cluster environment.

This chapter contains the following procedures:

• How to Upgrade Storage Array Firmware

• How to Remove a Storage Array

For detailed information about storage array architecture, features, and configuration utilities, see the StorageTek documentation listed in Related Documentation.

FRUs That Do Not Require Sun Cluster Maintenance Procedures

In general, the following is a list of administrative tasks that require no cluster-specific procedures. See the base-product documentation for these procedures. Refer to your documentation for components not listed below.

Depending on your configuration type and the state of your cluster, a few of the following FRUs might require cluster-specific steps. Some FRUs include the DSP and the storage array.

• Adding a disk drive

• Replacing a storage array's chassis

• Replacing an Ethernet cable

• Replacing a power supply

• Replacing the power cable on the storage array

• Replacing a power and cooling unit (PCU)

• Replacing a controller

Maintaining Storage Arrays

This section contains the procedures about how to maintain a storage system in a running cluster. Table 3–1 lists these procedures.

Most storage arrays are maintained through common array management software. For example, see Sun StorageTek Common Array Manager Software.

How to Upgrade Storage Array Firmware

Use this procedure to upgrade storage array firmware in a running cluster. Storage array firmware includes controller firmware, unit interconnect card (UIC) firmware, EPROM firmware, and disk drive firmware.

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 cldevice check or 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 cldevice repair or scdidadm -R command for each affected device.

1. Stop all I/O to the storage arrays you are upgrading.

2. Apply the controller, disk drive, and loop-card firmware patches by using the arrays' GUI tools.

   For specific instructions, see your storage array's documentation.

3. Confirm that all storage arrays that you upgraded are visible to all nodes.

   # luxadm probe

4. Restart all I/O to the storage arrays.

   You stopped I/O to these storage arrays in Step 1.

How to Remove a Storage Array

Use this procedure to permanently remove a storage array from a running cluster.

During this procedure, you lose access to the data that resides on the storage array that you are removing. Back up the data before you proceed.

1. If you are using Sun Cluster Geographic Edition, you might need to back up all database tables, data services, and volumes that are associated with each partner group that is affected.

2. Remove references to the volumes that reside on the storage array that you are removing. For instructions, see How to Remove a Volume From a Device Group (VERITAS Volume Manager) in Sun Cluster System Administration Guide for Solaris OS.

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

3. If you have a Fibre Channel array, disconnect the cables that connected Node N to the FC switches in your storage array.

4. On all nodes, remove the obsolete Solaris links and device IDs.

   • If you are using Sun Cluster 3.2, use the following command:

     # devfsadm -C # cldevice clear

   • If you are using Sun Cluster 3.1, use the following command:

     # devfsadm -C # scdidadm -C

5. Repeat Step 3 and Step 4 for each node that is connected to the storage array.