Forum Discussion
Why it does not switching secondary ip address on azure when failover???
Device 1 : #1 (Active)
Device 2 : #2 (Standby)
I performed a failover.
Active device running Failover script, but it fail.
There seems to be an abnormal operation on the secondary IP.
to assign both equipment 1 and 2 to equipment NIC 2.
I need reset the failover extention or get metadate(azure) information.
How can I?
Hi JRahm
I couldn't find a solution from the data you gave me.
but I will try the following measures.
Clear the statusdb file:
1. In the Azure portal, go into the storage account ending with 'data000'
2. Go to containers, "failover" container
3. Delete statusdb file
- Jeff_Giroux_F5Ret. Employee
If using the cloud failover extension (assumed here) then take a look at the tshooting section in F5 CloudDocs. The Cloud Failover tshooting section talks about resetting state file and reviewing logs...
https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/userguide/troubleshooting.html
Also helps to know how you initially deployed the BIG-IP devices...using templates? Manually through marketplace then manually doing HA setup? Here's a tshooting section from the ARM templates github repo...
- Hooni_LCirrus
- JRahmAdmin
Hi Hooni_L, Jeff_Giroux_F5 has an article with lightboards on Azure HA that might be helpful: https://community.f5.com/t5/technical-articles/lightboard-lessons-big-ip-deployments-in-azure-cloud/ta-p/284445. If that doesn't help directly, drop Jeff a comment in the article and post back here on status. I'm out on vacation after today until Tuesday.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com