Committing the Candidate Configuration Using NETCONF
When you commit the candidate configuration on a device running Junos OS, it becomes the active configuration on the routing, switching, or security platform. For more detailed information about commit operations, including a discussion of the interaction among different variants of the operation, see the CLI User Guide.
In a NETCONF session with a device running Junos OS, to commit the candidate configuration, a client application encloses the <commit/> tag in an <rpc> tag element.
The NETCONF server confirms that it committed the candidate configuration by returning the <ok/> tag in the <rpc-reply> tag element:
If the NETCONF server cannot commit the candidate configuration, the <rpc-reply> tag element instead encloses an <rpc-error> tag element explaining the reason for the failure. The most common causes are semantic or syntactic errors in the candidate configuration.
To avoid inadvertently committing changes made by other users or applications, a client application locks the candidate configuration before changing it and emits the <commit/> tag while the configuration is still locked. After committing the configuration, the client application unlocks the candidate configuration.
