From: ccie2be (ccie2be@nyc.rr.com)
Date: Thu Jun 09 2005 - 16:50:03 GMT-3
From a lab point of view, unless there's an explicit requirement to use as
little overhead as possible, it won't matter if wccp is applied in the in or
out direction.
The real issue is on what type of interfaces can wccp be applied to.
L2 or L3, or SVI or BVI or logical, etc etc.
Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
sumit.kumar@comcast.net
Sent: Thursday, June 09, 2005 3:44 PM
To: Zouta oxpf
Cc: Varthis Vassilantonakis; Groupstudy
Subject: Re: WCCP redirect in
Well I disagree there, the recommendations were changed for v2.
As longs as you are provided with an input interface you shouldnot use "out"
since it adds overhead.
Here's an excerpt from CCO doc.
"As indicated by the out and in keyword options in the ip wccp service
redirect command, redirection can be specified for outbound interfaces or
inbound interfaces. Inbound traffic can be configured to use Cisco Express
Forwarding (CEF), Fast Forwarding, or Process Forwarding.
Configuring WCCP for redirection for inbound traffic on interfaces allows
you to avoid the overhead associated with CEF forwarding for outbound
traffic. Setting an output feature on any interface results in the slower
switching path of the feature being taken by all packets arriving at all
interfaces. Setting an input feature on an interface results in only those
packets arriving at that interface taking the configured feature path;
packets arriving at other interfaces will use the faster default path.
Configuring WCCP for inbound traffic also allows packets to be classified
before the routing table lookup, which translates into faster redirection of
packets."
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuratio
n_guide_chapter09186a008030c778.html#wp1001272
-------------- Original message --------------
> From the router's perspective, its always: ip wccp web-cache redirect
> out; at the interface connected to the web server (internet). The
> router is saying send all web traffic out this interface meant for
> this web server to the Cache engine.
>
> Seems like the thinking is different for the switches (3550s at
> least). The command:
> ip wccp web-cache redirect in; is configured on the interface where
> the clients are, which is something like: send all web traffic
> received on this interface and meant for the Web server to the cache
> engine.
>
> I'm not sure if configuring the clients interface on a router with ip
> wccp web-cache redirect in, is correct or not (it seems reasonable)
> but without a real cache engine to lab it up I'll stick with the norm.
>
> HTH
> ZO.
>
>
>
> On 6/9/05, sumit.kumar@comcast.net wrote:
> > Varthis,
> >
> > You should look at the direction of traffic to be re-directed.
> >
> >
> > Sumit
> > -------------- Original message --------------
> >
> > > Hello group,
> > >
> > > I am a bit confused with wccp.
> > > When should ip wccp web-cache redirect in ... be used ?
> > >
> > > To figure out the direction, should we look on where the web-cache
> > > server is actually located in respect with our router being configured
> > > or is it something else?
> > > And what happens if we have our users and our web-cache server located
> > > on the same subnet (on the same lan, and under for example RouterA's
> > > ethernet ). What should be configured then on RouterA???
> > >
> > > redirect out or redirect in?
> > >
> > > TIA
> > >
> > > Varthis
> > >
> > >
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:41 GMT-3