Forum Discussion
CirrusQuestion about source persistence across traffic group
Hello,
Hope you are doing great!
I would like to know if it is supported to mirror persistence between 2 DC's across 2 Traffic Groups, each one is Active on a DC.
DC 1 Active on TG1
DC 2 Active on TG2
Client established connection on DC1, if it reconnected in DC2 traffic should be rerouted to DC1 backend. (There's no application level session synchronization)
Any suggestions would be appreciated!
Thank you.
Regards!
9 Replies
Hello AmineZAKARIA
My question is how a user could end up to a different DC? Is there a GSLB in front?
You could try cookie persistence.
Not sure if the built in cookie persistence mechanism will work in this case. But with an irule you could inject a custom cookie an use it later to make load balance decisions. Of course your client should always send the cookie.
- AmineZAKARIA
Hello 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?
