Last Modified: Sep 13, 2023
Known Affected Versions:
18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.4, 188.8.131.52, 13.1.5, 184.108.40.206, 14.1.4, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.1.5, 220.127.116.11, 15.1.6
17.0.0, 18.104.22.168, 22.214.171.124, 14.1.5
Opened: Oct 08, 2020 Severity: 3-Major
HTTPS monitor marks pool member/nodes as down and they remain down until bigd is restarted or the monitor instance is removed and created again.
HTTPS monitor shows pool members or nodes down when they are up.
BIG-IP is configured with restrictive ciphers that are only compatible with TLS 1.2 (ECDH+AESGCM) but all of the TLS protocol versions are allowed. When HTTPS monitor TLS 1.0 handshake fails, due to incompatible ciphers with the server being monitored. It does not try TLS 1.2 version and marks pool members or nodes as down.
Restart bigd or remove and add monitors.
In case of handshake failure, BIG-IP will try TLS 1.2 version.