For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Daniel_Epperson's avatar
Daniel_Epperson
Icon for Employee rankEmployee
Jun 25, 2015
Hi Steve, I have a few questions for you. 1. What process are you using to restart the instances? 2. Are you trying to make any changes to the instance since it was deployed? 3. Can you provide me the exact AMI id and Availability Zone you are using? 4. From a recovered unit, can you collect a "quick view" (qkview from cli)? In your case it appears that something at the "hardware" layer is changing. We want the hardware to look basically exactly the way it did when the instance first started up. If you need to change to a bigger instance, deploy a new instance with the new instance type and migrate the configuration. In my lab, I wasn't able to replicate your issue using F5 Networks Hourly Hotfix-BIGIP-11.6.0.4.0.420-HF4 - Good 25Mbps (ami-297dc634) using a variety of methods. I tried rebooting the unit via SSH, sending reboot command from AWS Console Instance State menu and manually stopping then starting the instance. In all cases my instance came up licensed okay. Maybe your issue is AZ or process specific. Using this this CloudFormation Template allowed me to very quickly deploy a new BIG-IP and VPC, you may find it useful as well. https://devcentral.f5.com/s/articles/aws-cft-for-hourly-big-ip-116-in-ec2 If you are able to, please upload a qkview file from one of your recovered instances so that I can look at the log files in detail. If you can access ihealth.f5.com then please upload the qkview directly there. If not, can you provide me your email address so that I can arrange a place for you to upload the files? Thanks! --Danny