Patching Sun Cluster Software and Firmware

This chapter provides the procedures for adding and removing patches for a Sun Cluster configuration.

This is a list of the procedures in this chapter.

• How to Apply a Rebooting Patch (Node)

• How to Apply a Rebooting Patch (Cluster and Firmware)

• How to Apply a Non-Rebooting Sun Cluster Patch

• How to Remove a Sun Cluster Patch

Patching Sun Cluster Overview

Due to the nature of a cluster, all cluster member nodes must be at the same patch level for proper cluster operation. When patching a node with a Sun Cluster patch, you might need to temporarily remove a node from cluster membership or stop the entire cluster before installing the patch. This section describes these steps.

Before applying a Sun Cluster patch, check the Sun Cluster web page for any special instructions; for the current URL, see the Sun Cluster Release Notes for Solaris OS or contact Enterprise Services. If there aren't any special instructions, check the patch's README file.

Note - For Sun Cluster patches, always defer to the patch's README file for instructions that supersede procedures in this chapter.

Patch installation on all cluster nodes falls into one of the following scenarios:

• Rebooting patch (node)--A node must be booted to single-user mode, using the command boot -sx or b -sx, before the patch can be applied, then rebooted to join the cluster. In doing so, you need to put the node into a "quiet" state by first switching any resource groups or disk device groups from the node to be patched to another cluster member. Also, apply the patch to one cluster node at a time to avoid bringing down the entire cluster.

  The cluster itself remains available during this type of patch application, even though individual nodes are temporarily shut down. A patched node is able to rejoin a cluster as a member node even though other nodes are not yet at the same patch level.

• Rebooting patch (cluster and firmware)--The cluster must be shut down and each node must be booted to single-user mode, using the command boot -sx or b -sx, to apply the software or firmware patch. Then, reboot the nodes to rejoin the cluster. For this type of patch, the cluster is unavailable during patch application.

• Non-rebooting patch--A node does not have to be in a "quiet" state (it can still be mastering resource groups or device groups), nor does it have to be shut down or rebooted when applying the patch. However, you should still apply the patch to one node at a time and verify that the patch works before patching another node.

Note - Underlying cluster protocols do not change due to a patch.

You use the patchadd command to apply a patch to the cluster, and patchrm to remove a patch (when possible).

Sun Cluster Patch Tips

Use the following tips to help you administer Sun Cluster patches more efficiently:

• Refer to the Sun Cluster website for any special instructions associated with the patch or firmware update. For the current URL, see the Sun Cluster Release Notes for Solaris OS or contact Enterprise Services.

• Always read the patch README file before applying the patch.

• Apply all patches (required and recommended) before running the cluster in a production environment.

• Check the hardware firmware levels and install any required firmware updates that may be needed.

• All nodes acting as cluster members must have the same patches.

• Keep cluster subsystem patches up to date. This includes volume management, storage device firmware, cluster transport, and so forth.

• Review patch reports regularly, such as once a quarter, and patch a Sun Cluster configuration using the recommended patch suite.

• Apply selective patches as recommended by Enterprise Services.

• Test failover after major patch updates; be prepared to back out the patch if cluster operation is degraded or impaired.

Patching Sun Cluster

Table 8-1 Task Map: Patching the Cluster

How to Apply a Rebooting Patch (Node)

Apply the patch to one node in the cluster at a time to keep the cluster itself operational during the patch process. With this procedure, you must first shut down the node and boot it to single-user mode using the boot -sx or b -sxcommand, before applying the patch.

1. Before applying the patch, check the Sun Cluster product web page for any special pre- or post-installation instructions.

2. Become superuser on the node to which you are applying the patch.

3. List the resource groups and device groups on the node being patched.

   # scrgadm -pv # scstat

   
   

4. Switch all resource groups, resources, and device groups from the node being patched to other cluster members.

   # scswitch -S -h node[,...]

   
   

   -S	Evacuates all device groups and resource groups from the specified node.
   -h node[,...]	Specifies the node from which you are switching the resource groups and device groups.

5. Shut down the node.

   # shutdown -g0 [-y] [-i0]

   
   

6. Boot the node in non-cluster, single-user mode.

   • SPARC:

     ok boot -sx

     
     

   • x86:

     <<< Current Boot Parameters >>> Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/ sd@0,0:a Boot args: Type b [file-name] [boot-flags] <ENTER> to boot with options or i <ENTER> to enter boot interpreter or <ENTER> to boot with defaults <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b -sx

     
     

7. Apply the patch.

   # patchadd -M patch-dir patch-id

   
   

   patch-dir	Specifies the directory location of the patch.
   patch-id	Specifies the patch number of a given patch.

   ---

   Note - Always defer to the instructions in the patch directory that supersede procedures in this chapter.

   ---

8. Reboot the node into the cluster.

   # reboot

   
   

9. Verify that the patch has been installed successfully.

   # showrev -p | grep patch-id

   
   

10. Verify that the patch works, and that the node and cluster are operating normally.

11. Repeat Step 2 through Step 10 for all remaining cluster nodes.

12. Switch resource groups, resources, and device groups as needed.

    After rebooting all the nodes, the last node rebooted will not have the resource groups and device groups online.

    # scswitch -z -D device-group[,...]-h node[,...] # scswitch -z -g resource-group[,...]-h nod[,...]e

    
    

    -z	Specifies the change in mastery of a resource group or device group.
    -h node[,...]	Specifies the nodes to which you are switching the resource groups and device groups.
    -D	Switches the specified device groups to the nodes identified by the -h option.
    -g	Switches the specified resource groups to the nodes identified by the -h option. If -h is not specified, the resource groups are taken offline.