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

[SRX] Commit fails in SRX chassis cluster with dual REs on each node

0

0

Article ID: KB27969 KB Last Updated: 05 Mar 2017Version: 3.0
Summary:

Commit command fails on SRX chassis cluster with dual Router Engines (RE) on each node. This article explains why commit fails, what is the cause and how the issue can be resolved.


Symptoms:

Commit command fails on SRX chassis cluster with dual Router Engines (RE) on each node.

Cause:

On an SRX cluster, setting up the command set system commit synchronize may cause the commit process to fail. This command is used to synchronize the configuration between two routing engines on the same node in a cluster, but in an  SRX cluster, the second RE is used for second control link. This second routing engine boots up in a single user mode, i.e. it does not boot completely.  As a result, the commit script cannot sync the configuration to the second routing engine, thus the entire commit  script fails.

The command set system commit synchronize is for Juniper Networks switches and routers which have dual routing engines as active/backup, and in which both routing engines boot up completely to operate. SRX switches do not have routing engine redundancy within the same node,  i.e.,  only one routing engine (RE0) is always active in an node.

After committing the configuration, the command commit | display detail will display the following messages. Note that in these messages, the commit script is not recognizing any changes.

root@01# commit | display detail
node0:
2013-07-31 12:32:25 CEST: merging latest committed configuration
2013-07-31 12:32:25 CEST: start loading commit script changes
2013-07-31 12:32:26 CEST: no commit script changes
2013-07-31 12:32:26 CEST: no transient commit script changes
2013-07-31 12:32:26 CEST: finished loading commit script changes
2013-07-31 12:32:26 CEST: copying juniper.db to juniper.data+
2013-07-31 12:32:26 CEST: finished copying juniper.db to juniper.data+
2013-07-31 12:32:26 CEST: exporting juniper.conf
2013-07-31 12:32:26 CEST: Exporting /config/juniper.conf.spu

Exiting from the configuration mode here would cause the configuration changes to be lost.

Solution:

In order to recover, delete the commit synchronize command from the system hierarchy, i.e.,   delete system commit synchronize.  After that, the SRX will be able to commit the configurations as expected. 



Related Links

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