Hyper-v NIC teaming, external network

http://blogs.technet.com/b/keithmayer/archive/2012/11/26/configuring-hyper-v-virtual-networking-in-w...Hello Yall's, Wanted to get some advise. I am running Server 2012r2 on the Host OS with 4 NICs... I team two of the NICs The team comes up active.1. I connect the team to a Virtual Switch in Hyper-v2 . I uncheck "Allow management operating system to share this network adapter"3. I connect a VM to this V-switchI feel like I am missing somethingProblem. Can't get no external network on the VM. Please advise.Thank u!
This topic first appeared in the Spiceworks Community

I raised this bug long ago (one year ago in fact) and it still happens today.
If you create a virtual switch, then add a management vNIC to it - there are times when you will get two hosts with the same MAC on the vNIC that was added for management.
I have seen this in my lab (and I can reproduce it at will).
Modify the entire Hyper-V MAC address pool. Or else you will have the same issue with VMs. This is the only workaround.
But yes, it is a very confusing issue.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Similar Messages

Windows Server 2012 R2 - Hyper-V NIC Teaming Issue

Hi All,
I have cluster windows server 2012 R2 with hyper-v role installed. I have an issue with one of my windows 2012 R2 hyper-v host.
The virtual machine network adapter show status connected but it stop transmit data, so the vm that using that NIC cannot connect to external network.
The virtual machine network adapter using Teamed NIC, with this configuration:
Teaming Mode : Switch Independent
Load Balance Algorithm : Hyper-V Port
NIC Adapter : Broadcom 5720 Quad Port 1Gbps
I already using the latest NIC driver from broadcom.
I found a little trick for this issue by disable one of the teamed NIC, but it will happen again.
Anyone have the same issue with me, and any workaround for this issue?
Please Advise
Thanks,

Hi epenx,
Thanks for the information .
Best Regards,
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V, NIC Teaming and 2 hosts getting in the way of each other

Hey TechNet,
After my initial build of 2 Hyper-V Core server which took me a bit of time without a domain, I started building 2 more for another site. After the initial two, setting up the new ones went very fast until I ran into a very funny issue. And I am willing
to bet it is just my luck but I am wondering if any other out there ended up with it.
So, I build these 2 new servers, create a NIC teaming on each host, add the management OS adapter, give it an IP and I can ping the world. So I went back to my station and tried to start working on these hosts but I kept getting DCed especially from one
of them. Reinstalled it and remade the NIC teaming config, just in case. Same issue
So I started pinging both of the servers and I remarked that when one was pinging, the other one tended to not answer ping anymore and vice versa. After testing the firewall and the switch and even trying to put the 2 machines on different switches, did
not help. So I thought, what the heck, let's just remove all the network config from both machine, reboot, and redo the network config. Since then no issue.
I only forgot to do one thing before removing the network configuration, I forgot to check if the MAC address on the Management OS adapters were the same. Even if it is a small chance, it can still happen (1 in 256^4 i'd say).
So to get to my question, am I that unlucky or might it have been something else ?
Enjoy your weekends

I raised this bug long ago (one year ago in fact) and it still happens today.
If you create a virtual switch, then add a management vNIC to it - there are times when you will get two hosts with the same MAC on the vNIC that was added for management.
I have seen this in my lab (and I can reproduce it at will).
Modify the entire Hyper-V MAC address pool. Or else you will have the same issue with VMs. This is the only workaround.
But yes, it is a very confusing issue.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Hyper-V NIC Team Load Balancing Algorithm: TranportPorts vs Hyper-VPorts

Hi,
I'm going to need to configure a NIC team for the LAN traffic for a Hyper-V 2012 R2 environment. What is the recommended load balancing algorithm?
Some background:
- The NIC team will deal with LAN traffic (NOT iSCSI storage traffic)
- I'll set up a converged network. So there'll be a virtual switch on top of this team, which will have vNICs configured for each cluster, live migration and management
- I'll implement QOS at the virtual switch level (using option -DefaultFlowMinimumBandwidthWeight) and at the vNIC level (using option -MinimumBandwidthWeight)
- The CSV is set up on an Equallogics cluster. I know that this team is for the LAN so it has nothing to do with the SAN, but this reference will become clear in the next paragraph.
Here's where it gets a little confusing. I've checked some of the Equallogics documentation to ensure this environment complies with their requirements as far as storage networking is concerned. However, as part of their presentation the Dell publication
TR1098-4, recommends creating the LAN NIC team with the TrasportPorts Load Balancing Algorithm. However, in some of the Microsoft resources (i.e. http://technet.microsoft.com/en-us/library/dn550728.aspx), the recommended load balancing algorithm is HyperVPorts.
Just to add to the confusion, in this Microsoft TechEd presentation, http://www.youtube.com/watch?v=ed7HThAvp7o, the recommendation (at around minute 8:06) is to use dynamic ports algorithm mode. So obviously there are many ways to do this, but which one is
correct? I spoke with Equallogics support and the rep said that their documentation recommends TransportPorts LB algorithm because that's what they've tested and works. I'm wondering what the response from a Hyper-V expert would be to this question. Anyway,
any input on this last point would be appreciated.

Gleb,
>>See Windows Server 2012 R2 NIC Teaming (LBFO) Deployment and Management for more
info
Thanks for this reference. It seems that I have an older version of this document where there's absolutely
no mention of the dynamic LBA. Hence my confusion when in the Microsoft TechEd presentation the
recommendation was to use Dynamic. I almost implemented this environment with switch dependent and Address Hash Distribution because, based on the older version of the document, this combination offered:
a) Native teaming for maximum performance and switch diversity is not required; or
b) Teaming under the Hyper-V switch when an individual VM needs to be able to transmit at rates in excess of what one team member can deliver
The new version of the document recommends Dynamic over the other two LBA. The analogy that the document
makes of TCP flows with human speech was really helpful for me to understand what this algorithm is doing. For those who will never read the document, I'm referring to this:
"The outbound loads in this mode are dynamically balanced based on the concept of
flowlets. Just as human speech has natural breaks at the ends of words and sentences, TCP flows (TCP communication streams) also have naturally
occurring breaks. The portion of a TCP flow between two such breaks is referred to as a flowlet. When the dynamic mode algorithm detects that a flowlet boundary has been encountered, i.e., a break of sufficient length has occurred in the TCP flow,
the algorithm will opportunistically rebalance the flow to another team member if apropriate. The algorithm may also periodically rebalance flows that do not contain any flowlets if circumstances require it. As a result the affinity
between TCP flow and team member can change at any time as the dynamic balancing algorithm works to balance the workload of the team members. "
Anyway, this post made my week. You sir are deserving of a beer!

Hyper-V Nic Teaming (reserve a nic for host OS)

Whilst setting up nic teaming on my host (server 2012 r2) the OS recommends leaving one nic for host management(access). IS this best practice? Seems like a waste for a nic as the host would hardly ever be accessed after initial setup.
I have 4 nics in total. What is the best practice in this situation?

Depending on if it is a single and the one and only or you build a Cluster you need some networks on your Hyper-V
at least one connection for the Host to do Management.
so in case of a single node with local disks you would create a Team with the 4 Nics and create a Hyper-V Switch with the Option checked for creating that Management OS Adapter what is a so called vNIC on that vSwitch and configure that vNIC with the needed
IP Setting etc...
If you plan a Cluster and also ISCSI/SMB for Storage Access take a look here
http://www.thomasmaurer.ch/2012/07/windows-server-2012-hyper-v-converged-fabric/
You find a few possible ways for teaming and the Switch Settings and also all needed Steps for doing a fully converged Setup via PowerShell.
If you share more Informations on you setup we can give more Details on that.

Windows Server 2012/2012R2 NIC Teaming Mode

Hi,
Question 1:
In Windows Server 2012 the following teaming mode was recommended for Hyper-V NIC teams:
Teaming mode: Switch Independent
Load balancing mode: Hyper-V Port
All Adapers Active
In a session at TechEd 2014 it was stated that Dynamic is the new recommendation for Windows Server 2012 R2. However, a Microsoft PFE stated a few weeks ago that he would still recommend Hyper-V Port for Windows Server 2012 R2. What is your opinions around
this?
Question 2:
We have a Hyper-V Failover Cluster which isn`t migrated to 2012 R2 yet, it`s running 2012. In this cluster we use Switch Independent/Hyper-V Port for the team. We also use converged networking, having 2 physical adapters bound to the NIC team, as well as
3 virtual adapters in the management OS for management, CSV and Live Migration. Recently one of the team NICs failed, and this incident also caused the cluster membership on the affected node to go offline even though the other team NIC was
connected. Is this expected behaviour? Would the behaviour be different if 2012 R2 with Dynamic mode was being used?

Hello,
As for question number 1:
For Hyper-V workload it's recommended to use Dynamic with
Switch Independent mode. Why?
This configuration will distribute the load based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm will redistribute flows to optimize team member bandwidth utilization so individual
flow transmissions may move from one active team member to another. The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets so it takes steps to minimize that possibility.
The receive side, however, will look identical to Hyper-V Port distribution. Each Hyper-V switch port’s traffic, whether bound for a virtual NIC in a VM (vmNIC) or a virtual NIC in the host (vNIC), will see all its inbound traffic arriving on a single
NIC.
This mode is best used for teaming in both native and Hyper-V environments except when:
1) Teaming is being performed in a VM,
2) Switch dependent teaming (e.g., LACP) is required by policy, or
3) Operation of a two-member Active/Standby team is required by policy.
As for question number 2:
The Switch Independent/Hyper-V Port will send packets using all active team members distributing the load based on the Hyper-V switch port number. Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port
is affinitized to exactly one team member at any point in time.
In all cases where this configuration was recommended back in Windows Server 2012 the new configuration in 2012 R2, Switch Independent/Dynamic, will provide better performance.
Microsoft recommend for a clustered Hyper-V deployment
in Windows server 2012 to use Switch Independent/Hyper-V Port as you mentioned and to configure
Hyper-V QoS that applies to the virtual switch. (Configure minimum bandwidth in
weight mode instead of in bits per second and Enable and configure QoS
for all virtual network adapters
Did you apply QoS on the Converged vSwitch after you
created the team?? However Nodes are considered down if they do not respond to 5 heartbeats. The Switch Independent/Hyper-V Port does not cause the cluster to goes down if one NIC failed. The issue is somewhere else and not in the teaming mode
that you choose.
Hope this help.
Regards,
Charbel Nemnom
MCSA, MCSE, MCS, MCITP
Blog: www.charbelnemnom.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if
a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!
http://www.youtube.com/watch?v=8mOuoIWzmdE
Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain as best I can and apologies from the start.
It’s a bit of both Hyper-v and Server 2012R2.
I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below
examples.
New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false
Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"
Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the
HostSwitchTeam for selection. When installed it shows the Microsoft Network Multiplexor Driver as the only option.
Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.
Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!
Any help would be much appreciated.
Paul
Paul Edwards

Hi P.J.E,
>>I have teams so a bit confused as to the adapter bindings and if the teams need to be added or just the vEthernet Nics?.
Nic 1,2
HostVMSwitchTeam
Nic 3,4,5
HostMgmtSwitchTeam
>>The adapter Binding settings are:
HostMgmtSwitchTeam
V-Curric
Nic 3
Nic 4
Nic 5
V-Livemigration
HostVMSwitch
Nic 1
Nic 2
V-iSCSI
V-HeartBeat
Based on my understanding of the description , "HostMgmtSwitchTeam and
HostVMSwitch " are teamed NIC .
You can think of them as two physical NICs (do not use NIC 1,2,3,4,5 any more , there are just two NICs "HostMgmtSwitchTeam and
HostVMSwitch").
V-Curric,
V-Livemigration , V-iSCSI ,
V-HeartBeat are just VNICs of host (you can change their name then check if the virtual switch name will be changed )
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V vSwitch on a NIC-Team (Server 2012 R2) has limited connectivity

Hi,
I have two servers both running Server 2012 R2. One of these servers is serving as a DC and is working fine. The other is supposed to be a Hyper-V-Host, but I cannot get networking working on this system. Both systems have Hyper-V role installed. Both have
2 NICs configured as a team. The team is configured as switch-independent, Hyper-V-Port, None (all adapters active). A Hyper-V-Switch using this team as external network is configured and is shared with the host operating system. This should work fine and
does on one of the servers. On the other I get a warning sign stating limited connectivity. The server seems to sent packages but it receives none. Deleting the switch and simply using the team for network access works fine. So it has to be related to the
switch. But I do not know what's wrong with it. Any ideas?
Regards,
Oliver

Hi ogerlach_isw,
Generally please don’t install others role on Hyper-V server, if your DC using NIC teaming, please break the teaming then monitor this issue again.
More information”
Everything you want to know about Network Teaming in Windows Server 2012
http://blogs.msdn.com/b/virtual_pc_guy/archive/2012/12/07/everything-you-want-to-know-about-network-teaming-in-windows-server-2012.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WIN2008R2: No external network access from Hyper-V guest using Virtual Machine Bus - Legacy ok

Windows Server 2008 R2 Enterprise x64 Hyper-V host
HP DL370 G6, HP NC375i integrated Quad Port Multifunction Gigabit Server Adapter
Static IP (.11), internet connection via a Cisco switch and PIX firewall
External virtual network connected to port 1, allowing management OS to share the network adapter
Windows Server 2008 R2 Enterprise x64 guest
Static IP (.21) on the same subnet, same subnet mask and default gateway (.1) as host
* with Virtual Machine Bus network adapter:
- host can ping guest (.21), switch (.5), and has internet access
- guest can ping host (.11), but cannot ping switch (.5) and has no internet access.
- network map shows the guest and host connected via a hub (Microsoft virtual switch), connected to a gateway, then a red X between gateway and internet
* with Legacy network adapter:
- host can ping guest (.21), switch (.5), and has internet access
- guest can ping host (.11), switch (.5) and has internet access.
- network map shows the guest and host connected via a hub (Microsoft virtual switch), connected to a gateway, and no red X between gateway and internet
I installed Hyper-V before adding the HP network drivers (there's a known problem if you install Hyper-V after adding the network drivers), so that's not it.
This happens both with straight network adapters, and also when two are configured as a network team - no difference.
I don't want to use the Legacy network adapter as the performance is terrible, but right now I have no choice as otherwise I can't get network or internet access from the guest.
Any ideas?

Hi,
Please refer to the following post to see whether you can resolve the issue.
Network Adapter (not Legacy) does not work on Virtual Machine after installation through ISO
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/b1e9d24c-e298-472e-ad72-90cf079f6fbd
By the way, did you only encounter this issue with one VM or all VMs? Please do the same test on VMs with other version of Windows such as Windows Server 2008 or Windows Server 2003.
Best Regards,
Vincent Hu

Nic Team network speed

Hello!
There're two physical servers (Hyper-V is not installed) with two nic teams, each consisting of two 1Gb nics:
To test these teams I tried to copy two files from server1 to server2:
1) I started copying the first file and ~20 sec later started copying the second file to the same SSD (from server1 to server2)
2) I copied ~simultaneously two different files to the two different SSDs (from server1 to server2)
As shown in the picture 1 when I added the second copying the first one had stopped completely, although this SSD can tolerate transfer rate up to 350-380MBps.
Both pictures show that the total file transfer speed was less than that of a single team member (1Gbps):
0+112MBps < 1Gbps
57.1 MBps + 56.5MBps < 1Gbps
According to http://technet.microsoft.com/en-us/library/hh831648.aspx
NIC Teaming, also known as load balancing and failover (LBFO), allows multiple network adapters on a computer to be placed into a team for the following purposes:
Bandwidth aggregation
Traffic failover to prevent connectivity loss in the event of a network component failure
Test1 and Test2 show no bandwith aggregation... Are my tests wrong?
Thank you in advance,
Michael

P.S. In a production network it means users would read data from servers using the total amount of a team's bandwidth but write data using the bandwidth of a single team member - that's not I would ever like to have in my network.
And once again: http://technet.microsoft.com/en-us/library/hh831648.aspx
Traffic distribution algorithms
NIC Teaming in Windows Server 2012 supports the following traffic distribution methods:
Hashing. This algorithm creates a hash based on components of the packet, and then it assigns packets that have that hash value to one of the available network adapters. This keeps all packets from the same TCP stream on the
same network adapter. Hashing alone usually creates balance across the available network adapters. Some NIC Teaming solutions that are available on the market monitor the distribution of the traffic and reassign specific hash values to different
network adapters in an attempt to better balance the traffic. The dynamic redistribution is known as smart load balancing or adaptive load balancing.
The components that can be used as inputs to the hashing function include:
Source and destination MAC addresses
Source and destination IP addresses, with or without considering the MAC addresses (2-tuple hash)
Source and destination TCP ports, usually used along with the IP addresses (4-tuple hash)
I don't see in this explanation any reason for not creating balance when the sourses are different but the destination is the same...
Regards,
Michael

Can you use NIC Teaming for Replica Traffic in a Hyper-V 2012 R2 Cluster

We are in the process of setting up a two node 2012 R2 Hyper-V Cluster and will be using the Replica feature to make copies of some of the hosted VM's to an off-site, standalone Hyper-V server.
We have planned to use two physical NIC's in an LBFO Team on the Cluster Nodes to use for the Replica traffic but wanted to confirm that this is supported before we continue?
Cheers for now
Russell

Sam,
Thanks for the prompt response, presumably the same is true of the other types of cluster traffic (Live Migration, Management, etc.)
Cheers for now
Russell
Yep.
In our practice we actually use converged networking, which basically NIC-teams all physical NICs into one pipe (switch independent/dynamic/active-active), on top of which we provision vNICs for the parent partition (host OS), as well as guest VMs.
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

Hyper-V cluster validation report "Found duplicate physical address" on nic team interfaces.

I recently built a Windows 2012 Hyper-V cluster with 5 nodes. The validation report shows “duplicate physical address” error (error text pasted below).
The hardware: HP BladeSystem – servers are BL460c blades, in a c7000 enclosure, connected to HP Virtual Connect switches.
Each server has 2 physcal nics, teamed in Windows. In the NIC Teaming console, I created the following Team Interfaces and assigned each a VLAN ID:
“Team1” (the default team)
“Team1 - VLAN 204 – Management”
“Team1 - VLAN 212 - 2012HB”
“Team1 - VLAN 211 -Exchange DAG Replication”
I also created 2 HV Virtual Switches. Neither one allows management interface to share. They are assigned to “Team1” and “Team1 - VLAN 211 -Exchange DAG Replication” respectively.
Therefore, in Network Connection, I see the 2 physical Ethernet nics, and 4 “virtual” nics. Only 2 of them have IP addresses assigned: Management and HB. These are the two that the validation wizard complains
about.
The MAC address is not configurable in the NIC Teaming console, so I don’t see a way to resolve this error, except to use separate physical nics. I don’t want to do that because a) I would lose the benefits of
the bandwidth aggregation that Virtual Connect provides, and b) When creating an Interface on a Team in Windows, it looks like it ALWAYS gives it the same MAC address, so that should be a supported configuration.
Everything works just fine, and there are no other errors or IP conflicts or anything else. But I really want to fix it because I don’t know what unknown problems this may be causing.
From the Cluster Validation report:
Found duplicate physical address 10-60-4B-A9-4A-30 on node Cluster201.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster201.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address F0-92-1C-13-3C-2C on node Cluster202.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster202.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C1-7E-9C on node Cluster210.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster210.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 3C-4A-92-DE-1E-74 on node Cluster211.OurDomain.local adapter VC-Team - VLAN 212 - 2012HB and node Cluster211.OurDomain.local adapter
VC-Team - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C0-3D-50 on node Cluster212.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster212.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Thanks!
Dan

Hi Dan,
"It turns out that both hosts had the same default MAC address ranges for their virtual switches. Since the host vNICs were attached to the virtual switch on each host they received the first couple of MAC addresses from the switches.
For details please refer to following link:
http://www.jefflafr.com/blog/4/19/2013/conflicting-mac-addresses-when-building-a-hyper-v-cluster-with-converged-networking
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

NIC Teaming for hyper-v serve.

I have installed windows server 2012 r2 on server. Server is having network adapters i have given static ip address to both nic's
LAN1: - 192.168.0.100 & LAN2: - 192.168.0.101 after enabling NIC Teaming server have added one more adapter called
"Network Adapter Multiplexor" after this above mentioned ip address are not responding to PING or any requests. Then i have given
192.168.0. 102 ip address to Multiplexor and its started working.
So my question do i need to give ip address to LAN1 &
LAN2 or i can just create team and give ip address to Multiplexor
Also if i installed hyper-v server on it will it give me failover thing for this machine.????
Akshay Pate

Hello Akshay,
In brief, after creating the Teaming adapter (Multiplexor) you'll use it's address for future networking purposes.
Regarding the lack of ping, I had the same "issue" and it seems like is block by the Microsoft code itself. Still couldn't find how to allow it.
When digging into W2k12(&R2) NIC Teaming this two pages were very explanative and usefull:
Geek of All Trades: The Availability Answer (by Greg Shields)
Windows server 2012 Hyper-V 3.0 network virtualization (if you need more technical detail)
Hope it helps!

NIC teaming and Hyper-V switch recommendations in a cluster

HI,
We’ve recently purchased four HP Gen 8 servers with a total of ten NICS to be used in a Hyper-V 2012 R2 Cluster
These will be connecting to ISCSI storage so I’ll use two of the NICs for the ISCSI storage connection.
I’m then deciding between to options.
1. Create one NIC team, one Extensible switch and create VNics for Management, Live Migration and CSV\Cluster - QOS to manage all this traffic. Then connect my VMs to the same switch.
2. Create two NIC teams, four adapters in each. Use one team just for Management, Live Migration and CSV\Cluster VNics - QOS to manage all this traffic.
Then the other team will be dedicated just for my VMs.
Is there any benefit to isolating the VMs on their own switch?
Would having two teams allow more flexibility with the teaming
configurations I could use, such as using Switch Independent\Hyper-V Port mode for the VM team? (I do need to read up on the teaming modes a little more)
Thanks,

I’m not teaming the ISCSI adapters. These would be configured with MPIO.
What I want to know,
Create one NIC team, one Extensible switch and create VNics for Management, Live Migration and CSV\Cluster - QOS to manage all this traffic. Then connect
my VMs to the same switch.
http://blogs.technet.com/b/cedward/archive/2014/02/22/hyper-v-2012-r2-network-architectures-series-part-3-of-7-converged-networks-managed-by-scvmm-and-powershell.aspx
What are the disadvantages to having this configuration?
Should RSS be disabled on the NICs in this configuration with DVMQ left enabled?
After reading through this post, I think I’ll need to do this.
However, I’d like to understand this a little more.
I have the option of adding an additional two 10GB NICS.
This would mean I could create another team and Hyper-V switch on top and then dedicate this to my VMs leaving the other team for CSV\Management and Live Migration.
How does this option affect the use of RSS and DVMQ?

Problem with network after deleting NIC teaming.

We have server HP ProLiant DL360p Gen8 with Windows Server 2012. Couple months ago I created a team NIC Teaming (use 2 network interfaces, the other 2 are disable and not connected). Also NLB (Network Load Balancing) feature was installed
but not configure (I think it is important). IIS and MS SQL 2012 Express were installed too and anything else
Now I need delete team NIC Teaming and use network interfaces separately (with different IPs but the same network 192.168.1.0). When I delete team and configure IPv4 with static IP (we don't have DHCP) network does nor work. Because there is no default gateway
in IPv4 properties. It is problem and I don't know how fix this. When I recover team NIC Teaming - all OK. I checked registry and Gateway is in Interfaces (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Adapter
GUID>)
I uncheked NLB in network adapter's settings.
I did
netsh interface ip reset
I checked Route Print - 0.0.0.0 to 192.168.1.1 is present in single copy.
I reinstalled drivers network adapter - it fixed problem before restart. After restart the problem recovered :)
I don't know what should do next.. I cannot resetup OS. Could you please help with this, please. And sorry for my English.
Best regards,
Alex.

Hi ,
After this please try to check the protocol which bounded properly .
If it is normal and still can not access outside as you mentioned above , please try to open the device manager -->
view --> show hidden devices --> then try to remove all the devices under network adapters
(I would recommend you to note the driver files' path in the properties of physical NIC in device manager --> tab
driver --> driver details , try to delete the file after remove the NIC in device manage )
Then restart your computer , install your NIC driver and retry .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Well, I fixed problem finally. :) I deleted all network adapters in device manager with driver file. Than I restarted server and Windows Server setuped Microsoft driver. After that all work! I tried to setup HP driver and problem comes back. I can
conclude that the problem is in the driver manufacturer. Thanks for all and good luck.

Hyper-v NIC teaming, external network

Similar Messages

Maybe you are looking for