Chapter 5 Upgrading Previous Versions of Sun Management Center on the Solaris Platform

This chapter describes how to upgrade Sun Management Center 3.0 software to Sun Management Center 3.6.1 on a single machine.

This chapter discusses the following topics:

• Upgrade Considerations

• Upgrading From Sun Management Center 3.0

• Upgrade from 3.5 to 3.5 Update 1

• Upgrade from 3.5 Update 1 to 3.6

• Upgrade from 3.6 to 3.6.1

---

Note –

If you do not want to migrate your Sun Management Center data, you must uninstall the existing Sun Management Center software before you can install Sun Management Center 3.6.1. To uninstall existing Sun Management Center software without saving your data, see Appendix A, Uninstalling Sun Management Center

---

Upgrade Considerations

When upgrading from any version of Sun Management Center software, the server and console layers must be upgraded first.

Sun Management Center 3.6.1 servers and consoles support previous versions of Sun Management Center agents. Consequently, Sun Management Center agents can be upgraded when time or circumstances permit.

All Sun Management Center software components should be upgraded to version 3.6.1 to take advantage of the improved monitoring and management capabilities provided by Sun Management Center 3.6.1.

---

Note –

When upgrading, make sure you use the same port number for the agent as you used in the previous installation. This advice is applicable to both an agent upgrade and a server upgrade.

---

Upgrading From Sun Management Center 3.0

As described in the following sections, Sun Management Center 3.6.1 provides several methods for upgrading the Sun Management Center 3.0 server and agent.

Upgrading the Server

You can upgrade the Sun Management Center 3.0 server to the Sun Management Center 3.6.1 using any of the following methods.

• Run the Sun Management Center 3.6.1 graphical user interface installation command es-guiinst.

• Run the Sun Management Center 3.6.1 command-line installation script es-inst.

• Uninstall Sun Management Center 3.0 and save the configuration data, then run either the Sun Management Center 3.6.1 es-guiinst command or the es-inst command.

The Sun Management Center 3.6.1 installation process detects the existing 3.0 installation and runs the Sun Management Center 3.0 es-uninst command-line script. The Sun Management Center es-uninst script gives you the option to save your Sun Management Center 3.0 data.

After you have installed Sun Management Center 3.6.1, if you saved your Sun Management Center 3.0 data the Sun Management Center 3.6.1 setup process detects the saved Sun Management Center 3.0 data and gives you the option to migrate the data to Sun Management Center 3.6.1.

To Upgrade From Sun Management Center 3.0

---

Note –

This procedure assumes that you installed Sun Management Center server in the default directory /opt. If you installed Sun Management Center in a different directory, substitute /opt with the name of the directory you specified.

---

Steps

1. Log in as root on the machine where the Sun Management Center 3.0 server is installed.

2. Stop Sun Management Center processes.

   Type the command es-stop -A. Wait until all Sun Management Center processes have been stopped.

3. Prepare the system for Sun Management Center 3.6.1 as described in Chapter 4, Preparing Systems for Sun Management Center Upgrade and Installation.

4. Upgrade the Solaris operating environment if necessary.

   If you are upgrading the Sun Management Center 3.0 server, the machine must be running either the Solaris version 8 or Solaris version 9 developer environment. For additional information, see Prerequisite Packages

   ---

   Caution –

   If you need to upgrade to Solaris version 8 or Solaris version 9, make sure you perform a Solaris upgrade. A fresh Solaris installation reformats the hard drive, which deletes your Sun Management Center 3.0 configuration data. If you perform a fresh Solaris installation, you will not be able to migrate your Sun Management Center 3.0 configuration data to Sun Management Center 3.6.1.

   ---

   1. Back up all Sun Management Center 3.0 directories.

      ---

      Tip –

      Use ufsdump to back up the Sun Management Center 3.0 directories to a different machine or backup device. usfdump preserves symbolic links.

      ---

      Sun Management Center 3.0 software is installed by default in /opt/SUNWsymon, /var/opt/SUNWsymon, and /etc/opt/SUNWsymon directories.

      • If Sun Management Center 3.0 software has been installed to non-default locations, examine the Sun Management Center 3.0 installation logs in /var/opt/SUNWsymon/install to determine where Sun Management Center 3.0 software has been installed.

      • If /var/opt/SUNWsymon/install does not contain the installation logs, or if /var/opt/SUNWsymon does not exist, you must determine where the Sun Management Center 3.0 software has been installed.

        Sun Management Center software is installed as install-path/SUNWsymon, where install-path is the parent directory hierarchy.

        For example, the Sun Management Center 3.0 core software could be installed in /export/applications/SUNWsymon. In this example, /export/applications is the install-path.

      To determine where the Sun Management Center 3.0 software has been installed, search for all SUNWsymon directories on the system as follows:

      1. Type the command pkgparam SUNWescom BASEDIR to determine the Sun Management Center 3.0 base directory. For example:

         # pkgparam SUNWescom BASEDIR /system/opt

      2. Type the command find / -name "SUNWsymon" -print to locate the Sun Management Center configuration directories.

   2. Upgrade the Solaris operating environment.

      Refer to your Solaris documentation for procedures.

   3. If necessary, restore the Sun Management Center 3.0 directories to the machine.

5. Upgrade the Sun Management Center 3.0 server to Sun Management Center 3.6.1 using any one of the following methods.

   • To upgrade to Sun Management Center 3.6.1 using es-guiinst, follow the procedures in Installing Sun Management Center.

   • To upgrade to Sun Management Center 3.6.1 using es-inst, follow the procedures in Installing Sun Management Center Using es-inst.

   • To upgrade to Sun Management Center 3.6.1 by first uninstalling the Sun Management Center 3.0 configuration data, follow the procedures in Uninstalling Sun Management Center 3.0.

Upgrade from 3.5 to 3.5 Update 1

Upgrading from Sun Management Center 3.5 to Sun Management Center 3.5 Update 1 is similar to the upgrading procedure from Sun Management Center 3.0 to Sun Management Center 3.5.

You can also upgrade from Sun Management Center 3.0 to Sun Management Center 3.5 Update 1.

On an installed, set up, and running Sun Management Center 3.5 host, do the following:

1. Run es-inst from the 3.5 Update 1 source image.

   The installation wizard automatically launches the uninstallation wizard. The script uninstalls Sun Management Center 3.5 and asks you whether to preserve the data.

2. Type y to preserve the data.

   After uninstallation of Sun Management Center 3.5 components, the new packages for Update 1 are installed. The Installer takes you to setup. The setup detects the preserved data and asks you whether or not to migrate the data.

3. Type y to migrate the data.

   The upgrade procedure is complete.

Upgrade from 3.5 Update 1 to 3.6

Upgrading from Sun Management Center 3.5 Update 1 to Sun Management Center 3.6 is similar to the upgrading procedure from Sun Management Center 3.5 to Sun Management Center 3.5 Update 1.

You can also upgrade from Sun Management Center 3.0 to Sun Management Center 3.6.

On an installed, set up, and running Sun Management Center 3.5 update 1 or 2 host, do the following:

1. Run es-inst from the 3.6 source image.

   The installation wizard automatically launches the uninstallation wizard. The script uninstalls Sun Management Center 3.5 update 1 or 2 and asks you whether to preserve the data.

2. Type y to preserve the data.

   After uninstallation of Sun Management Center 3.5 update 1 or 2 components, the new packages for 3.6 are installed. The Installer takes you to setup. The setup detects the preserved data and asks you whether or not to migrate the data.

3. Type y to migrate the data.

   The upgrade procedure is complete.

Upgrade from 3.6 to 3.6.1

Upgrading from Sun Management Center 3.6 to Sun Management Center 3.6.1 is similar to the upgrading procedure from Sun Management Center 3.5 to Sun Management Center 3.5 update 1 or 2.

You can also upgrade from Sun Management Center 3.0 to Sun Management Center 3.6.1.

On an installed, set up, and running Sun Management Center 3.6 host, do the following:

1. Run es-inst from the 3.6.1 source image.

   The installation wizard automatically launches the uninstallation wizard. The script uninstalls Sun Management Center 3.6 and asks you whether to preserve the data.

2. Type y to preserve the data.

   After uninstallation of Sun Management Center 3.6 components, the new packages for 3.6.1 are installed. The Installer takes you to setup. The setup detects the preserved data and asks you whether or not to migrate the data.

3. Type y to migrate the data.

   The upgrade procedure is complete.

Upgrading Agents

You can upgrade the Sun Management Center 3.0 agent to the Sun Management Center 3.6.1 agent using either of the following methods.

• Create an agent-only installation image on the Sun Management Center server as described in To Create an Agent-Only Installation Image Using es-makeagent. When you have created the agent-only installation image, apply the image to the agent hosts using the es-inst -a command as described in To Install Agents From an Agent-Only Installation Image Using es-inst -a.

• Create an agent-update image using either es-gui-imagetool as described in To Create an Agent-Update Image Using es-gui-imagetool, or by using es-imagetool as described in To Create an Agent-Update Image Using es-imagetool. When you have created the agent-update image, apply the image to the agent hosts using the agent-update.bin executable file as described in To Install or Update Agents From an Agent-Update Image Using agent-update.bin.