UIM alarms still open after closed in DX O2
search cancel

UIM alarms still open after closed in DX O2

book

Article ID: 444773

calendar_today

Updated On:

Products

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

Issue/Introduction

Alarm closures triggered in DX OI are not being propagated back to UIM 23.4.6, leaving alarms in an open state on the UIM side despite being cleared in DX OI.
What I have to check?

Environment

DX O2 SaaS
DX O2 On premise 25x
DX UIM 23.4

Resolution

Troubleshooting - Alarms Closed in DX O2 Not Reflecting in UIM

Root Cause Analysis

The most common causes of this issue are:

  • UIM URL field in the DX O2 Southbound Gateway is empty or pointing to an unreachable address
  • OC Host Name in oi_connector is set to a private IP unreachable from DX O2 SaaS
  • DX O2 closes the alarm internally but cannot notify UIM due to connectivity failure
  • oi_connector keeps sending the alarm as UPDATED from UIM to DX O2, since the alarm remains open in UIM - creating a sync loop

Problem Flow

Step

What Happens

Status

1

DX O2 closes the alarm via Policy

CLOSED in DX O2

2

DX O2 attempts to notify UIM via Southbound Gateway

FAILURE - URL unreachable

3

Alarm remains OPEN in UIM

OPEN in UIM

4

oi_connector sends the alarm as UPDATED from UIM to DX O2

DX O2 receives UPDATED

5

DX O2 may reopen or retain the alarm - loop persists

Persistent inconsistency

Checks in the UIM Admin Console

oi_connector - OC Connection Details

  • Confirm OC Host Name is NOT a private IP address
  • Confirm HTTPS Enabled is checked when using port 443
  • Test connectivity: curl -I https://<oc-host-name>/operatorconsole_portlet/overview

oi_connector - Log Level

  • Set Log Level to 5 - Trace during troubleshooting
  • Review oi_connector.log at: Nimsoft/probes/gateway/oi_connector/
  • Search for: grep -i 'CLOSED|close|southbound' oi_connector.log

NAS probe - Auto-Operator Profiles

  • Verify that a profile is configured to receive alarm closure actions from DX O2
  • Confirm the wasp probe is active and the nisapi package is deployed

Checks in DX O2 SaaS

  • Settings -> Integrations -> Configure Gateways -> confirm UIM URL is filled in
  • Verify the UIM URL is reachable from the internet (not a private IP)
  • Manually close a UIM alarm in DX O2 and verify if it is reflected in the UIM Operator Console

Known Limitations

Limitation

Description

Workaround

Multiple UIM/Spectrum setups

Alarm actions on multiple UIM or Spectrum setups are not supported

Maintain only one UIM setup connected to DX O2

Short-lived alarms

CLOSED status may not be updated for ephemeral alarms

Enable es_enabled = true in oi_connector raw config

Private IP in OC Host Name

DX O2 SaaS cannot reach private IP addresses (10.x.x.x)

Use a public FQDN or configure DX Gateway as intermediary

Unsupported alarm types for southbound

Anomaly, prediction, and custom alarms are not sent back to UIM

Only UIM and Spectrum alarm types are supported

 

Powered by Wolken Software