Server 2012 R2 NIC Teams

Hey guys, i was hoping someone could help me understand this. I kind of get how this teaming stuff works, but i want to make sure I'm not doing anything wrong/ not supported.
So for the past few days I've been trying to wrap my head around this stuff. And this is what I have so far.
R720 Dell Server --> 4 Teamed NICs ---> Multiplexor --> vSwitch --> VMs
So the vSwitch is connected to the multiplexor and the VMs are connected to that switch. I figured I'd try to see if i saw any performance differences. As a matter of fact I saw it got worse. Sometimes the VM on the server stays connected, other times it
gets disconnected and wont reconnect
When I do a LAN speed test to another server i get like 9 Mbps vs other servers that are connected strait from a nic to a switch and that switch to a server that gets 800 Mbps +
I did a switch independent with dynamic LB. I did some looking up on all of the settings, but I really dont understand why its so slow.
Also if i were to create vNICs based off that switch for lets say, management, cluster, live migration etc..
So, the NICs are based off that vSwitch and you can do the Qos for those NICs, but I'm confused as to how those NICs are specifically used.
If none of that made sense, i'll be around looking for some more info and i can elaborate if need be.

Hi,
In switch
independent mode, outbound traffic bandwidth could be increased. If you want improve both inbound and outbound bandwidth you could configure a switch dependent
mode. And it is recommended to choose hyper-v switch port as
Traffic distribution algorithms.
For dynamic teaming
most switches require manual administration to enable LACP on the port.
At last, you referred that VM lose connection intermittently. I wonder the VM lose connection with your virtual switch or lose connection with the other servers.
A good blog for you:
NIC teaming on Virtual Machines
http://blog.marcosnogueira.org/nic-teaming-on-virtual-machines/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Hope this helps.

Similar Messages

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.

Windows Server 2012 R2 NIC Teaming and DHCP Issue

Came across a weird issue today during a server deployment. I was doing a physical server deployment and got Windows installed and was getting ready to connect it to our network. Before connecting the Ethernet cables to the network adapters, I created a
NIC Team using Windows Server 2012 R2 built-in software with a static IP address (we'll say its 192.168.1.56). Once I plugged in the Ethernet cables, I got network access but was unable to join our domain. At this time, I deleted the NIC team and the two network
adapters got their own IP addresses issued from DHCP (192.168.1.57 and 192.168.1.58) and at this point I was able to join our domain. I recreated the NIC team and set a new static IP (192.168.1.57) and everything was working great as intended.
My issue is when I went into DHCP I noticed a random entry that was using the IP address I used for the first NIC teaming attempt (192.168.1.56), before I joined it to the domain. I call this a random entry because it is using the last 8 characters of the
MAC address as the hostname instead of the servers hostname.
It seems when I deleted the first NIC team I created (192.168.1.56), a random MAC address Server 2012 R2 generated for the team has remained embedded in the system. The IP address is still pingable even though an ipconfig /all shows the current NIC team
with the IP 192.168.1.57. There is no IP address of 192.168.1.56 configured on the current server and I have static IPs set yet it is still pingable and registering with DHCP.
I know this is slightly confusing but I am hoping someone else has encountered this issue and may be able to tell me how to fix this. Simply deleting the DHCP entry does not do the trick, it comes back.

Hi,
Please confirm you have choose the right NIC team type, If you’ve previously configured NIC teaming, you’re aware NIC teams usually require the assistance of network-side
protocols. Prior to Windows 2012, using a NIC team on a server also meant enabling protocols like EtherChannel or LACP (also known as 802.1ax or 802.3ad) on network ports.
More information:
NIC teaming configure in Server 2012
http://technet.microsoft.com/en-us/magazine/jj149029.aspx
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.

Server 2012 R2 Network Teaming Issues After Adding WOW64 Feature

Recently I have had a specific issue adding the WOW64 feature to an active Server 2012 R2 server in core mode (no management). The server had two active virtual machines. A server 2008 R2 in version 1 mode and a 2012 R2 in version 2.
All were up2date as of April 10 2015. This was a domain connected core with domain connected virtual machines. We are the domain administrator.
After using powershell to install WOW64 and issuing a restart we lost all external network connectivity to the server once the server came back up. From the console we could ping 127.0.0.1 and all the network addresses of each VM but not the
default gateway or any address on the local network. We tried several resolutions including disabling all firewall rules and assigning a known VLAN but nothing worked. Something went completely haywire within Windows 2012 R2 and network teaming
and the virtual switch that supplies the VM's with communication.
What we had to do was remove one of the physical network adapters from the team using powershell from the core console. We then assigned an address to the nic and whallah we were able to remotely communicate to the server again but the problem
still remained with communicating to the team.
After hours of trials we finally stumbled on a solution deleting the hyper-v virtual switch though a remote console, then the team through powershell. This of course broke all the hyper-v VM's. We said f'it and rebooted.
This is the magical combination apparently
We then recreated the team using the remote management GRAPHICAL widget using every physical EXCEPT the nic we were communicating to.   Then we recreated the hyper-v virtual switch remotely again with the GRAPHICAL widget and assigned
it an address using the command line sconfig tool.   We then went into the GRAPHICAL hyper-v manager and assigned all VM's to the new virtual switch. WOW everything works again
Let me just say here in this post that the lack of graphical management in CORE mode is a complete nightmare. The fact we have to use some graphical tools to perform certain tasks and the command line for others is just silly. The sconfig.exe
tool should have built-in teaming commands as inexperienced remote administrators are very difficult to work with over the phone trying to explain spelling of the upper/lowercase commands.
This post is more informative than really asking a specific question but if I were to ask one I'd ask, why did installing the WOW64 feature and rebooting break the external communication of the team and the virtual switch?

Hi gettnmorebetter,
Could you try to confirm whether you have in the following situation, if you do not found the related symptom please try to install the latest update then monitor the issue
again.
Event ID 106 when a Hyper-V virtual switch is bound to an LBFO team
https://support.microsoft.com/en-us/kb/2974384
I’m glad to be of help to you!
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 Support, contact [email protected]

2012 R2 NIC Teaming and netwroking

I have a 4 port NIC, all connected to the same network using DHCP, when I team two cards, they no longer have an IP address. Is that by design?
Where can I find more information about the virtual networking how to?
TIA

Yes it is by design.
If individual NICs are configured with IP settings and then you create a NIC teaming the individual nics will lose their IP settings.
And you will no longer be able to configure the ip settings on the individual NICs which are part of a NIC team. Instead you will need to assign the ip address on the NIC Team.
To assign ip address to the NIC teams, go to control Panel\ Network and Internet\ Network Connections
To assign VLANs and manage/update Team interfaces: In the Server Manager select the local server and then in the local server properties section click on Nic Teaming "Enabled" link.
This will open the NIC teaming window and here you can manage the NIC teams.
For more information on NIC teams please refer to:
http://blogs.technet.com/b/keithmayer/archive/2012/11/20/vlan-tricks-with-nic-teaming-in-windows-server-2012.aspx
Kind Regards Tim (Canberra)

HYPer-v 2012 R2 NIC team breadown after Broadcom Driver upgradation

Hi Team ,
I am using Blade server with Two Broadcom BCM57800 NetXtream 10 G ports . Both Network card configured in one team with Switch independent and Hyper-v Port configuration using Windows Native teaming.
I upgraded the firmware driver of network card to the latest level and then after Hyper-v Team stop responding.
i am using Single virtual Switch with one vNIC so hyper-v can talk to mgmt LAN on Vlan X.
as an work around i break the team and configure one nic for Mgmt IP and other for VDItraffic (Virtual Switch)
please let me know if any one face similar issue and able to resolved it.
Thanks
Ravi
Ravi

Hi Ravi,
I would like to check if the issue had been resolved .
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 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!

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/

Windows server 2008 R2 to Windows server 2012 R@ Upgrade

We have Team Foundation server 2010 server configured in our environment.
operating system: windows server 2008 R2 Datacenter
Server installed: Team foundation server 2010 with share point services 3.0.
we need to upgrade this server with windows server 2012 R2 and Team foundation server 2010 as it is.
need to upgrade as below:
operation system windows server 2012 R2 Datacenter
Server Installed : Team foundation server 210 with sharepoint services 3.0 as it is.
I have tried to direct upgrade by running a setup of windows server 2012 R2 but it shows error message if : "
When you upgrade Windows Server 2008 to Windows Server 2012, you receive the following error message:
Windows won’t install unless each of these things is taken care of. Close Windows Setup, take care of each one, and then restart Windows Setup to continue.
Windows needs to be restarted so necessary changes to system files can be made before continuing.
Make these changes:
Turn off these Windows features.
Windows SharePoint Services 3.0 – Please read Microsoft Knowledge Base article: 962216
I have installed sharepoint 3.0 with sp3. but still I am geeing same error.
we need to upgrade operating system,n in place.
Kindly request you for the quick response.

Hi,
To understand more clearly regarding upgrading issue here providing you link for more information.
Upgrade Options for Windows Server 2012 R2
http://technet.microsoft.com/en-us/library/dn303416.aspx
Install and Deploy Windows Server 2012 R2 and Windows Server 2012
http://technet.microsoft.com/en-us/library/hh831620.aspx
Hope it helps!
Regards.

Server 2012 R2 Crashes with NIC Team

Server 2012 R2 Core configured for Hyper-V. Using 2-port 10Gbe Brocades, we want to use NIC teaming for guest traffic. Create the team... seems fine. Create the virtual switch in Hyper-V, and assign it to the NIC team... seems fine. Create
a VM, assign the network card to the Virtual switch... still doing okay. Power on the VM... POOF! The host BSOD's. If I remove the switch from the VM, I can run the VM from the console, install the OS, etc... but as soon as I reassign the virtual
NIC to the switch, POOF! Bye-bye again. Any ideas here?
Thank you in advance!
EDIT: A little more info... Two 2-port Brocades and two Nexus 5k's. Running one port on NIC1 to one 5k, and one port on NIC2 to the other 5k. NIC team is using Switch Independent Mode, Address Hash load balancing, and all adapters active.

Hi,
Have you updated the NIC driver to latest?
If issue persists after updating the driver, we can use WinDbg to analyze a crash dump.
If the NIC driver cause the BSOD, please consult the NIC manufacture about this issue.
For detailed information about how to analyze a crash dump, please refer to the link below,
http://blogs.technet.com/b/juanand/archive/2011/03/20/analyzing-a-crash-dump-aka-bsod.aspx
Best Regards.
Steven Lee
TechNet Community Support

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.

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.

NIC teaming and direct access in windows 2012 server core

Hello All,
I have installed windows 2012 r2 server core and i want to implement direct access with nic teaming enabled.
Has anyone tried this kind of setup? Were they successful in it? Moreover can we configure Direct access when we have NIC teaming configured?
-Ashish

Hi There - NIC teaming in both core and gui is a standard feature and there is no reason (and I have used it successfully) why you cannot do so. As always make sure you look at TCP Offload as per UAG / TMG Days to ensure best performance and also Network
Card Binding Order.
The link for details is here -
http://technet.microsoft.com/en-us/library/hh831648.aspx
Kr
John Davies

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.

NIC teaming shows no adapters (server 2012 R2)

I think you are almost to the point of nuke and pave to fix the issue. (well not totally yet).
What I would do is go into the device manager and remove all physical network adapters. Reboot and then let windows redetect and add them. This should fix the network communication issue.
With that done, you need to answer what Rod-IT asked, how are you teaming these NICs? Are you using the computer manufacturer's program, the network adapter manufacturer's program or something else? Once you get beyond that what type of teaming are you trying to setup fail over (hot spare), LACP, switch assisted load balancing. Some load balancing settings need you to change the switch settings too.
Also what brand of NICs are these?

I have a server 2012 R2 system and on the NIC teaming it shows no adapters and windows network and sharing center shows none as well.
I do not want to have to reinstall :( I've tried rebuilding wmi repository and it doesn't work)
This topic first appeared in the Spiceworks Community

Server 2012 R2 NIC Teams

Similar Messages

Maybe you are looking for