Re: WCCP redirect out/in

From: Stefan Brunner (s_brunner1@gmx.net)
Date: Sun Jul 11 2004 - 14:53:12 GMT-3


Hello Scott,

I understand the redirect in, but why do you also say that it needs a
redirect out on S1.

Cisco's Doc example only has redirect in, with no redirect
out.

http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12120ea2/3550scg/swwccp.htm

Also, do you know why Cisco's example specify Layer 3 routing on the client
& internet connected interfaces. (Not on the Cache engine interface). None
of the configs I have seen so far had this implemented. Is this needed ?

Thanks Stefan

e-mail: s_brunner1@gmx.net

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: Saturday, March 08, 2003 17:38 PM
To: ccielab@groupstudy.com
Subject: WCCP redirect out/in

The application of the statement depends on the flow of traffic!

Given your example, think of the way that http requests will be going.
>From Clients to the internet, the requests will be:

INbound to E0
OUTbound to S1

You can apply the statement in either location. As far as the "why" one or
the other, in your example the effect would be the same. In a larger
router, you may have different statements inbound in different client
interfaces (perhaps more than one cache engine), or just one statement
outbound on S1 to catch ALL clients together.

Hope that helps.

Scott

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of S
kumar
Sent: Saturday, March 08, 2003 10:57 AM
To: ccielab@groupstudy.com
Subject: WCCP redirect out/in

All,

Please explain the ip wccp web-cache redirect out/ in.
I found some documentation just refering to "out" and
a document said using "in" is better and gives better performance.

In a scnerio like this

    E0(Clients)
    --------R1-------------E2 ( Cache-Engine)
             |
             |
             |S1(Internet)

Where should I apply ip wccp web-cache redirect
out/in.
Will appreciate any help.

S K



This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:52 GMT-3