How to Replace a Host Adapter When Using a Single, Dual-Port HBA to Provide Both Paths to Shared Data

Before You Begin

This procedure relies on the following prerequisites and assumptions.

• You are using a single, dual-port HBA to provide the redundant paths to your shared data.

  For an explanation of the limitations and risks of using this configuration, see Configuring Cluster Nodes With a Single, Dual-Port HBA in Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS.

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

• Your nodes are not configured for dynamic reconfiguration.

  You cannot use dynamic reconfiguration for this procedure when using a single HBA.

• Node A is the node with the failed host adapter.

This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS.

1. Become superuser or assume a role that provides solaris.cluster.read and solaris.cluster.modify RBAC authorization.

2. If you are using scalable and failover services, determine the resource groups and device groups that are running on Node A.

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

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

     # clresourcegroup status -n NodeA # cldevicegroup status -n NodeA

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

     # scstat

3. Record the details of metadevices that are affected by the failed host adapter.

4. SPARC: If you are using Oracle Real Application Clusters, shut down all RAC instances running in your cluster.

   To shut down and restart an Oracle instance in the RAC environment, refer to the Oracle 9iRAC Administration Guide.

5. Shut down the cluster.

   To shut down a cluster, see your Sun Cluster system administration documentation.

6. Power off Node A.

7. Replace the failed host adapter.

   To remove and add host adapters, see the documentation that shipped with your nodes.

8. Power on Node A.

9. Boot all nodes into cluster mode.

   For the procedure about booting cluster nodes, see Chapter 3, Shutting Down and Booting a Cluster, in Sun Cluster System Administration Guide for Solaris OS.

10. If necessary, upgrade the host adapter firmware on Node A.

    If you use the Solaris 8, Solaris 9, or Solaris 10 Operating System, Sun Connection Update Manager keeps you informed of the latest versions of patches and features. Using notifications and intelligent needs-based updating, Sun Connection helps improve operational efficiency and ensures that you have the latest software patches for your Sun software.

    You can download the Sun Connection Update Manager product for free by going to http://www.sun.com/download/products.xml?id=4457d96d.

    Additional information for using the Sun patch management tools is provided in Solaris Administration Guide: Basic Administration at http://docs.sun.com. Refer to the version of this manual for the Solaris OS release that you have installed.

    If you must apply a patch when a node is in noncluster mode, you can apply it in a rolling fashion, one node at a time, unless instructions for a patch require that you shut down the entire cluster. Follow the procedures in How to Apply a Rebooting Patch (Node) in Sun Cluster System Administration Guide for Solaris OS to prepare the node and to boot it in noncluster mode. For ease of installation, consider applying all patches at the same time. That is, apply all patches to the node that you place in noncluster mode.

    For a list of patches that affect Sun Cluster, see the Sun Cluster Wiki Patch Klatch.

    For required firmware, see the Sun System Handbook.

11. Perform any volume management maintenance procedures that are necessary to fix any metadevices affected by this procedure.

    For more information, see your volume manager software documentation.

12. (Optional) If necessary, move the device groups back to the original node.

    Perform the following step for each device group you want to return to the original node.

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

      # cldevicegroup switch -n NodeA devicegroup

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

      # scswitch -z -D devicegroup -h NodeA

13. (Optional) If necessary, move the resource groups back to the node.

    Perform the following step for each resource group you want to return to the original node.

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

      # clresourcegroup switch -n NodeA resourcegroup

      nodename

      For failover resource groups, the node to which the groups are returned. For scalable resource groups, the node list to which the groups are returned.

      resourcegroup

      The resource group that is returned to the node or nodes.

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

      # scswitch -z -g resourcegroup -h NodeA

14. (Optional) Bring all Oracle Real Application Clusters instance online.

    To shut down and restart an Oracle instance in the RAC environment, refer to the Oracle 9iRAC Administration Guide.