Bug ID 614509: iRule use of 'all' keyword with 'class match' on large external datagroups may result in TMM restart

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2

Fixed In:
13.0.0, 12.1.2 HF1

Opened: Sep 05, 2016
Severity: 2-Critical


When the 'all' keyword is used with 'class match' on large external datagroups, the results will be incorrect and may result in TMM restarting.


Traffic disrupted while tmm restarts.


iRule utilizing 'all' keyword with 'class match' on large external datagroups. A more unusual case is external datagroups with the tmm.classallocatemetadata bigdb entry set to the non-default 'disable' value.


No reasonable workaround short of not using 'all' keyword with 'class match' in iRules.

Fix Information

'all' keyword with 'class match' now returns the correct results and TMM does not restart.

Behavior Change