Symptoms

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.

Impact

Improper sorting of topology records will cause errors during load balancing on wide IPs that use topology load balancing.

Conditions

Using negated or wildcard topology records with longest match sorting enabled. Or only topology records with longest match sorting enabled.

Workaround

Disable longest match sorting and manually sort topology records.

Fix Information

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.

Behavior Change