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

Brad Hedlund brhedlun at cisco.com
Fri May 22 21:53:12 EDT 2009


One thing you could do to make this transition hitless would be to first
apply "No Optimization" policies in your WAAS appliances for the flows in
question (VoIP call signaling).

Once this is done any new flows will go into "pass through" mode on WAAS
while existing flows are still optimized.  When all existing flows
eventually close you have no optimized connections for this traffic and you
can at this point apply your WCCP redirect list with no impact -- result #2.


Brad Hedlund
bhedlund at cisco.com

On 5/22/09 12:06 AM, "Dale Shaw" <dale.shaw+cisco-nsp at gmail.com> wrote:

> Hi all,
> On Fri, May 22, 2009 at 1:38 PM, Dale Shaw
> <dale.shaw+cisco-nsp at gmail.com> wrote:
>> Can anyone provide any insight?
> Thanks for the replies -- that makes sense. I'm proceeding on the
> basis that by _not_ intercepting/redirecting, the affected flows will
> barf, as I'm sure that TFO, at least, is in effect.
> FWIW, the affected TCP protocols are a bunch of Nortel media gateway
> to call server IPTel related (signalling) connections.
> 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