VMware Cloud Community
JasonGillis
Enthusiast
Enthusiast

dvSwitch uplink assignments not restored at boot

Hi all,

I'm seeing an intermittent boot issue with our ESXi 5.1 systems that causes a bit of pain sometimes.  Essentially, what happens is that when the system boots, the physical network interface to dvSwitch uplink assignments don't get restored properly.  This is especially painful when the uplinks for the management network don't get set properly, which means that the systems can't communicate with the vCenter server, meaning we have to intervene at the console and restore the mapping of the uplink to the proper vmnic.  Once that happens, the system is visible on the network again and happiness prevails.

So, has anyone seen anything like this before, or are there any suggestions on how to troubleshoot what's preventing the uplinks from being configured properly?

Thanks,

Jason

Tags (3)
Reply
0 Kudos
2 Replies
cwm08
Contributor
Contributor

Something similar happened to us. It wasn't a reboot. We were updating a vDS in preparation to add a new host. Went into vDS, edit the uplinks, add 2 new ones and boom. Calls started right away. Turns out the assignments got shuffled and vmnic-to-uplink relationship was wonky. Intervened by jumping on the hosts and resetting the mapping assignments.

Has this happened to anyone else?

Reply
0 Kudos
JasonGillis
Enthusiast
Enthusiast

I found this blog post by Shane Creech that seems to be the same issue:  Partly Cloudy with a Touch of Virtualization: Lose vmnic on vDS Uplink Configuration When ESXi Host ...

The note from VMware support that he posted suggests that a fix will be in 5.1U2.  Hopefully, that's soon.

Jason

Reply
0 Kudos