Sun Cluster 3.1 10/03 Software Installation Guide

Upgrading to Sun Cluster 3.1 10/03 Software (Rolling)

This section provides the following procedure to perform a rolling upgrade from Sun Cluster 3.1 software to Sun Cluster 3.1 10/03 software. In a rolling upgrade, you upgrade one cluster node at a time, while the other cluster nodes remain in production.

To upgrade from Sun Cluster 3.0 software, perform the procedures in Upgrading to Sun Cluster 3.1 10/03 Software (Nonrolling).


Note –

Sun Cluster 3.1 10/03 software does not support rolling upgrade from Solaris 8 software to Solaris 9 software. You can 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, perform the procedures in Upgrading to Sun Cluster 3.1 10/03 Software (Nonrolling).


Table 3–2 Task Map: Upgrading to Sun Cluster 3.1 10/03 Software (Nonrolling)

Task 

Instructions 

1. Read the upgrade requirements and restrictions. 

Upgrade Requirements and Restrictions

2. Take the cluster out of production, disable resources, and ensure that shared data and system disks are backed up.  

How to Prepare the Cluster for Upgrade (Rolling)

3. Upgrade the Solaris software, if necessary, to a supported Solaris update release. Optionally, upgrade VERITAS Volume Manager (VxVM).  

How to Upgrade to a Solaris Maintenance Update Release (Rolling)

4. Upgrade to Sun Cluster 3.1 10/03 framework and data-service software. If necessary, upgrade applications. If you upgraded VxVM, upgrade disk groups. 

How to Upgrade to Sun Cluster 3.1 10/03 Software (Rolling)

5. Upgrade the Sun Cluster module to Sun Management Center, if needed. Reregister resource types, enable resources, and bring resource groups online. 

How to Finish Upgrading to Sun Cluster 3.1 10/03 Software (Rolling)

How to Prepare the Cluster for Upgrade (Rolling)

Perform this procedure on one node at a time. The upgraded node is taken out of the cluster, while the remaining nodes continue to function as active cluster members.


Note –

Do not use any new features of the update release, install new data services, or issue any administrative configuration commands until all nodes of the cluster are successfully upgraded.


  1. Ensure that the configuration meets requirements for upgrade.

    See Upgrade Requirements and Restrictions.

  2. Have available the CD-ROMs, documentation, and patches for all the software products you are upgrading before you begin to upgrade the cluster.

    • Solaris 8 or Solaris 9 operating environment

    • Sun Cluster 3.1 10/03 framework

    • Sun Cluster 3.1 10/03 data services (agents)

    • Applications that are managed by Sun Cluster 3.1 10/03 data-service agents

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

  3. (Optional) Install Sun Cluster 3.1 10/03 documentation.

    Install the documentation packages on your preferred location, such as an administrative console or a documentation server. See the index.html file at the top level of the Sun Cluster 3.1 10/03 CD-ROM to access installation instructions.

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

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

  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 evacuation completed successfully.


    # scstat -g -D
    
    -g

    Show status for all resource groups

    -D

    Show status for all disk device groups

  8. Ensure that the system disk and data is backed up.

  9. Shut down the node to upgrade and boot it into noncluster mode.


    # shutdown -y -g0
    ok boot -x
    

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

  10. Do you intend to upgrade the Solaris software to a Maintenance Update release?


    Note –

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


How to Upgrade to a Solaris Maintenance Update Release (Rolling)

Perform this procedure to upgrade the Solaris 8 or Solaris 9 operating environment to a supported Maintenance Update release.


Note –

To upgrade a cluster from Solaris 8 to Solaris 9 software, with or without upgrading Sun Cluster software as well, you must perform a nonrolling upgrade. Go to Upgrading to Sun Cluster 3.1 10/03 Software (Nonrolling).


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

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

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

  3. Follow instructions in your installation procedures for the Solaris Maintenance Update version you are upgrading to.


    Note –

    Do not reboot the node when prompted to reboot.


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

  5. 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 6.


  6. Reboot the node into noncluster mode.

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


    # reboot -- -x
    

  7. Upgrade the Sun Cluster software.

    Go to How to Upgrade to Sun Cluster 3.1 10/03 Software (Rolling).

How to Upgrade to Sun Cluster 3.1 10/03 Software (Rolling)

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


Note –

Do not use any new features provided in the Sun Cluster 3.1 10/03 software until all nodes of the cluster are upgraded.


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

    If you upgraded the Solaris operating environment to a Maintenance Update release, also ensure that all steps in How to Upgrade to a Solaris Maintenance Update Release (Rolling) are completed.

  2. Upgrade to Sun Cluster 3.1 10/03 software.

    1. Insert the Sun Cluster 3.1 10/03 CD-ROM into the CD-ROM drive on the node.

      If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/suncluster_3_1_u1 directory.

    2. Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .


      # cd /cdrom/suncluster_3_1_u1/SunCluster_3.1/Sol_ver/Tools
      

    3. Install the Sun Cluster 3.1 10/03 software.


      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 3.1 10/03 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 using 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.


      Tip –

      If upgrade processing is interrupted, use the scstat(1M) command to ensure that the node is in noncluster mode (Offline), then restart the scinstall command.


      # scstat -n
      -- Cluster Nodes --
                         Node name      Status
                         ---------      ------
        Cluster node:    nodename        Offline
        Cluster node:    nodename        Offline

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

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


      Note –

      Sun Cluster 3.1 software requires at least version 3.5.1 of Sun Explorer software. Upgrade 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 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 recreated.


    4. Change to the CD-ROM root directory and eject the CD-ROM.

    5. Install any Sun Cluster 3.1 10/03 software patches.

  3. Do you intend to upgrade any data services?

  4. Upgrade applications as needed.


    Note –

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


    Follow the instructions that are provided in your third-party documentation.

  5. (Optional) For each node on which data services are installed, upgrade to the Sun Cluster 3.1 10/03 data-service update software.


    Note –

    You must upgrade the Sun Cluster HA for Oracle 3.0 64–bit for Solaris 9 data service to the Sun Cluster 3.1 10/03 version. Otherwise, you can continue to use Sun Cluster 3.0 data services after upgrade to Sun Cluster 3.1 10/03 software.


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

    2. Install the Sun Cluster 3.1 10/03 data-service–update patches.

      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-image
        
        -u update

        Upgrades a cluster node to a later Sun Cluster software release

        -s srvc

        Upgrades the specified data service

        -d cdrom-image

        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-image
        

        -s all

        Upgrades all data services

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

    3. Change to the CD-ROM root directory and eject the CD-ROM.

    4. Install any Sun Cluster 3.1 10/03 data-service software patches.

    5. Verify that each data-service update patch is installed successfully.

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

  6. Reboot the node into the cluster.


    # reboot
    

  7. Run the following command on the upgraded node to verify that Sun Cluster 3.1 10/03 software is installed successfully.


    # scinstall -pv
    

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


    % scstat
    % scrgadm -pv[v]

    Output should be the same as for Step 4 in How to Prepare the Cluster for Upgrade (Rolling).

  9. Do you have another node to upgrade?

How to Finish Upgrading to Sun Cluster 3.1 10/03 Software (Rolling)

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

  2. Are you using Sun Management Center to monitor your Sun Cluster configuration?

    • If no, proceed to Step 3.

    • If yes, perform the following steps

    1. Ensure that all Sun Management Center core packages are installed on the appropriate machines, as described in your Sun Management Center installation documentation.

      This step includes installing Sun Management Center agent packages on each cluster node.

    2. Become superuser on the Sun Management Center server machine.

    3. Insert the Sun Cluster 3.1 10/03 CD-ROM into the CD-ROM drive.

    4. Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Packages directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .


      # cd /cdrom/suncluster_3_1_u1/SunCluster_3.1/Sol_ver/Packages
      

    5. Install the Sun Cluster–module server package SUNWscssv.


      # pkgadd -d . SUNWscssv
      

    6. Change to the CD-ROM root directory and eject the CD-ROM.

    7. Become superuser on the Sun Management Center help-server machine.

    8. Repeat Step e through Step g to install the Sun Cluster–module help-server package SUNWscshl.

  3. Reregister and re-version all resource types that received a new version from the upgrade, then re-enable resources and bring resource groups back online.

    1. From any node, start the scsetup(1M) utility.


      # scsetup
      

    2. To work with resource groups, type 2 (Resource groups).

    3. To register resource types, type 4 (Resource type registration).

      Type yes when prompted to continue.

    4. Type 1 (Register all resource types which are not yet registered).

      The scsetup utility displays all resource types that are not registered.

      Type yes to continue to register these resource types.

    5. Type 8 (Change properties of a resource).

      Type yes to continue.

    6. Type 3 (Manage resource versioning).

      Type yes to continue.

    7. Type 1 (Show versioning status).

      The scsetup utility displays which resources you can upgrade to new versions of the same resource type, and the state that the resource should be in before the upgrade can begin.

      Type yes to continue.

    8. Type 4 (Re-version all eligible resources).

      Type yes to continue when prompted.

    9. Return to the Resource Group Menu.

    10. Type 6 (Enable/Disable a resource).

      Type yes to continue when prompted.

    11. Select a resource to enable and follow the prompts.

    12. Repeat Step k for each disabled resource.

    13. When all resources are re-enabled, type q to return to the Resource Group Menu.

    14. Type 5 (Online/Offline or Switchover a resource group).

      Type yes to continue when prompted.

    15. Follow the prompts to bring each resource group online.

    16. Exit the scsetup utility.

      Type q to back out of each submenu, or press Ctrl-C.

  4. Restart any applications.

    Follow the instructions that are provided in your third-party documentation.

The cluster upgrade is complete.