Identify UIM Robots Connected to Failover Hubs or Missing Primary Hub Configuration
Article ID: 440302
Updated On:
Products
Issue/Introduction
- Robots are appearing under a failover/secondary hub in Infrastructure Manager (IM) instead of their primary hub.
- The robot.cfg file is missing primary hub configuration details and only lists secondary hub information.
- Robots do not automatically roll back to the primary hub after a failover event.
Environment
- DX Unified Infrastructure Management (UIM) 20.4 or higher
- Robot (controller/spooler) 20.4 or higher
Cause
Robots switch to a secondary hub if the primary hub becomes unavailable. If the robot.cfg is incorrectly updated or missing the primary hub parameters, the robot remains connected to the failover hub. Additionally, if proxy_mode = 1 is enabled for firewall traversal, automatic fallback is not supported by design, requiring a manual robot restart to reconnect to the primary hub.
Resolution
Step 1: Identify Affected Robots via SQL Query
-- To list all robots across all hubs that are currently connected via failover settings:
SELECT * FROM CM_NIMBUS_ROBOT WHERE flags = 0;
-- To list robots for a specific hub (replace 'hub_name' with your target hub):
SELECT robot, hub, ip FROM CM_NIMBUS_ROBOT WHERE flags = 0 AND hub = '<hub_name>';
Step 2: Verify in Infrastructure Manager (IM)
Launch the Infrastructure Manager console.
Navigate to the specific hub identified in the query.
Review the robot list and check the Type column.
Robots currently connected via a failover/secondary hub will be displayed with the type "Temporary".
To restore the primary hub connection, ensure the following parameters are correctly configured in the robot.cfg file:
Step 3: Correct the Configuration
To restore the primary hub connection, ensure the following parameters are correctly configured in the robot.cfg file:
hubip = <primary_hub_ip_address>
If the configuration needs to be applied to multiple robots, create a Configuration-Only package in the Archive and deploy it to the target robots.
Note: If proxy_mode = 1 is set in robot.cfg, you must manually restart the robot service for the changes to take effect and for the robot to successfully reconnect to the primary hub.
Additional Information
Feedback
