Quantcast
Viewing all articles
Browse latest Browse all 20614

VM's Losing Network When Migrated to New ESXi Host

Ok, this has been a tough one to google (or the week has just been too long), but...

 

We have a 10 host cluster, ESXi 5.1, with SAN storage.  We also use a vSphere Distributed Switch with eleven port groups (for each vlan, management, and vMotion).  Each server has eight 1Gb physical network ports.

 

This week we replaced two of our host servers (i.e. new hardware).  I went through the normal process of building the ESXi box, network/storage config, etc.  Initially, I connected one physical NIC to a vSphere Standard Switch and then after the machine was built, added it to the dvSwitch, migrated the management connection to a virtual adapter, created the vMotion virtual adapter, etc. (the same thing that I have done several times before).

 

Because the new servers were added to the same dvSwitch as the existing servers, they automatically see the existing port groups.  The problem is that whenever I try to migrate a VM to one of the new servers, the VM loses its network link as soon as vMotion completes.  The only way for me to reconnect the VM is to either migrate it to one of the eight existing hosts or I can right click on the dvSwitch, Manage Hosts, choose the problem host, and skip through to "Migrate virtual machine networking," expand the VM to expose the network adapter, and then migrate the adapter to the proper destination port group (the SAME one that it was already assigned to).

 

This happens repeatedly.  I can then move the VM off and back onto that same host and it will continue to function.  If I go to migrate another VM (with the same port group, another port group, etc), I will have to go through the same process.  This has not happened in the past when replacing ESXi hosts.  Has anyone run across this?  Is there something that I am missing?

 

Thanks,

Jesse


Viewing all articles
Browse latest Browse all 20614

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>