For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

ijdod's avatar
ijdod
Icon for Nimbostratus rankNimbostratus
Oct 07, 2014

Unexpected persistence result

Platform: LTM2000S, 11.4.1HF3

While troubleshooting an unrelated problem, I noticed an unexpected persistence happening. Two servers (out of many) connect to a pool of 4 members. Default source_addr persistence is configured, which results in the traffic of these two servers being loadbalanced over a maximum of 2 members, as expected. However, when I look at the persistence records, it seems that not all traffic from the same source address it sent to the same member. Is this normal behaviour?

source-address  xxx.xxx.xxx.50   10.10.88.46%20:443  10.10.129.30%20:443  (tmm: 2)
source-address  xxx.xxx.xxx.50   10.10.88.46%20:443  10.10.129.30%20:443  (tmm: 3)
source-address  xxx.xxx.xxx.50   10.10.88.46%20:443  10.10.129.30%20:443  (tmm: 1)
source-address  xxx.xxx.xxx.50   10.10.88.46%20:443  10.10.129.29%20:443  (tmm: 0)
source-address  xxx.xxx.xxx.51   10.10.88.46%20:443  10.10.129.29%20:443  (tmm: 2)
source-address  xxx.xxx.xxx.51   10.10.88.46%20:443  10.10.129.29%20:443  (tmm: 0)
source-address  xxx.xxx.xxx.51   10.10.88.46%20:443  10.10.129.29%20:443  (tmm: 1)
source-address  xxx.xxx.xxx.51   10.10.88.46%20:443  10.10.129.30%20:443  (tmm: 3)

1 Reply

  • Hi ijdod,

     

    This could be due to CMP (Clustered Multiprocessing) enabled on the VIP. reference below, hope it helps.. https://support.f5.com/kb/en-us/solutions/public/14000/300/sol14358.html