Bug ID 832133: In-TMM monitors fail to match certain binary data in the response from the server

Last Modified: Sep 14, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,

Fixed In:
17.1.0,,, 15.1.7

Opened: Sep 27, 2019

Severity: 3-Major


Pool members are incorrectly marked DOWN by a monitor. The pool members send the expected response to the probe, but the BIG-IP system marks them DOWN.


Objects that are meant to be marked UP are marked DOWN. As a result, no load balancing occurs to affected resources.


This issue occurs when all of the following conditions are met: - In-TMM monitoring is enabled on the system (the 'bigd.tmm' db key is set to 'enable'; note this is set to 'disable' by default). - One or more TCP or HTTP monitors specify a receive string using HEX encoding, in order to match binary data in the server's response. - Depending on the HEX values specified (currently values in the range of 0x80-0xBF are believed to be affected), response matching fails.


Either one of the following workarounds can be used: - Disable in-TMM monitoring by setting 'bigd.tmm' to 'disable'. - Do not monitor the application through a binary response (if the application allows it).

Fix Information

The monitor finds the recv string and shows the pool or member as available.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips