For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

BIG-IP 11.4 Behavior Change: Global Data Now Partitioned by Traffic Group

  Prior to v11, active-standby and active-active in paired devices were your only options for failover configurations. Traffic groups were introduced in BIG-IP version 11 to allow administrator...
Published Jun 18, 2013
Version 1.0
BIG-IP
hardware
infrastructure
us
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
netsecurity_666's avatar
netsecurity_666
Icon for Nimbostratus rankNimbostratus
Jan 31, 2017

Hello,

 

I actually have this problem on LTM version 12.0

 

I need to cross-reference persist record across different traffic-group. I tried setting the DB variable tmm.sessiondb.match_ha_unit to false, but without success.

 

Do you know if this behaviour is to be "fixed" or has been "fixed" in current or upcoming releases?

 

Thanks, Andrea