[c-nsp] WCCPv2 - what happens to existing connections when redirect-list is modified?

Brad Hedlund brhedlun at cisco.com
Thu May 21 23:58:01 EDT 2009


If the affected flows are NOT being optimized by WAAS (pass-through
connections), your result should be #2.

If the affected flows ARE being optimized by WAAS, your result should be #3.


Brad Hedlund
bhedlund at cisco.com

On 5/21/09 10:38 PM, "Dale Shaw" <dale.shaw+cisco-nsp at gmail.com> wrote:

> Hi all,
> Scenario: WCCPv2 configured and active for WAAS, all TCP traffic
> redirected (no redirect-list configured for service groups 61 and 62)
> What happens to active/existing TCP sessions that _are_ being
> intercepted/redirected if I configure a redirect-list with a 'deny'
> statement that matches the session?
> I'm not intimately familiar with WCCPv2 operation but I assume these
> are the possibilities:
> 1) existing connections are not affected and continue to be
> intercepted/redirected in spite of ACL; new connections are not
> intercepted/redirected; WCCP is smart!
> 2) new packets for existing connections stop being
> intercepted/redirected and are routed normally - TCP copes OK and
> sessions stay up; TCP is amazing!
> 3) as above, but TCP does not cope, as SEQs/ACKs etc. change; sessions
> are torn down/time out; TCP is only human
> 4) something else :-)
> Can anyone provide any insight?
> Adrian Chadd, I'm shining the bat torch towards the sky, are you out there?
> :-)
> cheers,
> Dale
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list