Forum Discussion
NimbostratusF5 EC2 Amazon VE edition 11.6.0.1.0.403-HF1 INOPERATIVE state
Hello,
Need help troubleshooting the VE in AWS. After deploying a new AMI F5 image everything is working correctly until I activate the license file.
"you have to call f5 support to get your license released"
Upon getting the new license file the f5 is working correctly.
I have to add an additional NIC to support additional Private IP addresses, when i reboot the device it comes up with these errors: and now this f5 is useless. Please help.
The connection to mcpd has been lost, try again. root@(ip-172-31-200-100)(cfg-sync )(INOPERATIVE)(/Common)(tmos) Mar 8 10:45:56 ip-172-31-200-100 emerg logger: Re-starting mcpd load sys config Loading system configuration... /defaults/asm_base.conf /defaults/config_base.conf /defaults/ipfix_ie_base.conf /defaults/ipfix_ie_f5base.conf /defaults/low_profile_base.conf /defaults/low_security_base.conf /defaults/policy_base.conf /defaults/wam_base.conf /defaults/analytics_base.conf /defaults/apm_saml_base.conf /defaults/app_template_base.conf /defaults/classification_base.conf /defaults/daemon.conf /defaults/profile_base.conf /defaults/sandbox_base.conf /defaults/security_base.conf /defaults/urldb_base.conf /usr/share/monitors/base_monitors.conf Loading configuration... /config/bigip_base.conf /config/bigip_user.conf /config/bigip.conf 01071029:5: Master Key not present. Unexpected Error: Loading configuration process failed. root@(ip-172-31-200-100)(cfg-sync )(INOPERATIVE)(/Common)(tmos) Mar 8 10:46:11 ip-172-31-200-100 emerg logger: Re-starting mcpd Mar 8 10:46:25 ip-172-31-200-100 emerg logger: Re-starting mcpd Mar 8 10:46:40 ip-172-31-200-100 emerg logger: Re-starting mcpd Mar 8 10:46:54 ip-172-31-200-100 emerg logger: Re-starting mcpd
5 Replies
Daniel_EppersonEmployee
The license is not working, preventing the instance from fully starting up. It sounds almost as though you moved a BYOL license into an hourly billed AWS instance (which is a no-go).
What is the AMI id that are you attempting to use?
How and where did you come across "you have to call f5 support to get your license released" and what did you do for that?
If you delete the extra ENI that you've added to the instance, does that resolve the problem?
Roberto_Glez_deI have the same problem with a hourly billed AWS instance. The only difference is that I do not see '"you have to call f5 support to get your license released"'. However I do see: 011d0002: Can not access the database because mcpd is not running. Apr 7 10:11:02 ip-172-31-65-145 emerg logger: Re-starting mcpd Apr 7 10:11:15 ip-172-31-65-145 emerg logger: Re-starting mcpd Apr 7 10:11:27 ip-172-31-65-145 emerg logger: Re-starting mcpd Apr 7 10:11:40 ip-172-31-65-145 emerg logger: Re-starting mcpd Apr 7 10:11:53 ip-172-31-65-145 emerg logger: Re-starting mcpd Apr 7 10:12:05 ip-172-31-65-145 emerg logger: Re-starting mcpd Apr 7 10:12:18 ip-172-31-65-145 emerg logger: Re-starting mcpd When I apply tmsh load /sys config verify, I obtain the following: [root@ip-172-31-65-145:INOPERATIVE:] config tmsh load /sys config verify Validating system configuration... /defaults/asm_base.conf /defaults/config_base.conf /defaults/low_profile_base.conf /defaults/low_security_base.conf /defaults/policy_base.conf /defaults/wam_base.conf /defaults/analytics_base.conf /defaults/apm_saml_base.conf /defaults/app_template_base.conf /defaults/classification_base.conf /defaults/daemon.conf /defaults/fullarmor_gpo_base.conf /defaults/profile_base.conf /defaults/sandbox_base.conf /defaults/security_base.conf /defaults/urldb_base.conf /usr/share/monitors/base_monitors.conf Validating configuration... /config/bigip_base.conf /config/bigip_user.conf /config/bigip.conf 01071029:5: Master Key not present. Unexpected Error: Validating configuration process failed. Any clues? Thanks!
- Daniel_EppersonThe error below seems to be the root of both failures. 01071029:5: Master Key not present. Unexpected Error: Loading configuration process failed. The OP didn't come back with any data to investigate further. We need to collect some data to figure out what happened. How were you using the instance? Did you make any recent changes? Is this a new deployment? What AMI ID are you using? What exact steps did you take, starting at AWS Marketplace and ending at "broken"?
- Roberto_Glez_deHello Danny, thanks for coming back to me. I am using two F5 BIG-IP 25 Mbps Best 11.5.2.0.0.141 m3.xlarge instances. Both instances were last 19th March set with basic configuration of 1 VIP and 3 pool members and HA Config Sync. They worked nice then and I also made UCS archive files, when I rebooted the instances back then, both finally after some rebooting attemps were finally coming up. However now that I use them again, I see both instances stuck at INOPERATIVE state always showing emerg logger: Re-starting mcpd. So I cannot even use tmsh load /sys config or tmsh load /sys ucs . I am considering on giving up F5 EC2 as they are having a lot of downsides for labbing real BIG-IP instances. I need this way as I want to do the 201 exam in 2 weeks, however as I am not in US nor work for a F5 partner, there is no way to obtain real F5 11.6 or higher than 11.3 images without the University F5 2-hour limited labs. Let me know if there is any short way to overcome the EC2 instances issues as I starting to run out of ideas. Thanks
- Roberto_Glez_deHello Danny, I am still wondering why my mcpd process is looping and not initializing properly. Could it be possible that the process mcpd is being blocked to my TMM interface via the port 6699?, as this article states for the configsync procedures: https://support.f5.com/kb/en-us/solutions/public/13000/900/sol13946.html Could this be related to that I have not told to my peer to save the configuration on automatic config sync? https://support.f5.com/kb/en-us/solutions/public/14000/600/sol14624.html Thanks in advance
