Hi,
You mention that you configured the devices from scratch. I am inferring this means that you did not use the our v1 CFTs or v2 CFTs.
My recommendation is that you go back and use the CFTs or other automation such as the terraform module. Manual setups are error prone as you need to create the security groups, rules, routes, IAM roles on your own. The automation tools address these for you and can save you alot of time figuring out is wrong.
Assuming that your security groups are correct, the route tables are correct, network acls are correct, you have S3 API and EC2 API access and DNS enabled in the VP and you have the proper routing set on the BIG-IPS it will come down to IAM. Based on some of the other problems you mention these items will also need your attention. For more information on the IAM role you can find it documented- Amazon Web Services: High Availability F5 BIG-IP Virtual Edition.
| Symptom |
Action |
| Both Devices Active |
Improper security group rules (refer to documentation), routing issue |
| Device cannot failover |
IAM issue, EC2 Access issue, S3 access issue, DNS issue |
| Peer Device offline (when it is actually not) |
Improper security group rules (refer to documentation), routing issue |
|
|
While testing this setup i saw that if active device goes offline for any reason, the peer device does nothing. Even, the CMI logs on stand-by unit says that the peer device unreachable. Is that normal? Should stand-by device take action to go active, after when it realized the peer is unreachable. - No this is not normal. There is something very wrong with your setup. The devices should take over “as normal” minus the fact that it is API driven event so it is much slower than one expects in a data center (AWS does not support GARP so remapping must be done at the API layer)
Despite there is a Sync-Failover device group configuration on both devices, each device says that they are “Active” itself. In setups with help of AWS Cloud Formation or Terraform guided, does this happen? No. The systems will build and cluster correctly. I suspect that the systems can support communication of port 443 but not UDP 1026.
Devices can sync objects i added including pools, iRules, nodes, virtual servers and etc. Also, the status indicator on top left corner says devices are “In Sync”. However, when i looked at “Device Manager > Devices”, each device sees other device is offline. Why? Your security group either does not have the correct ports open or you have not setup the correct routes for the peers to communicate on the systems. The cause can very based if this is single NIC, two NIC, three NIC deployment and which peer addresses you used to peer and the routes configured. See comment above.
When i use GUI for failover, it takes around 1 minute and 20 seconds. But if i trigger failover with “curl” command it only takes 5 seconds. Is that normal? Above you say that failover does not happen here you say it does. When you manually failover does the failover persist or does it revert to both systems thinking they are active? See comments above about SG, Routing. I suspect you have a scenario where you attempt to failover and the device bounces back to active.