Windows Server 2012 - HyperV: Best practise for Networking with SR-IOV enabled?


hi,

i have following question regarding network configuration in hyper-v:

the server has 2 dualport 1gbit/s nic's sr-iov functionality. both ports of each nic connected 2 different switches. these 2 switches connects second datacenter (2 gbit/s interlink) , server same config located.

from these 2 servers want build cluster vm.

when follow best practises hyper-v, should supply different networks: management, lan, cluster, live migration (storage san based). could use each of ports in dualport nic's different networks , have sr-iov support - correct?

now i'd more improved (fail-safe) and want use nic teaming (one team nic port connected each switch) - i have learned is if using nic teaming sr-iov not possible, correct?

so best configuration in case when sr-iov concern? (unfortunately network infrastructure bandwith limitations is predefined , not easy change)

any ideas , "real world solutions" appreciated :-)

regards,
markus

the way use sr-iov teaming have virtual adapters teamed inside guest. windows server guests, limits 2012 or higher. have break teams indicated.

unless anticipate heavy networking workloads, may more mileage out of traditional teaming on gigabit. also, sr-iov adapters provide limited number of virtual functions, make know you're buying. once you're out, you're out. can cause live/quick migration problems too. if vm actively using vf, must have available vfs @ destination or migration fail.

we had discussion microsoft field engineer it, , our decision hold off on sr-iov implementation time being. there's not yet lot of accumulated real-world data on them yet , balance of micromanagement costs against unknown of performance paybacks didn't work out in our situation. we're going team our adapters instead.

as cluster networks, should have management , live migration network. whether or not have dedicated cluster network you. more necessary in 2008 r2 redirected access common occurrence. now, cluster network isn't push other heartbeat , configuration changes. if want use sr-iov, recommendation set these networks , allow cluster network carry live migration traffic well. give failover live migration , multi-pathing cluster communications.

i'm assuming "lan" network have drawn guests? it's not technically cluster resource since hosts don't need participate in , cluster service can't control virtual switch. "vnic lan" should not exist. importance of distinction don't have isolate own subnet way have.


eric siron
http://www.altaro.com/hyper-v/



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file