Sun Cluster 3.1 Software Installation Guide

How to Upgrade the Solaris Operating Environment

Perform this procedure on each node in the cluster to upgrade the Solaris operating environment to support Sun Cluster 3.1 software. However, if the cluster is already installed with a version of Solaris software supported by Sun Cluster 3.1 software and you do not intend to upgrade to a later compatible update of the Solaris software, you do not otherwise need to perform this procedure. Instead, go to How to Upgrade Cluster Software.


Note –

The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris 8 or Solaris 9 operating environment to support Sun Cluster 3.1 software. See “Supported Products” in Sun Cluster 3.1 Release Notes for more information.

Upgrade from Solaris 8 to Solaris 9 software is not supported in a Sun Cluster configuration.


  1. Become superuser on the cluster node to upgrade.

  2. Does your cluster use VxVM?

    • If no, go to Step 3.

    • If yes, follow upgrade procedures in your VxVM installation documentation, then return to Step 3 when the VxVM procedure says to upgrade Solaris software.


      Note –

      When instructed to boot into single-user mode, use the following command to reboot into single-user non-cluster mode:


      # boot -- -xs
      


  3. Determine whether the following Apache links already exist, and if so, whether the file names contain an uppercase K or S.


    /etc/rc0.d/K16apache        
    /etc/rc1.d/K16apache        
    /etc/rc2.d/K16apache        
    /etc/rc3.d/S50apache        
    /etc/rcS.d/K16apache

    If these links already exist and contain an uppercase K or S in the file name, no further action is necessary concerning these links. If these links do not exist, or if these links exist but contain lowercase k or s in the file name, you will move aside these links in Step 6.

  4. Upgrade the Solaris software.


    Note –

    Sun Cluster software does not support upgrade from Solaris 8 to Solaris 9 software.


    1. Do you intend to use the Maintenance Update method to upgrade the Solaris software?

      • If yes, go to Step b.

      • If no, make a record of all entries that are already commented out for later reference, then temporarily comment out all global device entries in the /etc/vfstab file.

        Do this to prevent the Solaris upgrade from attempting to mount the global devices. This step is not necessary if you use the Maintenance Update method to upgrade Solaris software.

    2. Follow upgrade instructions for the version of Solaris to which you will upgrade your cluster.


      Note –

      To reboot a node during Solaris software upgrade, always add the -x option to the command. This ensures that the node reboots into non-cluster mode. The following two commands boot a node into single-user non-cluster mode:


      # reboot -- -xs
      ok boot -xs
      


    3. Did you comment out the global device entries in the /etc/vfstab file in Step a?

      • If no, go to Step 6.

      • If yes, uncomment all global device entries that you commented out in the /a/etc/vfstab file.


        Note –

        Leave commented out all entries that were already commented out before you performed Step a.


  5. Did you perform VxVM procedures in Step 2 to upgrade Solaris software?

    • If no, go to Step 6.

    • If yes, perform the remaining steps in the VxVM upgrade procedure you used, but do not reboot except into non-cluster mode.


      # reboot -- -x
      

  6. If the Apache links in Step 3 did not already exist or they contained a lowercase k or s in the file names before you upgraded the Solaris software, move aside the restored Apache links.

    Use the following commands to rename the files with a lowercase k or s.


    # mv /a/etc/rc0.d/K16apache /a/etc/rc0.d/k16apache        
    # mv /a/etc/rc1.d/K16apache /a/etc/rc1.d/k16apache
    # mv /a/etc/rc2.d/K16apache /a/etc/rc2.d/k16apache
    # mv /a/etc/rc3.d/S50apache /a/etc/rc3.d/s50apache
    # mv /a/etc/rcS.d/K16apache /a/etc/rcS.d/k16apache
    

  7. Reboot the node in non-cluster mode, if you have not already done so.

    Include the double dashes (--) in the command.


    # reboot -- -x
    

  8. Install any Solaris software patches and hardware-related patches, and download any needed firmware contained in the hardware patches. For Solstice DiskSuite software, install any Solstice DiskSuite software patches.


    Note –

    Do not reboot after adding patches. You will reboot the node after you upgrade the Sun Cluster software.


    See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

  9. Upgrade to Sun Cluster 3.1 software.

    Go to How to Upgrade Cluster Software.