MCS alarm policy for url_response probe QOS Metric associated with wrong poller

Products

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

Issue/Introduction

In certain scenarios, the alarm policy for a url_response MCS QOS metric is getttng assigned to the wrong source/poller. 

When a policy is updated (e.g., deleting one of the conditions) for a "locally hosted URL" URL Monitoring and text is modified, the update works for one server, but not for a second server which still contains multiple conditions (old and new one).

Environment

• DX UIM 23.4 CU5
• Issue also occurs in CU 1, CU2, CU3, and C4
• Fixed in DX UIM 23.4.5.1

 

Cause

• policy_management_ws defect

Resolution

With the fix attached policy_management_ws and the build (v23.4.5.1)

The following scenarios are fixed while modifying the alarm messages:

• Creating a policy condition on device X from monitoring host A (Local).
• Adding another policy condition on device X from monitoring Host B (Remote).
• Removing Condition that belongs to monitoring host A.
• Adding another policy condition on device X from monitoring Hosts A & C (Remote).
• Modifying the alarm message with out any changes to the policy conditions

Steps to deploy:

1) Download the attached fix

2) Import to the local archive

3) Deploy to the OC Server robot

Additional Information

Note: Fix requires DX UIM 23.4.5