Closed guqingyuan closed 4 years ago
Try adding the route stanza with a fake route, even though you don't have a route, and see if you get the same error. This might be related to an issue where the Cloud Failover Extension gets confused with missing stanzas.
This is a known issue, internal issue AUTOSDK-158, and will be fixed in the next release.
Closing this issue
As of release CFE 1.2 we moved this CFE repo under F5Networks. Your issue was recreated there. To follow-up on this issue visit:
https://github.com/F5Networks/f5-cloud-failover-extension/issues/12
Here are two problems in AWS China. In my case, when the failover occurs, I just want to switch Elastic IP to another device. So my declaration is
First problem: there is some error log
When I try to click force to standby in bigip GUI, I can see error log in /var/log/restnoded/restnoded.log on new active device.
And in my S3 bucket, here is a file named f5cloudfailoverstate.json.
But in AWS console, I can see Elastic IP is already bound to another Private IP. Does this error have an effect?
Second problem: It takes too much time to switch elastic ip
I click force to standby in bigip GUI, and after about two minutes, I can see the ealstic ip bound to another Private IP. I think it took too long. Is this normal?