Bug ID 760166: Run-time configuration might differ from bigip.conf after upgrading from pre-v13.1.0 to post-v13.1.0

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, 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,,,,,,, 14.1.5,,,, 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,, 15.1.7, 15.1.8,

Opened: Mar 01, 2019
Severity: 3-Major


If using HTTPS monitor, after upgrading from pre-v13.1.0 to post-v13.1.0, the run-time configuration differs from 'bigip.conf'. Run-time configuration uses the SSL profile attached to the monitor, while 'bigip.conf' still shows the original SSL-related attributes in the monitor configuration.


The run-time configuration will be different from 'bigip.conf'.


When using LTM https monitor and upgrading from pre-v13.1.0 to post-v13.1.0.


Save run-time configuration changes to 'bigip.conf' by running the following command after upgrade: save sys config

Fix Information


Behavior Change