Loading...
Loading...
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.
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.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.