Sun Cluster Software Installation Guide for Solaris OS

Performing a Rolling Upgrade

This section provides procedures to perform a rolling upgrade from Sun Cluster 3.1 software to Sun Cluster 3.1 8/05 software. In a rolling upgrade, you upgrade one cluster node at a time, while the other cluster nodes remain in production. After all nodes are upgraded and have rejoined the cluster, you must commit the cluster to the new software version before you can use any new features.

To upgrade from Sun Cluster 3.0 software, follow instead the procedures in Performing a Nonrolling Upgrade.


Note –

Sun Cluster 3.1 8/05 software does not support rolling upgrade from Solaris 8 software to Solaris 9 software or from Solaris 9 software to Solaris 10 10/05 software. You can only upgrade Solaris software to an update release during Sun Cluster rolling upgrade. To upgrade a Sun Cluster configuration from Solaris 8 software to Solaris 9 software or from Solaris 9 software to Solaris 10 10/05 software or compatible, perform instead the procedures in Performing a Nonrolling Upgrade.


Table 5–2 Task Map: Performing a Rolling Upgrade to Sun Cluster 3.1 8/05 Software

Task 

Instructions 

1. Read the upgrade requirements and restrictions. 

Upgrade Requirements and Software Support Guidelines

2. On one node of the cluster, move resource groups and device groups to another cluster node, and ensure that shared data and system disks are backed up. If the cluster uses dual-string mediators for Solstice DiskSuite or Solaris Volume Manager software, unconfigure the mediators. Then reboot the node into noncluster mode. 

How to Prepare a Cluster Node for a Rolling Upgrade

3. Upgrade the Solaris OS on the cluster node, if necessary, to a supported Solaris update release. SPARC: Optionally, upgrade VERITAS File System (VxFS) and VERITAS Volume Manager (VxVM). 

How to Perform a Rolling Upgrade of a Solaris Maintenance Update

4. On all cluster nodes, install or upgrade software on which Sun Cluster 3.1 8/05 software has a dependency. 

How to Upgrade Dependency Software Before a Rolling Upgrade

5. Upgrade the cluster node to Sun Cluster 3.1 8/05 framework and data-service software. If necessary, upgrade applications. SPARC: If you upgraded VxVM, upgrade disk groups. Then reboot the node back into the cluster. 

How to Perform a Rolling Upgrade of Sun Cluster 3.1 8/05 Software

6. Repeat Tasks 3 through 5 on each remaining node to upgrade. 

 

7. Use the scversions command to commit the cluster to the upgrade. If the cluster uses dual-string mediators, reconfigure the mediators. Optionally, migrate existing resources to new resource types.

How to Finish a Rolling Upgrade to Sun Cluster 3.1 8/05 Software

8. (Optional) SPARC: Upgrade the Sun Cluster module to Sun Management Center.

SPARC: How to Upgrade Sun Cluster Module Software for Sun Management Center

ProcedureHow to Prepare a Cluster Node for a Rolling Upgrade

Perform this procedure on one node at a time. You will take the upgraded node out of the cluster while the remaining nodes continue to function as active cluster members.

Before You Begin

Perform the following tasks:

Observe the following guidelines when you perform a rolling upgrade:

Steps
  1. (Optional) Install Sun Cluster 3.1 8/05 documentation.

    Install the documentation packages on your preferred location, such as an administrative console or a documentation server. See the Solaris_arch/Product/sun_cluster/index.html file on the Sun Cluster 2 of 2 CD-ROM, where arch is sparc or x86, to access installation instructions.

  2. If you are upgrading from the Sun Cluster 3.1 9/04 release, ensure that the latest Sun Cluster 3.1 Core Patch is installed.

    This Core Patch contains the code fix for 6210440, which is necessary to enable rolling upgrade from Sun Cluster 3.1 9/04 software to Sun Cluster 3.1 8/05 software.

  3. Become superuser on one node of the cluster to upgrade.

  4. For a two-node cluster that uses Sun StorEdge Availability Suite software, ensure that the configuration data for availability services resides on the quorum disk.

    The configuration data must reside on a quorum disk to ensure the proper functioning of Sun StorEdge Availability Suite after you upgrade the cluster software.

    1. Become superuser on a node of the cluster that runs Sun StorEdge Availability Suite software.

    2. Identify the device ID and the slice that is used by the Sun StorEdge Availability Suite configuration file.


      # /usr/opt/SUNWscm/sbin/dscfg
      /dev/did/rdsk/dNsS
      

      In this example output, N is the device ID and S the slice of device N.

    3. Identify the existing quorum device.


      # scstat -q
      -- Quorum Votes by Device --
                           Device Name         Present Possible Status
                           -----------         ------- -------- ------
         Device votes:     /dev/did/rdsk/dQsS  1       1        Online

      In this example output, dQsS is the existing quorum device.

    4. If the quorum device is not the same as the Sun StorEdge Availability Suite configuration-data device, move the configuration data to an available slice on the quorum device.


      # dd if=`/usr/opt/SUNWesm/sbin/dscfg` of=/dev/did/rdsk/dQsS
      

      Note –

      You must use the name of the raw DID device, /dev/did/rdsk/, not the block DID device, /dev/did/dsk/.


    5. If you moved the configuration data, configure Sun StorEdge Availability Suite software to use the new location.

      As superuser, issue the following command on each node that runs Sun StorEdge Availability Suite software.


      # /usr/opt/SUNWesm/sbin/dscfg -s /dev/did/rdsk/dQsS
      
  5. From any node, view the current status of the cluster.

    Save the output as a baseline for later comparison.


    % scstat
    % scrgadm -pv[v]

    See the scstat(1M) and scrgadm(1M) man pages for more information.

  6. Move all resource groups and device groups that are running on the node to upgrade.


    # scswitch -S -h from-node
    
    -S

    Moves all resource groups and device groups

    -h from-node

    Specifies the name of the node from which to move resource groups and device groups

    See the scswitch(1M) man page for more information.

  7. Verify that the move was completed successfully.


    # scstat -g -D
    
    -g

    Shows status for all resource groups

    -D

    Shows status for all disk device groups

  8. Ensure that the system disk, applications, and all data are backed up.

  9. If your cluster uses dual-string mediators for Solstice DiskSuite or Solaris Volume Manager software, unconfigure your mediators.

    See Configuring Dual-String Mediators for more information.

    1. Run the following command to verify that no mediator data problems exist.


      # medstat -s setname
      
      -s setname

      Specifies the disk set name

      If the value in the Status field is Bad, repair the affected mediator host. Follow the procedure How to Fix Bad Mediator Data.

    2. List all mediators.

      Save this information for when you restore the mediators during the procedure How to Finish a Rolling Upgrade to Sun Cluster 3.1 8/05 Software.

    3. For a disk set that uses mediators, take ownership of the disk set if no node already has ownership.


      # scswitch -z -D setname -h node
      
      -z

      Changes mastery

      -D

      Specifies the name of the disk set

      -h node

      Specifies the name of the node to become primary of the disk set

    4. Unconfigure all mediators for the disk set.


      # metaset -s setname -d -m mediator-host-list
      
      -s setname

      Specifies the disk-set name

      -d

      Deletes from the disk set

      -m mediator-host-list

      Specifies the name of the node to remove as a mediator host for the disk set

      See the mediator(7D) man page for further information about mediator-specific options to the metaset command.

    5. Repeat these steps for each remaining disk set that uses mediators.

  10. Shut down the node that you want to upgrade and boot it into noncluster mode.

    • On SPARC based systems, perform the following commands:


      # shutdown -y -g0
      ok boot -x
      
    • On x86 based systems, perform the following commands:


      # shutdown -y -g0
      ...
                            <<< 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 -x
      

    The other nodes of the cluster continue to function as active cluster members.

Next Steps

To upgrade the Solaris software to a Maintenance Update release, go to How to Perform a Rolling Upgrade of a Solaris Maintenance Update.


Note –

The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris OS to support Sun Cluster 3.1 8/05 software. See the Sun Cluster 3.1 8/05 Release Notes for Solaris OS for information about supported releases of the Solaris OS.


If you do not intend to upgrade the Solaris OS, go to How to Upgrade Dependency Software Before a Rolling Upgrade.

ProcedureHow to Perform a Rolling Upgrade of a Solaris Maintenance Update

Perform this procedure to upgrade the Solaris OS to a supported Maintenance Update release.


Note –

To upgrade a cluster from Solaris 8 to Solaris 9 software or from Solaris 9 to Solaris 10 10/05 software or compatible, with or without upgrading Sun Cluster software as well, you must instead perform a nonrolling upgrade. Go to Performing a Nonrolling Upgrade.


Before You Begin

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

Steps
  1. Temporarily comment out all entries for globally mounted file systems in the node's /etc/vfstab file.

    Perform this step to prevent the Solaris upgrade from attempting to mount the global devices.

  2. Follow the instructions in the Solaris maintenance update installation guide to install the Maintenance Update release.


    Note –

    Do not reboot the node when prompted to reboot at the end of installation processing.


  3. Uncomment all entries in the /a/etc/vfstab file for globally mounted file systems that you commented out in Step 1.

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


    Note –

    Do not reboot the node until Step 5.


  5. Reboot the node into noncluster mode.

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


    # reboot -- -x
    
Next Steps

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

ProcedureHow to Upgrade Dependency Software Before a Rolling Upgrade

Perform this procedure on each cluster node to install or upgrade software on which Sun Cluster 3.1 8/05 software has a dependency. The cluster remains in production during this procedure. If you are running SunPlex Manager, status on a node will not be reported during the period that the node's security file agent is stopped. Status reporting resumes when the security file agent is restarted, after the common agent container software is upgraded.

Before You Begin

Perform the following tasks:

Steps
  1. Become superuser on the cluster node.

  2. For the Solaris 8 and Solaris 9 OS, ensure that the Apache Tomcat package is at the required patch level, if the package is installed.

    1. Determine whether the SUNWtcatu package is installed.


      # pkginfo SUNWtcatu
      SUNWtcatu       Tomcat Servlet/JSP Container
    2. If the Apache Tomcat package is installed, determine whether the required patch for the platform is installed.

      • SPARC based platforms require at least 114016-01

      • x86 based platforms require at least 114017-01


      # patchadd -p | grep 114016
      Patch: 114016-01 Obsoletes: Requires: Incompatibles: Packages: SUNWtcatu
    3. If the required patch is not installed, remove the Apache Tomcat package.


      # pkgrm SUNWtcatu
      
  3. Insert the Sun Cluster 1 of 2 CD-ROM.

  4. Change to the /cdrom/cdrom0/Solaris_arch/Product/shared_components/Packages/ directory, where arch is sparc or x86 .


    # cd Solaris_arch/Product/shared_components/Packages/
    
  5. Ensure that at least version 4.3.1 of the Explorer packages is installed.

    These packages are required by Sun Cluster software for use by the sccheck utility.

    1. Determine whether the Explorer packages are installed and, if so, what version.


      # pkginfo -l SUNWexplo | grep SUNW_PRODVERS
      SUNW_PRODVERS=4.3.1
    2. If a version earlier than 4.3.1 is installed, remove the existing Explorer packages.


      # pkgrm SUNWexplo SUNWexplu SUNWexplj
      
    3. If you removed Explorer packages or none were installed, install the latest Explorer packages from the Sun Cluster 1 of 2 CD-ROM.

      • For the Solaris 8 or Solaris 9 OS, use the following command:


        # pkgadd -d . SUNWexpl*
        
      • For the Solaris 10 OS, use the following command:


        # pkgadd -G -d . SUNWexpl*
        

        The -G option adds packages to the current zone only. You must add these packages only to the global zone. Therefore, this option also specifies that the packages are not propagated to any existing non-global zone or to any non-global zone that is created later.

  6. Ensure that at least version 5.1,REV=34 of the Java Dynamic Management Kit (JDMK) packages is installed.

    1. Determine whether JDMK packages are installed and, if so, what version.


      # pkginfo -l SUNWjdmk-runtime | grep VERSION
      VERSION=5.1,REV=34
    2. If a version earlier than 5.1,REV=34 is installed, remove the existing JDMK packages.


      # pkgrm SUNWjdmk-runtime SUNWjdmk-runtime-jmx
      
    3. If you removed JDMK packages or none were installed, install the latest JDMK packages from the Sun Cluster 1 of 2 CD-ROM.

      • For the Solaris 8 or Solaris 9 OS, use the following command:


        # pkgadd -d . SUNWjdmk*
        
      • For the Solaris 10 OS, use the following command:


        # pkgadd -G -d . SUNWjdmk*
        
  7. Change to the Solaris_arch/Product/shared_components/Solaris_ver/Packages/ directory, where arch is sparc or x86 and where ver is 8 for Solaris 8, 9 for Solaris 9, or 10 for Solaris 10.


    # cd ../Solaris_ver/Packages
    
  8. Ensure that at least version 4.5.0 of the Netscape Portable Runtime (NSPR) packages is installed.

    1. Determine whether NSPR packages are installed and, if so, what version.


      # cat /var/sadm/pkg/SUNWpr/pkginfo | grep SUNW_PRODVERS
      SUNW_PRODVERS=4.5.0
    2. If a version earlier than 4.5.0 is installed, remove the existing NSPR packages.


      # pkgrm packages
      

      The following table lists the applicable packages for each hardware platform.


      Note –

      Install packages in the order in which they are listed in the following table.


      Hardware Platform 

      NSPR Package Names 

      SPARC 

      SUNWpr SUNWprx

      x86 

      SUNWpr

    3. If you removed NSPR packages or none were installed, install the latest NSPR packages.

      • For the Solaris 8 or Solaris 9 OS, use the following command:


        # pkgadd -d . packages
        
      • For the Solaris 10 OS, use the following command:


        # pkgadd -G -d . packages
        
  9. Ensure that at least version 3.9.4 of the Network Security Services (NSS) packages is installed.

    1. Determine whether NSS packages are installed and, if so, what version.


      # cat /var/sadm/pkg/SUNWtls/pkginfo | grep SUNW_PRODVERS
      SUNW_PRODVERS=3.9.4
    2. If a version earlier than 3.9.4 is installed, remove the existing NSS packages.


      # pkgrm packages
      

      The following table lists the applicable packages for each hardware platform.


      Note –

      Install packages in the order in which they are listed in the following table.


      Hardware Platform 

      NSS Package Names 

      SPARC 

      SUNWtls SUNWtlsu SUNWtlsx

      x86 

      SUNWtls SUNWtlsu

    3. If you removed NSS packages or none were installed, install the latest NSS packages from the Sun Cluster 1 of 2 CD-ROM.

      • For the Solaris 8 or Solaris 9 OS, use the following command:


        # pkgadd -d . packages
        
      • For the Solaris 10 OS, use the following command:


        # pkgadd -G -d . packages
        
  10. Change back to the Solaris_arch/Product/shared_components/Packages/ directory.


    # cd ../../Packages
    
  11. Ensure that at least version 1.0,REV=25 of the common agent container packages is installed.

    1. Determine whether the common agent container packages are installed and, if so, what version.


      # pkginfo -l SUNWcacao | grep VERSION
      VERSION=1.0,REV=25
    2. If a version earlier than 1.0,REV=25 is installed, stop the security file agent for the common agent container on each cluster node.


      # /opt/SUNWcacao/bin/cacaoadm stop
      
    3. If a version earlier than 1.0,REV=25 is installed, remove the existing common agent container packages.


      # pkgrm SUNWcacao SUNWcacaocfg
      
    4. If you removed the common agent container packages or none were installed, install the latest common agent container packages from the Sun Cluster 1 of 2 CD-ROM.

      • For the Solaris 8 or Solaris 9 OS, use the following command:


        # pkgadd -d . SUNWcacao*
        
      • For the Solaris 10 OS, use the following command:


        # pkgadd -G -d . SUNWcacao*
        
  12. Change to a directory that does not reside on the CD-ROM and eject the CD-ROM.


    # eject cdrom
    
  13. Insert the Sun Cluster 2 of 2 CD-ROM.

  14. Install or upgrade Sun Java Web Console packages.

    1. Change to the Solaris_arch/Product/sunwebconsole/ directory, where arch is sparc or x86.

    2. Install the Sun Java Web Console packages.


      # ./setup
      

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

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


    # eject cdrom
    
  16. Ensure that the /usr/java/ directory is a symbolic link to the minimum or latest version of Java software.

    Sun Cluster software requires at least version 1.4.2_03 of Java software.

    1. Determine what directory the /usr/java/ directory is symbolically linked to.


      # ls -l /usr/java
      lrwxrwxrwx   1 root   other    9 Apr 19 14:05 /usr/java -> /usr/j2se/
    2. Determine what version or versions of Java software are installed.

      The following are examples of commands that you can use to display the version of their related releases of Java software.


      # /usr/j2se/bin/java -version
      # /usr/java1.2/bin/java -version
      # /usr/jdk/jdk1.5.0_01/bin/java -version
      
    3. If the /usr/java/ directory is not symbolically linked to a supported version of Java software, recreate the symbolic link to link to a supported version of Java software.

      The following example shows the creation of a symbolic link to the /usr/j2se/ directory, which contains Java 1.4.2_03 software.


      # rm /usr/java
      # ln -s /usr/j2se /usr/java
      
Next Steps

Upgrade Sun Cluster software. Go to How to Perform a Rolling Upgrade of Sun Cluster 3.1 8/05 Software

ProcedureHow to Perform a Rolling Upgrade of Sun Cluster 3.1 8/05 Software

Perform this procedure to upgrade a node to Sun Cluster 3.1 8/05 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.


Before You Begin

Ensure that dependency software is installed or upgraded. See How to Upgrade Dependency Software Before a Rolling Upgrade.

Steps
  1. Become superuser on the node of the cluster.

  2. Insert the Sun Cluster 2 of 2 CD-ROM in the CD-ROM drive on the node.

    If the volume management daemon vold(1M) is running and is configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0/ directory.

  3. 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, 9 for Solaris 9, or 10 for Solaris 10 .


    # cd /cdrom/cdrom0/Solaris_arch/Product/sun_cluster/Solaris_ver/Tools
    
  4. Start the scinstall utility.


    # ./scinstall
    

    Note –

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


  5. From the Main Menu, choose the menu item, Upgrade this cluster node.


      *** Main Menu ***
    
        Please select from one of the following (*) options:
    
          * 1) Install a cluster or cluster node
            2) Configure a cluster to be JumpStarted from this install server
          * 3) Add support for new data services to this cluster node
          * 4) Upgrade this cluster node
          * 5) Print release information for this cluster node
    
          * ?) Help with menu options
          * q) Quit
    
        Option:  4
    
  6. From the Upgrade Menu, choose the menu item, Upgrade Sun Cluster framework on this node.

  7. Follow the menu prompts to upgrade the cluster framework.

    During Sun Cluster upgrade, scinstall might make one or more of the following configuration changes:

    Upgrade processing is finished when the system displays the message Completed Sun Cluster framework upgrade and prompts you to press Enter to continue.

  8. Press Enter.

    The Upgrade Menu is displayed.

  9. (Optional) Upgrade Java Enterprise System data services from the Sun Cluster 2 of 2 CD-ROM.

    1. From the Upgrade Menu of the scinstall utility, choose the menu item, Upgrade Sun Cluster data service agents on this node.

    2. Follow the menu prompts to upgrade Sun Cluster data service agents that are installed on the node.

      You can choose from the list of data services that are available to upgrade or choose to upgrade all installed data services.

      Upgrade processing is finished when the system displays the message Completed upgrade of Sun Cluster data services agents and prompts you to press Enter to continue.

    3. Press Enter.

      The Upgrade Menu is displayed.

  10. Quit the scinstall utility.

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


    # eject cdrom
    
  12. Upgrade Sun Cluster data services from the Sun Cluster Agents CD.

    • If you are using the Sun Cluster HA for NFS data service and you upgrade to the Solaris 10 OS, you must upgrade the data service and migrate the resource type to the new version. See Upgrading the SUNW.nfs Resource Type in Sun Cluster Data Service for NFS Guide for Solaris OS for more information.

    • 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 8/05 version.

    • The upgrade of any other data services to the Sun Cluster 3.1 8/05 version is optional. You can continue to use any other Sun Cluster 3.x data services after you upgrade the cluster to Sun Cluster 3.1 8/05 software.

    1. Insert the Sun Cluster Agents CD in the CD-ROM drive on the node.

    2. Start the scinstall utility.

      For data-service upgrades, you can use the /usr/cluster/bin/scinstall command that is already installed on the node.


      # scinstall
      
    3. From the Main Menu, choose the menu item, Upgrade this cluster node.

    4. From the Upgrade Menu, choose the menu item, Upgrade Sun Cluster data service agents on this node.

    5. Follow the menu prompts to upgrade Sun Cluster data service agents that are installed on the node.

      You can choose from the list of data services that are available to upgrade or choose to upgrade all installed data services.

      Upgrade processing is finished when the system displays the message Completed upgrade of Sun Cluster data services agents and prompts you to press Enter to continue.

    6. Press Enter.

      The Upgrade Menu is displayed.

    7. Quit the scinstall utility.

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


      # eject cdrom
      
  13. As needed, manually upgrade any custom data services that are not supplied on the product media.

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

  15. Install any Sun Cluster 3.1 8/05 software patches, if you did not already install them by using the scinstall command.

  16. Install any Sun Cluster 3.1 8/05 data-service software patches.

    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.

  17. 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 8/05 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.


  18. Reboot the node into the cluster.


    # reboot
    
  19. Run the following command on the upgraded node to verify that Sun Cluster 3.1 8/05 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.

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


    % scstat
    % scrgadm -pv[v]

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

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


Example 5–2 Rolling Upgrade From Sun Cluster 3.1 to Sun Cluster 3.1 8/05 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 8/05 software on the Solaris 8 OS. The example includes the upgrade of all installed data services that have new versions on the Sun Cluster Agents CD. The cluster node name is phys-schost-1.


(Upgrade framework software from the Sun Cluster 2 of 2 CD-ROM)
phys-schost-1# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools/
phys-schost-1# ./scinstall
 
(Upgrade data services from the Sun Cluster Agents CD)
phys-schost-1# scinstall

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

(Verify that software upgrade succeeded)
# scinstall -pv

(Verify cluster status)
# scstat
# scrgadm -pv

Next Steps

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

ProcedureHow to Finish a Rolling Upgrade to Sun Cluster 3.1 8/05 Software

Before You Begin

Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.

Steps
  1. From one node, check the upgrade status of the cluster.


    # scversions
    
  2. From the following table, perform the action that is listed for the output message from Step 1.

    Output Message 

    Action 

    Upgrade commit is needed.

    Proceed to Step 4.

    Upgrade commit is NOT needed. All versions match.

    Skip to Step 6.

    Upgrade commit cannot be performed until all cluster nodes are upgraded. Please run scinstall(1m) on cluster nodes to identify older versions.

    Return to How to Perform a Rolling Upgrade of Sun Cluster 3.1 8/05 Software to upgrade the remaining cluster nodes.

    Check upgrade cannot be performed until all cluster nodes are upgraded. Please run scinstall(1m) on cluster nodes to identify older versions.

    Return to How to Perform a Rolling Upgrade of Sun Cluster 3.1 8/05 Software to upgrade the remaining cluster nodes.

  3. After all nodes have rejoined the cluster, from one node commit the cluster to the upgrade.


    # scversions -c
    

    Committing the upgrade enables the cluster to utilize all features in the newer software. New features are available only after you perform the upgrade commitment.

  4. From one node, verify that the cluster upgrade commitment has succeeded.


    # scversions
    Upgrade commit is NOT needed. All versions match.
  5. Copy the security files for the common agent container to all cluster nodes.

    This step ensures that security files for the common agent container are identical on all cluster nodes and that the copied files retain the correct file permissions.

    1. On each node, stop the Sun Java Web Console agent.


      # /usr/sbin/smcwebserver stop
      
    2. On each node, stop the security file agent.


      # /opt/SUNWcacao/bin/cacaoadm stop
      
    3. On one node, change to the /etc/opt/SUNWcacao/ directory.


      phys-schost-1# cd /etc/opt/SUNWcacao/
      
    4. Create a tar file of the /etc/opt/SUNWcacao/security/ directory.


      phys-schost-1# tar cf /tmp/SECURITY.tar security
      
    5. Copy the /tmp/SECURITY.tar file to each of the other cluster nodes.

    6. On each node to which you copied the /tmp/SECURITY.tar file, extract the security files.

      Any security files that already exist in the /etc/opt/SUNWcacao/ directory are overwritten.


      phys-schost-2# cd /etc/opt/SUNWcacao/
      phys-schost-2# tar xf /tmp/SECURITY.tar
      
    7. Delete the /tmp/SECURITY.tar file from each node in the cluster.

      You must delete each copy of the tar file to avoid security risks.


      phys-schost-1# rm /tmp/SECURITY.tar
      phys-schost-2# rm /tmp/SECURITY.tar
      
    8. On each node, start the security file agent.


      phys-schost-1# /opt/SUNWcacao/bin/cacaoadm start
      phys-schost-2# /opt/SUNWcacao/bin/cacaoadm start
      
    9. On each node, start the Sun Java Web Console agent.


      phys-schost-1# /usr/sbin/smcwebserver start
      phys-schost-2# /usr/sbin/smcwebserver start
      
  6. If your configuration uses dual-string mediators for Solstice DiskSuite or Solaris Volume Manager software, restore the mediator configurations.

    1. Determine which node has ownership of a disk set to which you are adding the mediator hosts.


      # metaset -s setname
      
      -s setname

      Specifies the disk-set name

    2. If no node has ownership, take ownership of the disk set.


      # scswitch -z -D setname -h node
      
      -z

      Changes mastery

      -D

      Specifies the name of the disk set

      -h node

      Specifies the name of the node to become primary of the disk set

    3. Re-create the mediators.


      # metaset -s setname -a -m mediator-host-list
      
      -a

      Adds to the disk set

      -m mediator-host-list

      Specifies the names of the nodes to add as mediator hosts for the disk set

    4. Repeat Step a through Step c for each disk set in the cluster that uses mediators.

  7. If you upgraded any data services that are not supplied on the product media, register the new resource types for those data services.

    Follow the documentation that accompanies the data services.

  8. (Optional) Switch each resource group and device group back to its original node.


    # scswitch -z -g resource-group -h node
    # scswitch -z -D disk-device-group -h node
    
    -z

    Performs the switch

    -g resource-group

    Specifies the resource group to switch

    -h node

    Specifies the name of the node to switch to

    -D disk-device-group

    Specifies the device group to switch

  9. Restart any applications.

    Follow the instructions that are provided in your vendor documentation.

  10. Migrate resources to new resource type versions.


    Note –

    If you upgrade to the Sun Cluster HA for NFS data service for the Solaris 10 OS, you must migrate to the new resource type version. See Upgrading the SUNW.nfs Resource Type in Sun Cluster Data Service for NFS Guide for Solaris OS for more information.

    For all other data services, this step is optional.


    See Upgrading a Resource Type in Sun Cluster Data Services Planning and Administration Guide for Solaris OS, which contains procedures which use the command line. Alternatively, you can perform the same tasks by using the Resource Group menu of the scsetup utility. The process involves performing the following tasks:

    • Registration of the new resource type

    • Migration of the eligible resource to the new version of its resource type

    • Modification of the extension properties of the resource type as specified in the manual for the related data service

Next Steps

If you have a SPARC based system and use Sun Management Center to monitor the cluster, go to SPARC: How to Upgrade Sun Cluster Module Software for Sun Management Center.

Otherwise, the cluster upgrade is complete.