WAAS POC - INline Deployment on VSAT Link

Unanswered Question
Aug 26th, 2010
User Badges:

HI,


I am trying to setup a POC for WAAS using inline in a VSAT environment. Once i've deployed the two devices inline am able to see traffic on the device using the command, "show stat connection" unfortunately they don't have any peer created. AM thinking this could be reason why optimizatin is not happening like it's supposed to.


When i do a traceroute from each of the WAAS devices they don't seem to use the same route. They show different hops in the service provider network. I was wondering if i create a GRE tunnel between the two sites, would it be able to optimize? would it resolve my problem? See below a caption of the "show stat connection" output


"Edge-WAE#sh stat conn


Current Active Optimized Flows:                      1
   Current Active Optimized TCP Plus Flows:          1
   Current Active Optimized TCP Only Flows:          0
   Current Active Optimized TCP Preposition Flows:   0
Current Active Auto-Discovery Flows:                 12
Current Reserved Flows:                              10
Current Active Pass-Through Flows:                   28
Historical Flows:                                    100



D:DRE,L:LZ,T:TCP Optimization RR:Total Reduction Ratio
A:AOIM,C:CIFS,E:EPM,G:GENERIC,H:HTTP,M:MAPI,N:NFS,S:SSL,V:VIDEO


ConnID        Source IP:Port          Dest IP:Port            PeerID Accel RR
  1503       10.27.2.7:17113        10.2.1.235:135               N/A E     00.0%
O-ST: Origin State, T-ST: Terminal State
E: Established, S: Syn, A: Ack, F: Fin, R: Reset
s: sent, r: received, O: Options, P: Passthrough


Local IP:Port       Remote IP:Port      Peer ID           O-ST T-ST ConnType
10.2.1.66:8088      10.27.2.29:4426     N/A               Sr   Sso  EXTERNAL CLIENT
10.2.5.206:445      10.27.2.33:1394     N/A               Sr   Ss   EXTERNAL CL
ENT
10.2.5.206:139      10.27.2.33:1395     N/A               Sr   Ss   EXTERNAL CL
ENT
10.2.1.66:8080      10.27.2.39:1711     N/A               Sr   Sso  EXTERNAL CL
ENT
10.2.1.78:8080      10.27.2.39:1717     N/A               Sr   Ss   EXTERNAL CL
ENT
10.2.1.78:8080      10.27.2.39:1718     N/A               Sr   Ss   EXTERNAL CL
ENT
10.2.1.66:8080      10.27.2.39:1716     N/A               Sr   Sso  EXTERNAL CL
ENT
10.2.1.66:8080      10.27.2.39:1712     N/A               Sr   Sso  EXTERNAL CL
ENT
10.2.1.66:8080      10.27.2.39:1713     N/A               Sr   Sso  EXTERNAL CL
ENT"


WIll appreciate prompt response. I've attached a topology diagram of the setup.


Thanks, Joy.

Attachment: 
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Michael Korenbaum Thu, 08/26/2010 - 08:24
User Badges:
  • Bronze, 100 points or more

Joy,


In past experience we have seen that VSAT providers add their own TCP options and/or strip the WAAS TCP options during the 3-way handshake.  Thus, making it impossible for the two WAEs to peer/ optimize TCP flows.


There are two options to resolve this situation (assuming the traffic is correctly being redirected/ traversing both WAEs).


1)  Contact the VSAT provider and ask them to configure their equipment to allow the WAAS TCP option 33 (0x21 HEX) in the TCP 3-way handshake.


2)  Build a GRE tunnel between your two sites so the VSAT provider equipment can not modify the TCP SYN/SYN-ACK packets option field after it leaves your WAAS devices.


Cheers,


Mike Korenbaum



Cisco WAAS PDI Help Desk

http://www.cisco.com/go/pdihelpdesk

P.S.  If this answers your question please mark it as answered with a 5.

Actions

This Discussion