Alarms are associated with the incorrect device in Operator Console

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Alarms generated by a probe (e.g., logmon, cdm, or boot alarms) are displayed in the Operator Console (OC) under an incorrect device name or dev_id.

Example: alarms generated by logmon probe for host EXAMPLEHOST001 are showing up on SAMPLEHOST999 instead.

Environment

DX UIM 20.x, 23.4
Operator Console 
Discovery Server

Cause

This issue typically occurs due to one of the following:

• Stale Correlation: The dev_id associated with the robot is incorrect or has been duplicated due to robot cloning or hardware movement.
• Discovery Cache: The discovery_server or the local robot niscache contains obsolete or conflicting information for the hostname/IP.
• Probe Configuration: The "Update Alarm Source as Device" setting in the probe profile is resolving to a hostname that does not match a discovered device in the UIM inventory.
• Known Defect: (Logmon specific) A defect (DE657445) in logmon version 5.02 prevents correct alarm-to-device correlation.

Resolution

1. Validate Discovery
   Confirm the target device is correctly discovered.
   Search for the correct hostname in OC > Inventory.
   If the device is missing or shows incorrect metadata, run a new discovery scan for that specific IP/hostname.
2. Reset Device ID and Clear Cache
   Force the robot and discovery server to re-identify the device.
   In Infrastructure Manager or Admin Console, select the controller probe on the affected robot.
   Open the Callbacks list and execute _reset_device_id.
   Clear the robot's local cache by following the steps in KB 46393: How to clear the niscache.
   Restart the discovery_server probe on the primary hub.
3. Check Probe "Alarm Source"
   Open the probe configuration (e.g., logmon).
   Ensure the "Update Alarm Source as Device" option is configured correctly.
   Verify that the variable used (e.g., ${host}) resolves to a name recognized by the UIM Inventory.
4. Upgrade logmon (if applicable) - logmon 5.02 and prior contain a defect which can cause this issue.  Upgrade to 5.04 or higher.