After Primary HUB Robot is restarted, we saw alarms from a device in maintenance mode.

Products

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

Issue/Introduction

• We have Robots that are currently in maintenance mode.
• When the Primary Hub server is rebooted (for example, patching) alarms coming visible for the Robots which are still in maintenance mode.
• The problem stopped automatically after a while.

Environment

• UIM any version

Cause

NAS probe acquires maintenance policy data through the maintenance_mode probe. Upon DX UIM robot watcher service restart on the Primary HUB Robot, NAS probe's first connection attempt to maintenance_mode probe fails, since NAS probe started faster than the maintenance_mode probe. NAS probe does not know current suppression policy until connection to maintenance_mode probe was restored. This is why you see alarms 'leaking' for a device that is in maintenance mode, and it automatically stops.

Resolution

1. Deactivate NAS probe prior to undergo shutdown UIM service in the Primary HUB Robot.
2. Start UIM service in the Primary HUB Robot.
3. Activate NAS probe as post-task

You could also utilize "start_after" parameter in controller.cfg to force NAS probe to start after maintenance_mode probe is fully started.

Add the following line under <alarm_enrichment> section in controller.cfg in primary HUB Robot.

start_after = maintenance_mode

With this setting, alarm_enrichment probe (and nas probe) will be started after maintenance_mode probe is fully started.