BYOL deployment fails.

[ciscoCruz]

Describe the bug

According to documentation the only thing I need to do is to change the init files and the Image to BYOL and that will do the trick to deploy 2 VEs in HA, however every time I try to create this deployment I get the following error:

Expected behavior

The end goal is to have a peer oof BIG-IPs across AZ

Current behavior

Template fails to create the BIG-IP instances

Possible solution

Not sure why your recommendations on the documentations aren't working:

https://github.com/F5Networks/f5-aws-cloudformation-v2/blob/main/examples/failover/README.md#changing-the-big-ip-deployment

Steps to reproduce

1. Click on Failover Existing Network button
2. Fill the template with the parameter of your environment
3. Change the init files to the BYOL ones
4. Change the image to the BYOL one I tried different software versions none of the work.
5. Your config should look as below

7. Submit
8. Wait for the template to fail

Screenshots

Context

My goal is to provide this solution to customer since the end goal is to have this 2 HA boxes deployed and license them through BIG-IQ

[mikeshimkus]

@ciscoCruz Can you provide the full list of input parameters? It appears that the external interface failed to create due to the self IP being in the subnet's reserved address range. Make sure the addresses provided for bigIpExternalSelfIp01 and bigIpExternalSelfIp02 are not in that range.

[ciscoCruz]

Here is the image,

[skilwork]

Hello, Facing this issue too. any solution on this. Or if someone who successfully implemented this template can provide their template values ?

[mikeshimkus]

@skilwork Are you also using the existing stack template? If so, do the self/VIP IPs in the parameters match the respective subnet address space?

[skilwork]

@mikeshimkus . thanks for the response. I am able to launch the instances. I am using existing template, I ensure that the IP values matched the subnets. However, for some reason EIP, example VIP and secondary IP are not assigned. So I cannot test the EIP failover.