Bug ID 1329653: Unexpected Virtual Server Behavior due to Removal of Unsupported Objects by BIG-IP Next

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) TMOS(all modules)

Fixed In:
20.1.0

Opened: Aug 11, 2023

Severity: 3-Major

Symptoms

The migration process guarantees the compatibility of application services with BIG-IP Next. If a property value lacks support in BIG-IP Next, it is eliminated and absent from the AS3 declaration. In cases where the object represented a default value, it is substituted with a default value supported by BIG-IP Next.

Impact

Default values of virtual server's objects may change, impacting virtual server's behavior.

Conditions

1. Migration of a UCS archive from BIG-IP to BIG-IP Next Central Manager. 2. Review the AS3 declaration during the Pre Deployment stage. Example for "cache-size" property of "web-acceleration" profile: - Original BIG-IP config cache-size = 500mb OR 0mb - AS3 schema supported range = 1-375mb - BIG-IP Next stack (clientSide/caching/cacheSize) supported range 1-375mb - AS3 output post-migration excludes "cacheSize" property if cache-size exceeds 375mb or falls below 1mb. - Deployment of AS3 declaration defaults to BIG-IP Next's values in both scenarios (cache-size 375 or 0mb).

Workaround

While unsupported values by BIG-IP Next are automatically replaced with defaults during migration, you can update the AS3 declaration to specify values other than the defaults. To modify the AS3 declaration, refer to the https://clouddocs.f5.com/bigip-next/latest/schemasupport/schema-reference.html for guidance on adding missing properties and specifying values within the supported range.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips