Committing The Candidate Configuration - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide

Committing the Candidate Configuration

134
<commit-check-success/>
</routing-engine>
</commit-results>
</rpc-reply>
If the syntax check fails, an
the error.
The tag can be combined with the
<check/>
"Verifying the Configuration on Both Routing Engines" on page 143.
To commit the candidate configuration, a client application encloses the empty
<commit-configuration/> tag in an
<rpc>
<commit-configuration/>
</rpc>
We recommend that the application lock the candidate configuration before changing
it and emit the
<commit-configuration/>
so avoids inadvertent commit of changes made by other users or applications. After
committing the configuration, the application must unlock it for other users and
applications to be able to make changes. For instructions, see "Exchanging Information
with the Junos XML Protocol Server" on page 45 and "Changing Configuration Information"
on page 103.
The Junos XML protocol server reports the results of the commit operation in
, and
<commit-results> <routing-engine>
the tag element encloses the
<routing-engine>
tag element, which reports the name of the Routing Engine on which the commit operation
succeeded ( re0 on devices that use a single Routing Engine, and either
devices that can have two Routing Engines):
<rpc-reply xmlns:junos="URL">
<commit-results>
<routing-engine>
<name>(re0 | re1)</name>
<commit-success/>
</routing-engine>
</commit-results>
</rpc-reply>
If the commit operation fails, an
describe the error. The most common causes of failure are semantic or syntactic errors
in the candidate configuration.
tag element encloses tag elements that describe
<xnm:error>
<synchronize/>
<rpc> tag element:
tag while the configuration is still locked. Doing
tag elements. If the commit operation succeeds,
<commit-success/>
tag element encloses tag elements that
<xnm:error>
tag, which is described in
<rpc-reply>
tag and the
<name>
re0 or re1
Copyright © 2010, Juniper Networks, Inc.
,
on