RE: TCP Window Optiimization with LFN.

This is a nasty issue - and can't be fixed easily...

You really need the Riverbed Steelhead appliance... it's like buying a BMW M5 for each location - but it works...

The only thing I can offer you is Windows 2008 R2 has a much improved stack out of the box, or if you can optimize your software to use "many" 3 Mbps transfers to get the aggregate bandwidth...

We tried adjusting windows 2003 server registry settings for many months - nothing but the riverbed worked..

Long Fat Networks are up there "Greedy Trial Lawyers" on my list of people to send to Mars with a limited oxygen supply

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of JB Poplawski
Sent: Thursday, August 16, 2012 2:07 PM
To: ccielab_at_groupstudy.com
Subject: TCP Window Optiimization with LFN.

Good afternoon,

My token question out to the group as I await TAC.

I have a network with Gb links between sites. Connected like such:
   Site A < 7ms > Site B < 71ms > Site C <9ms> Site D

End to end latency between Site A and Site D is 69ms. My numbers above are the average given from CLI.

I've been reading on LFNs (Long Fat Networks) and basically I need to optimize the TCP Window size (calculated to 8625KB).

My question, where do I implement it?
Site A and Site D? Or Site B and Site C?

If I implement on Site B and Site C, how does that impact Site C to Site D, etc?

Any ideas?

We previously had MPLS connection with WAAS which optimized traffic. Now since we're running Gb, we removed WAAS (our WAAS boxes were only rated to 50Mbps).

Any suggestions? Am I on the right path?

Any help is greatly appreciated.
JB

Blogs and organic groups at http://www.ccie.net
Received on Thu Aug 16 2012 - 18:21:26 ART