test

Sun Update Connection - Enterprise Release Notes

Chapter 2 Upgrading From Sun Aduva OnStage to Sun Update Connection – Enterprise

This chapter covers the process of upgrading a Sun Aduva OnStage 439 installation with the Sun Update Connection – Enterprise 1.0.x product.

To upgrade from Version 439 of Sun Aduva OnStage to Sun Update Connection – Enterprise 1.0.x, you must upgrade each Sun Aduva OnStage component that you have installed. Each task ensures that the software is upgraded correctly and that all applications continue to function. These tasks also ensure that you have a backup of your Sun Aduva OnStage or Sun Update Connection – Enterprise entities, if needed.

For information about known upgrade issues, see Upgrade Issues.

Note –

The upgrade process usually takes between five and ten minutes for each channel. The amount of time depends on the type of system used by the local host and the environment.

Before you begin the upgrade process, you must have a license for the new version. You must also have the relevant license and entitlements for each of the operating systems and distributions that you plan to manage. Place the new Sun Update Connection – Enterprise license file, license.lic, in an accessible directory so that you can access it during the upgrade process.

Backing Up and Upgrading From Sun Aduva OnStage to Sun Update Connection – Enterprise

ProcedureTo Back Up Your Existing Sun Aduva OnStage Installation

This procedure will back up the data from the Sun Aduva OnStage installation except for the following:

To perform the upgrade from Sun Aduva OnStage 439 to Sun Update Connection – Enterprise 1.0.x, see To Upgrade From Sun Aduva OnStage to Sun Update Connection – Enterprise.

  1. Log in as superuser on your Sun Update Connection – Enterprise system dependency server.

  2. Back up the Sun Aduva OnStage product.

    The script is a tar file of your existing Sun Aduva OnStage installation.


    # cd /usr/local/aduva/install
# ./backup.sh

    The backup.sh script performs the following steps:

    • Stops the Sun Aduva OnStage services.

    • Verifies that the local system is the SDS.

    • Saves the data in the following directories and files under backup names:

      • /usr/local/aduva/director_server/public/* – Universal rules and components

      • /usr/local/aduva/director_server/private/* – Local rules and components

      • /usr/local/aduva/director_engine/*/bin – Settings files and encryption keys

      • /usr/local/aduva/install/* – Application installers, restore scripts, and support scripts

      The databases are backed up.

      All backup files created by the script are stored in one archive and saved in /usr/local/OnStage_backup/backup-yyyy-mm-dd-hh-mm.tar.gz.

    Save a copy of this archive file for possible future use.

  3. Check the names of the categories that you created under Local.

    Make sure that all names are unique.

    For example, say that you use the following categories:

    • Local/Configuration files/test

    • Local/Macros/test

    • Local/Probes/test

    • Local/Post-Actions/test

    • Local/Pre-Actions/test

    Change the test categories to the following:

    • test_files

    • test_macros

    • test_probes

    • test_postactions

    • test_preactions

  4. Complete the following checklist for jobs in the Status window:

    1. Decide whether to stop any incomplete jobs or to run any incomplete jobs to completion.

    2. For running running jobs that have a schedule, ensure that the next time it is scheduled to run is after the upgrade completes.

    3. Make sure that idle scheduled jobs are set to next run after the upgrade.

    4. Stop the jobs that are waiting for offline hosts.

    5. Run remaining active jobs to completion.

  5. Complete the following checklist for the Consoles, APIs, CLIs and Agents:

    1. Exit all the Consoles.

    2. If a host is running the CLI or API commands, wait for the job to complete.

    3. Check that the Agent application on the managed hosts is not busy with any task.

    4. Check that the Agent application on the managed hosts is up and running.

  6. Verify that you have no running jobs before you start the upgrade.

    See the jobs listed in Step 4.

ProcedureTo Upgrade From Sun Aduva OnStage to Sun Update Connection – Enterprise

This procedure describes how to upgrade your Sun Aduva OnStage 439 installation to Sun Update Connection – Enterprise 1.0.x.

For information about known upgrade issues, see Upgrade Issues.

  1. Become superuser.

  2. Upgrade the system dependency server (SDS).

    1. Download the Sun Update Connection – Enterprise 1.0.x tar bundle, extract it to a temporary directory, and execute the ./ezInstall script.

      The ./ezInstall script starts the installation program.

    2. Follow the onscreen prompts to install the Sun Update Connection – Enterprise 1.0.x software.

    3. Back up your data.

      The following message appears:


      Older version of Sun Aduva OnStage or Sun Update Connection Enterprise detected on your system. 
It is advised you backup your data before you continue. Would you like to continue now?

      Select Yes and then press Enter to continue.

    4. Specify the full path name of the license file.

    5. Provide information to complete the upgrade.

      The ezInstall script completes the upgrade as follows:

      • Checks your connection to the SDS and configures ports.

      • Upgrades the SDS.

      • Upgrades the knowledge base and the dependency manager.

      • Prepares files for the installation of the agents, the console, the CLI, and the proxy SDS.

      When the upgrade process completes, the following message appears:


      Upgrade to Sun Update Connection Enterprise was successful. 
There are Sun Aduva OnStage directories that are no longer in use. 
Please remove them, once you have removed your private data from the following directories:
	/usr/local/aduva 
	/etc/director_server 
	/var/log/director_server

      Press Enter to exit the ezInstall script.

  3. Upgrade the console, the CLI, and the proxy SDS.

    1. Copy the console-mmdd.tar.gz file to the console system.

      • Expand the contents of the console tar file.


        # tar xPfzv console-mmdd.tar.gz

      • The uce_console directory is created.

      • Start the console installer program.


        # ./uce_console/Install

        Use -i flag to run the non-graphical, non-interactive installation, which is faster.

      The console upgrade is installed.

    2. (Optional) Repeat this procedure to install the CLI.

      The CLI tar file is called cli-mmdd.tar.gz.

    3. (Optional) Repeat this procedure to install the proxy SDS.

      The proxy SDS tar file is called proxy-mmdd.tar.gz.

    4. Start the new console by typing the uce_console command.

  4. Upgrade the agent on a Linux system.

    Perform the following steps for each Linux distribution.

    1. In the Hosts section of the Console, select a distribution.

    2. In the Components List, right-click Local/Local RPMs and choose Add from the Local menu.

      The Add Software window opens.

    3. Browse to the Agent RPM, UCE_-version-release/rpms/sun-uce-agent*.rpm.

    4. For the selected distribution, select the file that applies to the platform of the hosts.

      Select one of the following platforms:

      • .i386.rpm

      • .ia64.rpm

      • .ppc.rpm

      • .s390.rpm

    5. Click Apply.

      Wait until each of the RPMs have been successfully uploaded to the local knowledge base.

    6. Close the Add Software window.

      The Agent RPM is added to the knowledge base, but it is not visible in the Components list.

    7. Log out of the Console.

    8. Restart the Console in upgrade mode.


      # uce_console -update_director_mode true

      The login window opens.

    9. Log in as the admin user.

      The Update window opens.

    10. Update the agents for each Linux distribution.

      i. From the Hosts list, select hosts of a single distribution.

      ii. From the Distro drop-down list, select the distribution of the selected hosts.

      iii. From the Components list, select the version of the Agent that matches the updated SDS.

      iv. Click Install.

      The Installing window opens and shows the status of the installations.

      Wait until the status icon in the Installed column is a checkmark in a green circle. This process might take several minutes for each Agent.

      v. Repeat these steps for each active Linux distribution.

    11. When you have upgraded each of the agents, close the Console.

    12. Start the Console in standard mode, uce_console.

    13. Check that all Agents are up and listed as connected in the Hosts list.

    14. Back up the new Sun Update Connection – Enterprise data.


      # ./backup.sh in /usr/local/uce/install

    15. Save the backup files for both the previous version and the latest version in a safe place.

  5. Upgrade the agent on a Solaris system.

    Perform the following steps for each Solaris version.

    1. Copy the agent tar file to the managed node.

    2. Remove the agent from the managed node.


      # pkgrm ADVagent

    3. Expand the contents of the agent tar file.

    4. Change to the uce_agent directory.


      # cd uce_agent

    5. Install the Solaris agent.


      # ./Install