Forum Discussion
meena_60183
Nimbostratus
Nimbostratusdouble entries in the persistence table
I have 2 entries for each source IP address on the persistence table.
I have a source_addr based persistence using an irule on a forwarding virtual server and have no idea why 2 entries get created. The timeout is set to 3600 seconds. Here is the sample
config b persist pool cf_clinic show all
PERSISTENT CONNECTIONS
| Mode source addr Value 10.27.243.207
| virtual any:any node 10.44.254.23 age 2074sec
| Mode source addr Value 10.27.243.210
| virtual any:any node 10.44.254.23 age 16sec
| Mode source addr Value 10.27.243.210
| virtual any:any node 10.44.254.23 age 21sec
| Mode source addr Value 10.27.240.2
| virtual any:any node 10.44.254.24 age 290sec
| Mode source addr Value 10.27.240.2
| virtual any:any node 10.44.254.24 age 46sec
| Mode source addr Value 10.27.243.211
| virtual any:any node 10.44.254.24 age 412sec
| Mode source addr Value 10.27.240.3
| virtual any:any node 10.44.254.25 age 41sec
| Mode source addr Value 10.27.240.3
| virtual any:any node 10.44.254.25 age 46sec
| Mode source addr Value 10.27.243.217
| virtual any:any node 10.44.254.25 age 2377sec
It is sent to the same server in the pool but why are there 2 entries?
Meena
4 Replies
hoolioCirrostratus
Hi Meena,
Which LTM version and platform are you running on? I wonder if this has something to do with multiple TMM instances.
Aaron
meena_60183Yes. It is due to multiple TMM instances. I opened a case with F5 support thinking that one of the problems I am seeing is caused by this issue but turned out to be something else. F5 support told me that it is due to multiple TMM instances.
Thank you for the response Aaron.
Meena- hoolioThanks for the follow up. So is this behavior expected then? I thought I remembered seeing dupe persistence tables briefly before one was removed on a CMP enabled platform.
Aaron - meena_60183Yes. It is an expected behavior. Here is the answer from F5 support.
"Your hardware platform has a dual processor which has a Traffic Management Microkernel (tmm) per cpu. Each tmm makes a load balancing decision independent of the other. So you can expect to see duplicate entries, one for each tmm. "
Meena
