alphabanks
n00b
- Joined
- Oct 31, 2012
- Messages
- 62
I would like to bring up the topic of Hyper V networking and using nic teaming along with vlans via Windows Server 2012 R2. I come from a Vmware shop one of our sister companies is going Hyper V so I decided to read up on it. From what I've read you have to configure vlan tags on each individual vm. So I would like to ask why can't I just create a nic team in windows than create sub teams off of that? After that go into the Hyper V switch manager and create a vswitch that's attached to the sub teams nic. That way an admin does not have to go into each vm to assign a tag to a guest vm. I was reading that this is not recommended and you should tag each vm with the tag of your choice. I know that if you have a lot of vlans this would result in a lot of vswitches. However, if you are configuring management traffic or storage traffic than it's ok to use a sub team. So in short why is it not advised to use sub team interfaces with virtual switches?
These are the two articles I read also notice the comments of the Aidan Finn link. Matt was told by Aidan that he was configuring networking the wrong way.
http://blogs.technet.com/b/keithmay...-with-nic-teaming-in-windows-server-2012.aspx
http://www.aidanfinn.com/?p=10164#comment-199346
These are the two articles I read also notice the comments of the Aidan Finn link. Matt was told by Aidan that he was configuring networking the wrong way.
http://blogs.technet.com/b/keithmay...-with-nic-teaming-in-windows-server-2012.aspx
http://www.aidanfinn.com/?p=10164#comment-199346