I'm using a Cisco AG3560 to run my wccp re-direct and have MWG 7.3. The MWG is ste to use "Proxy (Optional WCCP)"
However, we are having the damnest time getting it to redirect traffic. It had been working for over a year, then out of the blue it just stopped working.
My IP for the web gateway is 10.1.252.19, and my wccp router is 10.1.252.10.
For whatever reason the web gateway is able to see the router and the "here i am packets" but I cannot get anything to redirect to it.
My wccp config is below.
ip wccp 51 redirect-list 120
ip address 10.1.254.17 255.255.255.255
description McAfee web gateway
switchport access vlan 1001
switchport mode access
ip address 10.1.252.10 255.255.255.252
ip wccp 51 redirect in
ip address 10.1.252.17 255.255.255.240
access-list 120 permit ip any any
Also here is my output for ip wccp view.
#sh ip wccp 51 view
WCCP Routers Informed of:
WCCP Clients Visible:
WCCP Clients NOT Visible:
I have the Web Gateway setup with process 51 and my wccp router on the MWG is 10.1.252.10.
I opened a ticket with McAfee support and the engineer was very helpful and examined our configs and feedback files. Here is the McAfee Engineer's response in red:
Everything on your Web Gateway configuration looks good,and the Cisco config seems OK as well.
Ultimately, we can see that the router sends 'I See You'packets to the Web Gateway, but does not assign any buckets to the WebGateway. As such, your router is notsending web traffic to the Web Gateway.
Take a look at the attached screenshot. We can see that, indeed the Router sends 'ISee You' packets back to the Web Gateway.
We see that the 'Receive ID' is valid, as it isincrementing properly each time.
The Forwarding method matches what you have defined inyour Web Gateway configuration, which looks OK.
However, there is an 'Unknown Capability Element' thatappears to be the result of a mismatch in configuration somewhere.
As a result, we don't ever see 'bucket assigments' in the'I See You' packets, and the router is not sending us data.
We are still waiting to hear back from Cisco on this as well.
I've attached screenshots of the configs
We've been working on this for nearly two weeks now trying to get it working and I have a feeling it is going to be something extremely silly. (Isn't it always something silly on problems that take forever to resolve?)