Forum Discussion
Updating BIG-IP in Azure
I'm attempting to update our Azure F5 instance and normally with our VE version on premise I import the ISO file, install it to the inactive boot location, then reboot the F5 from that boot location to move to the new version. On our Azure F5 though, I only see one boot location. Is this normal? How do you go about updating an F5 with only one boot location?
- bsm1970Nimbostratus
Still looking for an answer on this.
Yes, it's normal base on the type of license. This is an example for AWS, but I guess Azure probably have a similar plan.
https://support.f5.com/csp/article/K49243459
KR,
Dario.
From what we are learning as we have the same issue, is that you would need a dual boot azure vm. We have to start from scratch it looks like and recreate in a new subnet. Hopefully this helps someone.
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