Is enabling NIC teaming service affecting?

Hi,
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
I want to enable NIC teaming on a CUCM 7.1 with the "set network failover enable" command. Is this a service affecting command (e.g. does it require a server reboot or cause phones to unregister)?
Thanks!
Mike

Hi Mike,
Configuring NIC Teaming via cli does not require a server
restart and will not cause the phones to re-register
Cheers!
Rob

Similar Messages

Enabling NIC teaming on Server slows down RDP connection

You shouldn't run teaming if the adapters are on different subnets; it's used for two adapters in the same subnet

I have psychical host with two NICs running server 2012 R2. Each NIC has it's own separate subnet. Reason why i wanted to enable teaming so i'm able to ping all the IP addresses in both range. After i enabled teaming i was no longer able to RDP in to machine, sometimes it will work but i will be painfully slow and will disconnect shortly after. This machines also hosts 4 VMs and i can RDP in to those VMs without any problem but the psychical host seems to have issues. i also tried to login to that host using logmein but logmein just keeps waiting on screen to load but never does where as VMs on that host work perfectly fine.
When i ping host using another computer on subnet ping response time all seems to be

Configuring NIC teaming

Hello, everyone. I'm hoping this thread is in the right place.
I've been doing some research trying to understand logical switches/port profiles/etc. in VMM and have been having a hard time. Most of the articles I've found either don't go into enough detail or seem to lack proper examples. My goal is to enable NIC teaming
on my cluster hosts.
Currently, each cluster node has 1 standard switch per physical NIC. One of these NICs is trunked, and the others are not. Everything is working fine, but I'm looking to improve the infrastructure behind these hosts.
I evicted one node from the cluster to experiment with. I enabled LACP on the switch side (Cisco) and enabled NIC teaming on the server (2012 R2). The server is online and functioning, but this is where my knowledge ends. I can't create a logical switch
and add it to this host as the job fails stating that the switch can't be added since the host is already teamed. I'm a little confused about the proper process of getting a logical switch created and added to my host. Do I need to remove LACP and disable
NIC teaming on the host and then re-enable it? Am I going down the wrong path by using LACP?
Any tips and advice would be greatly appreciated. I'd also be happy to provide any additional details I may have left out.

We use LACP teaming for four NICs, two teams, one Production vSwitch and one for management.
We create the management team on the HyperV host first, add it into VMM then push out a team FROM VMM for the switch. The trick is to create a port profile (using algorithm Hyper-V Port and Teaming Mode LACP.) bind this port profile to your logical network(s).
then create your virtual switch and select uplink mode TEAM. and add in your uplink port profile.
Once you have done this you can then right click the host (in VMs and Services) Properties and navigate to virtual switches. Add a new Virtual Switch (New logical switch) then you will be able to add multiple adapters to the switch.
Hit apply and it *should* team for you.
If you need further clarification I can send screen prints and exact steps on tuesday when i'm back in the office.

Relationship between coherence and NIC teaming

Hi,
We are using Tangosol coherence for clustering purpose in our product Webmethods Integration server.
When our server starts up it tries to jojn tne cluster.
Our scenario is this :-
We have 2 servers running on 2 separate boxes A&B.
They are on same network segment.
Multicast test is working properly .
The issue is only one of the nodes(which is started first) in becoming the part of the cluster and other one remain disabled.
We found out that the NIC teaming was disabled in the boxes.
When we enabled NIC teaming with smart load balancing then both the nodes are able to join the cluster.
My specific question is,
Is there any relationship between Tangosol coherence and NIC teaming? If yes, what's the relationship.
Regards,
Ritwik Bhattacharyya

I did some tinkering a while back trying to get 4Gb/s bonded etherchannels going on linux boxes but I had issues with out of order and missing packets:
4Gb/s bonded ethernet test results - finally...
But to answer your question there is no reason that you would need NIC teaming on in order to make Coherence work. It sounds like something is not configured correctly with your NIC or switch. Maybe try connecting the machines with a crossover cable instead of a switch just to eliminate the switch as a possible problem. It sounds like maybe you're just using the wrong ethernet port on a server or something.
-Andrew

SR-IOV Uplink Port with NIC Teaming

Hello,
I'm trying to setup my uplink port profile and logical switch with NIC Teaming and SR-IOV support. In Hyper-V this was easy, just had to create the NIC Team (which I configured as Dynamic & LACP) then check the box on the virtual switch.
I'm VMM it does not seem to like to enable NIC Teams with SR-IOV:
Can anyone advise? I'm not using any virtual ports. I just want all my VMs to connect to the physical switch though the LACP NIC Team, something which I thought would be simple.
I have a plan B - don't use Microsoft's NIC Teaming and instead use the Intel technology to present all the adapters as one to the host. I'd rather no do this.
Thanks
MrGoodBytes

Hi Sir,
"SR-IOV does have certain limitations. If you configure port access control lists (ACLs), extensions or policies in the virtual switch, SR-IOV is disabled because its traffic totally bypasses the switch.
You can’t team two SR-IOV network cards in the host. You can, however, take two physical SR-IOV NICs in the host, create separate virtual switches and team two virtual network cards within a VM. "
There is really a limitation when using NIC teaming :
http://technet.microsoft.com/en-us/magazine/dn235778.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

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!

VMQ issues with NIC Teaming

Hi All
Apologies if this is a long one but I thought the more information I can provide the better.
We have recently designed and built a new Hyper-V environment for a client, utilising Windows Server R2 / System Centre 2012 R2 however since putting it into production, we are now seeing problems with Virtual Machine Queues. These manifest themselves as
either very high latency inside virtual machines (we’re talking 200 – 400 mSec round trip times), packet loss or complete connectivity loss for VMs. Not all VMs are affected however the problem does manifest itself on all hosts. I am aware of these issues
having cropped up in the past with Broadcom NICs.
I'll give you a little bit of background into the problem...
Frist, the environment is based entirely on Dell hardware (Equallogic Storage, PowerConnect Switching and PE R720 VM Hosts). this environment was based on Server 2012 and a decision was taken to bring this up to speed to R2. This was due to a number
of quite compelling reasons, mainly surrounding reliability. The core virtualisation infrastructure consists of four VM hosts in a Hyper-V Cluster.
Prior to the redesign, each VM host had 12 NICs installed:
Quad port on-board Broadcom 5720 daughter card: Two NICs assigned to a host management team whilst the other two NICs in the same adapter formed a Live Migration / Cluster heartbeat team, to which a VM switch was connected with two vNICs exposed to the
management OS. Latest drivers and firmware installed. The Converged Fabric team here was configured in LACP Address Hash (Min Queues mode), each NIC having the same two processor cores assigned. The management team is identically configured.
Two additional Intel i350 quad port NICs: 4 NICs teamed for the production VM Switch uplink and 4 for iSCSI MPIO. Latest drivers and firmware. The VM Switch team spans both physical NICs to provide some level of NIC level fault tolerance, whilst the remaining
4 NICs for ISCSI MPIO are also balanced across the two NICs for the same reasons.
The initial driver for upgrading was that we were once again seeing issues with VMQ in the old design with the converged fabric design. The two vNics in the management OS for each of these networks were tagged to specific VLANs (that were obviously accessible
to the same designated NICs in each of the VM hosts).
In this setup, a similar issue was being experienced to our present issue. Once again, the Converged Fabric vNICs in the Host OS would on occasion, either lose connectivity or exhibit very high round trip times and packet loss. This seemed to correlate with
a significant increase in bandwidth through the converged fabric, such as when initiating a Live Migration and would then affect both vNICS connectivity. This would cause packet loss / connectivity loss for both the Live Migration and Cluster Heartbeat vNICs
which in turn would trigger all sorts of horrid goings on in the cluster. If we disabled VMQ on the physical adapters and the team multiplex adapter, the problem went away. Obviously disabling VMQ is something that we really don’t want to resort to.
So…. The decision to refresh the environment with 2012 R2 across the board (which was also driven by other factors and not just this issue alone) was accelerated.
In the new environment, we replaced the Quad Port Broadcom 5720 Daughter Cards in the hosts with new Intel i350 QP Daughter cards to keep the NICs identical across the board. The Cluster heartbeat / Live Migration networks now use an SMB Multichannel configuration,
utilising the same two NICs as in the old design in two isolated untagged port VLANs. This part of the re-design is now working very well (Live Migrations now complete much faster I hasten to add!!)
However…. The same VMQ issues that we witnessed previously have now arisen on the production VM Switch which is used to uplink the virtual machines on each host to the outside world.
The Production VM Switch is configured as follows:
Same configuration as the original infrastructure: 4 Intel 1GbE i350 NICs, two of which are in one physical quad port NIC, whilst the other two are in an identical NIC, directly below it. The remaining 2 ports from each card function as iSCSI MPIO
interfaces to the SAN. We did this to try and achieve NIC level fault tolerance. The latest Firmware and Drivers have been installed for all hardware (including the NICs) fresh from the latest Dell Server Updates DVD (V14.10).
In each host, the above 4 VM Switch NICs are formed into a Switch independent, Dynamic team (Sum of Queues mode), each physical NIC has
RSS disabled and VMQ enabled and the Team Multiplex adapter also has RSS disabled an VMQ enabled. Secondly, each NIC is configured to use a single processor core for VMQ. As this is a Sum of Queues team, cores do not overlap
and as the host processors have Hyper Threading enabled, only cores (not logical execution units) are assigned to RSS or VMQ. The configuration of the VM Switch NICs looks as follows when running Get-NetAdapterVMQ on the hosts:
Name                           InterfaceDescription
Enabled BaseVmqProcessor MaxProcessors NumberOfReceive
Queues
VM_SWITCH_ETH01                Intel(R) Gigabit 4P I350-t A...#8 True    0:10             1
7
VM_SWITCH_ETH03                Intel(R) Gigabit 4P I350-t A...#7 True    0:14             1
7
VM_SWITCH_ETH02                Intel(R) Gigabit 4P I350-t Ada... True    0:12             1
7
VM_SWITCH_ETH04                Intel(R) Gigabit 4P I350-t A...#2 True    0:16             1
7
Production VM Switch           Microsoft Network Adapter Mult... True    0:0
28
Load is hardly an issue on these NICs and a single core seems to have sufficed in the old design, so this was carried forward into the new.
The loss of connectivity / high latency (200 – 400 mSec as before) only seems to arise when a VM is moved via Live Migration from host to host. If I setup a constant ping to a test candidate VM and move it to another host, I get about 5 dropped pings
at the point where the remaining memory pages / CPU state are transferred, followed by an dramatic increase in latency once the VM is up and running on the destination host. It seems as though the destination host is struggling to allocate the VM NIC to a
queue. I can then move the VM back and forth between hosts and the problem may or may not occur again. It is very intermittent. There is always a lengthy pause in VM network connectivity during the live migration process however, longer than I have seen in
the past (usually only a ping or two are lost, however we are now seeing 5 or more before VM Nework connectivity is restored on the destination host, this being enough to cause a disruption to the workload).
If we disable VMQ entirely on the VM NICs and VM Switch Team Multiplex adapter on one of the hosts as a test, things behave as expected. A migration completes within the time of a standard TCP timeout.
VMQ looks to be working, as if I run Get-NetAdapterVMQQueue on one of the hosts, I can see that Queues are being allocated to VM NICs accordingly. I can also see that VM NICs are appearing in Hyper-V manager with “VMQ Active”.
It goes without saying that we really don’t want to disable VMQ, however given the nature of our clients business, we really cannot afford for these issues to crop up. If I can’t find a resolution here, I will be left with no choice as ironically, we see
less issues with VMQ disabled compared to it being enabled.
I hope this is enough information to go on and if you need any more, please do let me know. Any help here would be most appreciated.
I have gone over the configuration again and again and everything appears to have been configured correctly, however I am struggling with this one.
Many thanks
Matt

Hi Gleb
I can't seem to attach any images / links until my account has been verified.
There are a couple of entries in the ndisplatform/Operational log.
Event ID 7- Querying for OID 4194369794 on TeamNic {C67CA7BE-0B53-4C93-86C4-1716808B2C96} failed. OidBuffer is failed. Status = -1073676266
And
Event ID 6 - Forwarding of OID 66083 from TeamNic {C67CA7BE-0B53-4C93-86C4-1716808B2C96} due to Member NDISIMPLATFORM\Parameters\Adapters\{A5FDE445-483E-45BB-A3F9-D46DDB0D1749} failed. Status = -1073741670
And
Forwarding of OID 66083 from TeamNic {C67CA7BE-0B53-4C93-86C4-1716808B2C96} due to Member NDISIMPLATFORM\Parameters\Adapters\{207AA8D0-77B3-4129-9301-08D7DBF8540E} failed. Status = -1073741670
It would appear as though the two GUIDS in the second and third events correlate with two of the NICs in the VM Switch team (the affected team).
Under MSLBFO Provider/Operational, there are also quite a few of the following errors:
Event ID 8 - Failing NBL send on TeamNic 0xffffe00129b79010
How can I find out what tNIC correlates with "0xffffe00129b79010"
Without the use of the nice little table that I put together (that I can't upload), the NICs and Teams are configured as follows:
Production VM Switch Team (x4 Interfaces) - Intel i350 Quad Port NICs. As above, the team itself is balanced across physical cards (two ports from each card). External SCVMM Logical Switch is uplinked to this team. Serves
as the main VM Switch for all Production Virtual machines. Team Mode is Switch Independent / Dynamic (Sum of Queues). RSS is disabled on all of the physical NICs in this team as well as the Multiplex adapter itself. VMQ configuration is as follows:
Interface Name          -      BaseVMQProc          -        MaxProcs
-      VMQ / RSS
VM_SWITCH_ETH01                  10
     1                           VMQ
VM_SWITCH_ETH02                  12
1                           VMQ
VM_SWITCH_ETH03                  14
   1                           VMQ
VM_SWITCH_ETH04                16
    1                           VMQ
SMB Fabric (x2 Interfaces) - Intel i350 Quad Port on-board daughter card. As above, these two NICs are in separate, VLAN isolated subnets that provide SMB Multichannel transport for Live Migration traffic and CSV Redirect / Cluster
Heartbeat data. These NICs are not teamed. VMQ is disabled on both of these NICs. Here is the RSS configuration for these interfaces that we have implemented:
Interface Name         -      BaseVMQProc         -        MaxProcs
-      VMQ / RSS
SMB_FABRIC_ETH01                18                                   2
RSS
SMB_FABRIC_ETH02                18                                   2
RSS
ISCSI SAN (x4 Interfaces) - Intel i350 Quad Port NICs. Once again, no teaming is required here as these serve as our ISCSI SAN interfaces (MPIO enabled) to the hosts. These four interfaces are balanced across two physical cards as per
the VM Switch team above. No VMQ on these NICS, however RSS is enabled as follows:
Interface Name          -      BaseVMQProc        -         MaxProcs
   -        VMQ / RSS
ISCSI_SAN_ETH01                    2                                    2
RSS
ISCSI_SAN_ETH02                    6                                    2
RSS
ISCSI_SAN_ETH03                    2
2                            RSS
ISCSI_SAN_ETH04                   6
2                            RSS
Management Team (x2 Interfaces) - The second two interfaces of the Intel i350 Quad Port on-board daughter card. Serves as the Management uplink to the host. As there are some management workloads hosted in this
cluster, a VM Switch is connected to this team, hence a vNIC is exposed to the Host OS in order to manage the Parent Partition. Teaming mode is Switch Independent / Address Hash (Min Queues). As there is a VM Switch connected to this team, the NICs
are configured for VMQ, thus RSS has been disabled:
Interface Name        -         BaseVMQProc        -         MaxProcs
-      VMQ / RSS
MAN_SWITCH_ETH01                 22                                  1
VMQ
MAN_SWITCH_ETH02                 22                                  1                           VMQ
We are limited as to the number of physical cores that we can allocate to VMQ and RSS so where possible, we have tried balance NICs over all available cores where practical.
Hope this helps.
Any more info required, please ask.
Kind Regards
Matt

NIC teaming - Server 2008 R2 DC combined with other Software

Hello!
I've been searching all morning for an answer of what we have in mind to do at work....
We've got a server installed with Windows Server 2008 R2 and have 4 NICs on it. We want to make it a DC (with DNS, DHCP and print services) and also want to install our Backup Solution (from Veeam) for our VMs. This server will be the only physical Microsoft
server next to our 3 ESX servers at the end.
I read here (http://markparris.co.uk/2010/02/09/top-tipactive-directory-domain-controllers-and-teamed-network-cards/) that there is a statement that a DC with NIC teaming is only using the FO (Fail-Over) feature of the teaming. Since there is also the backup
solution on this server, it would be great also to use the LB (Load-Balancing) feature. My question is, when I active NIC teaming and install the DC roles, does the roles just use the FO feature and neglect the LB feature or does it enable/disable those modes/features
of NIC teaming? Cause it would be nice if the backup solution could use the LB for bigger bandwidth for backup and restores and I wouldn't really care about the FO for the DC role.
cheers
Ivo

Hi,
I think the issue is related to the third party NIC teaming solution. You can refer to the third party manufacture.
Here I should remind you something else, a DC with multiple NICs will cause many problems. So I would recommend you run a dedicated
Hyper-v server and promote a DC on one of the virtual machine.
Hope this helps.

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.

Switch-independent load-balancing NIC teaming on server-side and MAC/ARP flapping on L2/L3 switches

Since active deployment of Windows Server 2012, our servers support team began to utilize new feature - switch-independent load-balancing NIC teaming. At first look it seems great - no additional network configuration is required and load balancing is performed by server itself by sending frames in round-robin or some hash algorithm out from different NICs (say two for simplicity) but with same MAC address. Theoretical bandwith is now grown up to 2Gbps (if we have two 1G NICs per server) against failover NIC teaming configuration, when one of two adapters is always down.
But how does this affect (if does) switching and routing performance of network equipment? From point of view of L2 switch - it has to rewrite its CAM table each time a server sends frame from different NIC. Isn't it expensive operation? Won't it affect switching in a bad way? We see in our logs that same server make switches to change mac-to-port associations several times per second.
Well, and how does it affect routing, if the switch to which server is connected is L3 switch an performs routing for the subnet server connected to? Will CEF operate well if ARP entry chages several times per second?
Thank you.

Since nobody answered here, we created service request and got the following answer (in short):
L2 MAC flapping between ports is very bad and you must avoid such configurations as much as possible. There is one possible variant that can be considered in your situation - use port-channel (either L2 or L3), in this configuration port-channel will be treted as single port and there won't be flapping.
Conversation example is here: https://ramazancan.wordpress.com/tag/best-practice/

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?

Windows 7/8.0/8.1 NIC teaming issue

Hello,
I'm having an issue with Teaming network adapters in all recent Windows client OSs.
I'm using Intel Pro Dual Port or Broadcom NetExtreme II GigaBit adapters with the appropriate drivers/applications from the vendors.
I am able to set up teaming and fail-over works flawlessly, but the connection will not use the entire advertised bandwidth of 2Gbps. Basically it will use either one port or the other.
I'm doing the testing with the iperf tool and am communicating with a unix based server.
I have the following setup:
Dell R210 II server with 2 Broadcom NetEtreme II adapters and a DualPort Intel Pro adapter - Centos 6.5 installed bonding configured and working wile communicating with other unix based systems.
Zyxel GS2200-48 switch - Link Aggregation configured and working
Dell R210 II with Windows 8.1 with Broadcom NetExtreme II cards or Intel Pro dualport cards.
For the Windows machine I have also tried Windows 7 and Windows 8, also non server type hardware with identical results.
so.. Why am I not getting > 1 Gbps throughput on the created team? although load balancing is activated, team adapter says the connection type is 2 Gbps, a the same setup with 2 unix machines works flawlessly.
Am I to understand that Link Aggregation (802.3ad) under Microsoft OS does not support load balancing if connection is only towards one IP?
To make it clear, I need client version of Windows OS to communicate unix based OS over a higher then 1Gbps bandwidth (as close to 2 Gbps as possible). Without the use of 10 Gbps network adapters.
Thanks in advance,
Endre

As v-yamliu has mentioned, NIC teaming through the operating system is
only available in Windows Server 2012 and Windows Server 2012 R2. For Windows Client or for previous versions of Windows Server you will need to create the team via the network driver. For Broadcom this is accomplished
using the Broadcom Advanced Server Program (BASP) as documented here and
for Intel via Advanced Network Services as documented here.
If you have configured the team via the drivers, you may need to ensure the driver is properly installed and updated. You may also want to ensure that the adapters are configured for aggregation (802.3ad/802.1ax/LACP), rather than fault tolerance or load
balancing and that the teaming configuration on the switch matches and is compatible with the server configuration. Also ensure that all of the links are connecting at full duplex as this is a requirement.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet

NIC Teaming on new 2012R2 install IntelX540-T2 Netgear XS712T not functioning properly

I have a new 2012R2 server with an Intel LOM X540-T2 Dual port, 10-gig copper NIC. I'm trying to team both ports to a Netgear 10-gig copper switch (XS712T, CAT6A cables) and not having much luck. Latest firmware/drivers all around. I reset to factory defaults
on the Netgear switch.
From a console, I go to server manager, NIC Teaming, New Team.
When I try Team Mode: Switch Independent / Load balancing mode: Dynamic. Both ports become Active. I understand that now the adapters listed in networking connections are to be left alone, and that configuration should take place on the Microsoft
Network Adapter Multiplexor Driver. The 'Team' adapter is supposed to DHCP, but never does, and ends up with a private 169.254 address. If I manually configure ip4 on the 'Team' adapter, I still have no communication to the network. Both ports are able
to DHCP when un-teamed. Something interesting is that port 1 only shows received packets, and none sent. At the same time, port 2 shows a much smaller number of sent packets, but zero received. Odd.
When I try Team mode: LACP / Load balancing mode: Dynamic. I add two of the Netgear ports to a LAG and enable LACP. One of the ports in Windows will show 'Active' (and has DHCP'd with normal send/receive), and the other port shows 'Faulted LACP Negotiation'
with very few sent packets and zero received.
Any ideas, or places to look next?
Edit: It looks like I can get physical port 1 to join the LACP group, but physical port 2 will not join, even after swapping cables and rebooting the Netgear switch. But port 1 still goes 'active' regardless of the switchport that it's plugged into.

Hi,
I agree with SpackTime, please confirm his replay.
Thanks.
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.

Correct binding order in a Cluster with logical switches, NIC teams, and vNICs on the host.

I have seen many recommendations to set the network binding order on you Hyper-V hosts to something similar to:
Management NIC
Cluster NICs
iSCSI NICS
However, all of these recommendations are for scenarios where the NICs are all physical NICs in the host.
Using Server 2012 R2, I am building converged networks with logical switches, NIC Teams, and vNICs on the host. So when I go set the network binding order, I now have all these components to deal with as well. For example, on a 4 adapter blade,
I might typically have the following items in the binding order drop-down.
4 - physical NICs (2- teamed for the 1 virtual switch, the other 2 used for iSCSI)
1 - Team interface (Datacenter_Switch)
5 - vNICs (Management, Cluster, LiveMigration, iSCSI-1, iSCSI-2)
So, should you only worry about order of the vNICS (placed at the top) and let the other components just fall to the bottom of the list? This seems to be likely to me, since the binding order applies to service access to the resources, and the other
components are not being directly accessed by network services?
Or, should the order start out with the physical resources needed to access the vNICs, followed by any intermediate resources (switches or team interfaces, then the vNICS themselves, to ensure that the resources are available to the subcompnents accessing
them?
Any help would be appreciated.
Thanks.
-Tim Reid

If by 'network binding order' you mean the order set in the Advanced Settings of the Network Connections of the Control Panel, then the most important one is to make sure the domain network is at the top of the list. Whichever network is at the top
of the list is used first for auth functions. So auth functions perform best when the proper network is placed first in the binding order. After that, I don't know that it makes much difference at all. (If it does, I'm sure my statement will
start a lively discussion. <grin>)
. : | : . : | : . tim

Dynamic(Switch Independent) NIC Teaming Mode Problem

Hi,
We are using Switch Independent Dynamic distribution NIC Teaming configuration on Hyper-V 2012 R2 cluster. In the following graphs between 19:48 - 19:58 you can see clearly how dynamic NIC teaming mode badly affected the web servers response times.
We have encountered this problem on the different cluster nodes that use different NIC chipsets Intel or Broadcom and configured with dynamic NIC teaming for VM Network connection.
If we change the teaming mode as Hyper-V Port or remove NIC teaming for VM network as you can see from the graphic, response times are back to normal.
Any ideas?
Regards

Hi,
In the heavy inbound and outbound network load, If you are using the “Switch Dependent”
mode, you must configure your switch have the same teaming support mode.
There have two scenario.
“Switch Dependent” with LACP if your switch supports the aka 802.1ax.
“Switch Dependent” mode with Static.
Example of Cisco® switch configuration when you using the “Switch Dependent” mode with “Static” mode:
CiscoSwitch(config)# int port-channel1
CiscoSwitch(config-if)# description NIC team for Windows Server 2012
CiscoSwitch(config-if)# int gi0/23
CiscoSwitch(config-if)# channel-group 1 mode on
CiscoSwitch(config-if)# int gi0/24
CiscoSwitch(config-if)# channel-group 1 mode on
CiscoSwitch(config)# port-channel load-balance src-dst-ip
Hope this helps.
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.

Is enabling NIC teaming service affecting?

Similar Messages

Maybe you are looking for