Preparing for SA upgrade

This section provides information on the following topics:

• Preparation for all upgrades to SA 10.51
• Preparing for all multimaster upgrades to SA 10.51

Preparation for all upgrades to SA 10.51

Before you upgrade a Single Core or Multimaster Core, perform the following tasks:

• Recertify the Cores if their certificates have MD5 hashing algorithms.
• Gather the correct values for the parameters shown in Core parameter values required for upgrade.
• The Core Gateways, Management Gateway and core services must be up and running.
• The core servers hosting the Model Repository and the Software Repository must have the en_US.UTF-8 locale installed. To display data from Managed Servers in various locales, the core server hosting the Global File System (OGFS) (part of the Slice Component bundle), must also have those locales installed.
• Notify SA users to cancel all scheduled Remediate Patch Policy jobs. After upgrading a Single Core or Multimaster Core to 10.51, SA users will not see their Remediate Patch Policy jobs in the Job Logs (SA Client) that ran or are scheduled to run. (By default, the data about a job is cleared from the Job Logs (SA Client) after 30 days.)

• Detach the “Python Opsware API Access” Software Policy from the Managed Servers corresponding to the Core hosts and then remediate to uninstall the policy items contained within.

  This Software Policy contains the OPSWpytwist ZIP package that should not be installed on Core hosts because the Core hosts already has the contents of this package already installed as an RPM package.
  

After the upgrade, set up the scheduled Remediate Patch Policy jobs again by using the Remediate function in the SA Client.

Preparing for all multimaster upgrades to SA 10.51

You must not proceed with a core upgrade in a Multimaster Mesh if transaction conflicts are present.

Before you upgrade a Multimaster Core to SA 10.51 ensure that there are no conflicts in the mesh. You should follow the procedures described in the SA Administering. “Viewing the State of the Multimaster Mesh - SA Client” to determine what transaction conflicts exist in the mesh, if any. If there are conflicts, follow the procedure described in the SA Administering, Resolving Mesh Conflicts - SA Client.