That's very odd, since traffic_wccp and traffic_manager link literally the same
code to perform WCCP operations. Any chance you can get a packet capture of the
two HERE_I_AM packets for comparison?
On Wednesday, November 30, 2016 9:49 AM, Chao Xu <xuc...@gmail.com> wrote:
Hi Alan,
I have setup an WCCP environment.
## Cisco Switch
R1#conf t
R1(config)#ip wccp 0
R1(config)#
R1#terminal monitor
R1#debug ip wccp events
WCCP events debugging is on
R1#debug ip wccp packets
WCCP packet info debugging is on
## ATS Configuration
add 2 lines into records.config
LOCAL proxy.config.wccp.addr STRING 192.168.0.211 // the ATS ip address
CONFIG proxy.config.wccp.services STRING /path/to/wccp.config
my wccp.config is:
services = (
{
name = "test";
description = "wccp test";
id = 0;
type = "DYNAMIC";
priority = 240;
protocol = 6;
primary-hash = ( "src_ip" );
ports = ( 80 );
assignment = ( "hash" );
forward = ( "l2" );
return = ( "l2" );
routers = ( "192.168.0.1" );
}
);
## Start the traffic_manager --debug "WCCP"
[E. Mgmt] log ==> [TrafficManager] using root directory '/usr'
[Nov 30 23:38:15.158] Manager {0x7f309db73740} NOTE:
[LocalManager::LocalManager] WCCP identifying address set to
"192.168.0.211".
[Nov 30 23:38:15.158] Manager {0x7f309db73740} NOTE:
[LocalManager::LocalManager] WCCP identifying address set to
"192.168.0.211".
traffic_server: using root directory '/usr'
[Nov 30 23:38:16.192] Manager {0x7f309db73740} DEBUG: (WCCP) 0 [0]: Sent
HERE_I_AM for SG 0 to seed router 192.168.0.1 [gen=#0,t=1480520296,n=108].
## Cisco Console
*Nov 30 15:41:11.322: WCCP-EVNT:D0: Here_I_Am packet from 172.22.21.211
ignored; bad web-cache id
*Nov 30 15:41:21.302: WCCP-EVNT:D0: Here_I_Am packet from 172.22.21.211
ignored; bad web-cache id
## Start the traffic_wccp --debug --address 192.168.0.211 --service
/etc/trafficserver/wccp.config
0 [0]: Sent HERE_I_AM for SG 0 to seed router 192.168.0.1
[gen=#0,t=1480520712,n=108].
0 [0]: Received WCCP2_I_SEE_YOU for group 0.
0 [1]: Added source router 192.168.0.1 to view 0
0 [0]: Service group 0 view change (1)
## Cisco Console
*Nov 30 15:44:17.398: WCCP-EVNT:D0: updating wc orig assign info
*Nov 30 15:44:17.402: WCCP-EVNT:D0: allocate wc orig hash info (40 bytes)
*Nov 30 15:44:17.402: WCCP-PKT:D0: Sending I_See_You packet to
192.168.0.211 w/ rcv_id 00000004
*Nov 30 15:44:27.514: WCCP-EVNT:D0: created adjacency interest,
192.168.0.211
*Nov 30 15:44:27.522: WCCP-EVNT:D0: nexthop update oce for wc 192.168.0.211
0x66824670
*Nov 30 15:44:27.522: WCCP-EVNT:D0: track nexthop for wc 192.168.0.211 (OK)
*Nov 30 15:44:27.522: %WCCP-5-SERVICEFOUND: Service 0 acquired on WCCP
client 192.168.0.211
*Nov 30 15:44:27.526: WCCP-PKT:D0: Received valid Here_I_Am packet from
192.168.0.211 w/rcv_id 00000004
The traffic_manager and traffic_wccp is different.
It seems traffic_manager not working properly.
I will try "ip wccp web-cache" with "STANDARD" in wccp.config later.
Oknet Xu
2016-11-30 18:46 GMT+08:00 Chao Xu <xuc...@gmail.com>:
> Hi Alan,
>
> 1) ./configure with "--enabled-wccp"
> 2) The WCCP configuration in records.config
>
> proxy.config.wccp.addr STRING 192.168.0.1 // the wccp router ip
>
> proxy.config.wccp.services STRING /path/to/wccp.config
>
> The wccp.config is setup by guide https://docs.
> trafficserver.apache.org/en/latest/admin-guide/configuration/transparent-
> proxy/wccp-service-config.en.html
>
>
> I will setup a WCCP environment and try it again.
>
>
> Oknet Xu
>
> 2016-11-30 0:44 GMT+08:00 Alan Carroll <solidwallofcode@yahoo-inc.
> com.invalid>:
>
>> As far as I know, WCCP is considered a finished feature and there is no
>> ongoing development. It is still just WCCP V2 because, AFAIK, WCCP V3 was
>> never released. I haven't used it for a while but I don't see what would
>> have broken it. Did you (1) --enable-wccp and (2) install a WCCP
>> configuration file for ATS?
>>
>>
>> On Tuesday, November 29, 2016 9:52 AM, Chao Xu <xuc...@gmail.com>
>> wrote:
>>
>>
>> I tried to setup WCCP with ATS 6.0.x but it did not work correctly.
>>
>> I really need it work correctly in Q1, 2017.
>>
>> It will be great if you could share any document or guidelines to support
>> me.
>>
>> BTW, do you known which ATS version the WCCP worked correctly ?
>>
>> Thanks.
>>
>> Oknet Xu
>>
>> 2016-11-29 22:38 GMT+08:00 Jonathan Adams <jonathan.ad...@clearswift.com
>> >:
>>
>> > Hi,
>> >
>> > I've been experimenting with WCCP support in ATS and had some questions.
>> >
>> > What is the current status of this support? Is it still under active
>> > development or is it considered "done"?
>> >
>> > I'm trying to use it with a gre tunnel and it is not registering with
>> the
>> > router properly. Based on my (limited) understanding of WCCP (and
>> comparing
>> > it to an alternative implementation) it appears to be doing the wrong
>> > thing. If I were to try and fix this how safe is it to *not* maintain
>> the
>> > existing behaviour?
>> >
>> > If I were to make changes it's unlikely I'd get time to do so for a
>> while
>> > (say, at least a year). Given the current rate of development in this
>> area
>> > would you expect anything to change in that time? Or can I assume that
>> > things will stay pretty much as they are currently?
>> >
>> > Thanks,
>> >
>> > Jonathan.
>> >
>> >
>> > Jonathan Adams
>> >
>> > Software Engineer
>> >
>> > [Telephone] +44 118 903 8610
>> >
>> > [Twitter]@clearswift
>> >
>> > [Clearswift] <http://www.clearswift.com/>
>> >
>> > 1310 Waterside | Arlington Business Park | Theale | Berkshire | RG7 4SA
>> |
>> > United Kingdom
>> >
>> > RELEASED: Clearswift v4.5 Gateways. Upgrade to the latest Clearswift
>> > technology today. Learn more here.<https://www.clearswift.
>> > com/training-and-support/migration-and-upgrades>
>> >
>> > This e-mail and any files transmitted with it are strictly confidential,
>> > may be privileged and are intended only for use by the addressee unless
>> > otherwise indicated. If you are not the intended recipient any use,
>> > dissemination, printing or copying is strictly prohibited and may be
>> > unlawful. If you have received this e-mail in error, please delete it
>> > immediately and contact the sender as soon as possible. Clearswift
>> cannot
>> > be held liable for delays in receipt of an email or any errors in its
>> > content. Clearswift accepts no responsibility once an e-mail and any
>> > attachments leave us. Unless expressly stated, opinions in this message
>> are
>> > those of the individual sender and not of Clearswift.
>> >
>> > This email message has been inspected by Clearswift for inappropriate
>> > content and security threats.
>> >
>> > To find out more about Clearswift’s solutions please visit
>> > www.clearswift.com
>> >
>> >
>>
>>
>>
>
>
