Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3
12.0.0, 11.6.0 HF4, 11.5.1 HF6, 11.4.1 HF9
Opened: Aug 12, 2014
If BIG-IP Edge Client for Windows connects to APM server using FQDN, it does not re-resolve the server hostname while reconnecting. In failover scenarios where one APM server goes down, Edge Client will continually try to connect to the non-existent IP of the APM server that went down and will not switch over to the next APM server.
The client does not re-resolve the server hostname while reconnecting and needs to be restarted to successfully connect again.
The problem occurs under these conditions. 1. Edge Client is connected to APM server using FQDN and 2. More than one APM servers are configured and a GTM, or another DNS server, is used for failing over.
To work around the problem, restart Edge Client and connect again.
Resolved this issue: when APM is configured with URL (https://....), BIG-IP Edge Client for Windows does not resolve the APM hostname while reconnecting.