Strange persist behaviour

Hi,

Thanks for the tips on logging. Having tried Aaron's logging suggestion, a pattern seems to be emerging. I've not included the whole logs as I've been through a lot to notice the pattern. Basically, I get consistent persistence within a tmm. If I trim the log to just the LB_SELECTED logging I get something like:

This is the logging line:

      
      when LB_SELECTED {      
          log local0. "[IP::client_addr]:[TCP::client_port] :[LB::server]"       
      }      
      

and this is the output:

      
         tmm   tmm[ 1835 ]   Rule test LB_SELECTED: 172.22.20.221:4918 squid-pool 172.22.21.249 80      
         tmm   tmm[ 1835 ]   Rule test LB_SELECTED: 172.22.20.221:4918 squid-pool 172.22.21.249 80      
         tmm1   tmm1[ 1861 ]   Rule test LB_SELECTED: 172.22.20.221:4777 squid-pool 172.22.21.250 80      
      

tmm will give consistent load balancing to one address and tmm1 will give consistent load balancing to another address (on some test runs, randomly, they are the same address).

I don't know what the host/service values in the log mean, but I'm guessing this could be something to do with CMP (clustered multi-processing).

I'm running on a BIG-IP 1600 9.4.5 Build 1049.10 Final.

Can anyone enlighten me?

Cheers

Andy