@nanog.org
Subject: Re: TCP Performance
If you have a router, you can turn on shaping to the bandwidth the link
will support.
-Blake
On Tue, Aug 27, 2013 at 12:11 PM, Nick Olsen n...@flhsi.com wrote:
I do indeed have stats for TX Pause Frames And they do increment.
However, Our router
Warnock tim...@timoid.org, nanog@nanog.org nanog@nanog.org
Subject: Re: TCP Performance
If you have a router, you can turn on shaping to the bandwidth the link
will support.
-Blake
On Tue, Aug 27, 2013 at 12:11 PM, Nick Olsen n...@flhsi.com wrote:
I do indeed have stats for TX Pause Frames
You didn't indicate this, but do you understand how TCP windowing works?
This conversation can go two very different ways depending on the answer.
To me, it looks like this is what you'd expect, and you need to fix your
packet loss issues, which possibly might be QoS settings related (but it's
Duplex mismatch has been checked across the board. On every device.
Nick Olsen
Network Operations (855) FLSPEED x106
From: Chad Dailey na...@thedaileyplanet.com
Sent: Tuesday, August 27, 2013 10:48 AM
To: n...@flhsi.com
Subject: Re: TCP Performance
@nanog.org nanog@nanog.org
Subject: Re: TCP Performance
You didn't indicate this, but do you understand how TCP windowing works?
This conversation can go two very different ways depending on the answer.
To me, it looks like this is what you'd expect, and you need to fix your
packet loss issues, which
Operations (855) FLSPEED x106
From: Chad Dailey na...@thedaileyplanet.com
Sent: Tuesday, August 27, 2013 10:48 AM
To: n...@flhsi.com
Subject: Re: TCP Performance
Check for duplex mismatch at the server.
On Mon, Aug 26, 2013 at 2:07 PM, Nick Olsen n
Regardless, your problem looks like either tail drops or packet loss, which
you showed originally. The task is to find out where this is occurring, and
which of the two it is. If you want to confirm what is going on, there are
some great bandwidth calculators on the internet which will show
...@flhsi.com n...@flhsi.com
*Cc*: nanog@nanog.org nanog@nanog.org
*Subject*: RE: TCP Performance
Regardless, your problem looks like either tail drops or packet loss,
which
you showed originally. The task is to find out where this is occurring,
and
which of the two it is. If you want
x106
From: Blake Dunlap iki...@gmail.com
Sent: Tuesday, August 27, 2013 11:42 AM
To: n...@flhsi.com
Cc: na...@thedaileyplanet.com, nanog@nanog.org nanog@nanog.org
Subject: Re: TCP Performance
This really sounds like you aren't testing the correct flow type
From: Tim Warnock tim...@timoid.org
Sent: Tuesday, August 27, 2013 1:08 PM
To: Blake Dunlap iki...@gmail.com, n...@flhsi.com n...@flhsi.com
Cc: nanog@nanog.org nanog@nanog.org
Subject: RE: TCP Performance
Regardless, your problem looks like either tail drops or packet loss,
which
Operations (855) FLSPEED x106
From: Blake Dunlap iki...@gmail.com
Sent: Tuesday, August 27, 2013 1:32 PM
To: n...@flhsi.com
Cc: Tim Warnock tim...@timoid.org, nanog@nanog.org nanog@nanog.org
Subject: Re: TCP Performance
If you have a router, you can turn
11 matches
Mail list logo
