Chapter 3 Change Manager Runtime Issues

This chapter describes runtime issues that are known to be problems.

Caution Regarding Live Upgrade

Change Manager uses the Solaris Live Upgrade software to perform software update operations on managed hosts.

Do not manually run Solaris Live Upgrade commands on managed hosts outside the context of Change Manager. Doing so might result in Change Manager obtaining an inconsistent view of the state of the managed host.

Caution Regarding Add-On Agent Modules

Although the Sun Management Center base agent is required by Change Manager, add-on agent modules such as those installed for Performance Reporting Manager (PRM), System Reliability Manager (SYSRM), and Advanced System Monitoring (ASM) cannot be properly configured when deployed in Solaris Flash archives. Therefore, when building a Solaris Flash archive that is to be deployed by Change Manager, you should not install agent add-on modules because they will be unconfigured when the Solaris Flash archive is deployed to a managed host. This limitation is not expected to be present in a future version of Change Manager.

Although "Creating a Deployable Solaris Flash Archive (Tasks)" in Sun Management Center Change Manager 1.0 Administration Guide suggests installing platform agent modules on the master host prior to creating the Flash Archive, these modules also might be unconfigured when the Solaris Flash archive is deployed to a managed host. This might limit the full use of the management capabilities provided by Sun Management Center for managed hosts deployed by Change Manager. This limitation is not expected to be present in a future version of Change Manager.

Re-Initializing the Change Manager Database

The Change Manager database is dependent on the underlying Sun Management Center database. Management operations, such as running es-setup or installing add-ons such as Sun Management Center 3.0 Performance Reporting Manager (PRM), can cause the database to be reinitialized. Therefore, you must run cmsetup(1MCM) to re-establish Change Manager's database configuration.

Note that cmsetup must be run after es-setup has completed. You must also run cmsetup after installing or re-initializing the PRM add-on.