Hi Deb,
The original problem was some odd delays/hanging at the squid proxy. I don't think it has any bearing on the persistence problem though.
There's nothing in the logs that I can see, although I am not sure what you meant by the LTM log (I'm looking at local traffic logs in the F5 web interface). There is only gateway_icmp monitoring on the pools at the moment.
I did notice something else odd. This is the persistence table data under pools->squid-proxy-pool->statistics.
Persistence value Persistence Mode Virtual Server Pool Pool Member Age
172.22.20.220 Source Address Affinity catchall-virtual squid-proxy-pool 172.22.21.249:80 4817 seconds
172.22.20.220 Source Address Affinity catchall-virtual squid-proxy-pool 172.22.21.249:80 1217 seconds
172.22.20.228 Source Address Affinity catchall-virtual squid-proxy-pool 172.22.21.250:80 731 seconds
172.22.20.228 Source Address Affinity catchall-virtual squid-proxy-pool 172.22.21.249:80 731 seconds
As you can see, there are two entries for each source IP address. Is it possible that multiple requests arrive simultaneously and are round robin load balanced over the pool, with each request causing an entry in the persistence tables. If so, how do I avoid that? If not, does anyone have an idea what's going on.
Cheers
Andy