Bandwidth Maximums on UCS virtual NICs

I'm creating some virtual NICs for ESXi hosts.
What is the maximum bandwidth per virtual NIC?
If I have 4 virtual NICs on a virtual switch in ESXi, what is the maximum bandwidth for the total of the 4 virtual NICs?

Hi
The total bandwidth doesn't depend on the number of vnics it depends on the blade model, adapter(s), and the type of IOM that you have installed (see link below) .
http://ucsguru.com/2013/03/13/20gb-20gb-10gb-m3-blade-io-explained/

Similar Messages

UCS Virtual Interface Card 1280 failover

Hi,
I'm facing some issues with failover and Cisco UCS Virtual Interface Card 1280.
I found some information regarding M81KR:
Cisco UCS M81KR has fabric failover
The Cisco UCS M81KR offers fabric failover, which enables interface failover at a physical level without involving the OS or hypervisor or certification overhead.
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10276/solution_overview_c22-555987_ps10280_Product_Solution_Overview.html
b) Both uplinks of one FI fail or FI fails : In this case the corresponding server links will be shut since there is no uplink available on an FI. The FI will propagate link-down status to the adapter. Once adapter link-down status occurs, it is the responsibility of the operating system to re-pin traffic to the remaining NIC/HBA. The exception here is with Palo adapter (M71KR and M81KR) which supports fabric failover.
https://supportforums.cisco.com/docs/DOC-18525
But I didn't found about Cisco UCS Virtual Interface Card 1280.
Cisco UCS Virtual Interface Card 1280 is newer than M81KR, anybody knows if 1280 has the same feature? is it possible the failover even if the Fabric Interconnect fails?
Thanks,

Hi Mauricio,
The VIC 1280 has fabric failover as well, from the spec sheet:
Network architecture
Provides a redundant path to the fabric interconnect using hardware-based fabric failover
http://www.cisco.com/en/US/prod/collateral/ps10277/ps11551/data_sheet_c78-677682.html

When setting up converged network in VMM cluster and live migration virtual nics not working

Hello Everyone,
I am having issues setting up converged network in VMM. I have been working with MS engineers to no avail. I am very surprised with the expertise of the MS engineers. They had no idea what a converged network even was. I had way more
experience then these guys and they said there was no escalation track so I am posting here in hopes of getting some assistance.
Everyone including our consultants says my setup is correct.
What I want to do:
I have servers with 5 nics and want to use 3 of the nics for a team and then configure cluster, live migration and host management as virtual network adapters. I have created all my logical networks, port profile with the uplink defined as team and
networks selected. Created logical switch and associated portprofle. When I deploy logical switch and create virtual network adapters the logical switch works for VMs and my management nic works as well. Problem is that the cluster and live
migration virtual nics do not work. The correct Vlans get pulled in for the corresponding networks and If I run get-vmnetworkadaptervlan it shows cluster and live migration in vlans 14 and 15 which is correct. However nics do not work at all.
I finally decided to do this via the host in powershell and everything works fine which means this is definitely an issue with VMM. I then imported host into VMM again but now I cannot use any of the objects I created and VMM and have to use standard
switch.
I am really losing faith in VMM fast.
Hosts are 2012 R2 and VMM is 2012 R2 all fresh builds with latest drivers
Thanks

Have you checked our whitepaper http://gallery.technet.microsoft.com/Hybrid-Cloud-with-NVGRE-aa6e1e9a for how to configure this through VMM?
Are you using static IP address assignment for those vNICs?
Are you sure your are teaming the correct physical adapters where the VLANs are trunked through the connected ports?
Note; if you create the teaming configuration outside of VMM, and then import the hosts to VMM, then VMM will not recognize the configuration.
The details should be all in this whitepaper.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Create Virtual NICs of a Teamed Interface

Dear All,
I am building a Hyper-V Failover Cluster. I have created a team (two physical nics) which I plan to only use for Cluster Communication, Heartbeat and Live Migration.
I have following questions:
1. How to create virtual NICs out of this teamed interface and assign them to respective networks?
2. Do Cluster Communication, Heartbeat and Live Migration Networks have to be on different subnet or they can be part of the same subnet as well?
3. In both cases that is same subnet or different subnet, how would networks be assigned?
Thanks in advance.

Hi Junkie,
Hope the following link is helpful :
http://technet.microsoft.com/en-us/library/dn550728.aspx
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.

Virtual NIC, DHCP and rc.conf

Hello!
I'm running an Arch box as my home server. My ISP offers me 5 public IP addresses, and I would like to have 2 assigned to my server. Is it possible to get Arch to use two ip addresses on the same NIC using rc.conf? I would also like to have the virtual NIC pull an IP address from the DHCP server.
Thanks!

I don't think you can do this in rc.conf because you can't have colons (:) in bash variable names I don't believe...
You can just add it to rc.local like:
ip a a x.x.x.x/yy dev eth0
Replace x.x.x.x/yy with the appropriate IP address and CIDR mask.

Find out virtual nic to physical nic mapping

any command in hyper-v / scvmm to find out virtual nic to physical nic mapping. In vmware we can get the same by esxtop N view shows VMname and the physical NIC used, simlarly any in hyper-v

I think that in a device driver you can use hat_getkpfnum(9F) to get the physical page number from a virtual address.
In crash(1m) the vtop command will translate a virtual to a physical address.
I would have thought you could also just use the virtual address against /dev/kmem, as opposed to using a physical address against /dev/mem?
Hope that helps.
Ralph
SUN DTS

VLAN and Networking and Virtual NIC

HI,
I have installed Oracle VM 3.2.2, the problem we are getting is when we change the VLAN network for the VM guest OS (OEL 5.5) from Oracle VM Server. the changes doesn't effect. I have shutdown the guest OS and remove the virtual network interface and need to add a new NIC with different MAC to modify the VLAN.
e.g.
there are two VLAN (segment 10 and 20) 192.168.10.0/24 and 192.168.20.0/24. defined in Oracle VM Server and assigned to all physical hosts.
if I assign segment 10 initially to the guest OS it works fine, but If we want to modify the segment it needs to remove the virtual NIC and have to add a different NIC with different MAC address to fix the issue.
Need to change the vlan segment without removing the NIC/MAC.

I don't think you can do this in rc.conf because you can't have colons (:) in bash variable names I don't believe...
You can just add it to rc.local like:
ip a a x.x.x.x/yy dev eth0
Replace x.x.x.x/yy with the appropriate IP address and CIDR mask.

Trouble getting virtual NICs to appear in VM

Hi all. We have the latest release of HyperV running on fully patched Windows 2008 host machine. We have 3 physical dual port NICs in the machine and we are having trouble creating virtual networks and having them show inside a guest VM.
Our guest VM is running Windows 2003 Web, SP2. No network adapters show up under Control Panel -> network connections
In device manager I notice a yellow exclamation under Other Devices. The details for this are as follows:
Unknown Device - Location: on Intel 82371AB/EB PCI to ISA bridge (ISA)
The drivers for this device are not installed.
Details: Value - ACPI\VMBUS\4&4B018EB&0
Here are the steps we took to create the virtual network:
1) Open Virtual Network Manager
2) Click Add on "External" virtual network
3) Select Intel Pro/1000 PT Dual Port Server Adapter (unused on host machine, but cable is plugged in) - External
4) Click OK to create virtual network
5) Go to Settings of VM and click Network Adapter
6) Select the virtual network we just created under Network: in Settings
7) Configure IP address etc on new VIRTUAL nic created on host machine. I have confirmed Hyper-V removed all checkboxes under properties of the physical NIC minus Microsoft Virtual Network Switch Protocol
Does anyone know what I am doing wrong? Is there some sort of driver/patch I am missing? Any help would be much appreciated!

I should have stated;
Windows Server 2003 x86 SE built on VS 2005 R2 sp1, transferred to Server 2008 with hyper V installed, upgraded to SP2. Integration Services setup disk has been run. Mouse control is in and running. Still no NIC drivers.
System built on 2008 Vhost with SE sp0 and upgraded works. I hadn't installed the integration disk. My bad.
So is there nic drivers available or not? The biggest business requirement for virtualization is to save on all the testbed workstations and servers. These run things like Windows 2000 server and workstation, Windows XP, server 2003 sp0. Various testing levels for compatibility with clients. Without this driver natively there seems to be no way forward for the company infrastructure.
meep.

HyperV Virtual NIC not Visable on SCVMM

HI I have installed Hyper V On One of the HP G7 hardware , and SCVMM is on G6 Hardware,
After configuring Hyper V Role, I have teamed the 4 NIC to One Teaming and created multiple VnNIC by using below Script.
Issue here After adding the Host to SCVMM i am unable to find the VNICs, I can see only Vswitch, Please suggest, I have attache3d the screenshot for the references.
New-NetLbfoTeam -Name TEAMNIC -TeamMembers NIC1,NIC2,NIC3,NIC4 -LoadBalancingAlgorithm HyperVPort -TeamingMode SwitchIndependent
New-VMSwitch -Name VSWITCH -NetAdapterName TEAMNIC -AllowManagementOS $False -MinimumBandwidthMode Weight
Set-VMSwitch VSWITCH -DefaultFlowMinimumBandwidthWeight 20
Add-VMNetworkAdapter -ManagementOS -Name "Management" -SwitchName "VSWITCH"
Add-VMNetworkAdapter -ManagementOS -Name "LiveMigration" -SwitchName "VSWITCH"
Add-VMNetworkAdapter -ManagementOS -Name "VirtualMachine" -SwitchName "VSWITCH"
Add-VMNetworkAdapter -ManagementOS -Name "CLuster" -SwitchName "VSWITCH"VSWITCH
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Management" -Access -VlanId 251
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "LiveMigration" -Access -VlanId 62
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "VirtualMachine" -Access -VlanId 62
Set-VMNetworkAdapter -ManagementOS -Name "Management" -MinimumBandwidthWeight 10
Set-VMNetworkAdapter -ManagementOS -Name "VirtualMachine" -MinimumBandwidthWeight 50
Set-VMNetworkAdapter -ManagementOS -Name "LiveMigration" -MinimumBandwidthWeight 30

The fact that this does not show up in SCVMM properly makes this an SCVMM issue.
And, SCVMM does not support everything that you can do with Hyper-V.
In this case, SCVMM needs to drive the configuration using Logical Networks and apply this configuration when you host is taken under management. Only then will SCVMM identify and list everything properly.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

UCS-C210: NIC 5709 installation error occurred in W2003 R2 64-bit version

See the error message, thank !

Windows Server 2003 is no longer supported on C210 M2's.
http://www.cisco.com/en/US/docs/unified_computing/ucs/interoperability/matrix/r_hcl_C_rel1.45.pdf
Even Broadcom no longer supports Server 2000 or 2003.
http://www.broadcom.com/support/ethernet_nic/netxtremeii.php
"Windows 2000, Windows Server 2003, Windows XP and Windows Vista are no longer supported by current chipsets."
If you still wish to try and use Server 2003 unsupported you can download and manually install Broadcom's legacy driver from here: http://www.broadcom.com/support/ethernet_nic/netxtremeii.php?legacy=1
Keep in mind if you have any issues Cisco TAC will not be able to provide support.
Regards,
Robert

From VM cannot ping host or gateway

Hi all,
I have installed Hyper-V 2012 R2 core of a brand new Dell Poweredge R720 server in core mode, no GUI.
Then a VM with Windows 2012 R2 VM with GUi has been created with Hyper-V manager, no problems there.
I used the Virtual Switch Manager to create a Virtual LAN adapter and selected the network card as an external type because I want to share the Hyper-V host network card.
I start the virtual machine, go into network connections, configure a static IP is the same subnet as the Hyper-V host, default gateway, DNS server etc.
When I try to ping the Hyper-V host or the router's default gateway, I get that it is unreachable.
If I try to ping the VM from the host same thing, unreachable.
I made sure to disable the Firewall in the Hyper-V host as well as the Virtual Machine for testing purposes.
What is the problem here?
I read somewhere on google that although the hyper-v host network config may appear fine, it might be messed up.
Also if you have more than 1 physical network adapter how to I select the correct index for the NIC in Hyperv manager Virtual switch manager?
Any responses will be greatly appreciated.
Thanks and regards
Alfred

I'll ask again for the output of ipconfig /all from the two machines you are testing. It is a challenge to assist in debugging network issues when we can't see how the network is configured.
.:|:.:|:. tim
Hi Tim,
sorry for the delay in answering and also thanks for your reply.
I have worked out what the problem was.
When I created the Virtual Switch in Hyper-V manager, I picked the wrong physical network card.
In the Poweredge R720 there are 8 physical nics and I picked the one called Broadcom NetXtreme Gigabit Ethernet (not connected and hence the apipa IP address), when it should have been Broadcom NetXtreme Gigabit Ethernet #5.
I had to go into powershell and execute get-netadapter to get the lists of NICs and their status.
Then I decided to create a NIC team to increase the bandwidth and create a virtual nic to assign to my VMs.
Now everything is working OK:
This is the output of my ipconfig /all on the core server:
Windows IP Configuration
Host Name . . . . . . . . . . . . : xxxhyperv1
Primary Dns Suffix . . . . . . . : xxxxxx.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xxxxxx.local
Ethernet adapter vEthernet (Virtual Switch 1):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::15be:46cd:a1c7:e2e2%35(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.20.44(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.20.1
DHCPv6 IAID . . . . . . . . . . . : 603503634
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-6
DNS Servers . . . . . . . . . . . : 192.168.20.5
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter SLOT 2 Port 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #4
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter SLOT 2 Port 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #3
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter SLOT 2 Port 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter SLOT 2 Port 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{92F333A4-9638-4721-AD23-E23B6FAA6541}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Thanks and regards
Ipnotech

Inside Virtual Machine I see 10Gbps for 40GB nic

Hi,
I have a 40GB nic in HOST. I have created a virtual switch and assigned to the VM.
In host I see 40GB Link speed but in VM i see 10 Gbps only. Virtual switch does not support 40Gbps or any configuration issue?
Thanks in advance.
Thanks, Krishna

Hi Krishna,
"I have created a virtual switch and assigned to the VM."
After you did "assign" , the virtual switch still belongs to Host .
"assigned it to VM" it means you connected the VM's virtual NIC to the Virtual Switch .
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.

New UCS and VMware setup Questions

/* 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-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-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
We are currently in the process of migrating out vmware infrastructure from HP to UCS. We are utilizing the Virtual Connect Adapters for the project. With the migration we also plan on implementing the cisco nexus v1000 in our environment. I have demo equipment setup and have had a chance to install a test environment, but still have a few design questions.
When implementing the new setup, what is a good base setup for the virtual connect adapters with the v1000? How many Nics should I dedicate? Right now I run 6 nics per server (2 console, 2 Virtual Machines, and 2 Vmotion). Is this a setup I should continue with going forward? The only other thing I am looking to implement is another set of nics for nfs access. In a previous setup at a different job, we had 10 nics per server (2 console, 4 virtual machines, 2 vmotion and 2 iSCSI). Is there any kind of standard for this setup?
The reason I am asking is I want to get the most out of my vmware environment as we will be looking to migrate Tier 1 app servers once we get everything up and running.
Thanks for the help!

Tim,
Migrating from HP Virtual Connect (VC) -> UCS might change your network design slightly, for the better of course . Not sure if you're using 1G or 10G VC modules but I'll respond as if you've using 10G modules because this is what UCS will provide. VC modules provide a 10G interface that you can logically chop up into a max of 4 host vNIC interfaces totaling 10G. Though it's handy to divide a single 10G interfaces into virtual NICs for Service Console, VMotion, iSCSI etc, this creates the opportunity for wasted bandwidth. The logical NICs VC creates provides a max limit of bandwidth to the adapter. For example if create a 2GB interface for your host to use for vMotion, then 2G of your 10G pipe is wastes when there's no vMotions taking place!
UCS & 1000v offer a different solution in terms of bandwidth utilization by means of QoS. We feel it's more appropriate to specifiy a "minimum" bandwidth guarantee rather than a hard upper limit - leading to wasted pipe. Depending on which UCS blade and mezz card option you have, the # of adapters you can present to the Host varies. B200 blades can support one mezz card (with 2 x 10G interfaces) while the B250 and B440 are full width blades and support 2 Mezz cards. In terms of Mezz cards now, there's the Intel/Emulex/Qlogic/Broamcom/Cisco VIC options. In my opinion the M81KR (VIC) is best suited for virtualized environments as you can present up to 56 virtual interfaces to the host, each having various levels of QoS applied. When you roll the 1000v into the mix you have a lethal combination of adding some of the new QoS features that automatically match traffic types such as Service Console, iSCSI, VMotion etc. See this thread for a list/explanation of new features coming in the next verison of 1000v due out in a couple weeks https://www.myciscocommunity.com/message/61580#61580
Before you think about design too much, tell us what blades & adapters you're using and we can offer some suggestions for setting them up in the best configuration for your virtual infrastructure.
Regards,
Robert
BTW - Here's a couple Best Practice Guides with UCS & 1000v that you might find useful.

Maximising throughput of a team in converged networking scenario using Hyper-V virtual switch

Hi,
Recently I have been looking into the converged network scenario, I have read quite a few resources about this but I am struggling to make sense of maximising the bandwidth I have available.
I understand that a single TCP stream can only go down 1 physical NIC, so even if I had a team of 6 x 1Gbps NICS – the team would be 6Gbps, but I will never have a single transfer go faster than 1 Gbps. I’m pretty sure that’s right, how I understood it anyway.
To make a converged network, I need to team adapters together, then make a virtual switch, and make virtual NIC’s off of that virtual switch. Each vNIC I can assign for different purposes,
such as ISCSI, data sync and backup traffic. In the diagram below I have shown this configuration, each green pNIC is only 1Gbps, on my blue vNICs I use the minimum weighting configuration.
In my example below, I have 1 ISCSI vNIC, if a physical NIC failed then I understand that to mean that the bandwidth won’t reduce for ISCSI because a single stream can only go down one
NIC anyway, the team will reduce to 5Gbps. No vNIC will go faster than 1Gbps.
If this is correct, then how would I increase bandwidth to the disk system using ISCSI, is it simply a case of creating an additional vNIC for ISCSI traffic, adding it to the same team
and configuring MPIO so the traffic will eventually end up through different pNICS? In my mind, MPIO can’t round robin ISCSI data to more physical NICs because the ISCSI and MPIO only know about the vNIC, I assume it is the team that ultimately handles the
placement of the stream onto the pNICS.
Do I simply do the same for Data Sync and Backup traffic?
I’m not too concerned about the VMNET team, I am mostly focused on getting the best out of the core cluster resources I have. I haven’t shown the physical switches to the right of the diagram,
but these are already configured to accept the VLAN traffic on the ports and the same is all configured for the other half of the solution.
Just a little confused over the whole thing on how I could potentially achieve the 6Gbps I have at my disposal. In this configuration and testing so far, it seems quite difficult for me
to exceed about 1.5-2Gbps combined across all the vNICS (in this particular test server I am limited to 1 physical disk so it’s hard to gauge the performance, the disk will take probably about 200MB/2Gbps maximum, that’s with ISCSI (file copying) and data
Sync going on between two servers at the same time.
many thanks for your help
Steve

Hi,
Recently I have been looking into the converged network scenario, I have read quite a few resources about this but I am struggling to make sense of maximising the bandwidth I have available.
I understand that a single TCP stream can only go down 1 physical NIC, so even if I had a team of 6 x 1Gbps NICS – the team would be 6Gbps, but I will never have a single transfer go faster than 1 Gbps. I’m pretty sure that’s right, how I understood it anyway.
To make a converged network, I need to team adapters together, then make a virtual switch, and make virtual NIC’s off of that virtual switch. Each vNIC I can assign for different purposes,
such as ISCSI, data sync and backup traffic. In the diagram below I have shown this configuration, each green pNIC is only 1Gbps, on my blue vNICs I use the minimum weighting configuration.
In my example below, I have 1 ISCSI vNIC, if a physical NIC failed then I understand that to mean that the bandwidth won’t reduce for ISCSI because a single stream can only go down one
NIC anyway, the team will reduce to 5Gbps. No vNIC will go faster than 1Gbps.
If this is correct, then how would I increase bandwidth to the disk system using ISCSI, is it simply a case of creating an additional vNIC for ISCSI traffic, adding it to the same team
and configuring MPIO so the traffic will eventually end up through different pNICS? In my mind, MPIO can’t round robin ISCSI data to more physical NICs because the ISCSI and MPIO only know about the vNIC, I assume it is the team that ultimately handles the
placement of the stream onto the pNICS.
Do I simply do the same for Data Sync and Backup traffic?
I’m not too concerned about the VMNET team, I am mostly focused on getting the best out of the core cluster resources I have. I haven’t shown the physical switches to the right of the diagram,
but these are already configured to accept the VLAN traffic on the ports and the same is all configured for the other half of the solution.
Just a little confused over the whole thing on how I could potentially achieve the 6Gbps I have at my disposal. In this configuration and testing so far, it seems quite difficult for me
to exceed about 1.5-2Gbps combined across all the vNICS (in this particular test server I am limited to 1 physical disk so it’s hard to gauge the performance, the disk will take probably about 200MB/2Gbps maximum, that’s with ISCSI (file copying) and data
Sync going on between two servers at the same time.
many thanks for your help
Steve

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.

Bandwidth Maximums on UCS virtual NICs

Similar Messages

Maybe you are looking for