"Not able to register the metric as cs_id is not available for met_id" is found in oi_connector.log

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The following messages are found in the oi_connector.log file:

<Date/Time Stamp> [pool-7-thread-3, oi_connector] Not able to register the metric as cs_id is not available for met_id: <MetricID> 
<Date/Time Stamp> [pool-7-thread-3, oi_connector] Not able to post the metric value to NASS as either cs_id, ci_name or metric_name is not available for the record: {product=UIM, product_version=23.4.0, qosName=<qosmetric>, origin=<HubName>, ip=<IPAddress>, source=<IPAddress>, target=<TargetName>, probe=<ProbeName>, dev_id=<DevID>, robot=<RobotName>, hub=<HubName>, domain=<DomainName>, host=<HostName>, met_id=<MetricID>} 

Are these error messages and, if so, what should be done to resolve this?

Environment

• DX UIM 23.4
• oi_connector 1.*/ 2.*

Cause

These messages appear when data that is posted to DXOI fails in some specific scenario and shouldn't be consider blocking or of any concern, if there is no issue and data is synching correctly. For example, this may happen when an alarm is older than 90 days, and the oi_connector is not able to register the metric. 

Resolution

If there isn't any issue and all metrics and alarms are correctly flowing to DXO2 via the oi_connectoor probe these messages can be ignored.

These messages are informative and only appear at log level >3. 

If there is any issue or if these messages are representing any issue, open a Case with Broadcom Support. 

Additional Information

Related KB:  Not able to post the metric value to NASS messages from the hubmon probe