C H A P T E R 4 - Preparing to Upgrade Sun Ray Server Software

C H A P T E R 4

Preparing to Upgrade Sun Ray Server Software

This chapter describes the preparations for upgrading from earlier versions of Sun Ray Server Software.

Topics in this chapter include:

Requirements

Failover Groups

Preserving Configuration Data

Unconfiguring the Sun Ray Server

Removing the Software

Requirements

You can upgrade your current Sun Ray Server Software if you have purchased a new Sun Ray Server Software 3.1 Right-to-Use license or have a Sun Ray Server Software service contract that entitles you to upgrades.

To upgrade from the earlier versions of Sun Ray Server Software, first determine whether you need to upgrade your operating system release, and perform the operating environment upgrade if necessary. See Upgrading the Operating System.

Note - If your current version is older than 2.0, you must either upgrade to 2.0 or 3.0 and then upgrade again to 3.1 or else perform a clean install. The clean install is usually preferable to upgrading twice.

Note - Before you upgrade Sun Ray Server Software, inform your users of your plans, and have them terminate their sessions. An effect of the upgrade procedure is that all active and suspended sessions are lost.

In addition, the utinstall script for SRSS 3.1 does not automatically add Sun Ray information to the crontab, syslog, PAM, and SunMC services as earlier versions did; instead, it adds them upon the first reboot after installation or upgrade.

The following table summarizes your upgrade requirements.

TABLE 4-1 Summary of Upgrade Requirements
If Upgrading the Operating System Release	If NOT Upgrading the Operating System Release
1. Preserve the configuration. Upgrading from previous releases of Sun Ray Server Software requires you to preserve the existing Sun Ray configuration manually. See Preserving Configuration Data.	1. Verify that you have installed the latest operating system patches. See Operating System Patch Requirements.
2. Run utadm -l and note the configuration for all existing Sun Ray subnetworks, then run utadm -r to unconfigure all active Sun Ray interfaces and remove all Sun Ray entries from the configuration databases.	2. Upgrade Sun Ray Server Software. See Upgrading the Sun Ray Server.
3. Unconfigure the server. Upgrading from earlier releases requires you to unconfigure the server manually. See Unconfiguring the Sun Ray Server.
4. Remove the existing Sun Ray software. See To Remove Sun Ray Server Software.
5. Upgrade the operating system. See To Upgrade the Operating System
6. Upgrade Sun Ray Server Software. See Upgrading the Sun Ray Server.

Note - It is not necessary to uninstall the current Sun Ray Server Software to perform the upgrade if you are not upgrading the operating system release.

Failover Groups

By configuring two or more Sun Ray servers in a failover group, you can reduce interruption of new service availability in the event that one server fails. If you plan to combine existing Sun Ray servers into a failover group, or to upgrade an existing failover group, please consider the following:

Before you upgrade a given server, Sun Ray DTU users should terminate their sessions.

Tip - If it is not convenient to upgrade all servers in a large configuration at once, upgrade one or two servers at a time until the entire configuration is complete.

For best results in groups of four or more servers, configure the primary server so that it serves only the Sun Ray Data Store. Configure the secondary servers so that they serve users directly in addition to serving the Data Store.

To take advantage of new features in SRSS 3.1, do not mix different Sun Ray Server Software versions within a failover group. Failover groups that use more than one software version revert to the functionality of the earliest version.

Using the Admin GUI to restart or reset Sun Ray services does not work across servers with different Sun Ray releases. For example, even if you use the Admin GUI to restart all the servers in a failover group that are running SRSS 3.1, you should still restart or reset any Sun Ray servers running earlier versions of SRSS manually. Please see the previous item.

When you configure a new server with utconfig, the Sun Ray Data Store uses port 7012 by default. When you upgrade an existing Sun Ray server, however, the 2.1 Sun Ray Data Store continues to use the old LDAP port 389, which can create port conflicts.

Tip - To avoid port conflicts, remove the old Sun Data Store product during the utinstall procedure. If you have any non-Sun Ray data stored in the Sun Data Store, back it up before upgrading the server so that you can restore the data later.

Turn off all firmware updates until all the servers in a failover group are upgraded. For instance:

# /opt/SUNWut/sbin/utfwadm -D -a -n all

Note - Even if you upgrade one or two servers per week, you must wait until all servers in the group are upgraded before you update their firmware.

If your configuration is a dedicated, private interconnect, disconnect the server from the Sun Ray interconnect.

Note - See To Configure the Sun Ray Server Hierarchy for instructions and Chapter 11 in the Sun Ray Server Software 3.1 Administrator's Guide for a more general discussion of failover groups, including diagrams of failover topologies.

To Disconnect the Sun Ray Server From the Interconnect

Caution - This procedure disconnects users from their sessions on the Sun Ray server. Make sure your users terminate their sessions before you continue.

1. As superuser, open a shell window on the Sun Ray server.

2. Disconnect the Sun Ray server from the Sun Ray interconnect:

# /opt/SUNWut/sbin/utadm -r

Tip - If you issue the signal <CTRL>C while performing utadm configuration, the Admin GUI may not function correctly the next time you invoke it. To correct this condition, type: dhtadm -R.

3. Perform one of the following tasks:

If you need to upgrade or re-install the operating system, see Preserving Configuration Data.

Otherwise, see Upgrading the Sun Ray Server.

Preserving Configuration Data

You must preserve your existing configuration before running the utinstall script if:

You are upgrading the Solaris operating environment, for instance, because you are upgrading from Sun Ray Server Software 2.0 or an earlier version.
or

You are already running Solaris 8 2/02 or later or Solaris 9 9/02 or later

If neither condition applies, go to Upgrading the Sun Ray Server.

The utpreserve script in the Sun Ray Server Software image directory preserves:

X user settings

Sun Ray Data Store

Sun Ray configuration and log files

Authentication Manager configuration files

utsettings properties

Failover group information

Note - The utpreserve script does not save all configuration files, so you must configure the Sun Ray interconnect interface, Sun Ray administration server, and SSL for the Administration Tool (optionally) after upgrading Sun Ray Server Software.

To Preserve the Sun Ray Server Configuration

If you have already mounted the Sun Ray Server Software 3.1 CD-ROM locally or from a remote server, or if you have extracted the ESD files to an image directory, begin at Step 3.

Caution - Running the utpreserve script stops all Sun Ray daemons and services, including the Sun Ray Data Store, causing users to lose all of their sessions, both active and disconnected. Please inform them of your plans.

Depending on the size of your configuration, this procedure, including the operating system software upgrade, may take anywhere from five minutes to several hours or even more to complete.

1. As superuser, open a shell window on the Sun Ray server.

2. Insert the Sun Ray Server Software 3.1 CD-ROM.

If a file manager window opens, close it. It is not necessary for installation.

3. Change to the image directory. For example:

# cd /cdrom/cdrom0

4. Preserve the Sun Ray configuration:

# ./utpreserve

The utpreserve script warns that it will stop all Sun Ray services, consequently terminating all user sessions, and asks if it should continue.

Caution - Answering y terminates all user sessions, both active and disconnected.

5. Answer y.

The utpreserve script:

Stops the Sun Ray services and the Sun Ray Data Store daemon.

Lists the files that are saved.

Tars and compresses the entire list of files as the /var/tmp/SUNWut.upgrade/preserve_version.tar.gz file, where version is the currently installed version of Sun Ray Server Software.

Ends, indicating that a log file is available at /var/adm/log/utpreserve.year_month_date_hour:minute:second.log:
where year, month, etc. are represented by numeric values reflecting the time utpreserve was started.

Tip - Be sure to check this log file for errors that are frequently overlooked.

Recommends that the /var/tmp/SUNWut.upgrade/preserve_version.tar.gz file be moved to a safe location before the operating system software upgrade.

6. Use NFS, FTP, or other means to copy the /var/tmp/SUNWut.upgrade/preserve_version.tar.gz
file to a safe location on another server.

7. Make a tape backup of the Sun Ray server's file systems.

Caution - If you have modified the /etc/pam.conffile in a previous version of Sun Ray Server Software, your changes may be lost when SRSS is upgraded to 3.1. To avoid losing your modifications, be sure to save a copy before performing the update, then use the saved copy to restore your earlier modifications.

Unconfiguring the Sun Ray Server

To upgrade Sun Ray Server Software, you must first remove the replication configuration, then unconfigure the Sun WebServer trademark .

To Unconfigure Sun Ray Server Software

1. As superuser, open a shell window on the Sun Ray server.

2. Remove the replication configuration:

# /opt/SUNWut/sbin/utreplica -u

3. Unconfigure Sun Ray Server Software:

# /opt/SUNWut/sbin/utconfig -u

4. Answer y to all the prompts.

5. Perform one of the following tasks:

To upgrade or re-install the operating system, see Upgrading the Operating System.

Otherwise, go to Upgrading the Sun Ray Server.

Removing the Software

Note - The following procedures are not required for installation or upgrade.

To Remove Sun Ray Server Software

To remove Sun Ray Server Software in its entirety, follow this procedure.

1. Log in as the superuser of the Sun Ray server.

You can log in locally or remotely use the rlogin or telnet commands.

2. Open a shell window and change to the following directory:

# cd /opt/SUNWut/sbin

3. If you are removing Sun Ray Server Software from a server in a failover group, follow steps a and b. Otherwise, skip to Step 4.

a. Disable Sun Ray DTU firmware downloads:

# ./utfwadm -D -a -n all

b. Remove the replication configuration:

# ./utreplica -u

4. Remove the Sun Ray network interface(s):

# ./utadm -r

5. Unconfigure the Sun Ray software:

# ./utconfig -u

Answer y to all of the prompts.

6. Uninstall Sun Ray Server Software:

# cd /

# /opt/SUNWut/sbin/utinstall -u

Answer y to all of the prompts.

7. Repeat the steps in this sub-section for all remaining Sun Ray servers.