Sun Cluster Software Installation Guide for Solaris OS

How to Perform a Rolling Upgrade of Sun Cluster 3.1 9/04 Software

Perform this procedure to upgrade a node to Sun Cluster 3.1 9/04 software while the remaining cluster nodes are in cluster mode.


Note –

Until all nodes of the cluster are upgraded and the upgrade is committed, new features that are introduced by the new release might not be available.


  1. Ensure that all steps in How to Prepare a Cluster Node for a Rolling Upgrade are completed.

  2. If you upgraded the Solaris OS to a Maintenance Update release, ensure that all steps in How to Perform a Rolling Upgrade of a Solaris Maintenance Update are completed.

  3. Ensure that you have installed all required Solaris software patches and hardware-related patches.

    For Solstice DiskSuite software (Solaris 8), also ensure that you have installed all required Solstice DiskSuite software patches.

  4. Become superuser on the node of the cluster.

  5. Install Sun Web Console packages.

    Perform this step on each node of the cluster. These packages are required by Sun Cluster software, even if you do not use Sun Web Console.

    1. Insert the Sun Cluster 3.1 9/04 CD-ROM in the CD-ROM drive.

    2. Change to the /cdrom/cdrom0/Solaris_arch/Product/sun_web_console/2.1/ directory, where arch is sparc or x86.

    3. Run the setup command.


      # ./setup
      

      The setup command installs all packages to support Sun Web Console.

  6. On the Sun Cluster 3.1 9/04 CD-ROM, change to the Solaris_arch/Product/sun_cluster/Solaris_ver/Tools/ directory, where arch is sparc or x86 and where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .


    # cd /cdrom/cdrom0/Solaris_arch/Product/sun_cluster/Solaris_ver/Tools
    

  7. Upgrade the cluster framework software.


    Note –

    Do not use the /usr/cluster/bin/scinstall command that is already installed on the node. You must use the scinstall command that is on the Sun Cluster 3.1 9/04 CD-ROM.



    ./scinstall -u update [-M patchdir=dirname]
    
    -M patchdir=dirname[[,patchlistfile=filename]]

    Specifies the path to patch information so that the specified patches can be installed by the scinstall command. If you do not specify a patch-list file, the scinstall command installs all the patches in the directory dirname, including tarred, jarred, and zipped patches.

    The -M option is not required. You can use any method you prefer for installing patches.

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


    Note –

    Sun Cluster 3.1 9/04 software requires at least version 3.5.1 of Sun Explorer software. Upgrading to Sun Cluster software includes installing Sun Explorer data collector software, to be used in conjunction with the sccheck utility. If another version of Sun Explorer software was already installed before the Sun Cluster upgrade, it is replaced by the version that is provided with Sun Cluster software. Options such as user identity and data delivery are preserved, but crontab entries must be manually re-created.


    Upgrade processing is finished when the system displays the message Completed Sun Cluster framework upgrade and the path to the upgrade log.

  8. Change to a directory that does not reside on the CD-ROM and eject the CD-ROM.


    # eject cdrom
    

  9. (Optional) Upgrade Sun Cluster data services.


    Note –

    If you are using the Sun Cluster HA for Oracle 3.0 64–bit for Solaris 9 data service, you must upgrade to the Sun Cluster 3.1 9/04 version.

    You can continue to use any other Sun Cluster 3.0 data services after you upgrade to Sun Cluster 3.1 9/04 software.


    1. Insert the Sun Cluster 3.1 9/04 Agents CD-ROM into the CD-ROM drive on the node.

    2. Upgrade the data-service software.

      Use one of the following methods:

      • To upgrade one or more specified data services, type the following command.


        # scinstall -u update -s srvc[,srvc,…] -d /cdrom/cdrom0
        

        -u update

        Upgrades a cluster node to a later Sun Cluster software release

        -s srvc

        Upgrades the specified data service

        -d

        Specifies an alternate directory location for the CD-ROM image

      • To upgrade all data services present on the node, type the following command.


        # scinstall -u update -s all -d /cdrom/cdrom0
        

        -s all

        Upgrades all data services

      The scinstall command assumes that updates for all installed data services exist on the update release. If an update for a particular data service does not exist in the update release, that data service is not upgraded.

      Upgrade processing is finished when the system displays the message Completed upgrade of Sun Cluster data services agents and displays the path to the upgrade log.

    3. Change to a directory that does not reside on the CD-ROM and eject the CD-ROM.


      # eject cdrom
      

  10. As needed, manually upgrade any custom data services that are not supplied on the Sun Cluster 3.1 9/04 Agents CD-ROM.

  11. Verify that each data-service update is installed successfully.

    View the upgrade log file that is referenced at the end of the upgrade output messages.

  12. Install any Sun Cluster 3.1 9/04 software patches, if you did not already install them by using the scinstall command.

  13. Install any Sun Cluster 3.1 9/04 data-service software patches.

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

  14. Upgrade software applications that are installed on the cluster.

    Ensure that application levels are compatible with the current versions of Sun Cluster and Solaris software. See your application documentation for installation instructions. In addition, follow these guidelines to upgrade applications in a Sun Cluster 3.1 9/04 configuration:

    • If the applications are stored on shared disks, you must master the relevant disk groups and manually mount the relevant file systems before you upgrade the application.

    • If 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:

      On SPARC based systems, perform the following commands:


      # reboot -- -xs
      ok boot -xs
      

      On x86 based systems, perform the following commands:


      # reboot -- -xs
      ...
                            <<< 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
      


    Note –

    Do not upgrade an application if the newer version of the application cannot coexist in the cluster with the older version of the application.


  15. Reboot the node into the cluster.


    # reboot
    

  16. Run the following command on the upgraded node to verify that Sun Cluster 3.1 9/04 software was installed successfully.


    # scinstall -pv
    

    The first line of output states which version of Sun Cluster software the node is running. This version should match the version you just upgraded to.

  17. From any node, verify the status of the cluster configuration.


    % scstat
    % scrgadm -pv[v]

    Output should be the same as for Step 7 in How to Prepare a Cluster Node for a Rolling Upgrade.

  18. If you have another node to upgrade, return to How to Prepare a Cluster Node for a Rolling Upgrade and repeat all upgrade procedures on the next node to upgrade.

  19. When all nodes in the cluster are upgraded, go to How to Finish a Rolling Upgrade to Sun Cluster 3.1 9/04 Software.

Example—Rolling Upgrade From Sun Cluster 3.1 to Sun Cluster 3.1 9/04 Software

The following example shows the process of a rolling upgrade of a cluster node from Sun Cluster 3.1 to Sun Cluster 3.1 9/04 software on the Solaris 8 OS. The example includes the installation of Sun Web Console software and the upgrade of all installed data services that have new versions on the Sun Cluster 3.1 9/04 Agents CD-ROM. The cluster node names is phys-schost-1.


(Install Sun Web Console software from the Sun Cluster 3.1 9/04 CD-ROM)
phys-schost-1# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/ \
Solaris_8/Misc
phys-schost-1# ./setup

(Upgrade framework softwarefrom the Sun Cluster 3.1 9/04 CD-ROM)
phys-schost-1# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools
phys-schost-1# ./scinstall -u update -S interact
 
(Upgrade data services from the Sun Cluster 3.1 9/04 Agents CD-ROM)
phys-schost-1# scinstall -u update -s all -d /cdrom/cdrom0

(Reboot the node into the cluster)
phys-schost-1# reboot

(Verify that software upgrade succeeded)
# scinstall -pv

(Verify cluster status)
# scstat
# scrgadm -pv