Last Modified: Nov 07, 2022
See more info
BIG-IP DNS, GTM, Link Controller
Known Affected Versions:
15.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 15.1.1, 15.1.2, 184.108.40.206, 15.1.3, 220.127.116.11, 15.1.4, 18.104.22.168, 16.0.0, 22.214.171.124, 16.0.1, 126.96.36.199, 188.8.131.52, 16.1.0, 16.1.1, 16.1.2
17.0.0, 184.108.40.206, 15.1.5
Opened: Aug 11, 2020
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.
The HTTP status code is now correctly searched only in the first line of the response.