test

Sun Cluster Software Installation Guide for Solaris OS

ProcedureHow to Perform a Nonrolling Upgrade of the Solaris OS

Perform this procedure on each node in the cluster to upgrade the Solaris OS. If the cluster already runs on a version of the Solaris OS that supports Sun Cluster 3.1 8/05 software, further upgrade of the Solaris OS is optional. If you do not intend to upgrade the Solaris OS, proceed to How to Perform a Nonrolling Upgrade of Sun Cluster 3.1 8/05 Software.

Caution – Caution –

Sun Cluster 3.1 8/05 software does not support upgrade from the Solaris 9 OS to the original release of the Solaris 10 OS, which was distributed in March 2005. You must upgrade to at least the Solaris 10 10/05 release or compatible.

Before You Begin

Perform the following tasks:

Steps

  1. Become superuser on the cluster node to upgrade.

  2. (Optional) SPARC: Upgrade VxFS.

    Follow procedures that are provided in your VxFS documentation.

  3. Determine whether the following Apache run control scripts exist and are enabled or disabled:


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

    Some applications, such as Sun Cluster HA for Apache, require that Apache run control scripts be disabled.

    • If these scripts exist and contain an uppercase K or S in the file name, the scripts are enabled. No further action is necessary for these scripts.

    • If these scripts do not exist, in Step 8 you must ensure that any Apache run control scripts that are installed during the Solaris OS upgrade are disabled.

    • If these scripts exist but the file names contain a lowercase k or s, the scripts are disabled. In Step 8 you must ensure that any Apache run control scripts that are installed during the Solaris OS upgrade are disabled.

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

    1. For later reference, make a record of all entries that are already commented out.

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

    Volume Manager 

    Procedure 

    Location of Instructions 

    Solstice DiskSuite or Solaris Volume Manager 

    Any Solaris upgrade method except the Live Upgrade method

    Solaris installation documentation 

    SPARC: 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.

    Make the following changes to the procedures that you use:

    • When you are instructed to reboot a node during the upgrade process, always reboot into noncluster mode.

      • For the boot and reboot commands, 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:

        • On SPARC based systems, perform either of the following commands:


          # reboot -- -xs
or
ok boot -xs

        • On x86 based systems, perform either of the following commands:


          # reboot -- -xs
or
...
                      <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ata@1/cmdk@0,0:b
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 -xs

      • If the instruction says to run the init S command, use the reboot -- -xs command instead.

    • Do not perform the final reboot instruction in the Solaris software upgrade. Instead, do the following:

      1. Return to this procedure to perform Step 7 and Step 8.

      2. Reboot into noncluster mode in Step 9 to complete Solaris software upgrade.

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

  8. If Apache run control scripts were disabled or did not exist before you upgraded the Solaris OS, ensure that any scripts that were installed during Solaris upgrade are disabled.

    To disable Apache run control scripts, 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

    Alternatively, you can rename the scripts to be consistent with your normal administration practices.

  9. Reboot the node into noncluster mode.

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


    # reboot -- -x

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

    Make the following changes to the procedure:

    • After VxVM upgrade is complete but before you reboot, 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.

    • When the VxVM procedures instruct you to perform a final reconfiguration reboot, do not use the -r option alone. Instead, reboot into noncluster mode by using the -rx options.


      # reboot -- -rx
    Note –

    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

  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 8/05 Release Notes for Solaris OS for the location of patches and installation instructions.

Next Steps

Upgrade dependency software. Go to How to Upgrade Dependency Software Before a Nonrolling Upgrade.

Note –

To complete the upgrade from Solaris 8 to Solaris 9 software or from Solaris 9 to Solaris 10 10/05 software or compatible, you must also upgrade to the Solaris 9 or Solaris 10 version of Sun Cluster 3.1 8/05 software, including dependency software. You must perform this task even if the cluster already runs on Sun Cluster 3.1 8/05 software for another version of Solaris software.