Metric Views shows CDM data gaps in the report

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Several robots show CDM data gaps in Metric View reports even though the CDM probe is active.

Observed the following when data is not collected:

*Deleting the device in OC Inventory temporarily resolves the issue, but the cdm data collection stoppage reappeared after some time. 

* CDM MCS Profiles disappear for the robot

* The `qos_target` variable in the `plugin_metric.cfg` has a different robot name instead of its own.

* Executing the `get_info` controller probe callback on both robots returns the same `robot_device_id`

* The `discovery_server` log captures entries confirming that robots are using the same robot device ID. 

For example:

* `com.nimsoft.discovery.server.nimbus.scan.RobotWithDuplicateDeviceIdPruner - Ignoring robot '/MyDomain/robot1'. IP: 'xx.xx.xxx.x'.`
* `com.nimsoft.discovery.server.nimbus.scan.RobotWithDuplicateDeviceIdPruner - Ignoring robot '/MyDomain/MyHub/robot2'. IP: 'xx.xx.xxx.xx'.`
* `com.nimsoft.discovery.server.nimbus.scan.RobotWithDuplicateDeviceIdPruner - Ignoring robot '/MyDomain/MyHub/robot3'. IP: 'xx.xx.xxx.xx'.`

Environment

Any UIM version

Resolution

1. Run the `_nis_cache_clean` and `_reset_device_id_and_restart` controller probe callbacks on robots with duplicate robot IDs, following the steps in the article "How to clear the niscache on an individual robot" 

2. After the CDM MCS profiles sync completes, please confirm that the `plugin_metric.cfg` file on the robots shows the correct robot name for `qos_target`.

Additional Information

We recommend configuring UIM to automatically fix robots with duplicate devices as per the procedure outlined in "How to automatically fix missing Operator Console robots due to cloning."