UIM upgrade from 20.1 to 20.3.0 to 20.3.3

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The following issues were identified upgrading UIM 20.1 to 20.3.0 and then to 20.3.3 on a Linux 7.4 system

Environment

Release : 20.1

Component : UIM - INSTALL

Backend Database: Oracle 12g

Resolution

Issue 1:

The user owner on the nimsoft installed folder on UIM and the OC servers was automatically changed from user "apm" to user "root" with limited permissions.

Solution:

We reverted the ownership back to apm and changed the file permissions to the default to proceed with the upgrade.

Issue 2:

After upgrading UIM to 20.3.0, the data_engine probe went into error state, the error message pointed out missing Oracle Client. Upon inspection, we found out:

- the environment variables in the robot.cfg were missing

- the file permissions on the robot.cfg of Primary UIM Hub got changed and

- the file owner was changed to root

Solution:

We reverted the ownership back to apm and changed the file permissions, corrected the environment variables referring the backup of data_engine.cfg

Issue 3:

We ran into following error when upgrading OC to 20.3.0:

Preparing to install
WARNING: /tmp does not have enough disk space! Attempting to use /root for install base and tmp dir.

WARNING! The amount of /root disk space required to perform this installation is greater than what is available. Please free up at least 219835 kilobytes in /root and attempt the installation again.

Solution:

We could not understand the cause of the issue as there was enough free space in /tmp, nevertheless, we took back up and removed all the files inside /tmp directory running the commands:

cd /tmp

sudo rm -rf *

Following the above procedure, we resolved the above mentioned error

Issue 4:

The Operator Console took very long time to verify probes on the OC robot (during the upgrade to 20.3.0 and 20.3.3) as well

Solution:

Looks the backend Oracle UIM database is running in a lot of load, would suggest to please perform maintenance tasks of the backend database regularly to avoid performance issues. Please have a look at the following documents:

nas Best Practices, Tips and Techniques (for Large Environments) (broadcom.com)

Additional Information

The following are high level steps.

Step 1:

Upgrade from 20.1 to 20.3:

(Download Link: Broadcom Support Portal)

a) Upgrade Primary UIM Server from 20.1 to 20.3, run the 20.3 server installer from Primary Hub Server:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/upgrade-uim-server.html

b) Upgrade the Infrastructure Manager following:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/optional-upgrade-the-infrastructure-manager.html

c) Upgrade the secondary hubs following:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/upgrade-the-hubs.html

d) Upgrade the robots following:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/upgrade-the-robots.html

e) Configure robot.cfg as described in:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/configure-robot-cfg.html

f) Upgrade the Operator Console, run the 20.3 server installer from Primary Hub Server, following:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/upgrade-ump.html

g) Upgrade the CABI following:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/upgrade-ca-business-intelligence-with-ca-uim.html

h) Upgrade Monitoring Configuration Service Templates following:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-3-deploy-the-upgrade/upgrade-monitoring-configuration-service-templates.html

i) Post upgrade verification and configuration:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/upgrading/ca-uim-upgrade-step-4-perform-post-upgrade-verification-and-configuration.html

Step 2:

Upgrade from 20.3 to 20.3.3:

High-Level Deployment Process

(Download link: UIM Hot Fixes link )

a) Run the 20.3.3 server installer from Primary Hub Server
b) Upgrade the robots on the OC and the CABI computers to the latest version released with 20.3.3.
c) Run the OC 20.3.3 installer from Primary Hub Server
d) Upgrade the other hubs to the latest version released with 20.3.3. For more information, see the Upgrade the Hubs article.
e) Upgrade the other robots to the latest version released with 20.3.3. For more information, see the Upgrade the Robots article.

Step 3:

Upgrade from 20.3.3 to 20.3.3 HF1:

High-Level Deployment Process

Steps to apply the patches:

1. Download the patches from the below link and import the zip files into the local archive:

Broadcom Support Portal

2. Deactivate the wasp probe on the Operator Console robot.

3. Deploy the imported packages to the Operator Console robot.

4. Activate the wasp probe.

Step 4:

Upgrade from 20.3.3 HF1 to 20.3.3 June 2021 Patch:

High-Level Deployment Process

Steps to apply the patches:

1. Download the patches from the below link and import the zip files into the local archive:

Broadcom Support Portal

2. Deactivate the wasp probe on the Operator Console robot.

3. Deploy the imported packages to the Operator Console robot (MCS, MCS CLI & MCS Recon from the Mon Config Service bundle has to be deployed on Primary Hub)

4. Activate the wasp probe.

Step 5:

Update the following probes to latest hotfixes

(Download from: UIM Hot Fixes )

1. Update hub to hub_9.33_HF1 following the release notes

2. Update robot to robot_update_9.33_HF2 following the release notes

3. Update nas to nas_9.32_HF1.zip following the release notes

4. Update mon_config_service bundle to mon_config_service_20.33_HF2 following the release notes

Integration Compatibility:

Please double check the integration compatibility with other products:

Integrating Other Products (broadcom.com)

Other Important Links: