> -----Original Message----- > From: Kris [mailto:christian@xxxxxxxxx] Hi Kris > 2. TCP Connection Failed Are you running iptables? If so, is the conntrack table overflowing? > my peer config > # cache_peer 10.10.10.10 sibling 3128 3130 no-netdb-exchange no-digest > no-delay round-robin proxy-only > cache_peer 10.10.10.11 sibling 3128 3130 no-netdb-exchange no-digest > no-delay round-robin proxy-only > cache_peer 10.10.10.12 sibling 3128 3130 no-netdb-exchange no-digest > no-delay round-robin proxy-only > cache_peer 10.10.10.13 sibling 3128 3130 no-netdb-exchange no-digest > no-delay round-robin proxy-only > > any suggestion what best configuration for sibling peer ? I'm not sure the above is going to give you good results. Enabling digest would save a lot of ICP traffic / lookups As pointed out by Chris, "round-robin" option is used with parent selection in the absence of ICP. But in your case you are using peers with ICP. If you are trying to prevent overlapping disk objects between the siblings then I reckon your syntax should just be something like this : cache_peer 10.10.10.1x sibling 3128 3130 proxy-only Michael.
