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

Junos 10.3 Junos XML Management Protocol Guide
Contents
158
To schedule the configuration for commit at a future time, enclose the
element in the
<commit-configuration>
time specifiers:
The string , to commit the configuration the next time the device reboots.
reboot
A time value of the form
commit the configuration at the specified time, which must be in the future but before
11:59:59 PM on the day the
24-hour time for the
hh
means 8:00 PM. The time is interpreted with respect to the clock and time zone
settings on the device.
A date and time value of the form
minutes, and, optionally, seconds), to commit the configuration at the specified date
and time, which must be after the
Use 24-hour time for the
on August 21, 2005. The time is interpreted with respect to the clock and time zone
settings on the device.
NOTE: The time you specify must be more than 1 minute later than the current time on
the device.
The configuration is checked immediately for syntactic correctness. If the check
succeeds, the configuration is scheduled for commit at the specified time. If the
check fails, the commit operation is not scheduled.
—Schedules the commit operation for a specified future time.
<at-time>
—Requests verification that the configuration is syntactically correct, but does
<check>
not actually commit it.
<confirmed> —Requests a commit of the candidate configuration and a rollback to the
previous configuration after a short time, 10 minutes by default. Use the
tag element to specify a different amount of time.
<confirm-timeout> —Specifies the number of minutes for which the configuration remains
active when the
<confirmed/>
—Records a message in the file
<log>
operation succeeds.
—On dual control plane systems, requests that the candidate configuration
<synchronize>
on one control plane be copied to the other control plane, checked for correct syntax,
and committed on both Routing Engines.
<force-synchronize> —On dual control plane systems, forces the candidate configuration
on one control plane to be copied to the other control plane.
tag element. There are three valid types of
(hours, minutes, and, optionally, seconds), to
hh:mm[:ss]
<commit-configuration>
value; for example,
04:30:00
yyyy-mm-dd hh:mm[:ss]
<commit-configuration>
hh value. For example, 2005-08-21 15:30:00
tag is enclosed in the
<commit-configuration>
/var/log/commits
<at-time>
tag element is emitted. Use
means 4:30:00 AM and
(year, month, date, hours,
tag element is emitted.
means 3:30 PM
<confirm-timeout>
tag element.
when the commit
Copyright © 2010, Juniper Networks, Inc.
tag
20:00