Bug ID 421966: Unable to determine what topology record was selected from pool and pool member decision logging

Last Modified: Jun 04, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP DNS(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5

Fixed In:
14.1.0

Opened: May 28, 2013
Severity: 4-Minor

Symptoms

Gtm pool and pool member selection and traversal logs do not indicate what topology records were used when using topology load balancing.

Impact

It may be more difficult to diagnose problems with a topology configuration.

Conditions

Occurs when topology is used for load balancing either by selecting the topology load balancing method on a gtm pool or wideip, or by selecting Quality of Service (QoS) with a non-zero topology weight.

Workaround

None. This information cannot be easily gleaned from elsewhere.

Fix Information

If pool or pool member traversal logging is enabled on a wideip and a listener has an attached dns profile that has logging enabled and a logging profile, then topology selections will be logged when topology is used for load balancing, including when a topology QoS score is generated.

Behavior Change