Bug ID 778333: GUI/CLI max-in-progress discrepancy occurs after upgrade from v11.x to v13.x or later

Last Modified: Sep 14, 2023

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

Known Affected Versions:
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,,,,

Fixed In:

Opened: Apr 30, 2019

Severity: 4-Minor


If there is an access profile that was created using BIG-IP v11.x or earlier, with a default value of max-in-progress(0), when the configuration is upgraded to v13.x or later, the GUI shows max-in-progress as 128, but at the CLI and in the database, the actual value is 0.


There is a max-in-progress discrepancy between the GUI and the CLI.


In versions earlier than v13.x, the field 'Max In Progress Sessions Per Client IP' was set to 0 by default; from v13.x, the value is 128.


During upgrade validation, manually add 'Max In Progress Sessions Per Client IP' to user_spec if it was set to the default value. The upgrade then treats the field as a customized value, so the discrepancy disappears.

Fix Information

The discrepancy is fixed: the GUI shows the value as 0 and marks as customized value. If you upgrade an access profile created using v11.x or earlier with max-in-progress(0) default value, the upgrade to v13.x or later is successful.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips