From: Raulinaitis, James (jamesr@netinfosys.com)
Date: Wed Jan 03 2007 - 04:00:57 ART
The topology diagram in that link doesn't reference the same interface
IDs as the sample router configuration. I believe this is throwing you
off. I think you have it correct.
Using the topology in the CCO link the following would cache client
requests from the MyClientLAN network.
interface Ethernet1/0
description MyClientLAN
ip address 10.1.0.1 255.255.255.0
ip wccp web-cache redirect in
! this means redirect web requests as they come IN the E1/0 interface
or
interface Ethernet0/0
description MyInternetConnection
ip address NOT_GIVEN?
ip wccp web-cache redirect out
! this means redirect web requests as they go OUT the E0/0 interface
I believe you can do just the opposite if you wanted to offload content
from an internal Web Server to clients on the internet, but typically
the above example is what you want.
- James
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Michy Eika
Sent: Wednesday, January 03, 2007 1:13 AM
To: 'Scott Morris'
Cc: ccielab@groupstudy.com
Subject: RE: IP WCCP
Thanks for your response.
For this topology in the following URL
http://www.cisco.com/warp/public/117/cache_engine/transparentconfig.html
I think It looks like below.
Client --> (IN) e1/0 (router) e0/0 (OUT) --> Internet
In the Above URL, the sample configuration is below.
interface Ethernet0/0
ip address 10.1.0.1 255.255.255.0
ip wccp web-cache redirect in <-----
full-duplex
In my opinion, it should be below.
interface Ethernet0/0
ip address 10.1.0.1 255.255.255.0
ip wccp web-cache redirect out
full-duplex
or
interface Ethernet1/0
ip address 10.1.0.1 255.255.255.0
ip wccp web-cache redirect in
full-duplex
Is this correct ?
Michy
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: Wednesday, January 03, 2007 1:43 PM
To: 'Michy Eika'; ccielab@groupstudy.com
Subject: RE: IP WCCP
The direction is from the perspective of the router itself....
Client --> (IN) Fa0/0 (router) S0/0 (OUT) --> Internet
You can intercept that stream of traffic at either point, and redirect
it to
a web-cache server. But the perspective is always that of the router.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
IPexpert VP - Curriculum Development
IPexpert Sr. Technical Instructor
smorris@ipexpert.com
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Michy Eika
Sent: Tuesday, January 02, 2007 10:31 PM
To: ccielab@groupstudy.com
Subject: RE: IP WCCP
According to this mail which was discussed about WCCP so far, following
URL
sample seems not to be a proper configuration.
http://www.cisco.com/warp/public/117/cache_engine/transparentconfig.html
[Abr]
interface Ethernet0/0
ip address 10.1.0.1 255.255.255.0
ip wccp web-cache redirect in <-----
full-duplex
In my opinion, the configuration below will be correct.
interface Ethernet0/0
ip address 10.1.0.1 255.255.255.0
ip wccp web-cache redirect out
full-duplex
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: Wednesday, October 11, 2006 1:01 AM
To: 'sabrina pittarel'; 'Chris Broadway'; ccielab@groupstudy.com
Subject: RE: IP WCCP
It means you could put inbound from all other interfaces (except the one
you're trying to avoid), or you could use the redirect-list portion of
the
global command to create an ACL with exclusions.
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
IPExpert VP - Curriculum Development
IPExpert Sr. Technical Instructor
smorris@ipexpert.com
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
sabrina pittarel
Sent: Tuesday, October 10, 2006 11:20 AM
To: Chris Broadway; ccielab@groupstudy.com
Subject: Re: IP WCCP
Think it in this way....
"inbound" means:
redirect all "inbound" traffic on
this interface to the cache engine(s)
"outbound" means:
redirect all
"outbound" traffic on this interface to the cache engine(s).
When you
configure WCCP on outbound direction you can exclude from redirection
some
ingress interface using the "redirect exclude in" intf command.
What it means
is the following:
"redirect to the cache engines all traffic outbound interface X, except
if
it was received on interface Y"
Hope this helps
Sabrina
----- Original Message ----
From: Scott Morris <swm@emanon.com>
To:
Chris Broadway <midatlanticnet@gmail.com>; ccielab@groupstudy.com
Sent:
Tuesday, October 10, 2006 6:31:27 AM
Subject: RE: IP WCCP
The redirect is
always from the perspective of the router. So follow the packet
(location
of the cache is mostly irrelevant for this).
User ------> (fa0/0) Router (s0/0)
----> Internet
As a user makes the request, AT the fa0/0 interface, this would be
inbound.
The same packet at the s0/0 interface would be outbound.
Make a choice!
It's useful in case there are multiple interfaces on your router (with
users) and you want to redirect some but not others. Just one redirect
is
necessary though.
I believe about 8-9 months ago there was a fairly detailed discussion
about
web caching and the actual packet flow on here if you want to search the
archives.
HTH,
Scott Morris, CCIE4
(R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE #153, CISSP, et
al.
CCSI/JNCI-M/JNCI-J
IPExpert VP - Curriculum Development
IPExpert Sr. Technical
Instructor
smorris@ipexpert.com
http://www.ipexpert.com
-----Original
Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Chris Broadway
Sent: Tuesday, October 10, 2006 9:05 AM
To:
ccielab@groupstudy.com
Subject: IP WCCP
Group,
I am a little confused by the
DOC on wccp. If I have a web cache system downstream on R1's E1
interface,
would my redirects be inbound or outbound?
From the DOC I get the impression
that the redirect command might mean what flow of traffic do I want to
redirect. For example, If I have traffic coming in on E0 and my web
cache
system is out e1, I would "redirect inbound on E0"...But I always
thought
the redirect was suppose to point to the cache system. In this case
there
would be a "redirect outbound" on E1. Did I mis read the doc?
-Broadway
This archive was generated by hypermail 2.1.4 : Thu Feb 08 2007 - 23:46:55 ART