test

Sun Cluster Software Installation Guide for Solaris OS

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

Perform this procedure to upgrade each node of the cluster to Sun Cluster 3.1 9/04 software. You must also perform this procedure to complete cluster upgrade from Solaris 8 to Solaris 9 software.

Tip –

You can perform this procedure on more than one node at the same time.

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

  2. If you upgraded from Solaris 8 to Solaris 9 software, ensure that all steps in How to Perform a Nonrolling Upgrade of the Solaris OS 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 a node of the cluster.

  5. Insert the Sun Java Enterprise System 1/05 2 of 2 CD-ROM into 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.

  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.

    • To upgrade from Sun Cluster 3.0 software, run the following command:


      # ./scinstall -u update -S interact [-M patchdir=dirname]
      -S

      Specifies the test IP addresses to use to convert NAFO groups to IP Network Multipathing groups

      interact

      Specifies that scinstall prompts the user for each test IP address needed

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

    • To upgrade from Sun Cluster 3.1 software, run the following command:


      # ./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.

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

    • Convert NAFO groups to IP Network Multipathing groups but keep the original NAFO-group name.

      See the scinstall(1M) man page for more information. See the IP Network Multipathing Administration Guide (Solaris 8) or System Administration Guide: IP Services (Solaris 9) for information about test addresses for IP Network Multipathing.

    • Rename the ntp.conf file to ntp.conf.cluster, if ntp.conf.cluster does not already exist on the node.

    • Set the local-mac-address? variable to true, if the variable is not already set to that value.

    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.

  15. After all nodes are upgraded, reboot each node into the cluster.


    # reboot

  16. Verify that all upgraded software is at the same version on all upgraded nodes.

    1. On each upgraded node, view the installed levels of Sun Cluster software.


      # scinstall -pv

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

    2. From any node, verify that all upgraded cluster nodes are running in cluster mode (Online).


      # scstat -n

      See the scstat(1M) man page for more information about displaying cluster status.

  17. If you upgraded from Solaris 8 to Solaris 9 software, verify the consistency of the storage configuration.

    1. On each node, run the following command to verify the consistency of the storage configuration.


      # scdidadm -c
      -c

      Perform a consistency check

      Caution – Caution –

      Do not proceed to Step b until your configuration passes this consistency check. Failure to pass this check might result in errors in device identification and cause data corruption.

      The following table lists the possible output from the scdidadm -c command and the action you must take, if any.

      Example Message 

      Action 

      device id for 'phys-schost-1:/dev/rdsk/c1t3d0' does not match physical device's id, device may have been replaced

      Go to Recovering From Storage Configuration Changes During Upgrade and perform the appropriate repair procedure.

      device id for 'phys-schost-1:/dev/rdsk/c0t0d0' needs to be updated, run scdidadm –R to update

      None. You update this device ID in Step b.

      No output message 

      None. 

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

    2. On each node, migrate the Sun Cluster storage database to Solaris 9 device IDs.


      # scdidadm -R all
      -R

      Perform repair procedures

      all

      Specify all devices

    3. On each node, run the following command to verify that storage database migration to Solaris 9 device IDs is successful.


      # scdidadm -c

      • If the scdidadm command displays a message, return to Step a to make further corrections to the storage configuration or the storage database.

      • If the scdidadm command displays no messages, the device-ID migration is successful. When device-ID migration is verified on all cluster nodes, proceed to Step 4.

  18. Go to How to Finish a Nonrolling Upgrade to Sun Cluster 3.1 9/04 Software.

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

The following example shows the process of a nonrolling upgrade of a two-node cluster from Sun Cluster 3.0 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 are phys-schost-1 and phys-schost-2.


(On the first node, 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

(On the first node, upgrade framework software from 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
 
(On the first node, 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
 
(On the second node, install Sun Web Console software from the Sun Cluster 3.1 9/04 CD-ROM)
phys-schost-2# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/ \
Solaris_8/Misc
phys-schost-2# ./setup

(On the second node, upgrade framework software from the Sun Cluster 3.1 9/04 CD-ROM)
phys-schost-2# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools
phys-schost-2# ./scinstall -u update -S interact
 
(On the second node, upgrade data services from the Sun Cluster 3.1 9/04 Agents CD-ROM)
phys-schost-2# scinstall -u update -s all -d /cdrom/cdrom0
 
(Reboot each node into the cluster)
phys-schost-1# reboot
phys-schost-2# reboot

(Verify that software versions are the same on all nodes)
# scinstall -pv 

(Verify cluster membership)
# scstat -n
-- Cluster Nodes --
                   Node name      Status
                   ---------      ------
  Cluster node:    phys-schost-1  Online
  Cluster node:    phys-schost-2  Online