Seek for your help here.
We are evaluating F5 AWS Instances since last couple of months. Everything seems good. Including Config-sync / Manual-device-failover / Automatic-device failover.
However traffic failover doesn't take place. We have to manually change the mapping to each IP addresses to instance ID when we experience device connectivity issue. So ultimately it is downtime until you manually finish the IP address to instance ID mapping.
We have referred AWS / F5 docs, couldn't find anything helpful.
I know it seems vague problem statement, but anyone have experience this issue or similar, please help. I would appreciate it.
Are you manually changing the mapping of Elastic IPs to the secondary private IPs of the instance? Are your virtual addresses configured in the proper traffic group(s)?
Check the following links for articles and deployment guide on F5 site to see if they might help you:
F5 in AWS Part 1 - AWS Networking Basics
F5 in AWS Part 2 - Running BIG-IP in an EC2 Virtual Private Cloud
F5 in AWS Part 3 - Advanced Topologies and More on Highly Available Services
F5 High Availability Across Amazon Web Services Availability Zones
We recently published an HA guide for AWS that you might find helpful: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-high-availability-amazon-ec2-12-1-0.html