Jumbo frames in team NIC's

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Hi, I want to enable jumbo frames for my Hyper-V VM's and live migration NIC's.
In google I found articles stating to only needing to enable jumbo frames in the VM NIC, and other articles stating to only do it on the actual host team member NIC's.

Which is it?
Physical team member NIC's?
Virtual team NIC?
Virtual VM NIC?
Combination?

P.
 

weust

Active Member
Aug 15, 2014
353
44
28
44
Virtual Machine NIC would make no sense as you're Live Migration a VM, no the Guest OS of the VM.

Here at work I use Qlogic QLE3242 adapters with four VNICs per port.
Teams are made of one VNIC per physical port (Port 1 Function 0 and Port 2 Function 1 for example).
On both VNICs I enable 9014 packet size (forgot the exact naming).

Note that I use the QLogic teaming software of the driver, not Windows Teaming.
Also, I don't use Jumbo Frames for the Live Migration team members. I have seen over 7 or 8Gbit/s while doing Live Migrations.
I do use them for the iSCSI team members. Which is even a VMSwitch too (for SQL 2012 servers) and here I do need to enable Jumbo Frames on the vEthernet created because of AllowManagement $true.

Anyway, you need to enable it on the adapters. Physical and teaming adapter.
 
Thanks for the reply.
After trying various unsuccessful combinations I reverted everything back to normal.

I am using an Intel I350T4 adapters and HP 1810 v2 switches.
I am testing using mturoute (mturoute.exe - official site

The team NIC does not have a jumbo frame configuration option.
There is a hidden multiplexor NIC that does have a jumbo option, but made no difference.

The only combination I've yet to try is to break the team, then set jumbo on all team members, then recreate the team.
I'll do this in a couple weeks when I can bring the server down.
 

weust

Active Member
Aug 15, 2014
353
44
28
44
A hidden multiplexor NIC? A Get-NetAdapter doesn't show it?

Anyway, please post back here. Would like to know the result.
 

weust

Active Member
Aug 15, 2014
353
44
28
44
Odd. The second link is how I do things for my iSCSI VMSwitch.
It connects to a NetApp with Jumbo Packets enabled.

The first link is way too cumbersome imo.
Sound like "scripting because I can" instead of typing one line (two if you need to know the interface index number or name".

But again, why use Jumbo Packets for Live Migration?
Do you have a paper or something about that?
 

weust

Active Member
Aug 15, 2014
353
44
28
44
Alright, get your point. And yes, it should work.
But are the ports on your switches configured to accept anything above the default 1472(forgot the exact default value).
 

legen

Active Member
Mar 6, 2013
213
39
28
Sweden
Everything in your communication chain needs to support jumbo frames. So start by testing parts of your communication chain with i.e. a laptop. Use the following list of commands for sending a jumbo frames ICMP packet,
Windows
ping -f -l 8958 IP_of_another_machine

OmniOS/Solaris
ping -s IP_of_another_machine 9000 4

Linux/xenserver
ping -M do -s 8972 IP_of_another_machine
If hyper-v to laptop works continue to hyper-v -> switch -> laptop etc etc.