We help IT Professionals succeed at work.
Get Started

"Enable virtual LAN identification" setting and value lost after every Migration

2,426 Views
Last Modified: 2013-11-06
I have a two-node Win 2008 R2 (obviously x64) cluster hosting a number of virtual machines.  I learned long, long ago that all VM settings need to be managed from within the Failover Cluster Manager, so please don't tell me that I need to do that or sync the settings; I'm NOT making changes with the old Hyper-V Manager, which I haven't used except to create the virtual network switches when I first built the cluster months ago.

Everything was fine except that one node was prone to BSODs which Dell helped me link back to the drivers for a quad-port Broadcom NIC.  I replaced all of those with Intel quad-port NICs.  It is important to note that I did NOT make any changes to the virtual networks that already existed on each node.  Thus, as each side changed from Broadcom to Intel all I had to do was temporarily change each VM to an internal network, then rebind it to the pre-existing virtual network after creating the appropriate VLANs in the Intel config.  This allowed me to avoid having to remove and re-create the VM in the cluster to avoid the dreaded "Network Configuration Error."

The other thing I learned was that the Intel NICs require one to specify the correct VLAN ID on the VM Settings by ticking the "Enable virtual LAN identification" box and then inputting the VLAN ID.  This box was grayed out under the Broadcom NICs.

For the few weeks where I had Intel on one side and Broadcom on the other, anytime I migrated from Broadcom to Intel I had to configure this setting to give the VM connectivity.  It 'washed away' anytime a migration was done back to the host with Broadcom.

I was unconcerned as I figured once both nodes were the same it would 'stick.'  No such luck.  So today during my maint window I decided to test completely re-creating a VM in the cluster with all of the Intel VLANs and virtual switch bindings already in place.

I removed a VM from the cluster and re-created it, something I'm quite familiar with.  The VLAN ID and checkbox are still cleared whenever the VM is migrated between nodes, which is not liveable for the long run.

I am now out of ideas.  How does one configure things with Intel NICs in a Hyper-V failover cluster so that the required VLAN ID on the VM Settings doesn't disappear after every migration?
Comment
Watch Question
Commented:
This problem has been solved!
Unlock 1 Answer and 1 Comment.
See Answer
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE