Robot overrides the assigned IP

[Anon Anon]

In our environment a lot of our servers have multiple IP addresses and NICs. In order to ensure that NimBUS robots can communicate we sometimes need to modify the robot.cfg file and add in the specific IP address to use. I have a server that this does not work on - the controller.log shows the following error:

 

Jul 12 09:14:22:066 [1584] Controller: Specified IP (172.30.14.23) is not recognized as a local ip. No IP change, using 192.168.1.1

 

I know that the specified IP is valid and is assigned to that server. Any help would be appreciated.

 

Thanks,

Richard

[Anon Anon]

Also - this is happening right after we update the robot to 5.32 or higher. Version 3.12 seems to work just fine.

 

Thanks,

Richard

 

[Anon Anon]

Can you attach the output of this command from that server?

 

ipconfig /all

 

[Anon Anon]

E:\Applications>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : LNNT59
   Primary Dns Suffix  . . . . . . . : na.intranet.msd
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : intranet.local
                                       na.intranet.msd
                                       amwaynet

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Loopback Adapter
   Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : na.intranet.msd
   Description . . . . . . . . . . . : HP NC7781 Gigabit Server Adapter
   Physical Address. . . . . . . . . : 00-11-85-63-94-0C
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 172.30.14.23
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   Default Gateway . . . . . . . . . : 172.30.14.1
   DNS Servers . . . . . . . . . . . : 172.30.54.10
                                       172.30.54.140
   Primary WINS Server . . . . . . . : 172.30.30.66
   Secondary WINS Server . . . . . . : 172.20.4.86

 

Worked just fine in the old robot version, new robot doesn't like this config.

[Anon Anon]

Thanks for posting that output. I thought it would be good to look for anything that might make that interface or IP look different to the controller, but I see nothing.

 

If you have not already done so, I would recommend opening a support case. This may be something that requires digging into the controller logic to figure out what is happening. If someone sees this on the forum and can explain it, you can always close the case.

 

-Keith

[Anon Anon]

I made a case. I'll update if there is a resolution.

 

Thanks,

Richard

 

[Anon Anon]

Hi Richard,

 

courious if you received update/resolution from your case.  

 

I'm experiencing same issue since I've upgraded my NMS 5.11 running robot 5.32.  My issue is the main HUB is a cluster and I used to be able to have the robot (controller) bound to the VIP.  Now I get duplicate records for stuff like cdm probe data one for each node's IP depending on which side is running nimsoft at that time.  Also experiencing strange behavior hub to hub which I believe is due to static records which I had set to always be the VIP (the constant available IP)

 

Thanks,

 

Joe

[Anon Anon]

From the release note for Robot 5.30:

 

"Added validation of specified robotip against known local interfaces, with alarm and reversion to last known good ip on error. Add 'local_ip_validation = no' if you need to turn off this functionality."

 

This functionality was added because of the situation which arises if the robot is misconfigured with the ip of another robot. This would create problems which where rather difficult to track down. With the added check the misconfiguration would be immediately detected. As you can see you can turn it off to get back the old behaviour.

 

Regards, Koert

[Louis Savage]

inside robot.cfg

make the following changes.

robotip = 127.0.0.1
robotip_alias = <This will be the ip you want it show up as for communication>

Everything should work like you expect from their.