Maintaining Storage Arrays

This section contains the procedures for maintaining a storage array in a Sun Cluster environment. Maintenance tasks are listed in Table 1–3 contain cluster-specific tasks. Tasks that are not cluster-specific are referenced in a list following the table.

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.

StorEdge 3510 and 3511 FC RAID Array FRUs

The following is a list of administrative tasks that require no cluster-specific procedures. See the Sun StorEdge 3000 Family Installation, Operation, and Service Manual for the following procedures.

• Replacing an Ethernet cable.

• Replacing the power cable on the storage array.

• Replacing a Power and Cooling Unit (PCU).

• Replacing the expansion unit-to-RAID storage array interconnect components such as SFPs and fiber-optic cables.

How to Remove a Storage Array From a Running Cluster

Use this procedure to permanently remove storage arrays and their submirrors from a running cluster.

If you need to remove a storage array from more than two nodes, repeat Step 6 to Step 11 for each additional node that connects to the storage array.

During this procedure, you lose access to the data that resides on each storage array that you are removing.

Steps

1. Does the storage array you are removing contain any quorum devices?

   # scstat -q

   • If no, proceed to Step 2.

   • If yes, choose another disk drive to configure as the quorum device. Then remove the old quorum device.

     For procedures on adding and removing quorum devices, see the Sun Cluster system administration documentation.

2. If necessary, back up all database tables, data services, and drives associated with each storage array that you are removing.

3. Determine the resource groups and device groups that are running on all nodes.

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

   # scstat

4. If necessary, run the appropriate Solstice DiskSuite or VERITAS Volume Manager commands to detach the submirrors from each storage array that you are removing to stop all I/O activity to the storage array.

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

5. Run the appropriate volume manager commands to remove references to each LUN that belongs to the storage array that you are removing.

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

6. Shut down the node.

   For the full procedure on shutting down and powering off a node, see the Sun Cluster system administration documentation.

7. If necessary, disconnect the storage arrays from the nodes or the FC switches.

8. Is the storage array that you are removing the last storage array connected to the node?

   • If no, skip to Step 11.

   • If yes, disconnect the fiber-optic cable between the node and the FC switch that was connected to this storage array.

9. Do you want to remove the host adapters from the node?

   • If no, skip to Step 11.

   • If yes, power off the node.

10. Remove the host adapters from the node.

    For the procedure on removing host adapters, see the documentation that shipped with your host adapter and nodes.

11. Boot the node into cluster mode.

    For more information on booting nodes, see the Sun Cluster system administration documentation.

12. Repeat steps Step 6 to Step 11 on each additional node that you need to disconnect from the storage array.

13. On all cluster nodes, remove the paths to the devices that you are deleting.

    # devfsadm -C

14. On all cluster nodes, remove all obsolete device IDs.

    # scdidadm -C

15. Return the resource groups and device groups that you identified in Step 3 to the original nodes.

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

See Also

To prepare the storage array for later use, unmap and delete all LUNs and logical drives. See How to Unmap and Remove a LUN for information about LUN removal. For more information about removing logical drives, see the Sun StorEdge 3000 Family Installation, Operation, and Service Manual.

How to Upgrade Storage Array Firmware

Use this procedure to upgrade storage array firmware in a running cluster.

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.

Steps

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

2. Download the firmware to the storage arrays.

   Refer to the Sun StorEdge 3000 Family RAID Firmware 3.25 and 3.27 User's Guide and to any patch readme files for more information.

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 Replace a Disk Drive

Use this procedure to replace a failed disk drive in a storage array in a running cluster.

Steps

1. Did the failed disk drive affect the storage array LUN's availability?

   • If no, proceed to Step 3.

   • If yes, use volume manager commands to detach the submirror or plex.

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

2. Is the LUN (in Step 1) a quorum device?

   # scstat -q

   • If no, proceed to Step 3.

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

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

3. Replace the failed disk drive.

   For instructions, refer to the Sun StorEdge 3000 Family Installation, Operation, and Service Manual.

4. (Optional) If you reconfigured a quorum device in Step 1, restore the original quorum configuration.

   For the procedure about how to add a quorum device, see your Sun Cluster system administration documentation.

5. Did you detach a submirror or plex in Step 1?

   • If no, you are finished with this procedure.

   • If yes, use volume manager commands to reattach the submirror or plex.

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

How to Replace a Host Adapter

Use this procedure to replace a failed host adapter in a running cluster. This procedure defines Node A as the node with the failed host adapter that you are replacing.

Before You Begin

This procedure relies on the following prerequisites and assumptions.

• Except for the failed host adapter, your cluster is operational and all nodes are powered on.

• Your nodes are not configured with dynamic reconfiguration functionality.

  If your nodes are configured for dynamic reconfiguration and you are using two entirely separate hardware paths to your shared data, see the Sun Cluster Hardware Administration Manual for Solaris OS and skip steps that instruct you to shut down the cluster.

  You cannot replace a single, dual-port HBA that has quorum configured on that storage path by using DR. Follow all steps in the procedure. For the details on the risks and limitations of this configuration, see Configuring Cluster Nodes With a Single, Dual-Port HBA in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS.

  Exceptions to this restriction include three-node or larger cluster configurations where no storage device has a quorum device configured.

Steps

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

   Record this information because you use this information in Step 9 of this procedure to return resource groups and device groups to Node A.

   # scstat

2. Move all resource groups and device groups off Node A.

   # scswitch -S -h nodename

3. Shut down Node A.

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

4. Power off Node A.

5. Replace the failed host adapter.

   For the procedure about how to remove and add host adapters, see the documentation that shipped with your nodes.

6. Do you need to upgrade the node's host adapter firmware?

   • If yes, boot Node A into noncluster mode. Proceed to Step 7.

     For more information about how to boot nodes, see your Sun Cluster system administration documentation.

   • If no, proceed to Step 8.

7. Upgrade the host adapter firmware on Node A.

   PatchPro is a patch-management tool that eases the selection and download of patches required for installation or maintenance of Sun Cluster software. PatchPro provides an Interactive Mode tool especially for Sun Cluster. The Interactive Tool makes the installation of patches easier. PatchPro's Expert Mode tool helps you to maintain your configuration with the latest set of patches. Expert Mode is especially useful for obtaining all of the latest patches, not just the high availability and security patches.

   To access the PatchPro tool for Sun Cluster software, go to http://www.sun.com/PatchPro/, click Sun Cluster, then choose either Interactive Mode or Expert Mode. Follow the instructions in the PatchPro tool to describe your cluster configuration and download the patches.

   For third-party firmware patches, see the SunSolve^SM Online site at http://sunsolve.ebay.sun.com.

8. Boot Node A into cluster mode.

   For more information about how to boot nodes, see your Sun Cluster system administration documentation.

9. Return the resource groups and device groups you identified in Step 1 to Node A.

   # 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.

Replacing a Node-to-Switch Component

Use this procedure to replace a node-to-switch component that has failed or that you suspect might be contributing to a problem.

Node-to-switch components that are covered by this procedure include the following components:

• Node-to-switch fiber-optic cables

• Gigabit interface converters (GBICs) or small form-factor pluggables (SFPs) on an FC switch

• FC switches

For the procedure about how to replace a host adapter, see How to Replace a Host Adapter.

This procedure defines Node A as the node that is connected to the node-to-switch component that you are replacing. This procedure assumes that, except for the component you are replacing, your cluster is operational.

Ensure that you are following the appropriate instructions:

• If your cluster uses multipathing, see How to Replace a Node-to-Switch Component in a Cluster That Uses Multipathing.

• If your cluster does not use multipathing, see How to Replace a Node-to-Switch Component in a Cluster Without Multipathing.

How to Replace a Node-to-Switch Component in a Cluster That Uses Multipathing

Steps

1. Is your configuration active-passive?

   If yes, and the active path is the path that needs a component replaced, make that path passive.

2. Replace the component.

   Refer to your hardware documentation for any component-specific instructions.

3. (Optional) If your configuration is active-passive and you changed your configuration in Step 1, switch your original data path back to active.

How to Replace a Node-to-Switch Component in a Cluster Without Multipathing

Steps

1. Check if the physical data path failed.

   If no, proceed to Step 2.

   If yes:

   1. Replace the component.

      Refer to your hardware documentation for any component-specific instructions.

   2. Fix the volume manager error that was caused by the failed data path.

   3. (Optional) If necessary, return resource groups and device groups to this node.

   You have completed this procedure.

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

   # scstat

3. Move all resource groups and device groups to another node.

   # scswitch -s -h from-node

4. Replace the node-to-switch component.

   Refer to your hardware documentation for any component-specific instructions.

5. (Optional) If necessary, return the resource groups and device groups that you identified in Step 2 to Node A.

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

How to Replace a Chassis in a Running Cluster

Use this procedure to replace a storage array chassis in a running cluster. This procedure assumes that you want to retain all FRUs other than the chassis and the backplane.

Steps

1. To stop all I/O activity to this storage array, detach the submirrors that are connected to the chassis you are replacing.

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

2. Is this storage array made redundant by host-based mirroring?

   • If yes, proceed to Step 3.

   • If no, shut down the cluster.

     For the full procedure on shutting down a cluster, see the Sun Cluster system administration documentation.

3. Replace the chassis and backplane.

   For the procedure on replacing a chassis, see the Sun StorEdge 3000 Family Installation, Operation, and Service Manual.

4. Did you shut down the cluster in Step 2?

   • If no, proceed to Step 5.

   • If yes, boot it back into cluster mode.

     For the full procedure on booting a cluster, see the Sun Cluster system administration documentation.

5. Reattach the submirrors that you detached in Step 1 to resynchronize them.

   ---

   Caution –

   The world wide numbers (WWNs) might change as a result of this procedure. If the WWNs change, and you must reconfigure your volume manager software to recognize the new WWNs.

   ---

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