test

Sun Cluster 2.2 Software Installation Guide

4.2.1 How to Upgrade From Solstice HA 1.3 to Sun Cluster 2.2

These are the high-level steps to upgrade from Solstice HA 1.3 to Sun Cluster 2.2. You can perform the upgrade either from an administrative workstation or from the console of any physical host in the cluster. Upgrading by using an administrative workstations provides the most flexibility during the process.

Note -

This procedure assumes you are using an administrative workstation.

Caution - Caution -

Back up all local and multihost disks before starting the upgrade. Also, all systems must be operable and robust. Do not attempt to upgrade if systems are experiencing any difficulties.

Caution - Caution -

On each node, if you customized hasap_start_all_instances or hasap_stop_all_instances scripts in Solstice HA 1.3 or Sun Cluster 2.1, save them to a safe location before beginning the upgrade to Sun Cluster 2.2. Restore the scripts after completing the upgrade. Do this to prevent loss of your customizations when Sun Cluster 2.2 removes the old scripts.

The configuration parameters implemented in Sun Cluster 2.2 are different from those implemented in Solstice HA 1.3 and Sun Cluster 2.1. Therefore, after upgrading to Sun Cluster 2.2, you will have to re-configure Sun Cluster HA for SAP by running the hadsconfig(1M) command. Before starting the upgrade, view the existing configuration and note the current configuration variables. For Solstice HA 1.3, use the hainetconfig(1M) command to view the configuration. For Sun Cluster 2.1, use the hadsconfig(1M) command to view the configuration. After upgrading to Sun Cluster 2.2, use the hadsconfig(1M) command to re-create the instance.

These are the detailed steps to upgrade from Solstice HA 1.3 to Sun Cluster 2.2.

  1. Load the Sun Cluster 2.2 client packages onto the administrative workstation.

    Refer to "3.2 Installation Procedures", to set up the administrative workstation, if you have not done so already.

  2. Stop Solstice HA on the first server to be upgraded. 

    phys-hahost1# hastop

    If your cluster is already running Solaris 2.6, and you do not want to upgrade to Solaris 7, skip to Step 5.

  3. Upgrade the operating environment to Solaris 2.6 or Solaris 7.

    To upgrade Solaris, you must use the suninstall(1M) upgrade procedure (rather than reinstalling the operating environment). You might need to increase the size of your root (/) and /usr partitions on the root disks of all Sun Cluster servers in the configuration to accommodate the Solaris 2.6 or Solaris 7 environment. You must install the Entire Distribution Solaris software packages. See the Solaris Advanced Installation Guide for details.

    Note -

    For some hardware platforms, Solaris 2.6 and Solaris 7 attempts to configure power management settings to shut down the server automatically if it has been idle for 30 minutes. The cluster heartbeat is not enough to prevent the Sun Cluster servers from appearing idle and shutting down. Therefore, you must disable this feature when you install Solaris 2.6 or Solaris 7. The dialog used to configure power management settings is shown below. If you do not see this dialog, then your hardware platform does not support this feature. If the dialog appears, you must answer -n to the first question and -y to the second to configure the server to work correctly in the Sun Cluster environment.

    ****************************************************************
 This system is configured to conserve energy.
 After 30 minutes without activity, the system state will be
 saved to disk and the system will be powered off automatically.

 A system that has been suspended in this way can be restored
 back to exactly where it was by pressing the power key.
 The definition of inactivity and the timeout are user
 configurable. The dtpower(1M) man page has more information.
 ****************************************************************

 Do you wish to accept this default configuration, allowing
 your system to save its state then power off automatically
 when it has been idle for 30 minutes?  (If this system is used
 as a server, answer n. By default autoshutdown is
 enabled.) [y,n,?] n

 Autoshutdown disabled.

 Should the system save your answer so it won't need to ask
 the question again when you next reboot? (By default the
 question will not be asked again.) [y,n,?] y

  4. Update the Solaris 2.6 or Solaris 7 kernel files.

    As part of the Solaris upgrade, the files /kernel/drv/sd.conf and /kernel/drv/ssd.conf will be renamed to /kernel/drv/sd.conf:2.x and /kernel/drv/ssd.conf:2.x respectively. New /kernel/drv/sd.conf and /kernel/drv/ssd.conf files will be created. Run the diff(1) command to identify the differences between the old files and the new ones. Copy the additional information that was inserted by Sun Cluster from the old files into the new files. The information will look similar to the following:

    # Start of lines added by Solstice HA
 sd_retry_on_reservation_conflict=0;
 # End of lines added by Solstice HA

  5. Upgrade to Solstice DiskSuite 4.2.

    1. Upgrade Solstice DiskSuite using the detailed procedure in the Solstice DiskSuite 4.2 Installation and Product Notes.

    2. On the local host, upgrade the Solstice DiskSuite mediator package, SUNWmdm.

      phys-hahost1# pkgadd -d /cdrom/suncluster_sc_2_2/Sun_Cluster_2_2/Sol2_x/ \
 Product/ SUNWmdm

 Processing package instance <SUNWmdm>...

 Solstice DiskSuite (Mediator)
 (sparc) 4.2,REV=1998.23.10.09.59.06
 Copyright 1998 Sun Microsystems, Inc. All rights reserved.

 ## Executing checkinstall script.
 			This is an upgrade. Conflict approval questions may be
 			displayed. The listed files are the ones that will be
 			upgraded. Please answer "y" to these questions if they are
 			presented.
 Using </> as the package base directory.
 ## Processing package information.
 ## Processing system information.
    10 package pathnames are already properly installed.
 ## Verifying package dependencies.
 ## Verifying disk space requirements.
 ## Checking for conflicts with packages already installed.

 The following files are already installed on the system and are 
 being used by another package:
   /etc/opt/SUNWmd/meddb
   /usr/opt <attribute change only>
   /usr/opt/SUNWmd/man/man1m/medstat.1m
   /usr/opt/SUNWmd/man/man1m/rpc.metamedd.1m
   /usr/opt/SUNWmd/man/man4/meddb.4
   /usr/opt/SUNWmd/man/man7/mediator.7
   /usr/opt/SUNWmd/sbin/medstat
   /usr/opt/SUNWmd/sbin/rpc.metamedd

 Do you want to install these conflicting files [y,n,?,q] y
## Checking for setuid/setgid programs.

 This package contains scripts which will be executed with super-user 
 permission during the process of installing this package.

 Do you want to continue with the installation of <SUNWmdm.2> [y,n,?] y

 Installing Solstice DiskSuite (Mediator) as <SUNWmdm.2>
 ...

  6. From the root (/) directory on the local host, use the scinstall(1M) command to update the cluster packages.

    Select Upgrade from the scinstall(1M) menu. Respond to the prompts asking for the location of the Framework packages and cluster name. The scinstall(1M) command replaces Solstice HA 1.3 packages with Sun Cluster 2.2 packages.

    phys-hahost1# cd /cdrom/suncluster_sc_2_2/Sun_Cluster_2_2/Sol_2.x/Tools
phys-hahost1# ./scinstall
Installing: SUNWscins

 Installation of <SUNWscins> was successful.

         Checking on installed package state
 ............

 None of the Sun Cluster software has been installed

         <<Press return to continue>>

 ==== Install/Upgrade Software Selection Menu =======================
 Upgrade to the latest Sun Cluster Server packages or select package
 sets for installation. The list of package sets depends on the Sun
 Cluster packages that are currently installed.

 Choose one:
 1) Upgrade            Upgrade to Sun Cluster 2.2 Server packages
 2) Server             Install the Sun Cluster packages needed on a server
 3) Client             Install the admin tools needed on an admin workstation
 4) Server and Client	 Install both Client and Server packages

 5) Close              Exit this Menu
 6) Quit               Quit the Program
 
 Enter the number of the package set [6]: 1

 What is the directory where the Framework packages can be found
 [/cdrom/cdrom0]: .

 ** Upgrading from Solstice HA 1.3 **

 What is the name of the cluster? sc-cluster
...

  7. Install the required patches for Sun Cluster 2.2.

    Install all applicable Solstice DiskSuite and Sun Cluster patches. If you are using SPARCstorage Arrays, the latest SPARCstorage Array patch should have been installed when you installed the operating environment. Obtain the necessary patches from Sun Enterprise Services. Use the instructions in the patch README files to install the patches.

  8. Reboot the machine.

    phys-hahost1# reboot

  9. Switch ownership of disks and data services from the remote host to the upgraded local host.

    1. Stop Solstice HA 1.3 services on the remote host.

      The remote host in this example is phys-hahost2.

      phys-hahost2# hastop

    2. After Solstice HA 1.3 is stopped on the remote host, start Sun Cluster 2.2 on the upgraded local host.

      Since the remote host is no longer running HA, use the scadmin(1M) command to start Sun Cluster. This causes the upgraded local host to take over all data services. In this example, phys-hahost1 is the local physical host name, and sc-cluster is the cluster name.

      phys-hahost1# scadmin startcluster phys-hahost1 sc-cluster

    3. Verify that the configuration on the local host is stable. 

      phys-hahost1# hastat

    4. Verify that clients are receiving services from the local host.

  10. Repeat Step 2 through Step 8 on the remote host.

  11. Return the remote host to the cluster. 

    phys-hahost2# scadmin startnode

  12. After cluster reconfiguration on the remote host is complete, switch over the data services to the remote host from the local host.

    phys-hahost1# haswitch phys-hahost2 hahost2

  13. Verify that the Sun Cluster 2.2 configuration on the remote host is in a stable state, and that clients are receiving services.

    phys-hahost2# hastat

    This completes the procedure to upgrade from Solstice HA 1.3 to Sun Cluster 2.2.