[132496] in North American Network Operators' Group
Re: Jumbo frame Question
daemon@ATHENA.MIT.EDU (Jon Meek)
Fri Nov 26 12:16:55 2010
In-Reply-To: <OFC3AC63A5.89DA6AE7-ON482577E6.0083ABB6-482577E7.00014359@hk1.ibm.com>
Date: Fri, 26 Nov 2010 12:16:48 -0500
From: Jon Meek <meekjt@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I have the "opposite problem". I use iperf to test WAN and VPN
throughput and packet loss, but find that the sending Linux system
starts out with the expected MTU / MSS but then ramps up the packet
size to way beyond 1500. The result is that network equipment must
fragment the packets. On higher bandwidth circuits there are a lot of
re-transmits that mask any real packet loss that might exist in the
path.
I have tried multiple methods to clamp the MTU, but nothing has worked
so far. This leads me to wonder how often real bulk transfer
applications start using jumbo packets that just end up getting
fragmented downstream.
The jumbo packets from iperf occur on various versions of the Linux
kernel and different distributions. It might only happen on GigE.
Suggestions on clamping the MTU are welcome.
Thanks,
Jon
On Thu, Nov 25, 2010 at 7:13 PM, Harris Hui <harris.hui@hk1.ibm.com> wrote:
>
> Hi
>
> Does anyone have experience on design / implementing the Jumbo frame
> enabled network?
