Forum Discussion
CirrusQuestion about source persistence across traffic group
CirrusHello Injeyan_Kostas
Yes there's GSLB.
Cookie persistence did work, but using source address persistence is not working even with match across option, not sure if there's a way to share persistence between TG except for cookie persistence.
Regards!
Cookie persistense is much more clear option for me in such case.
As for source address persistence and match across option, did you select match across virual servers? Also are you sure clients reach both traffic groups with their original source IP and there is no SNAT somewhere between?
- AmineZAKARIA
Hello Injeyan_Kostas
Yes i did use the match across virtual server and of course i am mirroring the persistence info, both VSs assigned with the same persistence profile.
Also are you sure clients reach both DC BIG-IPs with their original source IP and there is no SNAT somewhere between?Yes using the same source ip address and persistence records create a new persistence record in TG2.
Regards!As far as I am aware persistence records are not tide to Traffic Group, but again cookie cookie persistence seems more reliable in this case
- AmineZAKARIA
Injeyan_Kostas
That's how the persist table looks like after failover to DC2.Btw i have enabled cache array instead of record based, and the source persistence kept pointing to the same backend server as i wanted.
Regards!
