Hi Issac08
The above steps you've taken are correct however, we would also null the ci_metric_id and restart the discovery_server & data_engine probes - have you also done that?. If not, I would recommend trying the following for this device and if the problem still persists raise a support ticket with the requested information attached for us to investigate further.
1. Run the following for the device that does not display data (note the cs_key value as it will be used in the next step)
SELECT name,ip,origin,cs_key FROM CM_COMPUTER_SYSTEM WHERE ip = '<ip>';
2. Remove the device. Select the discovery_server probe and press Ctrl-P from your keyboard. On the probe command set select 'remove_master_devices_by_cskeys'. On the bottom of the probe utility GUI you will see the csKeys input box, place the affected device "cs_key". Press the green play button on the probe utility and it will execute the command.
3. Clear robot niscache. Within IM, navigate to the controller probe on the robot in question. Open up the probe utility. Open the Options dialog by pressing the second to the right icon. In options, select the "Expert Mode" checkbox and press OK. In the probe commandset, select "_nis_cache_clean" and press the green arrow button to run it.
4. Again, on the controller probe for the robot in question. Open the probe utility. In the probe commandset, select "_reset_device_id_and_restart" and run it.
5. In the database run the following: update s_qos_data set ci_metric_id = NULL where source = '<source_ip_address>'
6. On the primary hub increase discovery_server log level to 3 (also increase log-size), restart the discovery_server and data_engine probes.
Once all of the above is complete, go back into USM and check if the server displays any metrics. If not, please raise a support ticket and attach the discovery_server.log and _discovery_server.log. This should provide information regarding the correlation (Provide hostname and IP so we can use this when searching the logs).
Hope this helps.
Kind regards,
Ryan