Nimbostratus
NimbostratusI have tried but it didn't change anything : requests were still handled by different tmm.
The user in this topic solved the problem by rebooting the bigip... :o( my bigip is in production so I don't want to reboot it for testing...
So I have found another solution (yes, my problem is solved !!) :
bigpipe virtual [virtual server name] cmp disable
bigpipe save
=> At this step, it didn't work. So, I removed my VS definition from bigip.conf and then :
bigpipe verify load (mandatory !!!)
bigpipe load
=> And then reinserted the definition into bigip.conf (check that "cmp disable" line is present in VS definition) and again :
bigpipe verify load
bigpipe load
=> Now all requests for that VS are handled by unique TMM thread and I have only one persistence entry per client !
I presume that changing the name of the VS into bigip.conf should be enough to make this VS considered as "new" by the bigip...and then really disable CMP but I haven't tested yet.
Just one last interesting thin I have seen here : https://support.f5.com/kb/en-us/solutions/public/7000/700/sol7751.html :
"The BIG-IP VIPRION introduced CMP Persistence in version 9.6. CMP Persistence adds support for session persistence mirroring when TMM is running in CMP mode"
=> Knowing that new v10 is unified for bigip and viprion....does v10 bigips support CMP Persistence ??? (which should be better than limiting VIP to only one tmm...)
Thanks !