Forum Discussion
Lukasz_01_15307
Nimbostratus
Nimbostratusunable to activate aws hourly license
Hi, I just deployed Big IP Version 12.1.0.1.1.1447 on AWS with the hourly license. Right now I'm stuck in the license screen and I'm wondering what I need to do to activate the license... according to the documentation this should be done auto-magically...
Also, recommended deployment guide is a little out of date... https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-setup-amazon-ec2-11-6-0/2.htmlunique_941942631
Hi, Try the following to see if that resolves your issue.
When deploying hourly billing BIG-IP Virtual Edition (VE) in AWS, ensure that eth0 (used for management access) can access the internet.
Associate a public IP to BIG-IP VE management ip (eth0)
-
In single NIC deployments, when configuring the instance details, in the Auto-assign Public IP list, select Enable
-
In multi-NIC deployments, associate an Elastic IP to the management NIC within a few minutes of deployment, or associate it later and restart the instance
These steps are required so that BIG-IP VE can be licensed with F5 when it boots when using version 12.1 and beyond. If desired, you can remove these public IP addresses after the instance is licensed.
-
Lukasz_01_15307according to our aws marketplace the license is active, however I'm still getting activate the license screen. Any ideas?
Hi, Try the following to see if that resolves your issue.
When deploying hourly billing BIG-IP Virtual Edition (VE) in AWS, ensure that eth0 (used for management access) can access the internet.
Associate a public IP to BIG-IP VE management ip (eth0)
-
In single NIC deployments, when configuring the instance details, in the Auto-assign Public IP list, select Enable
-
In multi-NIC deployments, associate an Elastic IP to the management NIC within a few minutes of deployment, or associate it later and restart the instance
These steps are required so that BIG-IP VE can be licensed with F5 when it boots when using version 12.1 and beyond. If desired, you can remove these public IP addresses after the instance is licensed.
- Lukasz_01_15307
Hi Kosan,
Thanks a lot for this, I got annoyed and bought lab BYOL... Your documentation should be updated to clearly state this as a limitation... our deployment requires management port to be in a private network that does not have internet access, also exposing management port on the internet is not the best security practice, especially on AWS where I can bet, their IP range is being scanned by not exactly friendly actors (call me paranoid).
But still it's good to know for the future! Thanks again
-