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

[Junos] What is difference between 'commit' and 'commit full'?

0

0

Article ID: KB15410 KB Last Updated: 17 Sep 2020Version: 4.0
Summary:

What is difference between 'commit' and 'commit full'?

Symptoms:

Console output of a 'commit' and 'commit full' are documented below.

Solution:

A 'commit' (performed after configuration changes) checks only the corresponding daemons. However, the 'commit full' action requires all daemons to check and evaluate the new configuration.  A 'commit full' is useful if you get an error with 'commit' or when you've changed the config significantly.

CAUTION: 'commit full' is an unsupported CLI command; it might cause a network outage since it does a replace of the entire config, not just a config change.

For example, when only the OSPF stanza is changed, only the routing protocol daemon responds as below:

commit |display detail 
2020-06-07 08:21:25 UTC: Obtaining lock for commit
2020-06-07 08:21:25 UTC: updating commit revision
2020-06-07 08:21:25 UTC: UI extensions feature is not configured
2020-06-07 08:21:25 UTC: Started running translation script
2020-06-07 08:21:25 UTC: Finished running translation script
2020-06-07 08:21:25 UTC: start loading commit script changes
2020-06-07 08:21:25 UTC: no commit script changes
2020-06-07 08:21:25 UTC: no transient commit script changes
2020-06-07 08:21:25 UTC: finished loading commit script changes
2020-06-07 08:21:25 UTC: No translation output from the scripts
2020-06-07 08:21:25 UTC: copying juniper.db to juniper.data+
2020-06-07 08:21:25 UTC: finished copying juniper.db to juniper.data+
2020-06-07 08:21:25 UTC: exporting juniper.conf
2020-06-07 08:21:25 UTC: expanding interface-ranges
2020-06-07 08:21:25 UTC: finished expanding interface-ranges
2020-06-07 08:21:25 UTC: expanding groups
2020-06-07 08:21:25 UTC: finished expanding groups
2020-06-07 08:21:25 UTC: setup foreign files
2020-06-07 08:21:25 UTC: update license counters
2020-06-07 08:21:25 UTC: finish license counters
2020-06-07 08:21:25 UTC: propagating foreign files
2020-06-07 08:21:25 UTC: cdg returns = 7(persist groups is not configured (needed for cdg))
2020-06-07 08:21:25 UTC: complete foreign files
2020-06-07 08:21:25 UTC: dropping unchanged foreign files
2020-06-07 08:21:25 UTC: executing 'ffp propagate'
2020-06-07 08:21:25 UTC: daemons checking new configuration
2020-06-07 08:21:25 UTC: commit wrapup...
2020-06-07 08:21:25 UTC: start ffp activate
2020-06-07 08:21:25 UTC: executing 'ffp activate'
2020-06-07 08:21:26 UTC: activating '/var/etc/pam.conf'
2020-06-07 08:21:26 UTC: activating '/var/etc/pam_radius.conf'
2020-06-07 08:21:26 UTC: activating '/var/etc/pam_tacplus.conf'
2020-06-07 08:21:26 UTC: activating '/var/etc/issue'
2020-06-07 08:21:26 UTC: activating '/var/etc/certs'
2020-06-07 08:21:26 UTC: activating '/var/etc/motd'
2020-06-07 08:21:26 UTC: activating '/var/etc/max-db-size-cfg'
2020-06-07 08:21:26 UTC: activating '/var/etc/subs-mgmt-cfg'
2020-06-07 08:21:26 UTC: activating '/var/etc/ephinst.conf'
2020-06-07 08:21:26 UTC: executing foreign_commands
2020-06-07 08:21:26 UTC: /bin/sh /etc/rc.ui ui_setup_users (sh)
2020-06-07 08:21:26 UTC: not executing ui_commit in rc.ui
2020-06-07 08:21:26 UTC: finish ffp activate
2020-06-07 08:21:26 UTC: copying configuration to juniper.save
2020-06-07 08:21:26 UTC: db_check_constraint_ids_clear start
2020-06-07 08:21:26 UTC: db_check_constraint_ids_clear done
2020-06-07 08:21:26 UTC: db_groups_info_clear start
2020-06-07 08:21:26 UTC: db_groups_info_clear done
2020-06-07 08:21:26 UTC: activating '/var/run/db/juniper.data'
2020-06-07 08:21:26 UTC: Rotate backup configs
2020-06-07 08:21:26 UTC: ssync begins
2020-06-07 08:21:26 UTC: ssync ends
2020-06-07 08:21:26 UTC: ssync begins
2020-06-07 08:21:26 UTC: ssync ends
2020-06-07 08:21:26 UTC: notifying daemons of new configuration
2020-06-07 08:21:26 UTC: ssync begins
2020-06-07 08:21:26 UTC: ssync ends
2020-06-07 08:21:26 UTC: commit complete
commit complete


See the attached for the 'commit full' detail list: KB15410 commit full detail [txt]
Note: All daemons are evaluated.


 
Modification History:

2020-07-07: ​Updated outputs from Junos 17.4R1.16.

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