Identify and Configure DX UIM Robot Secondary Hub settings

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

• Is there a report or query to identify which secondary hub robots are pointing to?
  
  
• Observed that some robots in the UIM environment are not explicitly configured with a secondary hub, how can I find which secondary hub is added to which robot? Is there an out of the box method? 

Environment

DX UIM 23.4.*

Cause

DX UIM does not natively parse and store the "secondary_hub" text string from local robot.cfg files into the database. The database only tracks the active connection, meaning a robot's configured-but-inactive failover destination is not visible via standard inventory tables.

Resolution

Is there a built-in SQL table or report for this? 

No. Natively, DX UIM does not parse and upload the offline secondary_hub parameter text from local robot.cfg files into database tables. The database only knows where the robot is currently talking to. 

 

Workaround 1: Use a Custom Lua Script (this is custom scripting and must be developed by the user)

To extract this data, UIM administrators typically write a Lua script in the nas probe or via the nsa (Nimsoft Script Agent) probe. The script loops through your inventory using callbacks to fetch the raw configuration of each robot's controller probe:

1. Use the gethubs callback on the primary hub to find all hubs.

2. Use the getrobots callback on those hubs to list all robot addresses.

3. Use a nimNamedRequest to issue a _get_info or get_config callback to the controller probe of each robot to query the secondary_hub section.

 

Workaround 2: Force Bulk Configuration Overrides (Broadcom Best Practice)

Because auditing many (hundresds?thousands?) of individual .cfg files via script can be time-consuming, the reccomendation is to push a Configuration-Only Package rather than trying to audit them first. If you want to guarantee all robots point to a specific secondary hub:

1. In Infrastructure Manager, go to your Archive.

2. Drag and drop a controller probe into the archive to generate a custom configuration package (e.g., robot_update_failover).

3. Right-click the new package, click Edit, and open the robot.cfx file. (right click edit)

4. Modify it so it strictly contains only your desired failover keys:

   <controller> overwrite
   secondary_domain = YourDomain
   secondary_hub = YourSecondaryHubName
   secondary_hubrobotname = YourSecondaryHubRobotName
   secondary_hubip = xxx.xxx.xxx.xxx
   secondary_hubport = 48002
   </controller>
   

5. Deploy this package to your target robots in bulk. They will adopt the secondary hub configurations instantly without you needing to manually hunt down which ones were missing it.

Additional Information

Related KB: Identify UIM Robots Connected to Failover Hubs or Missing Primary Hub Configuration