Moving a robot to a different hub, actually moves another robot.
search cancel

Moving a robot to a different hub, actually moves another robot.

book

Article ID: 385436

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When moving with Infrastructure Manager (IM) a robot to another hub we see some inconsistencies. Moving one specific robot ends up moving a different one. 

Why is this happening? 

For example, when moving robot named robot_a with ip: 192.0.2.1 from "hub1" to a different hub ("hub2"), another robot named robot_b with ip: 192.0.2.2 is actually moved  - while robot_a remains on "hub1".

robot_a's (192.0.2.1) hostname is "robot_a"

robot_b's (192.0.2.2) hostname is also "robot_a"

Environment

DX UIM 23.4.*

Cause

In the example above, the 2 robots share the hostname but they are two different devices with different IPs and different robot names. Inconsistent moving is caused by DNS resolution conflict caused by hostname vs robot. 

Resolution

To avoid this issue, if two systems share the same hostname avoid naming the robot hostname with the same name as the shared hostname.

So, rename the robot to something different from the same hostname as another server. After this, moving the robot will be consistent.