[173467] in North American Network Operators' Group
Re: TCP Window Scaling issue
daemon@ATHENA.MIT.EDU (Larry Sheldon)
Thu Jul 24 22:09:36 2014
X-Original-To: nanog@nanog.org
Date: Thu, 24 Jul 2014 21:07:44 -0500
From: Larry Sheldon <LarrySheldon@cox.net>
To: nanog@nanog.org
In-Reply-To: <WGxi1o01H1cZc5601Gxkuh>
Errors-To: nanog-bounces@nanog.org
On 7/24/2014 11:51 AM, Zach Hill wrote:
> Also just to reiterate I would lean more heavily on something fishing in
> the WAN cloud if all traffic from Site 1 to Site 2 were not seeing tcp
> window scaling properly, however it's only for Server A that is seeing
> this. Server A is able to properly TCP window scale for any local traffic.
>
>
> On Thu, Jul 24, 2014 at 12:47 PM, Zach Hill <zach.reborn@gmail.com> wrote:
>
>> Hi Machael,
>>
>> Let me setup another packet capture at each side to see if the initial
>> packets are being modified at all.
>>
>> Thanks,
>>
>>
>> On Thu, Jul 24, 2014 at 12:39 PM, Michael Brown <michael@supermathie.net>
>> wrote:
>>
>>> On 14-07-24 12:30 PM, Zach Hill wrote:
>>>> Hi Tony. No firewall in the way.
>>>>
>>>> Physical flow is as below.
>>>>
>>>> Server A -> Nexus 7k -> 3845 router -> Sprint MPLS -> 3845 router ->
>>> Cisco
>>>> 3750x stack -> Server B
>>>>
>>> I blame the cloud.
>>>
>>> Dump the actual packets as they leave Server A and arrive at Server B
>>> (and vice-versa!). Does it get modified en route?
>>>
>>> M.
>>>
>>> --
>>> Michael Brown | The true sysadmin does not adjust his behaviour
>>> Systems Administrator | to fit the machine. He adjusts the machine
>>> michael@supermathie.net | until it behaves properly. With a hammer,
>>> | if necessary. - Brian
>>>
>>>
>>
>
--
Requiescas in pace o email Two identifying characteristics
of System Administrators:
Ex turpi causa non oritur actio Infallibility, and the ability to
learn from their mistakes.
(Adapted from Stephen Pinker)
