Last Modified: May 14, 2019
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11
Opened: Jan 18, 2018
Related AskF5 Article: K53330514
BIG-IP fails to reattach floating addresses to local interfaces during failover, when two or more objects are configured with the same IP address in a given traffic group. Failover fails with the following error in /var/log/ltm: err logger: /usr/libexec/aws/aws-failover-tgactive.sh (traffic-group-1): Failed to reassign some or all address(es): <IP address> <the same IP address> on interface <eni address>.
Failover will fail; some or all IP addresses will not be transferred to the active BIG-IP system.
-- AZ AWS failover. -- Same IP address is used for two or more virtual addresses, self IPs, NAT, SNAT translation. Note: Having two virtual servers with the same IP address (but different ports) does not cause the problem. Also, there is no conflict when using the same IP address for different traffic groups.
The only workaround is to change the configuration to use unique IP addresses for conflicting objects.
This issue has been resolved.