Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: Upgrading, Uninstalling, and Reinitializing Software on the Change Manager Server (Task Map)
- Next: Authorizing Users to Access Change Manager

# Upgrading, Uninstalling, and Reinitializing Software on the Change Manager Server

Change Manager 1.0.1 is based on Sun Management Center 3.5, while Change Manager 1.0 is based on Sun Management Center 3.0. If you have a Change Manager 1.0 server and you want to run Sun Management Center 3.5, do the following:

1. Upgrade from Sun Management Center 3.0 server software to Sun Management Center 3.5 server software.

2. Install the Change Manager 1.0.1 server software.

Procedures for performing these tasks are provided in these sections:

- How to Upgrade a Change Manager 1.0 Server to Run Sun Management Center 3.5 Server Software

- How to Install and Set Up Change Manager Server Software After an Upgrade

You can also uninstall the Sun Management Center software or the Change Manager software from the Change Manager server or from a master system. Or you can reinitialize the Change Manager database on the Change Manager server.

Procedures for performing these tasks are provided in these sections:

- How to Uninstall Sun Management Center 3.0 Software When Change Manager 1.0 Is Installed

- How to Uninstall Change Manager Software

- How to Reinitialize an Existing Change Manager Database Setup

## How to Upgrade a Change Manager 1.0 Server to Run Sun Management Center 3.5 Server Software

If you want to run Sun Management Center 3.5 but have Change Manager 1.0 installed, first upgrade Sun Management Center 3.0 to Sun Management Center 3.5. Then you can install the Change Manager 1.0.1 server software. Follow this procedure:

1. Become superuser.

2. From the SunSolveTM Patch Portal, download one of the following patches to your system.

   - If Sun Management Center 3.0 is running on a Solaris 9 system, install patch 113106-01.

   - If Sun Management Center 3.0 is running on a Solaris 8 system, install patch 113105-01.

3. Use the `unzip` command to expand the patch from the ZIP archive.

       # unzip patch-number.zip

4. Change to the patch directory.

       # cd patch-number

5. Install the patch.

       # patchadd `pwd`

6. Upgrade the Sun Management Center 3.0 Server component to the Sun Management Center 3.5 Server component.

   When you begin to install the Sun Management Center 3.5 Server component, choose to uninstall the Sun Management Center 3.0 server software.

   For more information, see the appropriate installation instructions in the Sun Management Center 3.5 Installation and Configuration Guide:

   - “To Install Sun Management Center 3.5 on the Solaris Platform”

   - “To Install Sun Management Center 3.5 Using the `es-inst` Script”

   If you preserve data during this upgrade procedure, the Change Manager 1.0 data is also preserved and can be restored.

7. Install and set up the Change Manager 1.0.1 server software.

   See How to Install and Set Up Change Manager Server Software After an Upgrade.

   If you preserved data during the Sun Management Center upgrade process, then you can restore the data when you install Change Manager 1.0.1 server software.

## How to Install and Set Up Change Manager Server Software After an Upgrade

Follow this procedure if you have just upgraded your Change Manager 1.0 server to run Sun Management Center 3.5 server software.

Note –

Though the graphical installation program and command-line installation program perform the same tasks, they might appear somewhat differently on the screen.

1. Become superuser.

2. Install the Change Manager 1.0.1 server software in one of the following ways:

   - Install the Change Manager software by using the GUI.

         # /opt/SUNWsymon/sbin/es-guiinst

   - Install the Change Manager software by using the command line.

         # /opt/SUNWsymon/sbin/es-inst

3. Specify the source directory of the Change Manager installation files.

   For example, if the directory in which you downloaded the Change Manager 1.0.1 software is called `/export/build/cm101`, then specify this directory.

   The installation program checks for add-on products to be installed.

4. Select the Change Manager product and any related patches to install.

   The Change Manager software, patches, and if necessary, the Sun Management Center Web Console packages are installed.

   After the installation completes, you are asked to run the setup.

5. Set up the Change Manager add-on product.

   The Sun Management Center components are stopped.

   Configure the add-on products only.

   The wizard checks for preserved Change Manager data from a previous Change Manager installation.

6. Specify whether to use or discard the preserved Change Manager data.

   - If you did not preserve data during the upgrade of the Sun Management Center server software, an empty database and repository are created.

   - If you preserved data, you are prompted to use the preserved data.

     - If you want to use the preserved data, then the data is restored and available.

       Go to Step 8 to specify the password used to generate security keys.

     - If you do not want to use the preserved data, then the data is removed and the database is initialized.

       Go to Step 7 to specify the location of the Change Manager repository.

7. Specify the directory in which to create the Change Manager repository.

   By default, the directory is `/var/opt/ichange`.

   The repository must be a local disk slice, which should be allocated several gigabytes of disk space. To determine the amount of space you need, estimate the number and size of the Solaris Flash archives, Solaris boot image (about 200 Mbytes each in size), manifests, and other data you plan to store in the repository.

   If `/var/opt/ichange` does not have sufficient disk space, then specify another directory that does.

8. Specify the password that was used to generate the security keys when you set up the Sun Management Center server.

   Change Manager must use the same security keys as those used by the Sun Management Center server. To do this, you must specify the same password that you supplied when you set up the Sun Management Center server software. By using the same password, identical security keys are generated.

   These security keys are used to configure the agent on the managed host after initial installation or update operations have been performed.

   The Change Manager database environment is set up.

9. Specify the directory in which to create the Change Manager database.

   By default, the directory is `/var/opt/ichange`.

   If the `/var/opt/ichange` directory does not have at least 0.5 Gbytes of available disk space, specify another directory that does.

   The Change Manager database setup is performed.

10. Specify whether to restart the Sun Management Center Web Console server.

    If you are setting up Change Manager for the first time, then you must restart the Sun Management Center Web Console server. If you do not restart it, you cannot access the Change Manager web application.

    The only time it is safe to restart the web console server is when no other users are using the web console. If you decide to wait to restart the web console server, you must restart it manually by running the `/usr/sadm/bin/smcwebserver restart` command.

    If you decide to restart the web console server now, it is restarted.

11. Start the Sun Management Center agent and server components.

    Starting the agent and server components takes a while.

After the installation completes, you can access the Change Manager user interfaces.

- To access the browser interface, see How to Log In to the Change Manager Server (Web Browser).

- To access the command-line interface, see Accessing the Change Manager Server by Using the Command-Line Interface.

## How to Uninstall Sun Management Center 3.0 Software When Change Manager 1.0 Is Installed

Systems that run Change Manager 1.0 server software must be patched before you attempt to uninstall Sun Management Center 3.0 server software.

1. Become superuser.

2. From the SunSolve Patch Portal, download one of the following patches to your system.

   - If Sun Management Center 3.0 is running on a Solaris 9 system, install patch 113106-01.

   - If Sun Management Center 3.0 is running on a Solaris 8 system, install patch 113105-01.

3. Use the `unzip` command to expand the patch from the ZIP archive.

       # unzip patch-number.zip

4. Change to the patch directory.

       # cd patch-number

5. Install the patch.

       # patchadd `pwd`

6. Uninstall the Sun Management Center 3.0 Server component.

   Use the `/opt/SUNWsymon/sbin/es-uninst` command to uninstall the Sun Management Center 3.0 server software. If you uninstall the Sun Management Center 3.0 software, the Change Manager 1.0 software is also uninstalled.

   For more information, see “Installing the Software on Your System” in the Sun Management Center 3.0 Software Installation Guide.

## How to Uninstall Change Manager Software

You can use the following procedure to uninstall the Change Manager server software or agent software. When you uninstall the software from the Change Manager server, you can specify whether to preserve or discard the Change Manager database and the Change Manager repository.

Note –

Though the graphical uninstallation program and command-line uninstallation program perform the same tasks, they might appear somewhat differently on the screen.

1. Become superuser.

2. Uninstall the Change Manager 1.0.1 software in one of the following ways:

   - Uninstall the Change Manager software by using the GUI.

         # /opt/SUNWsymon/sbin/es-guiuninst

   - Uninstall the Change Manager software by using the command line.

         # /opt/SUNWsymon/sbin/es-uninst

3. Uninstall the Change Manager product.

   If you choose to uninstall the Production Environment, then Change Manager is also uninstalled.

   - If you are uninstalling the Change Manager server software, then determine whether you want to save Change Manager data.

     - If you save Change Manager data, it can be restored.

     - If you do not save Change Manager data, then the database and the data in the repository is removed.

   - If you are uninstalling the Change Manager agent software, then continue.

4. Proceed with the uninstallation.

   The Sun Management Center processes are stopped, which might take a while. Then, the Change Manager software is uninstalled.

## How to Reinitialize an Existing Change Manager Database Setup

Follow this procedure if you want to reinitialize the Change Manager database setup you created when you first installed Change Manager 1.0.1 server software.

Note –

Though the graphical installation program and command-line installation program perform the same tasks, they might appear somewhat differently on the screen.

1. Become superuser.

2. Set up the Change Manager 1.0.1 server software in one of the following ways:

   - Set up the Change Manager software by using the GUI.

         # /opt/SUNWsymon/sbin/es-guisetup -p ichange

   - Set up the Change Manager software by using the command line.

         # /opt/SUNWsymon/sbin/es-setup -p ichange

   The Sun Management Center components are stopped.

   Configure the add-on products only.

   The wizard checks for an existing Change Manager database setup and finds one.

   - Go to Step 3 if the database is valid.

   - Go to Step 4 if the database is invalid.

3. Specify whether to use or discard the Change Manager database that was found.

   - If you want to use the database, then you are done with the Change Manager setup.

     Go to Step 9 to restart the Sun Management Center agent and server components.

   - If you do not want to use the database, then the database is reinitialized and the data is discarded.

     Go to Step 5 to specify the location of the Change Manager repository.

4. Determine what to do if an invalid database was found.

   - Try restoring the database from a backup, then rerun the check starting with Step 2.

   - If you do not want to use the database, then discard the data from the repository and reinitialize the database.

     If you choose to reinitialize the database, be sure to make a copy of the repository before it is discarded.

5. Specify the directory in which to create the Change Manager repository.

   By default, the directory is `/var/opt/ichange`.

   The repository must be a local disk slice, which should be allocated several gigabytes of disk space. To determine the amount of space you need, estimate the number and size of the Solaris Flash archives, Solaris boot image (about 200 Mbytes each in size), manifests, and other data you plan to store in the repository.

   If `/var/opt/ichange` does not have sufficient disk space, then specify another directory that does.

6. Specify the password that was used to generate the security keys when you set up the Sun Management Center server.

   Change Manager must use the same security keys as those used by the Sun Management Center server. To do this, you must specify the same password that you supplied when you set up the Sun Management Center server software. By using the same password, identical security keys are generated.

   These security keys are used to configure the agent on the managed host after initial installation or update operations have been performed.

   The Change Manager database environment is set up.

7. Specify the directory in which to create the Change Manager database.

   By default, the directory is `/var/opt/ichange`.

   If the `/var/opt/ichange` directory does not have at least 0.5 Gbytes of available disk space, specify another directory that does.

   The Change Manager database setup is performed.

8. Specify whether to restart the Sun Management Center Web Console server.

   If you are setting up Change Manager for the first time, then you must restart the Sun Management Center Web Console server. If you do not restart it, you cannot access the Change Manager web application.

   The only time it is safe to restart the web console server is when no other users are using the web console. If you decide to wait to restart the web console server, you must restart it manually by running the `/usr/sadm/bin/smcwebserver restart` command.

   If you decide to restart the web console server now, it is restarted.

9. Start the Sun Management Center agent and server components.

   Starting the agent and server components takes a while.

## How to Regenerate the Security Keys by Changing the Password

You should change the security keys periodically and when they have been compromised. For more information, see “Regenerating Security Keys” in the Sun Management Center 3.5 User's Guide.

This process requires you to make manual changes on the Change Manager server and on each managed host controlled by that server.

1. Choose a new password.

2. Update the password on the Change Manager server.

   1. Become superuser on the Change Manager server.

   2. Set the new password.

          # /opt/SUNWsymon/sbin/es_run base-usm-seed.sh -s new_seed \
          -u public

   3. Update the value of `agentseed` in the `/var/opt/SUNWsymon/cfg/ichange.cfg` file to match the new password.

   4. Restart the Sun Management Center server software on the Change Manager server.

          # /opt/SUNWsymon/sbin/es-start -A

3. Update the password on each managed host.

   1. Become superuser on the managed host.

   2. Set the new password.

          # /opt/SUNWsymon/sbin/es_run base-usm-seed.sh -s new_seed \
          -c agent -u public

   3. Restart the Sun Management Center agent on the managed host.

          # /opt/SUNWsymon/sbin/es-start -A

## Change Manager Configuration File

You can change the behavior of the Change Manager application by modifying certain runtime parameters. These parameters are stored in the application configuration file, `ichange.cfg`. The configuration file is located in the `/var/opt/SUNWsymon/cfg` directory.

Note –

When you make changes to the `ichange.cfg` file, you must restart the Sun Management Center services before the changes can take effect.

Restart the Sun Management Center services by running the following command as superuser:

    # /opt/SUNWsymon/sbin/es-start -S

For information about the parameters described by the `ichange.cfg` file, see the ichange.cfg(4CM) man page.

- Previous: Upgrading, Uninstalling, and Reinitializing Software on the Change Manager Server (Task Map)
- Next: Authorizing Users to Access Change Manager

- © 2010, Oracle Corporation and/or its affiliates