Bug ID 818789: Setting ssl profile to none in https monitor, not setting Ciphers to DEFAULT as in serverssl Profile

Last Modified: Apr 11, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 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, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,

Fixed In:
17.0.0,,, 14.1.5

Opened: Aug 29, 2019

Severity: 3-Major


With in-tmm monitoring enabled (or sys db bigd tmm set to enable) and with https monitor's ssl-profile set to none, the expected behavior is to send ciphers in ClientHello based on default serverssl profile as mentioned in GUI help for https monitor.


Ciphers are not exchanged as expected in the ClientHello Packets


Configure HTTPS Monitor with ssl-profile "None".


Configure HTTPS Monitor without ssl-profile option, default serverssl profile will be used

Fix Information

GUI Help updated, and tmm now handles the None field from the GUI or tmsh.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips