wccp2 and squid reload semantics

From: Adrian Chadd <adrian@dont-contact.us>
Date: Tue, 18 Apr 2006 10:49:45 +0800

Hiya,

I've completed the WCCP2 configuration changes. Here's an example setup
from the cachemgr config output:

wccp2_router 192.168.2.2:2048
wccp2_version 4
wccp2_forwarding_method 1
wccp2_return_method 1
wccp2_service dynamic 80
wccp2_service standard 0
wccp2_service_info 80 priority=240 flags=src_ip_hash,ports_defined ports=80,81,82,83 protocol=tcp
wccp2_incoming_address 0.0.0.0
wccp2_outgoing_address 255.255.255.255

(Its a bit redundant, but you get the idea.)

What should the cache reload semantics be when Squid is reloaded?
Should I just start sending the updated here_i_am messages and let
the routers sort everything out? Or is there a better way to handle
this?

Adrian
Received on Mon Apr 17 2006 - 20:51:08 MDT

This archive was generated by hypermail pre-2.1.9 : Mon May 01 2006 - 12:00:03 MDT