Forum Discussion
NimbostratusReasons why source persistence would not stay persistent
We are seeing something strange. We have a VIP that has source address persistence enabled. Yet when I look in the source persistence records I see the following...
source-address 10.85.105.31 10.204.254.15:443 10.131.4.175:4443 (slot/tmm: 1/5)
source-address 10.85.105.31 10.204.254.15:443 10.131.4.164:4443 (slot/tmm: 1/1)
source-address 10.85.105.31 10.204.254.15:443 10.131.4.175:4443 (slot/tmm: 1/2)
source-address 10.85.105.31 10.204.254.15:443 10.131.4.175:4443 (slot/tmm: 1/10)
Any ideas why this is happening? Why would any connection pop up in the persistence table to a different node?
6 Replies
DevBabu_174449Cirrus
what version you are using there was an issue in earlier versions.
https://support.f5.com/kb/en-us/solutions/public/12000/500/sol12538.html
Brian_Gibson_30Dev,
11.6 HF4.
- DevBabu_174449
I believe the tmms should share the persistence table information.
But from your output they are not sharing. Unless any other forum member has good reasons, I would go ahead and open a case with F5 support. Might be a bug?
- DevBabu_174449
Hey Brian.. any news on this one.
pete_71470Cirrostratus
You've probably already consider this, but was pool member 10.131.4.175 continuously available? If it was DOWN briefly, and then came back UP, persistence to 10.131.4.164 could have been established while DOWN. Similar issues could arise with connection limits.
- nitass
Employee
i understand ID438792 is already fixed in 11.6.0 hf4 but would you like to try the workaround in sol14918?
ID438792 - Node flapping may lead to inconsistent persistence entries across TMMs
sol14918: Node flapping may cause inconsistent persistence records
https://support.f5.com/kb/en-us/solutions/public/14000/900/sol14918.html
