Downgrade or restart all cdm probes due to unexpected alarms being generated when using cdm with MCS

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Customer needs to downgrade and/or restart all cdm probes to resolve unwanted alarm issues with cdm when using MCS

Environment

• DX UIM 23.4 CU3

Cause

Reason for unwanted alarms being generated:

• By default, when the probe is deployed on the robot, some alarms are enabled. If the corresponding metric thresholds are breached, alarms will be generated.
  
  
• However, when an MCS profile is created and deployed, those alarms are disabled, and the probe is expected to restart so it can apply the updated configuration. In the current scenario, the probe did not restart as expected, so it continued to use the old configuration and generated alarms. The issue was resolved after manually restarting the probe.

Resolution

Easily downgrade all cdm probes on a group of robots by creating an IM Infrastructure Group and populate it with your chosen robots, and that will restart the cdm probes.

If you only need to restart all or a given selection of cdm probes you can use:

1. IM->Tools->Find, probes, enter probe name, e.g., cdm

2. Using the mouse, and the SHIFT or Ctrl key, select one or more cdm probe instances

3. Then Rt-click and choose Security->Validate-> Yes to All and that will force the cdm probes to restart.