There is another Domain Controller, which is a physical machine running Windows 2008, on the network that also has DNS and DHCP running, with the same scope (different exclusions to prevent overlap) and the same devices set up as reservations. With the cables plugged in the devices themselves work normally – are ping-able on their DHCP Reservation assigned .x IP addresses, the ARP table shows the correct (non-conflicting) MAC address associated with that IP address.
If I pull the network cable on the three devices, the problem on the server goes away. Here is an interesting part – the three devices that it claims to have an IP address conflict with are all DHCP reservations in the problem server’s DCHP server configuration. Even so, with the new IP address I’ll get the same problem the next time the machine boots.Ĭhanging the IP address and then changing it back right away to the original IP sometimes temporarily fixes the problem until the next boot. This is not ideal, since the server is a DNS server I have to push out the IP address change to all the workstations.
Sometimes, that doesn’t work, but if I manually change the IP address it works. Usually, I can go on the problem server, disable and then enable the “Local Area Connection”, and it is fine until the next reboot. None of the MAC addresses are the same as the problem guest server, or the Hyper-V host server. At various times, the hardware address noted in the error belongs to one of three different devices on my network. Now, there is definitely no IP address conflict, nor is there any MAC address conflict. Network operations on this system may be disrupted as a The problem server is a domain controller, as well as DHCP and DNS server.Īlmost every time the server is rebooted, it loses network connectivity because of an IP address conflict with address 0.0.0.0.Ĭonflict for IP address 0.0.0.0 with the system having network hardware addressĠ0-1E-58-XX-XX-XX. This is a Windows 2008 R2 server running as a guest machine on a Win 2008 R2 Hyper-V host.
I'll go to the datacenter and see if the cabling is correct.I am getting an IP address conflict on one of my servers that I am unable to resolve. That explains the flapping, though it's a bit weird that the only ports mentioned in the HOSTFLAPPING-message of the 4506 are the traffic ports of ESX-004.
VMWARE MAC ADDRESS 0A 00 27 00 00 09 UPDATE
Apparently, ESX does not update its config when the NIC gets changed. After pointing this out to the VMware people, they said it might be possible that ESX-004, during installation, may have had the physical NIC that now resides in ESX-005. I only do network stuff, and I have asked the VMware guys for a text-config all the time, since I don't trust that cross-checking GUI settings between ESX'es shows us the whole truth.Īnyway, the esx.conf of ESX-004 showed me that it has the same MAC-addresses on some vmnics as ESX-005 has. I compared this to the esx.conf of two other ESX'es which behave normally, looking for differences in the config. I logged into the command line of ESX-004, and found the text file which contains the config of the ESX (/etc/vmware/esx.conf). If we power on a guest on the ESX, the ports start flapping.įinally, I found the reason for this conundrum. I can't say I trust that to be true, since comparing and verifying my 4-5 lines of config of each port is a fairly easy task to accomplish.Īll ESX'es are set up with NIC1 and NIC2 in a Virtual Switch, and the 4 traffic ports in a Distributed Virtual Switch. Switchport trunk allowed vlan add 70-73,76-79,81-91,93,95-99,199Īccording to our VMware personell, ESX-004 is configured exactly like the other ESX'es. Several IBM x3850s running VMware ESX 4.0.0 332073 are connected to the 4506 with 4 traffic ports, 2 management ports and 1 RSA port each.Īll of these ESX'es behave themselves, except one. We have a Cisco 4506 with a Supervisor V, running cat4500-ENTSERVICES-M, version 12.2(46)SG.