Nimbostratus
NimbostratusI 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!
Employee