Chapter 3 Maintaining a Sun StorEdge 9900 Storage Array

This chapter contains a limited set of procedures about how to maintain a storage array. Contact your service provider to add, remove, or replace any storage array components.

This chapter contains the following procedures:

• How to Remove a Storage Array

• How to Replace a Host Adapter

• How to Replace an FC Switch or Storage Array-to-Switch Component

• Replacing a Node-to-Switch Component

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.

Maintaining Storage Arrays

This section contains the procedures for maintaining a storage system in a running cluster. Table 3–1 lists these procedures.

How to Remove a Storage Array

Use this procedure to permanently remove a storage array. This procedure provides the flexibility to remove the host adapters from the nodes that are attached to the storage array that you are removing.

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

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

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

Steps

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

2. Determine if the storage array that you plan to remove is configured as a quorum device.

   # scstat -q

   • If the storage array is not a quorum device, proceed to Step 3.

   • If the storage array is configured as a quorum device, choose and configure another device to be the new quorum device. Then remove the old quorum device.

     To add and remove a quorum device in your configuration, see your Sun Cluster system administration documentation.

3. If necessary, detach the submirrors from the storage array that you are removing in order to stop all I/O activity to the storage array.

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

4. Run the appropriate Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager commands to remove the references to the logical volume(s) from any diskset or disk group.

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

5. Are your nodes enabled with the Solaris dynamic reconfiguration (DR) feature?

   • If yes, disconnect the fiber-optic cables and, if desired, remove the host adapters from both nodes. Then perform Step 22 on each node that was connected to the storage array

     For the procedure about how to remove a host adapter, see the documentation that shipped with your host adapter or updated information on the manufacturer's web site.

   • If no, proceed to Step 6.

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

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

   # scstat

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

7. Do you want to remove any multipathing software?

   • If no, proceed to Step 8.

   • If yes, remove the multipathing software packages.

8. Stop the Sun Cluster software on Node A, and then shut down Node A.

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

9. Disconnect the fiber-optic cable between the storage array and Node A.

10. Do you want to remove the host adapter from Node A?

    • If no, skip to Step 13.

    • If yes, power off Node A.

11. Remove the host adapter from Node A.

    For the procedure about how to remove host adapters, see the documentation that shipped with your host adapter or updated information on the manufacturer's web site.

12. Without enabling the node to boot, power on Node A.

    For more information, see the documentation that shipped with your server.

13. Boot Node A into cluster mode.

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

14. On Node A, update the device namespace.

    # devfsadm -C

15. Stop the Sun Cluster software on Node B, and then shut down Node B.

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

16. Disconnect the fiber-optic cable between the storage array and Node B.

17. Do you want to remove the host adapter from Node B?

    • If no, skip to Step 20.

    • If yes, power off Node B.

18. Remove the host adapter from Node B.

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

19. Without enabling the node to boot, power on Node B.

    For more information, see the documentation that shipped with your server.

20. Boot Node B into cluster mode.

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

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

22. On Node B, update the device namespace.

    # devfsadm -C

23. Repeat Step 15 through Step 22 for each additional node that connects to the storage array.

24. From one node, remove device ID references to the storage array that was removed.

    # scdidadm -C

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.

How to Replace an FC Switch or Storage Array-to-Switch Component

Use this procedure to replace an FC switch, or the following storage array-to-switch components in a running cluster.

• Fiber-optic cable that connects an FC switch to a storage array

• GBIC on an FC switch, connecting to a storage array

• FC switch

Step

Replace the component by using the following references.

• For the procedure about how to replace a fiber-optic cable between a storage array and an FC switch, see the documentation that shipped with your switch hardware.

• For the procedure about how to replace a GBIC on an FC switch, see the documentation that shipped with your switch hardware.

• For the procedure about how to replace an SFP on the storage array, contract your service provider.

• For the procedure about how to replace an FC switch, see the documentation that shipped with your switch hardware.

  ---

  Note –

  If you are replacing an FC switch and you intend to save the switch configuration for restoration to the replacement switch, do not connect the cables to the replacement switch until after you recall the Fabric configuration to the replacement switch. For more information about how to save and recall switch configurations see the documentation that shipped with your switch hardware.

  ---

  ---

  Note –

  Before you replace an FC switch, be sure that the probe_timeout parameter of your data service software is set to more than 90 seconds. Increasing the value of the probe_timeout parameter to more than 90 seconds avoids unnecessary resource group restarts when one of the FC switches is powered off.

  ---

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