Committing a Configuration at a Specified Time

To commit a configuration at a specified time in the future, a client application encloses the <at-time> tag element in <commit-configuration> and <rpc> tag elements:

To indicate when to perform the commit operation, the application includes one of three types of values in the <at-time> tag element:

The string reboot, to commit the configuration the next time the device reboots.
A time value of the form hh:mm[:ss] (hours, minutes, and optionally seconds), to commit the configuration at the specified time, which must be after the time at which the application emits the <commit-configuration> tag element, but before 11:59:59 PM on the current day. For example, if the <at-time> tag element encloses the value 02:00 (2:00 AM) and the application emits the <commit-configuration> tag element at 2:10 AM, the commit will never take place, because the scheduled time has already passed for that day.
Use 24-hour time; for example, 04:30:00 means 4:30:00 AM and 20:00 means 8:00 PM. The time is interpreted relative to the clock and time zone settings on the device..
A date and time value of the form yyyy-mm-dd hh:mm[:ss] (year, month, date, hours, minutes, and optionally seconds), to commit the configuration at the specified day and time, which must be after the <commit-configuration> tag element is emitted. Use 24-hour time. For example, 2006-08-21 15:30:00 means 3:30 PM on August 21, 2006. The time is interpreted relative to the clock and time zone settings on the device.

Note: The specified time must be more than 1 minute later than the current time on the device.

The Junos XML protocol server immediately checks the configuration for syntactic correctness and returns <rpc-reply>, <commit-results>, and <routing-engine> tag elements. If the syntax check succeeds, the <routing-engine> tag element encloses the <commit-check-success/> tag and the <name> tag element, which reports the name of the Routing Engine on which the check succeeded (re0 on devices that use a single Routing Engine, and either re0 or re1 on devices that can have two Routing Engines). It also encloses an <output> tag element that reports the time at which the commit will 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 <xnm:error> tag element encloses tag elements that describe the error. The commit operation is not scheduled.

The <at-time> tag element can be combined with the <synchronize/> tag, the <log/> tag element, or both. For more information, see Committing and Synchronizing a Configuration on Redundant Control Planes and Logging a Message About a Commit Operation.

The following example shows how to schedule a commit operation for 10:00 PM on the current day.