Bug ID 636853: Under some conditions, a change in the order of GTM topology records does not take effect.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP DNS, GTM(all modules)

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1, 12.1.3.2, 11.6.3

Opened: Jan 05, 2017

Severity: 3-Major

Related Article: K19401488

Symptoms

A change in the order of topology records does not take effect in GTM until the configuration is reloaded or a topology record is added or deleted.

Impact

In certain configurations, the topology load balancing decision may not be made correctly.

Conditions

This occurs only when Longest Match is disabled and the order of topology records is changed without adding or deleting records.

Workaround

Reload the GTM configuration or add/delete a topology record.

Fix Information

Changes in the order of topology records now take effect immediately.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips