test

Sun Cluster Software Installation Guide for Solaris OS

How to Upgrade the Solaris Operating Environment (Nonrolling)

Perform this procedure on each node in the cluster to upgrade the Solaris operating environment. If the cluster already runs on a version of the Solaris environment that supports Sun Cluster 3.1 4/04 software, this procedure is optional.

Note –

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

  1. Ensure that all steps in How to Prepare the Cluster for Upgrade (Nonrolling) are completed.

  2. Become superuser on the cluster node to upgrade.

  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 do contain an uppercase K or S in the file name, no further action is necessary for these links.

    • If these links do not exist, or if these links exist but instead contain a lowercase k or s in the file name, you move aside these links in Step 8.

  4. Comment out all entries for globally mounted file systems in the /etc/vfstab file.

    1. Make a record of all entries that are already commented out for later reference.

    2. Temporarily comment out all entries for globally mounted file systems in the /etc/vfstab file.

      Entries for globally mounted file systems contain the global mount option. Comment out these entries to prevent the Solaris upgrade from attempting to mount the global devices.

  5. Determine which procedure to follow to upgrade the Solaris operating environment.

    Volume Manager 

    Procedure to Use 

    Location of Instructions 

    Solstice DiskSuite/Solaris Volume Manager 

    Any Solaris upgrade method except the Live Upgrade method.

    Solaris 8 or Solaris 9 installation documentation 

    VERITAS Volume Manager 

    “Upgrading VxVM and Solaris” 

    VERITAS Volume Manager installation documentation 

    Note –

    If your cluster has VxVM installed, you must reinstall the existing VxVM software or upgrade to the Solaris 9 version of VxVM software as part of the Solaris upgrade process.

  6. Upgrade the Solaris software, following the procedure that you selected in Step 5.

    Note the following special instructions:

    • Do not perform the final reboot instruction in the Solaris software upgrade. Instead, return to this procedure to perform Step 7 and Step 8, then reboot into noncluster mode in Step 9 to complete Solaris software upgrade.

    • When you are instructed to reboot a node during the upgrade process, always add the -x option to the command.

      The -x option ensures that the node reboots into noncluster mode. For example, either of the following two commands boot a node into single-user noncluster mode:


      # reboot -- -xs
ok boot -xs

  7. In the /a/etc/vfstab file, uncomment those entries for globally mounted file systems that you commented out in Step 4.

  8. Move aside restored Apache links if either of the following conditions was true before you upgraded the Solaris software:

    • The Apache links listed in Step 3 did not exist.

    • The Apache links listed in Step 3 existed and contained a lowercase k or s in the file names.

    To move aside restored Apache links, which contain an uppercase K or S in the name, 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

  9. Reboot the node into noncluster mode.

    Include the double dashes (--) in the following command:


    # reboot -- -x

  10. If your cluster runs VxVM, perform the remaining steps in the procedure “Upgrading VxVM and Solaris” to reinstall or upgrade VxVM.

    Note the following special instructions:

    • If you see a message similar to the following, type the root password to continue upgrade processing. Do not run the fsck command nor type Ctrl-D.


      WARNING - Unable to repair the /global/.devices/node@1 filesystem. 
Run fsck manually (fsck -F ufs /dev/vx/rdsk/rootdisk_13vol). Exit the 
shell when done to continue the boot process.

Type control-d to proceed with normal startup,
(or give root password for system maintenance):  Type the root password

    • When the VxVM procedures instruct you to perform a final reconfiguration reboot by using the -r option, reboot into noncluster mode by using the -x option instead.


      # reboot -- -x

    • After VxVM upgrade is complete, verify the entries in the /etc/vfstab file. If any of the entries that you uncommented in Step 7 were commented out, make those entries uncommented again.

  11. Install any required Solaris software patches and hardware-related patches, and download any needed firmware that is contained in the hardware patches.

    For Solstice DiskSuite software (Solaris 8), also install any Solstice DiskSuite software patches.

    Note –

    Do not reboot after you add patches. Wait to reboot the node until 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.

  12. Upgrade to Sun Cluster 3.1 4/04 software.

    Go to How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling).

    Note –

    To complete upgrade from Solaris 8 to Solaris 9 software, you must also upgrade to the Solaris 9 version of Sun Cluster 3.1 4/04 software, even if the cluster already runs on Sun Cluster 3.1 4/04 software.