Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[vSRX] Why does vSRX instance (automated using Cloud-Init) load with factory default configuration instead?

0

0

Article ID: KB32982 KB Last Updated: 21 Sep 2019Version: 2.0
Summary:

This article describes steps which can be performed to troubleshoot the vSRX loading with the factory default configuration instead of configuration used in Cloud-Init in OpenStack and AWS environments.

Symptoms:

A few different issues may occur when initialization of the vSRX instances is automated using Cloud-Init. Three cases where the the vSRX loads with the factory default are listed below.

Note: The cloud-init log file is located in WRL at: /var/log/cloud-init.log

Case 1: Error reported in boot up log: ERROR: Failed to commit user data configuration!​

  • User-data file is supplied in text format; but vSRX boots up with factory default configuration.​
  • Boot up logs contains one of these strings:

    # ERROR: Failed to commit user data configuration!​
    # Using the factory default configuration

Case 2: Error reported in boot up log: #junos-config is missing in user-data is reported

  • Boot up logs contain the string:

    #junos-config is missing in user-data​

Case 3: No errors reported in boot up log, but vSRX loads with factory default configuration.

  • Cloud-init logs contain the string:
    ​#junos-config
Solution:

Case 1: Error reported in boot up log: ERROR: Failed to commit user data configuration!​

  • Configuration is incorrect. This indicates that the user provided configuration failed the mgd commit.​
  • Copy the /config/juniper_user_data.conf file to a running vSRX ​
  • In the configuration mode, run the command: load override <juniper_user_data.conf>
  • Confirm the error has been corrected.

Case 2: Error reported in boot up log: #junos-config is missing in user-data is reported

  • Make sure the user-data file contains the string:
    #junos-config

Case 3: No errors reported in boot up log, but vSRX loads with factory default configuration.

  • Check if the network is unreachable.
  • Check if DHCP leases are available.
  • Make sure the metadata service is running on the specified IP for the platform


For more details, refer to the following technical documentation links:

Using Cloud-Init to Automate the Initialization of vSRX Instances in AWS
Using Cloud-Init in an OpenStack Environment to Automate the Initialization of vSRX Instances

 
Modification History:

2019-09-20: Added links to technical documentation for more information.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search