Forum Discussion
mdvucak_136600
Nimbostratus
NimbostratusDuplicate persistence entries in persistence table
Hi,
I wrote a short iRule to keep persistent connections between clients and certain pool members. The iRule uses "s_id" values as persistence keys from URIs (requests) and HTTP headers (responses)...
Why is the "Client Addr" field empty on TMM1?
no idea why but, you know, null client addr won't affect how persistence works because persistence key is not client address.
nitass_89166
Noctilucent
Noctilucentwhy do I see duplicate entries with different timeouts?
are you using cmp platform? i guess it is duplicated because of cmp (one record per tmm).
mdvucak_136600Nimbostratus
NimbostratusI'm using BIG-IP 3900 with 4 TMM instances. So I guess each TMM can have it's own persistence entry. I found out that this can be verified by running "*tmsh show ltm persistence persist-records all-properties*"
Here's a additional question. Below is the output of the above command for one duplicated entry:
~~~
universal - 10.100.190.70:80 - 10.100.110.2:80
----------------------------------------------------
TMM 3
Mode universal
Key fffa505e-03ff-4192-8b2e-21b354992939
Age (sec.) 733
Virtual Name LOAD_TEST
Virtual Addr 10.100.190.70:80
Node Addr 10.100.110.2:80
Pool Name LOAD_TEST
Client Addr 10.100.110.2
universal - 10.100.190.70:80 - 10.100.110.2:80
----------------------------------------------------
TMM 1
Mode universal
Key fffa505e-03ff-4192-8b2e-21b354992939
Age (sec.) 707
Virtual Name LOAD_TEST
Virtual Addr 10.100.190.70:80
Node Addr 10.100.110.2:80
Pool Name LOAD_TEST
Client Addr ::
~~~
Why is the "Client Addr" field empty on TMM1?
I read around that this can happen when there is only one TMM instance, but here there are clearly two separate ones.