Some robots with CDM MCS profiles are missing CDM data in Metric Views

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

CDM profiles on various robots always remain with a "Pending" status and never change to "Active" status.
The suspect robots report to different hubs, with each hub having over 500 robots.
This issue is causing a problem where CDM QOS is not collected.

The secondary hub does not capture any errors in the CSR (configuration_reader_service) log except for the log on the Primary hub

Example of error captured on the Primary Hub CSR log for different secondary hubs:

ERROR [attach_socket, com.ca.uim.probe.mcs.readerService.robot.HubInfo] Error in refreshing robot details, hub:/DOMAINNAMEXAMPLE/<secondaryhubname>/<hubrobotname> Cause:No element found for key device_id
[attach_socket, com.ca.uim.probe.mcs.readerService.robot.HubInfo] End: Refreshing all robots on /DOMAINNAMEXAMPLE/<secondaryhubname>/<hubrobotname>/hub

Environment

DX UIM 23.4.0 through CU4

Resolution

Deploy the attached configuration_reader_service version (23.4.4.4) to all Hubs

Note: This version includes fixes to handle a higher number of robots per hub, specifically addressing instances where the getRobots callback from a secondary hub sometimes caused parsing issues.

This fix is included in DX UIM 23.4 CU6, configuration_reader_service 23.4.6