Forum Discussion

John_Heyer_1508's avatar
Icon for Cirrostratus rankCirrostratus
Jul 20, 2018

Rapid failover/failback problem in AWS

We experienced a network-based failover on our F5 pair in AWS. Both are running The logs from secondary show it detected a connectivity problem to primary and took over:

Jul 19 16:26:49 f5bigip-2 notice sod[6127]: 010c007e:5: Not receiving status updates from peer device /Common/ ( (Disconnected).

When this occurred, the primary released its traffic group and AWS moved the floating IP to secondary.

Almost immediately, the primary was detected to be healthy again:

Jul 19 16:26:49 f5bigip-2 notice sod[6127]: 010c007f:5: Receiving status updates from peer device /Common/ ( (Online)

This triggered a failback to primary. However, the floating IP stayed on the secondary.

I theorize the sudden failover/failback caused a problem for the "ec2:assignprivateipaddresses" API call to AWS EC2 that is responsible for shifting the floating IP between AWS instances. I have opened case with F5 & AWS for troubleshooting, but just curious if anyone has run in to this before.

1 Reply