Committing the Candidate Configuration Only After Confirmation
Copyright © 2010, Juniper Networks, Inc.
The Junos XML protocol server immediately checks the configuration for syntactic
correctness and returns
<rpc-reply>
elements. If the syntax check succeeds, the
<commit-check-success/>
the Routing Engine on which the check succeeded (
Routing Engine, and either
also encloses an
<output>
occur:
<rpc-reply xmlns:junos="URL">
<commit-results>
<routing-engine>
<name>(re0 | re1)</name>
<commit-check-success/>
<output>commit at will be executed at timestamp</output>
</routing-engine>
</commit-results>
</rpc-reply>
The configuration is scheduled for commit at the specified time. The Junos XML protocol
server does not emit additional tag elements when it performs the actual
commit operation.
If the configuration is not syntactically correct, an
elements that describe the error. The commit operation is not scheduled.
The
tag element can be combined with the
<at-time>
tag element, or both. For more information, see "Committing and Synchronizing a
Configuration on Redundant Control Planes" on page 140 and "Logging a Message About
a Commit Operation" on page 145.
The following example shows how to schedule a commit operation for 10:00 PM on the
current day.
Client Application
Junos XML Protocol Server
<rpc>
<commit-configuration>
<at-time>22:00</at-time>
</commit-configuration>
</rpc>
<rpc-reply xmlns:junos="URL ">
<commit-results>
<routing-engine>
</routing-engine>
</commit-results>
</rpc-reply>
To commit the candidate configuration but require an explicit confirmation for the commit
to become permanent, a client application encloses the empty
and
<commit-configuration>
<rpc>
,
<commit-results>
<routing-engine>
tag and the
tag element, which reports the name of
<name>
re0
or
on devices that can have two Routing Engines). It
re0
re1
tag element that reports the time at which the commit will
<xnm:error>
<name>re1</name>
<commit-check-success/>
<output>commit at will be executed at date 22:00:00 timezone</output>
tag elements:
<rpc>
Chapter 6: Committing a Configuration
, and
tag
<routing-engine>
tag element encloses the
on devices that use a single
tag element encloses tag
tag, the
<synchronize/>
<log/>
tag in
<confirmed/>
137