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.

Forum Discussion

AndyC_86542's avatar
AndyC_86542
Icon for Nimbostratus rankNimbostratus
Jan 26, 2009

Strange persist behaviour

I have this little section of code in an iRule that decides which of various pools to send an HTTP request to. I wanted to make sure that requests from a single client go through the same proxy server...
application delivery
dev
devops
iRules
Jos_52767's avatar
Jos_52767
Historic F5 Account
Feb 17, 2009
Hi all,

 

 

I want to clarify two important points in this thread:

 

- An iRule will always take precedence over persistence set in a profile as it is executed after the profile has been parsed. It is for this reason that if an iRule makes an LB decision persistence should also be handled by the iRule.

 

- The use of an iRule and / or Persistence is not compatible with CMP, and as such, using any of these should automatically disable CMP for the virtual. For more details review solution SOL7751: https://support.f5.com/kb/en-us/solutions/public/7000/700/sol7751.html

 

 

SOL7751 also indicates that CMP can be disabled via the command line:

 

bigpipe virtual cmp

 

 

This is the workaround for the issue that sorbukar mentions - it ensures that CMP is disabled for the virtual, which will prevent multiple persistence entries between the TMMs. The "b save" command will ensure that the change in CMP status survives a reboot.