Change Manager Server Installation Problems

The following troubleshooting issues relate to the installation of Sun Management Center 3.5 and Change Manager 1.0.1 on the designated Change Manager server.

Sun Management Center Agent Cannot Communicate With the Change Manager Server After Installing a Managed Host

Description:

When you upgrade your Change Manager 1.0 server to be a Change Manager 1.0.1 server (see How to Upgrade a Change Manager 1.0 Server to Run Sun Management Center 3.5 Server Software), you might experience a problem when installing managed hosts. After you install a Solaris Flash archive on a managed host, the managed host fails to communicate with the Change Manager server.

Cause:

The custom JumpStart files that were created for the Change Manager 1.0 server are retained. So, if you install a managed host by using these old custom JumpStart files, then the Sun Management Center agent might not communicate with the Change Manager server.

This problem will occur if you change the value of the “Sun Management Center server seed” during the upgrade of the Change Manager server.

Solution:

Run Set Up for Install or changemgr setup for each managed host that you want to install. This step re-creates the custom JumpStart files for each managed host you specify.

Stale Custom JumpStart Data Not Removed When Change Manager 1.0 Server Software Is Uninstalled

Description:

If you upgrade your Change Manager 1.0 server to run Sun Management Center 3.5 server software and you do not preserve the data, then only the Change Manager 1.0 server software is uninstalled. None of the Change Manager data (the custom JumpStart data and the Change Manager repository) is removed from the Change Manager server.

Cause:

This situation occurs when Change Manager 1.0 server software is uninstalled in one of the following two ways:

• Using the es-guiinst command or the es-inst command to upgrade from Sun Management Center 3.0 to Sun Management Center 3.5

• Using the es-uninst command to uninstall Sun Management Center 3.0 server software

Solution:

Manually clean up entries in the /etc/dfs/dfstab file and in the /etc/bootparams file. Then, delete the Change Manager 1.0 repository. The directory that holds the Change Manager repository is specified by the value of the cmdataroot property in the /var/opt/SUNWsymon/cfg/ichange.cfg file.

Information About Managed Hosts and Host Groups Created by Change Manager Remains in the Topology Database Even After Change Manager Software Is Uninstalled

Description:

Managed hosts and host groups created by Change Manager appear in the Sun Management Center topology database even after Change Manager has been uninstalled and data has been discarded.

You can access these managed hosts and host groups from the Sun Management Center Console. If you reinstall Change Manager later, you can also access these managed hosts and host groups. However, you will be unable to run any Change Manager operations, such as an update, on them.

Cause:

Change Manager needs more information about managed hosts than Sun Management Center does. The information that remains in the Sun Management Center topology database must be augmented before such hosts can be fully managed by Change Manager.

Solution:

If you intend to reinstall Change Manager software, you must first update the host configuration for each of the existing managed hosts.

Update the configuration by setting all of the required host properties and by associating each managed host with a shared profile or Solaris Flash archive. Once these changes have been made, you can perform Change Manager operations on these managed hosts.

If you do not intend to reinstall Change Manager software, remove the managed hosts and host groups from the Sun Management Center topology database. You can perform this cleanup by using the Sun Management Center Console.