I cloned this server from opennebula to esxi and have tried everything. I keep getting a weird IP address starting in 41. during boot which causes the nfs mounts to time out.. eventually after the nfs mounts time out I get the correct IP

It seems like some old remnants of a network adapter are present but I cannot find anything.

This is what I am getting in the beginning of boot -

Bringing up interface eth0: Determining if ip address 41.35.176.179 is already in use for device eth0...

and then after nfs mounts time out etc..

Determining if ip address 172.16.192.85 is already in use for device eth0...

which is the correct IP

The distro and version would assist us.

I assume you had some image of a cloud based OS that you are now trying to run on a local esxi correct? Yes, clones tend to have to have settings changed to match the current hardware (even if it is virtual hardware).

We can't guess what the correct ip should be, you'd need to tell us that. Also does this boot from a nfs mount? Why is that in the question or where in the question does it exist?

This is on CentOS 6.9 and this was previously on a kvm hypervisor (opennebula) hosted here locally and I have run vmware converter to clone the vm to esxi. NFS mounts have nothing to do with the problem sorry for the confusion.

I have the same problem with some other CentOS vms I have cloned as well.

Correct IP is 172.16.192.85 I have no idea where this other 41.35.176.179 IP is coming from

Thanks

That IP may be assigned to Egypt but I can't be sure.


Clones on RH based distro's don't usually have correct nic configuration.

There are only a few places a nic could get an ip from I'd think. One is from loader. Two is some static entry and three is dhcp for the most part.

Look at loader for any settings. Look at any rc script or network config file that could be trying this.

I think it unlikely that esxi could be doing this but there may be some setting there.

Shouldn't it have been using the new naming convention for nic's?

PXE boot or router?