Hyper-V vSwitch kills server.

I have built a 2016 server running Hyper-V, 1 NIC for data and 4 others for iSCSI.  I have setup a vswitch (no VLANs) but when I point the switch to the data network card it kills my server.  I have to remote in via iDRAC to disconnect the vswitch from that particular NIC and point it to another NIC to power it back up.  The NIC drivers are the latest versions and there doesn't seem to be a great deal of comment on the WWW about this issue or much within the KBs.  Has anybody else encountered and more importantly resolved this issue?
Andy the contractor.Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
There are no issues with binding the virtual switch to a NIC port or team.

When doing so, there is an option to "Share with the Host OS" or not. If not, then the TCP/IP stack gets pulled from the host altogether thus loss of network.

Five network ports sounds like an odd number. Probably one on-board port with a four port add-in card?

That leaves a single point of failure across several network access points.

I suggest teaming the single plus Port 0 on the add-in card then binding an External vSwitch to that team allowing the host OS to share it. That will allow for some redundancy for the VMs but not for the storage if the add-in card fails.

I suggest reading through my EE articles on Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
Andy the contractor.Author Commented:
One on-board with an add in card is correct, 2 ports on each are used for iSCSI traffic.
Once the vSwitch is bound to the data NIC the machine shuts down, it doesn't when it is bound to the other NICs but they're for iSCSI traffic only - it's a real head scratcher.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Please post the results of the following elevated PowerShell commands into a CODE snippet to make it easier to work with:

Get-VMSwitch | FL

Open in new window

SolarWinds® Network Configuration Manager (NCM)

SolarWinds® Network Configuration Manager brings structure and peace of mind to configuration management. Bulk config deployment, automatic backups, change detection, vulnerability assessments, and config change templates reduce the time needed for repetitive tasks.

Andy the contractor.Author Commented:
there are no NICs teamed - here's the output:

PS C:\Windows\system32> Get-NetAdapter

Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
----                      --------------------                    ------- ------       ----------             ---------
vEthernet (VSwitch)       Hyper-V Virtual Ethernet Adapter             40 Up           00-0A-F7-CA-A7-21         1 Gbps
SLOT 5 Port 4 - iSCSI ... Broadcom NetXtreme Gigabit Ethernet #6        6 Disabled     00-0A-F7-CA-A7-23          0 bps
SLOT 5 Port 3             Broadcom NetXtreme Gigabit Ethernet #8       13 Not Present  00-0A-F7-CA-A7-22          0 bps
SLOT 5 Port 2 - iSCSI 132 Broadcom NetXtreme Gigabit Ethernet #2       11 Up           00-0A-F7-CA-A7-21         1 Gbps
SLOT 5 Port 1 - iSCSI 131 Broadcom NetXtreme Gigabit Ethernet #5       20 Up           00-0A-F7-CA-A7-20         1 Gbps
NIC4 - Data Network (v... Broadcom NetXtreme Gigabit Ethernet           9 Up           80-18-44-F2-71-DF         1 Gbps
NIC3                      Broadcom NetXtreme Gigabit Ethernet #4       14 Not Present  80-18-44-F2-71-DE          0 bps
NIC2 - iSCSI 132          Broadcom NetXtreme Gigabit Ethernet #7        5 Up           80-18-44-F2-71-DD         1 Gbps
NIC1 - iSCSI 131          Broadcom NetXtreme Gigabit Ethernet #3       15 Up           80-18-44-F2-71-DC         1 Gbps

PS C:\Windows\system32> Get-NetLbfoTeam
PS C:\Windows\system32> Get-VMSwitch | fl

Name                                : VSwitch
Id                                  : 067bcc49-d271-4e35-9810-a2ca3f462a15
Notes                               :
Extensions                          : {Microsoft Windows Filtering Platform, Microsoft Azure VFP Switch Extension,
                                      Microsoft NDIS Capture}
BandwidthReservationMode            : Absolute
PacketDirectEnabled                 : False
EmbeddedTeamingEnabled              : False
IovEnabled                          : False
SwitchType                          : External
AllowManagementOS                   : True
NetAdapterInterfaceDescription      : Broadcom NetXtreme Gigabit Ethernet #2
NetAdapterInterfaceDescriptions     : {Broadcom NetXtreme Gigabit Ethernet #2}
IovSupport                          : False
IovSupportReasons                   : {This network adapter does not support SR-IOV.}
AvailableIPSecSA                    : 0
NumberIPSecSAAllocated              : 0
AvailableVMQueues                   : 0
NumberVmqAllocated                  : 0
IovQueuePairCount                   : 0
IovQueuePairsInUse                  : 0
IovVirtualFunctionCount             : 0
IovVirtualFunctionsInUse            : 0
PacketDirectInUse                   : False
DefaultQueueVrssEnabledRequested    : True
DefaultQueueVrssEnabled             : False
DefaultQueueVmmqEnabledRequested    : False
DefaultQueueVmmqEnabled             : False
DefaultQueueVmmqQueuePairsRequested : 16
DefaultQueueVmmqQueuePairs          : 0
BandwidthPercentage                 : 10
DefaultFlowMinimumBandwidthAbsolute : 100000000
DefaultFlowMinimumBandwidthWeight   : 0
CimSession                          : CimSession: .
ComputerName                        :Localhost
IsDeleted                           : False

PS C:\Windows\system32>
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
There are eight ports total in the server. Please do the following:

1: Plug all ports in
2: Follow the instructions in my EE article to disable Virtual Machine Queues (VMQ) for each port at the driver level
3: Create a team with Port 0 on both NICs and set the production/management IP setup there
4: Create a team with Port 1 and bind the vSwitch exclusively to that team
5: Use the four ports left over for iSCSI and MPIO
Andy the contractor.Author Commented:
VMQ is disabled at NIC and individual VM level.
Andy the contractor.Author Commented:
Philip, thanks for your help but i've fixed it with a great deal of help from here:  Hyper-V vSwitch explanation.
It transpires that the vSwitch NIC requires the IP address that was previously assigned to the data NIC which then deals with all of the traffic.  This is contrary to thinking that the data NIC passes the data to the vSwitch.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
My first post explained that? Why no points?
Andy the contractor.Author Commented:
The vSwitch NIC requires the IP address that was previously assigned to the data NIC which then deals with all of the traffic.  This is contrary to thinking that the data NIC passes the data to the vSwitch.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.