Virtual Switch on Teamed NICs = slow VMs?

-

 

wonder if has seen or might able suggest troubleshooting pointers.

 

i have hyper-v evaluation system. the hardware dell poweredge 2950:  2 x dual core 3.0ghz xeons, 32gm ram, 2 internal broadcom netextreme ii nics, 1 intel pro 1000 pt 4-port nic card, external sas array (dual channels, 14 disk raid 10).

 

os rtm w2k8 standard x64.  hyper-v in-the-rtm box version.

 

i have run while using 1 of internal nics system's nic , other nic virtual switch bound to.  once intel released w2k8 drivers, installed , set intel card 4 port team , created new virtual switch , bound intel team.

 

then fired vms , found vms multiple virtual nics unresponsive.  clicks take forever responded to, windows open molasses, etc.  vms respond pings though without issue (~4000 1 lost <1ms response time).

 

the vms in question using w2k8 standard x64.  (these dual nic'd vms testing exchange 2007 rollout in case curious -- ht servers, mb servers, , cas servers...)

 

these configs worked fine solo nic virtual switch.  ideas on look?  have forgotten provide useful clues?

 

thanks in advance advice or smacks upside head!

 

=== mf

 

 

generally speaking if function correctly without teaming driver present - not work teaming driver present - 99% bug teaming driver.  using standard ndis interfaces under windows our thing.

 

cheers,

ben



Windows Server  >  Hyper-V



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more