We have two ESX 4U1 servers running in a cluster, and decided to patch them with the latest updates. We staged all the patches and then ran the remediate task on the first of our servers. The updates installed were:
ESX400-201005401-SG
ESX400-201005402-SG
ESX400-201005403-SG
ESX400-201005404-SG
ESX400-201005405-SG
ESX400-201005406-SG
ESX400-201005407-SG
ESX400-201005408-SG
ESX400-201005409-SG
After the server rebooted, vSphere Server initiated vMotion tasks and moved three VMs to the updated ESX server. After vMotion completed, those three VMs immediately lost connection to our physical network. I checked the network adapter configuration for that server, and now all ports on its quad port NIC show a Full-Duplex gigabit connection, but are unable to observe any IP ranges. I've attached an image to this post that shows the configuration. This setup was working fine until the updates, so I don't think the NIC has failed. A consultant we work with mentioned a network driver update was amongst the updates installed. Is it possible a bug in the new drivers caused this behavior? Any other thoughts?
Also, it may be important to note that vmnic4 and vmnic5 are still able to contact the iSCSI datastores hosting our virtual machines, even though they cannot observe an IP range. It's vmnic2 and vmnic3 that are used for our Virtual Machine Network. Thanks in advance for your replies.
