Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(CM) TMOS
Known Affected Versions:
20.1.0, 20.1.1
Fixed In:
20.2.0
Opened: Jan 08, 2024 Severity: 3-Major
When migrating to BIG-IP Next Central Manager, the migration process might change the order of iRules, which can invalidate the application service.
The iRule list is out of order from the pre-migration configuration.
1. Upload a UCS file to BIG-IP Next Central Manager's migration tool. The UCS includes iRules configured in a set order. For example: { /Common/b_irule_order_1st /Common/c_irule_order_2nd /Common/a_irule_order_3rd } 2. Complete the application migration process. 3. Check the iRule order in the application service's declaration.
Verify the order of the iRules in the declaration post-migration: Before deploying the application service, save the application service as a draft, and correct the order of the iRules in the declaration before you deploy to an instance.
None