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
StephanManthey's avatar
StephanManthey
Icon for Nacreous rankNacreous
Sep 23, 2013
Being aware of this behaviour is relevant in with SNAT deployments.

 

We need to apply SNATs and floating self IPs per traffic group to make sure the servers responses will reach the right device.

 

If no virtual address is available for SNAT in a traffic group, the local self IP (traffic-group-local-only) will be picked for SNAT. But the servers responses to this address will be dropped now.

 

In the past it was possible to make use of the 'global' tables by applying mirroring to handle asymmetric traffic as a workaround. This won´t work anymore, I guess.