Committing A Private Copy Of The Configuration - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Committing a Private Copy of the Configuration

Copyright © 2010, Juniper Networks, Inc.
To commit a private copy of the configuration so that it becomes the active configuration
on the routing, switching, or security platform, a client application encloses the
empty <commit-configuration/>
candidate configuration):
<rpc>
<commit-configuration/>
</rpc>
The Junos XML protocol server creates a copy of the current regular candidate
configuration, merges in the changes made to the private copy, and commits the combined
candidate to make it the active configuration on the device. The server reports the results
of the commit operation in
If the private copy does not include any changes, the server emits the
and </commit-results> tags with nothing between them:
<rpc-reply xmlns:junos="URL">
<commit-results>
</commit-results>
</rpc-reply>
If the private copy includes changes and the commit operation succeeds, the server emits
the <load-success/> tag when it merges the changes in the private copy into the candidate
configuration. The subsequent
tag and the
<commit-success/>
Routing Engine on which the commit operation succeeded (
single Routing Engine, and either
<rpc-reply xmlns:junos="URL">
<commit-results>
<load-success/>
<routing-engine>
<name>(re0 | re1)</name>
<commit-success/>
</routing-engine>
</commit-results>
</rpc-reply>
If the private copy includes changes that conflict with the regular candidate configuration,
the commit fails. The
<load-error-count>
an tag element encloses tag elements that describe the error.
<xnm:error>
There are restrictions on committing a private copy. For example, the commit fails if the
regular candidate configuration is locked by another user or application, or if it includes
uncommitted changes made since the private copy was created. For more information,
see the Junos CLI User Guide.
Most of the variants of the commit operation are available for a private copy. The variants
are described in subsequent sections in this chapter:
Scheduling the commit for a later time, as described in "Committing a Configuration
at a Specified Time" on page 136.
tag in an <rpc> tag element (just as for the
<rpc-reply> and <commit-results>
<routing-engine> tag element encloses the
tag element, which reports the name of the
<name>
or on devices that can have two Routing Engines):
re0 re1
tag element reports the number of errors and
Chapter 6: Committing a Configuration
tag elements.
<commit-results>
on devices that use a
re0
135