F5 VM deletes itself after deployment

[rjohnson318]

After a successful deployment of the SACAv2 Azure Government Tier 1, the first f5 VM deletes itself automatically. I have tried deploying this 4x with the same result each time. Also, I cannot access the F5 frontend at all, it just times out. The management network is not the value I set it to be aswell. Any help would be great, thank you.

[Mikej81]

Just tested successful several times. What Region? Are you sure you are deploying in MAG? Are there limits on your subscription?

Management network is not configurable. Unless referring to VDMS, but there are no resources in the VDMS subnet.

There is no F5 Front-End, Management is tunneled through the PIP and only accessible via 3389 and 22 to the Bastion Hosts.

[rjohnson318]

Thanks for the assistance.

Region- usdodeast Limits- No, I deployed it before (about 4mo ago) with no issues VDMS address field, I put an IP of 10.x.x.x/24 in the portal it shows 192.x.x.x for the mgmt ip, is that by design? The F5 frontend, I was referring to public DNS address used to access and manage the F5. I cannot access that anymore it just times out, I never see the login page. Why does the VM delete itself or go into an unknown state?

[Mikej81]

VDMS is blank, it should create with the specified subnet IP space. The BIG-IP management is OOB, and not part of the VDMS. It has to be left alone for this quickstart template because of the AS3. If you want to change those, you will need to fork the repo and change as needed.

As far as the VM deletion, there is nothing in the ARM that would cause this, you may want to open a ticket with Azure as they just updated a bunch of things in the portal this week. I have deployed several times in US Gov Virginia this morning without issues, my subscription does not have DOD, but we have people on site running the templates this week in DoD and they havent mentioned any issues.

You can also reach out to your F5 account team and they can loop me in and we can tackle from that direction, we can even involve the MS architects.

[rjohnson318]

I have F5 coming onsite Monday to assist in the setup of our F5s. I was hoping to have this deployed ahead of them getting onsite so we can focus on other things besides deployment, I will keep troubleshooting from my end. If F5 or myself reach a solution I will update the issue here.

Thanks for the help :)

[Mikej81]

Just tested Single Tier again in US Gov Virginia and worked 100%. It could be something in the DOD regions that I don't have access to to test. If you receive any errors from Azure, then post those in.

You can also verify via stderr and stdout in /shared/vadc/azure/custom-scripts/download/0/ and share those to see what may be happening.

VM deletion isn't something we would see though. DOD region may require a downgraded Schema as well. Wont know without further testing, although I know the Microsoft Architects have successfully deployed in DOD.

[rjohnson318]

I know for a fact that usgovvirginia and usdodeast work slightly different, we have built environments in both some services do not make it up to usdodeast. So it is possible that the DoD region needs something specific but, it worked before.. I am deploying it now using default setting to see if the vm deletion still takes place and to gather some logs. I will share those when I get them.

[Mikej81]

Roger. There have been a ton of updates in the past 4 months. We changed a lot of the Microsoft SKU's and some of the underlying scripts. If any you or any of the f5 consultants figure something out, please post it back here so we can get it fixed.

[F5Rob]

I am onsite with the customer and we deployed the BIG-IPs via the marketplace manually and configured the environment manually.

[Mikej81]

I have not been able to recreate this issue. Going to close. If the issue happens again and can be recreated please re-open.