UIM - Secondary Hub keeps disconnecting without being down
search cancel

UIM - Secondary Hub keeps disconnecting without being down


Article ID: 94969


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Several secondary hubs are disconnecting and stop sending alerts, but there is no alert that the secondary hub is in a non-functional state. The VM does not go down, the robot is still running, and all probes are running within IM, but, stop receiving alerts until a force stop the nimsoft watcher service on the secondary hub is performed. Critical alerts are missed, due to this.

Monitoring for the hub has been set up per Broadcom's recommendations, but the alerts aren't triggering because the robot stops sending alerts, without actually going down.



UIM Versions  20.4.x 

hub 9.x 


For all hubs:

- set the following key in the hub section using raw config and let the hub probe restart after adding or changing: 

cache_remote_nametoip = no 

For problem hubs:

- delete the hubs.sds and robots.sds files from the hub directory 
- restart the robot from the windows service