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
AndyC_86542's avatar
AndyC_86542
Icon for Nimbostratus rankNimbostratus
Feb 11, 2009
Hi Jos,

I tried converting everything to UIE persistence based on [IP::client_addr] instead of source_addr persistence and got exactly the same results. I also tried that after doing "b virtual all cmp disable" - same result.

I've now resorted to limiting the BIGIP1600 to one tmm by doing 

bigpipe db Provision.tmmCount 1

from the console and rebooting [as suggested in https://support.f5.com/kb/en-us/solutions/public/7000/700/sol7751.html].

That seems to have stopped the problem, but presumably I've halved the capacity of my F5 by doing it which is not ideal.

Is there some obscure console command that forces a single persistence table shared between TMMs rather than one each?

Cheers

Andy