Amos Jeffries wrote:
?huh? your example omits cache_peer order.
Which is half the critical config for failover sequencing.
{important stuff in previous email}
Amos
Thanks Amos,
yeah, that was a too-fast hit-send email mistake. with typos too. ARRGH
acl s1 dstdomain "/s1"
acl s2 dstdomain "/s2"
cache_peer 172.16.10.5 parent 80 0 no-query originserver name=server_s1 login=PASS
cache_peer_access server_s1 allow s1
cache_peer 172.16.10.7 parent 80 0 no-query originserver name=bu_s1 login=PASS
cache_peer_access bu_s1 allow s1
cache_peer 172.16.10.7 parent 80 0 no-query originserver name=server_s2 login=PASS
cache_peer_access server_s2 allow s2
cache_peer 172.16.10.5 parent 80 0 no-query originserver name=bu_s2 login=PASS
cache_peer_access bu_s2 allow s2
so if 5 is off all traffic will go to 7 and vice-versa.
if both are on it should be split up. i'll test it.
Waitman
