VMware Cloud Community
malnic
Contributor
Contributor
‎07-10-2008 06:42 AM

Using VC with a NAT'ed IP

We have ESX servers on the 10. LAN and on the 172. LAN.

The VC server is located primarily on the 10. LAN and part of the domain, and only has a 10. IP address. It has just had a 146 IP added, and the 146 IP is NAT'ed to a 172 IP.

However, i can add the ESX hosts on the 172. LAN, but after 4 minutes, they go to "not responding". If i use the VI Client and connect directly to a ESX Host on the 172. LAN, it thinks its been managed by the 146 IP, and as such tries to send traffic to the 146 IP, rather than the 172 IP.

Anybody any ideas?

0 Kudos
1 Reply
malnic
Contributor
Contributor
‎07-21-2008 03:33 AM

Ok, so i've used the vmware <managed ip></managed ip> option to tell my ESX hosts behind the firewall to use the NAT'ed IP.

However, when i reboot any of the hosts, there's a 50/50 chance it'll obtain the correct VC IP, depending on what IP i've enetered into the setting <managed ip></managed ip>.

Question is, can i manually enter this information into the vpxa.cfg file on each ESX host, then make that file Read Only? Or will things break if i set the file to read only?

0 Kudos