some oi_connector alarms sent with "cs_id: 0" therefore service mapping fails in OI

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Some UIM alarm types (nas, data_engine, etc) send incorrect entity "cs_id: 0" (instead of the correct cs_id ) and therefore the alarm->service mapping doesnt work in OI + the action policy triggering neither for alarm notification.

Environment

• DX UIM 23.4.*
• oi_connector 1.56

Cause

As of oi_connector 1.56 there is a limitation for raw alarms to be mapped to the proper cs_id. 

Resolution

To Resolve this problem: 

• With oi_connector 1.56: 
  

  The "raw" alarms (alarms with cs_id = 0) can be either discarded or recieved as cs_id = 0.

  • raw alarms are discarded:  ingest_raw_alarm_to_oi = false 

  • raw alarms are received with dummy cs_id: ingest_raw_alarm_to_oi = true




• With oi_connector-1.57-20250213.134850-37.zip - We have identified a feasible approach where the cs_id can be obtained based on host parameter information available in alarm payload.
  
  Steps to apply the fix: 
  
  
  • Download the fix attached to this Article.
  • Directly deploy the 1.57-* test fix over 1.56
  • After applying the test fix, go to the OI Connector Probe configuration UI and perform Fetch Probes and readjust the probe selections made, as during the upgrade there may be a chance of probe keys number shift.
    
                                                                 

Additional Information

NOTE [Known issue]: When the close event is sent, it still might send "cs_id = 0". This will be addressed on future releases.