Bug ID 935249: GTM virtual servers have the wrong status

Last Modified: Feb 07, 2024

Affected Product(s):
BIG-IP DNS, GTM, Link Controller(all modules)

Known Affected Versions:
15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2

Fixed In:
17.0.0,, 15.1.5

Opened: Aug 11, 2020

Severity: 3-Major


GTM virtual servers have the wrong status (up when they should be down, or down when they should be up).


The system incorrectly matches the status code in a response line which is not the Status-Line. As a result, the availability status reported for a virtual server may be incorrect. This may cause the GTM system to send traffic to unsuitable resources causing application disruptions.


-- The GTM virtual servers are monitored with an HTTP or HTTPS monitor that performs HTTP status matching. -- The status code (for example, 200) being searched for in the response appears elsewhere than in the first line (for example, in a following header).


You can work around this issue by not performing HTTP status matching in your HTTP/HTTPS GTM monitors.

Fix Information

The HTTP status code is now correctly searched only in the first line of the response.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips