<commit-configuration>

Usage

<rpc>
    <commit-configuration/>

    <commit-configuration>
        <at-time>time-specification</at-time>
    </commit-configuration>

    <commit-configuration>
        <check/>
    </commit-configuration>

    <commit-configuration>
        <confirmed/>
        <confirm-timeout>rollback-delay</confirm-timeout>
    </commit-configuration>

    <commit-configuration>
        <synchronize/>
    </commit-configuration>

</rpc>

Description

Request that the JUNOScript server perform one of the following actions, depending on the tag element's contents:

• Commit the current candidate configuration, making it the active configuration on the router. Emit the empty <commit-configuration/> tag.
• Schedule the current candidate configuration for commit at a future time. Enclose the <at-time> tag element in the <commit-configuration> tag element. There are three valid types of time specifiers:

• The string reboot, to commit the configuration the next time the router 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 in the future but before 11:59:59 PM on the day the <commit-configuration> tag element is emitted. Use 24-hour time for the hh value; for example, 04:30:00 means 4:30:00 AM and 20:00 means 8:00 PM. The time is interpreted with respect to the clock and time zone settings on the router.
• 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 date and time, which must be after the <commit-configuration> tag element is emitted. Use 24-hour time for the hh value. For example, 2003-03-21 12:30:00 means 12:30 PM on August 21, 2003. The time is interpreted with respect to the clock and time zone settings on the router.

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.

• Verify the syntactic correctness of the current candidate configuration without actually committing it. Enclose the <check/> tag in the <commit-configuration> tag element.
• Commit the current candidate configuration but roll back to the previous configuration after a short time. Enclose the <confirmed/> tag in the <commit-configuration> tag element. By default, the rollback occurs after 10 minutes; to set a different rollback delay, also emit the optional <confirm-timeout> tag element.

To delay the rollback again (past the original rollback deadline), emit the <confirmed/> tag (enclosed in the <commit-configuration> tag element) again before the deadline passes. Include the <confirm-timeout> tag element to specify how long to delay the next rollback, or omit that tag element to use the default of 10 minutes. The rollback can be delayed repeatedly in this way.

To commit the configuration immediately and permanently after emitting the <confirmed/> tag, emit the empty <commit-configuration/> tag before the rollback deadline passes. The JUNOScript server commits the current candidate configuration and cancels the rollback. If the candidate configuration is still the same as the current committed configuration, this effectively recommits the current committed configuration.

• On a router with multiple Routing Engines, copy the candidate configuration stored on the local Routing Engine to the other Routing Engine, verify the candidate's syntactic correctness, and commit it on both Routing Engines. Enclose the <synchronize/> tag in the <commit-configuration> tag element.

Contents

at-time—Schedules the commit operation for a specified future time.

check—Requests verification that the configuration is syntactically correct, but does not actually commit it.

confirmed—Requests a commit of the current candidate configuration and a rollback to the previous configuration after a short time, 10 minutes by default. Use the <confirm-timeout> 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/> tag is enclosed in the <commit-configuration> tag element.

synchronize—Requests that the candidate configuration on the local Routing Engine be copied to the other Routing Engine, checked for correct syntax, and committed on both Routing Engines.

See Also

<commit-results>, <rpc>