Sun Cluster 2.2 Software Installation Guide

4.3 Upgrading From Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2

To upgrade from Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2, you must upgrade the Sun Cluster client software on the administrative workstation or install server, and then upgrade the Sun Cluster server software on all nodes in the cluster. Use the two procedures described in "4.3.3 Performing the Upgrade".

4.3.1 Planning the Upgrade

If you are working with greater than two-node clusters, consider logical host availability when planning your upgrade. Depending on the cluster configuration, it might not be possible for all logical hosts to remain available during the upgrade process. The following configuration examples illustrate upgrade strategies that minimize downtime of logical hosts.

Two Ring (Cascade) Configuration

Table 4-1 shows a four-node cluster with four logical hosts defined. The table shows which physical nodes can master each of the four logical hosts.

To upgrade this configuration, you can remove nodes 1 and 3 from the cluster and upgrade them without losing access to any logical hosts. After you upgrade nodes 1 and 3 there will be a brief service outage while you take down nodes 2 and 4 and bring up nodes 1 and 3. Nodes 1 and 3 can then provide access to all logical hosts while nodes 2 and 4 are upgraded.

Table 4-1 Four Nodes with Four Logical Hosts


	Logical Host 1	Logical Host 2	Logical Host 3	Logical Host 4
Node 1	X	X
Node 2		X	X
Node 3			X	X
Node 4	X			X

N+1 Configuration

In an N+1 configuration, one node is the backup for all other nodes in the cluster. Table 4-2 shows the logical host distribution for a four-node N+1 configuration with three logical hosts. In this configuration, upgrade node 4 first. After you upgrade node 4, it can provide all services while nodes 1, 2, and 3 are upgraded.

Table 4-2 Three Nodes with Three Logical Hosts


	Logical Host 1	Logical Host 2	Logical Host 3
Node 1	X
Node 2		X
Node 3			X
Node 4	X	X	X

4.3.2 Using Terminal Concentrator and System Service Processor Monitoring

Sun Cluster 2.2 monitors the Terminal Concentrator (TC), or the System Service Processor (SSP) on E10000 machines, on clusters with greater than two nodes. You can use this feature if you are upgrading from Sun Cluster 2.0 to Sun Cluster 2.2. To enable it, you will need to provide the following information to the scinstall(1M) command during the upgrade procedure:

TC or SSP name(s).
IP addresses for the TC or SSP.
The root password for the TC or the user ssp password for the SSP.

Caution -

The TC and SSP passwords are required for failure fencing to work correctly in the cluster. Failure to correctly set the TC or SSP password might cause unpredictable results in the event of a node failure.

The physical port numbers to which each server is connected. This is the port number to which the serial line is connected, not the telnet(1) port number used in the /etc/serialports file. For example, if /etc/serialports defines a port connection as 5006, the physical port number is 6.
The server architecture type. For each cluster node this is either "E10000" or "other."

4.3.3 Performing the Upgrade

Use the two procedures in this section to perform the upgrade. You should also have available for reference the Sun StorEdge Volume Manager Installaton Guide.

Note -

If you want to use the Cluster Monitor to continue monitoring the cluster during the upgrade, then upgrade the server software first and the client software last. That is, first perform the procedure "4.3.5 How to Upgrade the Server Software From Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2" and then perform the procedure "4.3.4 How to Upgrade the Client Software From Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2".

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

Caution -

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.

4.3.4 How to Upgrade the Client Software From Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2

Upgrading the client software involves removing old client software packages and replacing them with new client software packages, on the administrative workstation.

Upgrading the client software includes:

Upgrading the Solaris operating environment on the administrative workstation
Removing the Sun Cluster 2.0 or 2.1 client packages from the administrative workstation
Installing the Sun Cluster 2.2 client packages on the administrative workstation
Changing the SNMP port number, if you will be using Sun Cluster SNMP

These are the detailed steps to upgrade the client software from Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2. This procedure assumes you are using an administrative workstation.

Upgrade the Solaris operating environment on the administrative workstation to Solaris 2.6 or 7.

For details, see the Solaris Advanced System Administration Guide and Chapter 2, Planning the Configuration.
1. Partition your local disk according to Sun Cluster guidelines.
  
  See Chapter 2, Planning the Configuration, for details.
2. Install Solaris patches.
  
  Check the patch database or contact your local service provider for any hardware or software patches required to run the Solaris operating environment, Sun Cluster 2.2, or your volume management software.
  
  Install any required patches by following the instructions in the README file accompanying each patch.
3. Reboot the administrative workstation.

Load the Sun Cluster 2.2 CD-ROM on the administrative workstation.

Use the Sun Cluster 2.0 or 2.1 version of scinstall(1M) to remove the 2.0 or 2.1 client software packages from the administrative workstation.

As root, invoke the Sun Cluster 2.0 or 2.1 version of scinstall(1M). Select "remove" from the scinstall(1M) menu and remove the Sun Cluster 2.0 or 2.1 client packages. The screens may vary, depending on your software version.

# /opt/SUNWcluster/bin/scinstall

 ====================================================
 	Sun Cluster package manager
 	Version: 2.1,rev 1.9

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

 ================= Package Set Selection ================

 The Sun Cluster software packages can be selected in sets,
 depending on the current state of installation

 Choose the appropriate set from the choices below:
    all	 	 	 	 	 All the client and server packages in this machine
    client	 	 	 	 	All the admin tools needed on an admin workstation
    server	 	 	 	 All the Sun Cluster packages needed on a server
 ...
 Select: [all client server] [all]: client
...

 =============== Sun Cluster Installation Manager ==================
  
 Current package set: client packages
 ...
 Choices:
    choose     Select the package set to manipulate
    install    Install the selected package sets
    remove     Remove the selected package sets
    obsolete   Remove obsolete packages
    verify     Sanity check the current installation
 ...
 Command: [choose install remove obsolete verify] [install]: remove
...
 Mode [manual automatic] [manual]: automatic

Exit the Sun Cluster 2.0 or 2.1 version of scinstall(1M).

Use the Sun Cluster 2.2 version of scinstall(1M) to install the Sun Cluster 2.2 client software packages on the administrative workstation.

From the scinstall(1M) main menu, select the client package set:

# cd /cdrom/suncluster_sc_2_2/Sun_Cluster_2_2/Sol_2.x/Tools
# ./scinstall

 ==== 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]:  3

Choose an install path for the client packages.

Normally the default location is acceptable:
What is the path to the CD-ROM image [/cdrom/cdrom0]:

Install the client packages.

Note that your packages might differ from those shown in the example.

Installing Client packages
 
 Installing the following packages: SUNWscch SUNWccon SUNWccp
 SUNWcsnmp SUNWscsdb
 
             >>>> Warning <<<<
   The installation process will run several scripts as root.  In
   addition, it may install setUID programs.  If you choose automatic
   mode, the installation of the chosen packages will proceed without
   any user interaction.  If you wish to manually control the install
   process you must choose the manual installation option.
 
 Choices:
 	manual						Interactively install each package
 	automatic						Install the selected packages with no user interaction.
 
 In addition, the following commands are supported:
    list						Show a list of the packages to be installed
    help						Show this command summary
    close						Return to previous menu
    quit						Quit the program
 
 
 Install mode [manual automatic] [automatic]:  automatic

The scinstall(1M) command now installs the client packages. After the packages have been installed, the main scinstall(1M) menu is displayed.

Verify the client installation and then quit scinstall(1M).

From the main menu, you can choose to verify the installation. Then quit to exit scinstall(1M).

============ Main Menu =================
 
 1) Install/Upgrade - Install or Upgrade Server Packages or Install Client Packages.
 2) Remove  - Remove Server or Client Packages.
 3) Verify  - Verify installed package sets.
 4) List    - List installed package sets.

 5) Quit    - Quit this program.
 6) Help    - The help screen for this menu.

 Please choose one of the menu items: [6]:  3

 ==== Verify Package Installation ==========================
 Installation
 	All  of the install										packages have been installed
 Framework
 	All  of the client										packages have been installed
 	None of the server										packages have been installed
 Communications
 	None of the SMA										packages have been installed
 ...

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 appendix on Sun Cluster SNMP management solutions in the Sun Cluster 2.2 System Administration Guide. You must stop and restart both the snmpd and smond daemons after changing the port number.

4.3.5 How to Upgrade the Server Software From Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2

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.

Upgrading the server software includes:

Stopping Sun Cluster 2.0 or 2.1 on the local host (the host to be upgraded first)
Unencapsulating the root disk if it is encapsulated
(Optional) Upgrading your operating environment to Solaris 2.6 or Solaris 7
(Optional) Upgrading your volume manager
Re-encapsulating the root disk, if it was encapsulated previously
Rebooting
Using the scinstall(1M) command to update the software packages and cluster configuration to Sun Cluster 2.2 on the local host
Installing required patches on the local host
Rebooting the local host and verifying the installation
Stopping Sun Cluster on the remote host
Starting Sun Cluster 2.2 on the host that will master the disks and data services on the local host
Repeating the upgrade steps on the remote host and verifying the upgrade

Note -

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

These are the detailed steps to upgrade the server software from Sun Cluster 2.0 or 2.1 to Sun Cluster 2.2. This example assumes an N+1 configuration using SSVM.

Stop the first node.
phys-hahost1# scadmin stopnode

If you are upgrading the operating environment and/or SSVM or CVM, run the command upgrade_start from the SSVM or CVM media.

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

If you are upgrading to Solaris 7, you must use SSVM 3.x. Refer to the Sun StorEdge Volume Manager Installaton Guide for details.

To upgrade CVM, refer to the Sun Cluster 2.2 Cluster Volume Manager Guide.

If you are upgrading the operating environment but not the volume manager, perform the following steps:
1. Remove the volume manager package.
  
  Normally, the package name is SUNWvxvm for both SSVM and CVM. For example:
  phys-hahost1# pkgrm SUNWvxvm
2. Upgrade the operating system.
  
  Refer to the Solaris installation documentation for instructions.
3. 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 removed in Step a from the Sun Cluster 2.2 CD-ROM.
  phys-hahost1# pkgadd -d CDROM_path/SUNWvxvm

If you upgraded SSVM or CVM, run the command upgrade_finish from the SSVM or CVM media.

In this example, CDROM_path is the path to the tools on the SSVM CD.
phys-hahost1# CDROM_path/Tools/scripts/upgrade_finish

Reboot the system.

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

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

phys-hahost1# cd /cdrom/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
 ...

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 a file, /var/tmp/tc_ssp_info. 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.

SC2.2 uses the terminal concentrator (or system service processor in the
 case of an E10000) for failure fencing. During the SC2.2 installation the
 IP address for the terminal concentrator along with the physical port numbers
 that each server is connected to is requested. This information can be changed 
 using scconf.

 After the upgrade has completed you need to run scconf to specify terminal
 concentrator information for each server. This will need to be done on each
 server in the cluster.

 The specific commands that need to be run are:

 scconf clustername -t <nts name> -i <nts name|IP address>
 scconf clustername -H <node 0> -p <serial port for node 0> \
         -d <other|E10000> -t <nts name>

 Repeat the second command for each node in the cluster. Repeat the first
 command if you have more than one terminal concentrator in your
 configuration.

 Or you can choose to set this up now. The information you will need is:

         +terminal concentrator/system service processor names
         +the architecture type (E10000 for SSP or other for tc)
         +the ip address for the terminal concentrator/system service
          processor (these will be looked up based on the name, you
          will need to confirm)
         +for terminal concentrators, you will need the physical
          ports the systems are connected to (physical ports
          (2,3,4... not the telnet ports (5002,...)

 Do you want to set the TC/SSP info now (yes/no) [no]?  y

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 "1.2.7 Terminal Concentrator or System Service Processor and Administrative Workstation", 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 appendix on Sun Cluster SNMP management soutions in the Sun Cluster 2.2 System Administration Guide.

Reboot the system.

Caution -
You must reboot at this time.

If your cluster is greater than two nodes and you are using a shared CCD, put all logical hosts into maintenance mode.
phys-hahost2# haswitch -m hahost1 hahost2
Note -
Greater than two-node clusters do not use a shared CCD. Therefore, for greater than two-node 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. At this point these messages are expected and can be safely ignored.

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

Upgrade the remaining nodes.

Repeat Step 2 through Step 9 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 monitoring Sun Cluster servers with Sun Cluster Manager in Chapter 2 of the Sun Cluster 2.2 System Administration Guide.

This completes the upgrade to Sun Cluster 2.2.