test

Sun Cluster Software Installation Guide for Solaris OS

Upgrading to Sun Cluster 3.1 4/04 Software (Rolling)

This section provides procedures to perform a rolling upgrade from Sun Cluster 3.1 software to Sun Cluster 3.1 4/04 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, follow the procedures in Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling).

Note –

Sun Cluster 3.1 4/04 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 4/04 Software (Nonrolling).

Task Map: Upgrading to Sun Cluster 3.1 4/04 Software (Rolling)

Table 5–2 Task Map: Upgrading to Sun Cluster 3.1 4/04 Software (Rolling)

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. If the cluster uses dual-string mediators for Solstice DiskSuite/Solaris Volume Manager, unconfigure the mediators. 

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 4/04 framework and data-service software. If necessary, upgrade applications. If you upgraded VxVM, upgrade disk groups. 

How to Upgrade to Sun Cluster 3.1 4/04 Software (Rolling)

5. If the cluster uses dual-string mediators, reconfigure the mediators. Register new resource types, migrate existing resources to new resource types, modify resource type extension properties as needed, enable resources, and bring resource groups online. Upgrade the Sun Cluster module to Sun Management Center, if needed.  

How to Finish Upgrading to Sun Cluster 3.1 4/04 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 4/04 framework

    • Sun Cluster 3.1 4/04 data services (agents)

    • Applications that are managed by Sun Cluster 3.1 4/04 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 4/04 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 Java Enterprise System 2004Q2 2 of 2 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 move 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. Does your cluster use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?

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


      # medstat -s setname
      -s setname

      Specifies the diskset 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.

      Use this information for when you restore the mediators during the procedure How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling).

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


      # metaset -s setname -t
      -t

      Takes ownership of the diskset

    4. Unconfigure all mediators for the diskset.


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

      Specifies the diskset name

      -d

      Deletes from the diskset

      -m mediator-host-list

      Specifies the name of the node ot remove as a mediator host for the diskset

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

    5. Repeat Step c through Step d for each remaining diskset that uses mediators.

  10. Shut down the node that you want 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.

  11. 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 4/04 software. See the Sun Cluster Release Notes for Solaris OS 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 4/04 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 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.

  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 4/04 Software (Rolling).

How to Upgrade to Sun Cluster 3.1 4/04 Software (Rolling)

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

Note –

Do not use any new features provided in the Sun Cluster 3.1 4/04 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 4/04 software.

    1. Insert the Sun Java Enterprise System 2004Q2 2 of 2 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, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

    2. From the /cdrom/cdrom0 directory, change to the Solaris_sparc/Product/sun_cluster/Solaris_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .

      The following example uses the path to the Solaris 8 version of Sun Cluster software.


      # cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools

    3. Install the Sun Cluster 3.1 4/04 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 Java Enterprise System 2004Q2 2 of 2 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.

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

      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 4/04 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 4/04 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 4/04 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 4/04 version. Otherwise, you can continue to use Sun Cluster 3.0 data services after upgrade to Sun Cluster 3.1 4/04 software.

    1. Insert the Java Enterprise System Accessory CD 3 CD-ROM into the CD-ROM drive on the node.

    2. Install the Sun Cluster 3.1 4/04 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.

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

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

    4. Install any Sun Cluster 3.1 4/04 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 4/04 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 4/04 Software (Rolling)

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

  2. Does your configuration use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?

    • If no, proceed to Step 3.

    • If yes, restore the mediator configurations.

    1. Determine which node has ownership of a diskset to which you will add the mediator hosts.


      # metaset -s setname
      -s setname

      Specifies the diskset name

    2. If no node has ownership, take ownership of the diskset.


      # metaset -s setname -t
      -t

      Takes ownership of the diskset

    3. Recreate the mediators.


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

      Adds to the diskset

      -m mediator-host-list

      Specifies the names of the nodes to add as mediator hosts for the diskset

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

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

    • If no, proceed to Step 4.

    • If yes, perform the following steps to upgrade the Sun Cluster-module software on the Sun Management Center server machine, help-server machine, and console machine.

      Note –

      Sun Cluster-module software on the cluster nodes was already upgraded during the cluster-framework upgrade.

      If you intend to upgrade the Sun Management Center software itself, do not perform this step. Instead, proceed to Step 4 to finish Sun Cluster software upgrade. Then go to How to Upgrade Sun Management Center Software to upgrade Sun Management Center software and the Sun Cluster module.

    1. As superuser, remove the existing Sun Cluster–module packages.

      Use the pkgrm(1M) command to remove all Sun Cluster–module packages from all locations listed in the following table. 


      # pkgrm module-package

      Location 

      Module Package to Remove 

      Sun Management Center console machine 

      SUNWscscn

      Sun Management Center server machine 

      SUNWscssv

      Sun Management Center help-server machine 

      SUNWscshl

      Note –

      Sun Cluster-module software on the cluster nodes was already upgraded during the cluster-framework upgrade.

    2. As superuser, reinstall Sun Cluster–module packages from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM to the locations listed in the following table.

      In the CD-ROM path, the value for ver is 8 (for Solaris 8) or 9 (for Solaris 9).


      # cd Solaris_sparc/Product/sun_cluster/Solaris_ver/Packages/
# pkgadd -d . module-package

      Location 

      Module Package to Install 

      Sun Management Center console machine 

      SUNWscshl

      Sun Management Center server machine 

      SUNWscssv

      Sun Management Center help-server machine 

      SUNWscshl

      You install the help-server package SUNWscshl on both the console machine and the help-server machine. You do not upgrade to a new SUNWscscn package on the console machine.

  4. If you upgraded any data services that are not supplied on the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM or the Java Enterprise System Accessory CD 3 CD-ROM, register the new resource types for those data services.

    Follow the documentation that comes with the data services.

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


    # scsetup

  6. Register the new resource types.

    1. From the Main Menu, choose Resource groups.

    2. Choose Resource type registration.

    3. Choose Register all resource types which are not yet registered.

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

      Follow the prompts to register the new resource types.

  7. Migrate all eligible resources to the new version of its resource type.

    1. From the Resource Group menu, choose Change properties of a resource.

    2. Choose Manage resource versioning.

    3. Choose Show versioning status.

      The scsetup utility displays all resources for which a new version of its resource type was installed during the upgrade. Make note of which new resource types you will upgrade the resources to.

    4. Choose Re-version all eligible resources.

      Follow the prompts to upgrade eligible resources to the new version of its resource type.

    5. Return to the Change properties of a resource menu.

  8. Modify extension properties for new resource type versions.

    1. For each new resource type that you migrated existing resources to, determine whether the new resource type requires additional modifications to its extension properties.

      Refer to each related data service manual for the requirements of each new resource type.

      Note –

      You do not need to change the Type_version property of a new resource type. That property was modified when you migrated resources to their new resource types in Step 7.

      • If no resource type requires additional modifications other than the Type_version property, go to Step 9.

      • If one or more resource types require additional modifications to extension properties, proceed to Step b.

    2. From the Change properties of a resource menu, choose Change extension resource properties.

    3. Follow the prompts to modify the necessary extension properties.

      Refer to your data service documentation for the names of extension properties and values to modify.

    4. Repeat for each resource type that requires modifications.

    5. Return to the Resource Groups menu.

  9. Re-enable all disabled resources.

    1. From the Resource Group Menu, choose Enable/Disable a resource.

    2. Choose a resource to enable and follow the prompts.

    3. Repeat Step b for each disabled resource.

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

  10. Bring each resource group back online.

    1. From the Resource Group Menu, choose Online/Offline or Switchover a resource group.

    2. Follow the prompts to put each resource group into the managed state and then bring the resource group online.

  11. When all resource groups are back online, exit the scsetup utility.

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

    The cluster upgrade is complete. You can now return the cluster to production.

  12. Restart any applications.

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

    The cluster upgrade is complete.