NIC Team won't work with HyperV Switch


hi everyone,

i have server setup in test lab windows server 2012r2.  i have created switch independent nic team 3 of 4 available network cards.  this team gets dhcp address no problem.  the 4th network port have management port can gain access host.  i have installed hyperv , created 1 windows server 2012 vm.  when go in hyperv virtual switch manager , create virtual switch, bind microsoft multiplexor blah blah adapter (aka nic team).  as connect nic team lose network access team , virtual switch.  to complicate matters more, can connect virtual switch management port , switch works fine , team comes well.  i have no clue i'm doing wrong, please help.  i know both nic team , virtual switch work correctly independently, won't work together.

the way virtual switch , nic team configured:

  1. virtual switch set external , have tried both creating in powershell or gui , allowing host os , not allowing host os.
  2. the nic team set switch independent , have tried dynamic, address hash, , hyper-v port load balancing modes.

thanks or insights!

as connect nic team lose network access team , virtual switch.

i think there may conceptual issues here. as loathe self-promotion, wrote blog article explains function of hyper-v virtual switch avoid retyping same information.

the load-balancing algorithm choose has no effect on basic connectivity. switch independent should fine unless switch configured panic if mac address changes switch ports. if so, need turn option off or set proper lag , use switch dependent mode.

as basic issue, cannot communicate hyper-v virtual switch. ever. can communicate virtual adapters on it. if not choose option "share", , don't have other virtual adapters, there's nothing communicate with. if choose option "share", should copy ip settings base adapter new virtual adapter creates. however, when it's team adapter, seems doesn't happen. since intentionally setting physical adapter management purposes, there no benefit in using "share" option. if want testing purposes, ensure newly minted virtual adapter has valid ip settings.


eric siron
altaro hyper-v blog
independent blog contributor, not altaro employee. solely responsible content of posts.



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group