Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual page 160

Junos 10.3 Junos XML Management Protocol Guide
138
<commit-configuration>
<confirmed/>
</commit-configuration>
</rpc>
If the commit is not confirmed within a certain amount of time (10 minutes by default),
the Junos XML protocol server automatically retrieves and commits (rolls back to) the
previously committed configuration. To specify a different number of minutes for the
rollback deadline, the application encloses a positive integer value in the
tag element:
<confirm-timeout>
<rpc>
<commit-configuration>
<confirmed/>
<confirm-timeout>minutes</confirm-timeout>
</commit-configuration>
</rpc>
NOTE: You cannot perform this commit operation on a private copy of the configuration.
The confirmed commit operation is useful for verifying that a configuration change works
correctly and does not prevent management access to the device. If the change prevents
access or causes other errors, the automatic rollback to the previous configuration restores
access after the rollback deadline passes.
In response to a confirmed commit operation, the Junos XML protocol server returns
<rpc-reply> , <commit-results>
operation succeeds, the
<routing-engine>
tag and the tag element, which reports the name of the Routing Engine on which
<name>
the commit operation succeeded (
either or on devices that can have two Routing Engines):
re0 re1
<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.
To delay the rollback to a time later than the current rollback deadline, the application
encloses the
<confirmed/>
the deadline passes. It can include the
long to delay the next rollback, or omit that tag element to delay the rollback by the
default of 10 minutes. The application can delay the rollback indefinitely by emitting the
<confirmed/> tag repeatedly in this way.
, and <routing-engine>
tag element encloses the
re0 on devices that use a single Routing Engine, and
tag element encloses tag elements that
<xnm:error>
tag in a
<commit-configuration>
<confirm-timeout>
tag elements. If the commit
<commit-success/>
tag element again before
tag element to specify how
Copyright © 2010, Juniper Networks, Inc.