How to move robots to a new domain via IM
search cancel

How to move robots to a new domain via IM


Article ID: 202155


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


How to move robots to a new domain via IM


Release : 20.1 or later

Component : UIM - ROBOT


- Robot administration


How to move robots within the same domain from one hub to another.

1. Select the robot in IM
2. Choose Tools->Connect Robot...
3. Click 'Get Info'

4. Click the 'Move...' button
5. Select the hub you want to move it to
6. Click Close
7. Press F5 to refresh IM

This should work for Windows as well as Linux machines, even when the machine is on a different subnet.

You can also try this -> In the Move dialog window, Select 'Use DNS Lookup' option and specify the 'FQDN' for the destination hub and click Ok.

If you encounter an error its mostly likely due to a communication/connectivity issue. You can also login to the IM on the Primary hub or another hub and try it from there.

If you add Static addresses in the two hubs name services Tabs so that they can 'see' each other directly, this may help. For example, in the hub Name Services Tab window, for remote HubA, enter the IP for remote HubB. In HubB, enter the IP for HubA and try to move the robot once again. If none of the above suggestions work, you can manually change the robot.cfg to point the robot(s) to the new hubrobotname and hubip.

***Note that this needs to be a 'PULL' operation, in other words, you have to start in IM in the domain you want the robot to end up in.***

If you encounter an error/issue when moving robots into another domain, it is most likely a connectivity issue between hubs which is why a Named Services mapping in the hub may help. The firewall needs to be open beforehand between the hubs and robots youre trying to move.

Tip: Note that you can use the IM 'Main Pane' and select small sets of robots via Ctrl and multi-select, then Rt-click and Move them to another hub.

Additional Information

Requirements when trying to move robots between domains

1) Basic network connectivity
2) Hub Name services entries to create static routes between hubs
Hubs discover other hubs by sending out broadcast (UDP) messages. Secondary hubs that are separated from the primary hub by routers or firewalls cannot discover other hubs over UDP. Configure a static route between the hubs. Static routes can be used to connect two hubs that are in the same environment, and reside on different network subnets.
3) Ability to access/reach the robot you're trying to Move
4) Connectivity check - use ping/traceroute/tracert
5) Make sure hub<->robot communication isn't being blocked, e.g., by local/remote firewall(s)
6) Ideally, robots/hubs are resolvable via DNS especially when using the DNS 'lookup' option in the Move utility