Scheduling Synchronization For A Specified Time; Synchronizing Configurations But Requiring Confirmation - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide
144
<synchronize/>
<check/>
</commit-configuration>
</rpc>
The
<force-synchronize/>
For more information about verifying configurations, see "Verifying a Configuration Before
Committing It" on page 133.

Scheduling Synchronization for a Specified Time

To commit a configuration on both Routing Engines at a specified time in the future, the
application encloses the
<synchronize/>
<commit-configuration> and
<rpc>
<commit-configuration>
<synchronize/>
<at-time>time</at-time>
</commit-configuration>
</rpc>
<rpc>
<commit-configuration>
<force-synchronize/>
<at-time>time</at-time>
</commit-configuration>
</rpc>
As when the tag element is emitted by itself, the Junos XML protocol server
<at-time>
verifies syntactic correctness immediately and does not emit additional tag elements
when it actually performs the commit operation on each Routing Engine. For information
about how to specify the time in the
Candidate Configuration Only After Confirmation" on page 137.

Synchronizing Configurations but Requiring Confirmation

To commit the candidate configuration on both Routing Engines but require confirmation
for the commit to become permanent, the application encloses the
, and (optionally)
<confirmed/>
<commit-configuration> and
<rpc>
<commit-configuration>
<synchronize/>
<confirmed/>
[<confirm-timeout>minutes</confirm-timeout>]
</commit-configuration>
</rpc>
The same rollback deadline applies to both Routing Engines and can be extended on
both at once by again emitting the
<confirm-timeout> tag elements on the Routing Engine where the tag elements were
emitted the first time.
tag cannot be combined with the
and
<at-time>
<rpc> tag elements:
tag element, see "Committing the
<at-time>
tag elements in
<confirm-timeout>
<rpc> tag elements:
,
<synchronize/> <confirmed/>
tag elements.
<check/>
tag elements in
<synchronize/>
, and (optionally)
Copyright © 2010, Juniper Networks, Inc.
,