How to Replace a Host Adapter When Using Failover and Scalable Data Services Only

Before You Begin

This procedure relies on the following prerequisites and assumptions.

• You are not using Oracle Real Application Clusters. If you are using Oracle Real Application Clusters, follow the instructions in How to Replace a Host Adapter When Using Oracle Real Application Clusters Only or How to Replace a Host Adapter When Using Both Failover and Scalable Data Services and Oracle Real Application Clusters.

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

If your nodes are configured for dynamic reconfiguration, see the Sun Cluster system administration documentation, and skip steps that instruct you to shut down the node.

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. Determine the resource groups and device groups that are running on Node A.

   Record this information because you use this information later in 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. (Optional) If necessary, move all resource groups and device groups off Node A.

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

     # clnode evacuate NodeA

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

     # scswitch -S -h NodeA

4. If the storage device that is attached to the failed host adapter is configured as a quorum device, add a new quorum device on a storage device that is not affected by this procedure. Then remove the old quorum device.

   To determine whether the affected device contains a quorum device, use one of the following commands.

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

     # clquorum show

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

     # scstat -q

   To add and remove quorum devices, see the Sun Cluster system administration documentation.

5. Detach the Solaris Volume Manager submirrors or Veritas Volume Manager plexes on the storage array.

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

6. Record the details of disk groups and volumes affected by the failed host adapter.

   Record this information because you use it in Step 16 of this procedure to reattach submirrors on the storage array. To determine which submirrors or plexes are affected, see your Solaris Volume Manager or Veritas Volume Manager documentation.

7. If Node A is enabled with the Solaris DR feature, perform any DR-specific steps and skip to Step 10.

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

8. Shut down Node A.

   To shut down and power off a node, see your Sun Cluster system administration documentation.

9. Power off Node A.

10. Replace the failed host adapter.

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

11. If Node A is enabled with the Solaris DR feature, perform any DR-specific steps and skip to Step 15.

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

12. Power on Node A.

13. x86: Set the HBA ports to ensure that each array has a unique SCSI address.

    For instructions on setting SCSI initiator IDs in x86 based systems, see x86: How to Install a Storage Array in a New x86 Based Cluster.

14. Boot Node A 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.

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

16. Reattach the Solaris Volume Manager submirrors or Veritas Volume Manager plexes on the storage array.

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

17. (Optional) If you moved device groups off the node in Step 4 of the disconnect procedure, move all device groups back to the 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 devicegroup1[ devicegroup2 ...]

      -n NodeA

      The node to which you are restoring device groups.

      devicegroup1[ devicegroup2 ...]

      The device group or groups that you are restoring to the node.

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

      # scswitch -z -D devicegroup -h NodeA

18. (Optional) If you moved resource groups off the node in Step 4 of the disconnect procedure, move all 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 resourcegroup1[ resourcegroup2 ...]

      -n NodeA

      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.

      resourcegroup1[ resourcegroup2 ...]

      The resource group or groups that you are returning to the node or nodes.

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

      # scswitch -z -g resourcegroup -h NodeA

19. If you relocated a quorum device in Step 4, and if you want the cluster configured as it was before replacing the host adapter, relocate the quorum device function back to this storage array.

    To add and remove quorum devices, see your Sun Cluster system administration documentation.