Skip Navigation





Windows Server 2016 Hyper-V Virtual Switch loses the underlying Physical Adapter connectivity in certain deployment scenarios.

Information

 
QuestionWindows Server 2016 Hyper-V Virtual Switch loses the underlying Physical Adapter connectivity in certain deployment scenarios resulting in Hyper-V Networking issues. In particular, Hyper-V Virtual Switch with Switch Embedded Teaming deployed via SCVMM 2016 fails to communicate with the underlying Physical NIC.
Answer

Regression details

The issue started to appear with Windows Server 2016 June servicing patch (KB4022715), in which the following OS behavior was changed –

“Addressed an issue where the network interface description name of a network adapter is not updated in Hyper-V after a device driver update. Management of a NIC Team or vSwitch within Hyper-V Administrator or System Center Virtual Machine Manager may be affected”.

 

Problem Symptoms as seen in SCVMM

Hyper-V SET Virtual Switch deployed via SCVMM does not work

After SET Virtual Switch is deployed via SCVMM, and system is rebooted, the newly deployed Virtual Switch loses underlying Physical Adapters in the SET. The problem symptom is illustrated via following screenshots -

SCVMM screenshot - SET Virtual Switch displaying the underlying adapters in the team right after SET Virtual Switch creation:
User-added image

 

SCVMM screenshot - SET Virtual Switch lost the underlying adapters in the team after the Hyper-V Server is rebooted:
User-added image


 

Resolution

For the 45000/41000 series products, the fix is in VBD [qevbd] driver version v8.20.4.0.
For the BCM578xx/BCM577xx series products contact your vendor for the [evbd] driver version 7.13.115.0 or newer.

 

Attachment