Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1
11.5.0, 11.4.1 HF6
Opened: Oct 02, 2013
Related AskF5 Article: K14794
1. GTM topology longest match sorting incorrectly orders wildcard and negated records above other types of topology records. This is incorrect and can result in improper load balancing behavior on wide IPs that use topology load balancing. 2. GTM topology records of the same types are incorrectly sorted in ascending order.
Improper sorting of topology records will cause errors during load balancing on wide IPs that use topology load balancing.
Using negated or wildcard topology records with longest match sorting enabled. Or only topology records with longest match sorting enabled.
Disable longest match sorting and manually sort topology records.
1. GTM topology longest match sorting now correctly orders negated records below non-negated topology records and places wildcard records at the end of the list. 2. GTM topology records of the same types are correctly sorted in descending order.