We cannot deploy any probes on the server and no metrics is appearing in MCS.
Below is the configuration
1) the robot has an IP address of 192.247.XXX.XXX
2) the NATED IP that the hub needs to communicate on is 10.70.XXX.XXX
3) the HUB IP is 10.50.XXX.XXX
In Infrastructure manager the robot shows up as 192.247.XXX.XXX and when we try to deploy configure the controller or deploy probes we get
a communication error because the hub can not communicate on 192.247.XXX.XXX
We tried setting the robotip = 10.70.XXX.XXX but we get the following error in the controller.log on loglevel 3
Jul 25 13:50:05:314  Controller: Specified IP (10.70.XXX.XXX) is not recognized as a local ip. No IP change, using 192.247.XXX.XXX
It is expected that a hub will be on the same network segment as the robot. In some cases this can not be accomplished and NAT is used.
The following three settings can be used to try and get around this issue.
local_ip_validation = yes /no
strict_ip_binding = yes / no
robotip_alias = XXX.XXX.XXX.XXX
A different combination of these might need to be tested.
To correct this issue for this client we had to do the following:
in the robot.cfg of the robot we set the following values
hubip = 10.50.XXX.XXX
robotip = 192.247.XXX.XXX
robotip_alias = 10.70.XXX.XXX
local_ip_validation = no
strict_ip_binding = no
Restart the robot watcher service.