Bug ID 423483: Edge Client incorrectly resolves APM hostname while reconnecting

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0, 11.4.1 HF9, 11.4.0 HF3, 11.3.0 HF8

Opened: Jun 18, 2013
Severity: 3-Major
Related AskF5 Article:
K15237

Symptoms

Sometimes Edge Client incorrectly resolves APM hostname while reconnecting, this triggers full reconnection even if it is not really needed.

Impact

Users may need to go through the full reconnection process including client checks and authentication when it's not really needed.

Conditions

GTM is used for load balancing APMs. HTTPS request to the resolved hostname should be redirected with HTTP 302 response.

Workaround

No.

Fix Information

Previously, when the primary APM hostname was successfully resolved by GTM but the first request to download configuration failed and the next one succeeded Edge Client made incorrect decision about the primary APM IP address. Eventually this led to full reconnection when Network Access connection was temporarily disrupted. Now Edge Client makes correct decision about the primary APM IP address in this scenario and performs quick reconnection instead.

Behavior Change