Hi all, I've got a strange issue that i've been trying to resolve. Quick overview: I have a four node hv2012 cluster with four nics in each node set up with two nic teams. One team has two interfaces, one for management and one for the cluster heartbeat
network. Team two has three interfaces; one for all the vms, and the other two for interfaces on networks connecting to our SAN. Here's the problem: I create either a Win2012 or Win2008R2 virtual machine and then start the vm and change the vm nic so that
it has a static ip address instead of a DHCP address. Sometimes, when the virtual machine reboots, you can see in Hyper-v manager on the networking tab at the bottom of the screen that it gets the static ip address that its been set to, then after about 60
seconds, it gets a second ip address of 169.254.x.y, which is the DHCP Automatic Private IP Address. How can that possibly happen when you set the ip address of a nic to a static ip address? It doesn't happen after every reboot but it will happen again
after several reboots. When the 169.254.x.y address gets assigned, the machine can't ping anything until you either disable/enable the nic or reboot again. I've been up and down through the logs and network settings and i just can't figure out why this is
happening. Does anyone have any ideas about what might be causing this or what to look for? Any feedback greatly appreciated.
↧
Hyper-v 2012 VM / Strange IP Address Assignments
↧