Alarm policies with TOT enabled auto closes alarms even though the threshold is in violation
search cancel

Alarm policies with TOT enabled auto closes alarms even though the threshold is in violation

book

Article ID: 406522

calendar_today

Updated On:

Products

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

Issue/Introduction

MCS Profiles deployed with Alarm policies and TOT enabled auto close alarms even though their threshold is in violation, and causes a scenario where an alarm is opened on the next poll.

Environment

  • DX UIM 23.4 CU3, CU4 and CU5
  • Robot: version 23.4.3, 23.4.4 and 23.4.5
  • mon_config_service (MCS)
  • nas 23.4.4
  • spooler

Cause

  • TOT not working consistently on generating alarms
  • spooler (plugin_metric)

Resolution

  1.  Download and import plugin_metric-23.4.4.1-20250814.103459-12.zip into the UIM Archive (see attached).

  2.  Distribute the plugin_metric-23.4.4.1 package to the target robot.

    ⚠️ Note: Installation will trigger an automatic restart of the robot service. Ensure a maintenance window is active if required.

  3.  Monitor TOT alarms to confirm the fix is active and the system remains stable.

A permanent fix is integrated into Robot version 23.4.6 (CU6) and all subsequent releases.

Attachments

plugin_metric-23.4.4.1-20250814.103459-12.zip get_app