cancel
Showing results for 
Search instead for 
Did you mean: 

iRule [after 8000] causing TMM reset

candc
Cirrus
Cirrus

Firstly, I note that I am running an old version -- we are in the process of replacing our devices and have put off the software upgrade as a result.

To that end, is it a known issue (particularly of 12.1.5.3) that...

when HTTP_REQUEST {    after 8000}

...causes all the TMM cores to reset (and my HA pair to failover)?

The intent was to add a tarpit to particular service, under certain conditions (the logic is more complex than above), but the second the `after` is called, the whole thing locks up for a bit.

I was under the impression that `after` was supposed to be ble to handle this in a TMM-friendly fashion, unlike a tight `while` loop.

Appreciating the old version, I was looking to see if there were any published articles describing this but, `after` isn't a particularly specific term to Google...

1 REPLY 1

Just check the big tracker with maybe "irule after" or the release notes for your version:

 

https://support.f5.com/csp/bug-tracker

https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-bigip-1...

 

Also see the ltm/kern/tmm logs about the error and if you can google it as this may help and the logs may also show if the CPU and memory/SWAP had issues because of the "after 8000" command. Here is a helpfull article that I did a long time ago:

 

https://community.f5.com/t5/crowdsrc/knowledge-sharing-investigating-troubleshooting-crash-and/ta-p/...