Performing the Upgrade (Sun Cluster 2.2 Software Installation Guide)

Sun Cluster 2.2 Software Installation Guide

Previous: Using Terminal Concentrator and System Service Processor Monitoring
Next: Upgrading to Sun Cluster 2.2 on Solaris 8 From Sun Cluster 2.2 on Solaris 2.6 or Solaris 7

Performing the Upgrade

This procedure describes the steps required to upgrade the server software on a Sun Cluster 2.0 or Sun Cluster 2.1 system to Sun Cluster 2.2, with a minimum of downtime. You should become familiar with the entire procedure before starting the upgrade.

Caution -

Before starting the upgrade, you should have an adequate backup of all configuration information and key data, and the cluster must be in a stable, non-degraded state.

Caution -

If you are running VxVM with an encapsulated root disk, you must unencapsulate the root disk before installing Sun Cluster 2.2. After you install Sun Cluster 2.2, encapsulate the disk again. Refer to your VxVM documentation for the procedures to encapsulate and unencapsulate the root disk.

Note -

During the upgrade procedure, all non-local private link IP addresses will be added, with root access only, to the /.rhosts file on every cluster node.

Note -

If you want to use the Cluster Monitor to continue monitoring the cluster during the upgrade, upgrade the server software first and the client software last.

How to Upgrade to Sun Cluster 2.2 From Sun Cluster 2.0 or 2.1

This example assumes an N+1 configuration using an administrative workstation.

(Sun Cluster HA for SAP only) Run the hadsconfig(1M) command to obtain the current configuration parameters.

The SAP instance configuration data is lost during the upgrade. Therefore, run the hadsconfig(1M) and make note of the current SAP parameters so you can restore them manually later. See Chapter 10, Installing and Configuring Sun Cluster HA for SAP for a description of the new Sun Cluster HA for SAP configuration parameters.
phys-hahost1# hadsconfig

Stop the first node.
phys-hahost1# scadmin stopnode

If you are upgrading the operating environment or upgrading from SSVM to VxVM, run the command upgrade_start from the new VxVM media.

In this example, CDROM_path is the path to the scripts on the new VxVM CD-ROM.
phys-hahost1# CDROM_path/upgrade_start
To upgrade the operating environment, follow the detailed instructions in the appropriate Solaris installation manual and also see Chapter 2, Planning the Configuration.

To upgrade from SSVM to VxVM, refer to your VERITAS Volume Manager documentation.

If you are upgrading the operating environment but not the volume manager, perform the following steps.
1. Remove the volume manager package.
  
  For example:
  phys-hahost1# pkgrm SUNWvxvm
2. Upgrade the operating system.
  
  Refer to your Solaris installation documentation for instructions.
3. If you are using NIS+, modify the /etc/nsswitch.conf file.
  
  Ensure that "service," "group," and "hosts" lookups are directed to files first. For example:
  hosts: files nisplus services: files nisplus group: files nisplus
4. Restore the volume manager package removed in Step 4a.
  
  Obtain the volume manager package from the Sun Cluster 2.2 CD-ROM. In this example, CDROM_path is the path to the tools on the VxVM CD-ROM.
  phys-hahost1# pkgadd -d CDROM_path/SUNWvxvm

If you upgraded from SSVM to VxVM, run the command upgrade_finish from the VxVM media.

In this example, CDROM_path is the path to the scripts on the VxVM CD-ROM
phys-hahost1# CDROM_path/upgrade_finish
.

Reboot the system.

Caution -
You must reboot at this time.

(Sun Cluster HA for SAP only) Perform the following steps.
1. Save to a safe location any customized hasap_start_all_instances or hasap_stop_all_instances scripts in Sun Cluster 2.1, before beginning the upgrade to Sun Cluster 2.2.
  
  Save the scripts to prevent loss of your customizations when Sun Cluster 2.2 removes the old scripts during the upgrade. Restore the scripts after completing the upgrade. Copy the scripts to a safe location. You will restore the scripts later in Step 9b.
  phys-hahost1# cp /opt/SUNWcluster/ha/sap/hasap_start_all_instances /safe_place phys-hahost1# cp /opt/SUNWcluster/ha/sap/hasap_stop_all_instances /safe_place
2. Remove the SUNWscsap package before using scinstall(1M) to update the cluster software.
  
  The SUNWscsap package is not updated automatically by scinstall(1M). You must first remove this package. You will add an updated version in Step 9.
  phys-hahost1# pkgrm SUNWscsap

Update the cluster software by using the scinstall(1M) command from the Sun Cluster 2.2 CD-ROM.

Invoke scinstall(1M) and select the Upgrade option from the menu presented.

phys-hahost1# cd /cdrom/multi_suncluster_sc_2_2/Sun_Cluster_2_2/Sol_2.x/Tools
phys-hahost1# ./scinstall

Removal of <SUNWscins> was successful.
Installing: SUNWscins

Installation of <SUNWscins> was successful.
Assuming a default cluster name of sc-cluster

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

============ Main Menu =================
1) Install/Upgrade - Install or Upgrade Server Packages or Install Client  Packages.
2) Remove  - Remove Server or Client Packages.
3) Change  - Modify cluster or data service configuration
4) Verify  - Verify installed package sets.
5) List    - List installed package sets.
6) Quit    - Quit this program.
7) Help    - The help screen for this menu.

Please choose one of the menu items: [7]:  1
...
==== 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 path to the CD-ROM image? [/cdrom/cdrom0]:  .

** Upgrading from Sun Cluster 2.1 **
	Removing "SUNWccm" ... done
...

(Sun Cluster HA for SAP only) Perform the following steps.

Add the SUNWscsap package from the Sun Cluster 2.2 CD-ROM.

Use pkgadd(1M) to add an updated SUNWscsap package to replace the package removed in Step 7. Answer y to all screen prompts that appear during the pkgadd process.
phys-hahost1# pkgadd -d \ /cdrom/multi_suncluster_sc_2_2/Sun_Cluster_2_2/Sol_2.x/Product/ SUNWscsap

Restore the customized scripts saved in Step 7a.

Copy the scripts to the /opt/SUNWcluster/ha/sap directory. The safe_place directory is the directory into which you saved the scripts in Step 7a. After restoring the scripts, use the ls -l command to verify that the scripts are executable.

phys-hahost1# cd /opt/SUNWcluster/ha/sap
phys-hahost1# cp /safe_place/hasap_start_all_instances .
phys-hahost1# cp /safe_place/hasap_stop_all_instances .
phys-hahost1# ls -l /opt/SUNWcluster/ha/sap/hasap_st*
-r-xr--r--   1 root     sys        18400 Feb  9 19:04 hasap_start_all_instances
-r-xr--r--   1 root     sys        25963 Feb  9 19:04 hasap_stop_all_instances

If the cluster has more than two nodes and you are upgrading from Sun Cluster 2.0, supply the TC/SSP information.

The first time the scinstall(1M) command is invoked, the TC/SSP information is automatically saved to the /var/tmp/tc_ssp_info file. Copy this file to the /var/tmp directory on all other cluster nodes so the information can be reused when you upgrade those nodes. You can either supply the TC/SSP information now, or do so later by using the scconf(1M) command. See the scconf(1M) man page for details.

When the scinstall(1M) command prompts for the TC/SSP information, you can either force the program to query the tc_ssp_info file, or invoke an interactive session that will prompt you for the required information.

The example cluster assumes the following configuration information:

Cluster name: sc-cluster
Number of nodes in the cluster: 2
Node names: phys-hahost1 and phys-hahost2
Logical host names: hahost1 and hahost2
Terminal concentrator name: cluster-tc
Terminal concentrator IP address: 123.4.5.678
Physical TC port connected to phys-hahost1: 2
Physical TC port connected to phys-hahost2: 3

See Chapter 1, Understanding the Sun Cluster Environment for more information on server architectures and TC/SSPs. In this example, the configuration is not an E10000 cluster, so the architecture specified is other, and a terminal concentrator is used:

What type of architecture does phys-hahost1 have? (E10000|other) [other] [?] other
What is the name of the Terminal Concentrator connected to the serial port of phys-hahost1 [NO_NAME] [?] cluster-tc
Is 123.4.5.678 the correct IP address for this Terminal Concentrator (yes|no) [yes] [?] yes
Which physical port on the Terminal Concentrator is phys-hahost2 connected to [?] 2
What type of architecture does phys-hahost2 have? (E10000|other) [other] [?] other
Which Terminal Concentrator is phys-hahost2 connected to:

0) cluster-tc       123.4.5.678
1) Create A New Terminal Concentrator Entry

Select a device [?] 0
Which physical port on the Terminal Concentrator is phys-hahost2 connected to [?] 3
The terminal concentrator/system service processor (TC/SSP) information has been stored in file /var/tmp/tc_ssp_data. Please put a copy of this file into /var/tmp on the rest of the nodes in the cluster. This way you don't have to re-enter the TC/SSP values, but you will, however, still be prompted for the TC/SSP passwords.

If you will be using Sun Cluster SNMP, change the port number used by the Sun Cluster SNMP daemon and Solaris SNMP (smond).

The default port used by Sun Cluster SNMP is the same as the default port number used by Solaris SNMP; both use port 161. Change the Sun Cluster SNMP port number using the procedure described in the SNMP appendix to the Sun Cluster 2.2 System Administration Guide.

(Solaris 2.6 and 7 only) Use the install_scpatches utility to install Sun Cluster patches from the Sun Cluster product CD-ROM.

Run the command from the Patches subdirectory on the new Sun Cluster CD-ROM.

# cd /cdrom/multi_suncluster_sc_2_2/Sun_Cluster_2_2/Sol_2.x/Patches
# ./install_scpatches

Patch install script for Sun Cluster 2.2 July 2000 Release

*WARNING* SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES:
With or without using the save option, the patch installation process
will still require some amount of disk space for installation and
administrative tasks in the /, /usr, /var, or /opt partitions where
patches are typically installed. The exact amount of space will
depend on the machine's architecture, software packages already
installed, and the difference in the patched objects size. To be
safe, it is not recommended that a patch cluster be installed on a
system with less than 4 MBytes of available space in each of these
partitions. Running out of disk space during installation may result
in only partially loaded patches. Check and be sure adequate disk space
is available before continuing.

Are you ready to continue with install? [y/n]: y

Determining if sufficient save space exists...
Sufficient save space exists, continuing...
Installing patches located in /cdrom/multi_suncluster_sc_2_2/Sun_Cluster_2_2/Sol_2.x/Patches
Using patch_order file for patch installation sequence
Installing 107388-03 ... okay.
Installing 107748-02 ... okay.
...
For more installation messages refer to the installation logfile:
/var/sadm/install_data/Sun_Cluster_2.2_July_2000_Release_log

Use '/usr/bin/showrev -p' to verify installed patch-ids.
Refer to individual patch README files for more patch detail.
Rebooting the system is usually necessary after installation.

Install any required or recommended Sun Cluster and volume manager patches.

Besides those patches installed in Step 12, also obtain any required or recommended patches from your service provider or from the patches website, http://sunsolve.sun.com. Follow the instructions in the patch README files to install the patches.

Reboot the system.

Caution -
You must reboot at this time.

If you are using a shared CCD, put all logical hosts into maintenance mode.
phys-hahost2# haswitch -m hahost1 hahost2
Note -
Clusters with more than two nodes do not use a shared CCD. Therefore, for these clusters, you do not need to put the data services into maintenance mode before beginning the upgrade.

If your configuration includes Oracle Parallel Server (OPS), make sure OPS is halted.

Refer to your OPS documentation for instructions on halting OPS.

Stop the cluster software on the remaining nodes running the old version of Sun Cluster.
phys-hahost2# scadmin stopnode

Start the upgraded node.
phys-hahost1# scadmin startcluster phys-hahost1 sc-cluster
Note -
As the upgraded node joins the cluster, the system might report several warning messages stating that communication with the terminal concentrator is invalid. These messages are expected at this point and can be ignored safely. You can also ignore any errors generated by Sun Cluster HA for SAP at this time.

(Sun Cluster HA for SAP only) Reconfigure the SAP instance by performing the following steps.
1. Use the hareg(1M) command to turn off the Sun Cluster HA for SAP data service.
  phys-hahost1# hareg -n sap
  Note -
  It is safe to ignore any errors generated while turning off Sun Cluster HA for SAP by running hareg(1M).
2. Run the hadsconfig(1M) command to restore the Sun Cluster HA for SAP configuration parameters.
  
  Refer to Chapter 10, Installing and Configuring Sun Cluster HA for SAP, for descriptions of the new configuration parameters. Also, refer to the configuration information you saved in Step 1.
  phys-hahost1# hadsconfig
  Note -
  It is safe to ignore any errors generated by hadsconfig(1M) at this time.
3. After you set the configuration parameters, use hareg(1M) to activate the data service:
  phys-hahost1# hareg -y sap
4. Manually copy the configuration file to other nodes in the cluster by using ftp.
  
  Overwrite the Sun Cluster 2.1 configuration files with the new Sun Cluster 2.2 files.
  phys-hahost1# ftp phys-hahost2 ftp> put /etc/opt/SUNWscsap/hadsconf

If you are using a shared CCD and if you upgraded from Sun Cluster 2.0, update the shared CCD now.

Run the ccdadm(1M) command only once, on the host that joined the cluster first.
phys-hahost1# cd /etc/opt/SUNWcluster/conf phys-hahost1# ccdadm sc-cluster -r ccd.database_post_sc2.0_upgrade

If you stopped the data services previously, restart them on the upgraded node.
phys-hahost1# haswitch phys-hahost1 hahost1 hahost2
If your cluster includes Sun Cluster HA for SAP, you must explicitly unregister and re-register the data service, using the following commands. Replace the string CI_logicalhost with the name of the logical host on which the SAP central instance is installed.
phys-hahost1# hareg -n sap phys-hahost1# hareg -u sap phys-hahost1# hareg -s -r sap -h CI_logicalhost phys-hahost1# hareg -y sap

Upgrade the remaining nodes.

Repeat Step 3 through Step 14 on the remaining Sun Cluster 2.0 or Sun Cluster 2.1 nodes.

After each node is upgraded, add it to the cluster.
phys-hahost2# scadmin startnode sc-cluster

Set up and start Sun Cluster Manager.

Sun Cluster Manager is used to monitor the cluster. For instructions, see the section on Sun Cluster Manager in the chapter on Sun Cluster administration tools in the Sun Cluster 2.2 System Administration Guide.

This completes the upgrade to Sun Cluster 2.2 from Sun Cluster 2.0 or 2.1.