VMware Cloud Community
hjv
Contributor
Contributor

vCloud assigns bogus IP's to VMs

We've had this problem since beginning that when setting a  NIC IP mode to "Static - IP Pool", vCloud seems to assign wrong and overlapping ip's to vm's when deploying. The guest customization is on and as far as I can see it does modify the /etc/sysconfig/network-scripts/ifcfg-eth0 accordingly but the problem is that it does not always match the IP that vCloud thinks.

Also it seems that some of the machines can't ping the gateway at all.

Example when deploying 9 virtual machines from template, pool 192.168.0.X

machine with configured ip .101 cannot ping gateway at all, no routing seems to work. When ssh'ing to 192.168.0.101 the connect goes to machine that vCloud informs to be .104.

Machine .108 by vCloud does not have internet connection at all. vCloud informs the IP to be .108, but ifcfg-eth0 tells it to be .102. When trying to bring the interface up it fails as there already is a .102 machine on the network.

What gives? Everything seems to be smooth otherwise but at some point it seems that vCloud is assigning the IP's randomly and not reporting them correctly. Also it's a mystery why one machine can't ping the gateway at all. All the machines are from same type of template and there is three different provider VDCs involved and this happens on random..

Also with win2008 it seems that the machine is getting their IP's from the DHCP-server, and have the ip of .18 (from DHCP pool). vCloud happily informs me that the ip is .112 (from static IP pool). It seems that the vcloud doesn't have any clue whatsoever what the actual IP address is?

Reply
0 Kudos
0 Replies