Bug ID 749689: HTTPS monitor sends different number of cipher suites in client hello after config load and bigd restart

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2

Fixed In:
15.0.0, 14.1.2.3, 13.1.1.5

Opened: Nov 14, 2018

Severity: 3-Major

Symptoms

HTTPS monitor sends different amount of cipher suites in client hello during SSL handshake and sometimes back end server fails to find a desired cipher suite from client hello. As a result, sometimes SSL handshake fails and monitor wrongly marks pool member down.

Impact

HTTPS monitor might incorrectly mark pool member down because of a failed SSL handshake.

Conditions

-- Have an SSL profile to be used by an HTTPS monitor. -- Load the same config more than once.

Workaround

Restart bigd using the following command: bigstart restart bigd

Fix Information

HTTPS monitor now sends a consistent number of cipher suites in the client hello message during the SSL handshake.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips