- play_arrow Overview
- play_arrow Junos XML Management Protocol and Junos XML API Overview
- play_arrow Junos XML Protocol and Junos XML Tags Overview
- XML and Junos OS Overview
- XML Overview
- XML and Junos XML Management Protocol Conventions Overview
- Map Junos OS Commands and Command Output to Junos XML Tag Elements
- Map Configuration Statements to Junos XML Tag Elements
- Using Configuration Response Tag Elements in Junos XML Protocol Requests and Configuration Changes
- play_arrow Junos XML Protocol and JSON Overview
-
- play_arrow Manage Junos XML Protocol Sessions
- play_arrow Junos XML Protocol Session Overview
- play_arrow Manage Junos XML Protocol Sessions
- Satisfy the Prerequisites for Establishing a Connection to the Junos XML Protocol Server
- Configure clear-text or SSL Service for Junos XML Protocol Client Applications
- Connect to the Junos XML Protocol Server
- Start a Junos XML Protocol Session
- Authenticate with the Junos XML Protocol Server for Cleartext or SSL Connections
- Send Requests to the Junos XML Protocol Server
- Parse the Junos XML Protocol Server Response
- Parse Response Tag Elements Using a Standard API in NETCONF and Junos XML Protocol Sessions
- How Character Encoding Works on Juniper Networks Devices
- Handle an Error or Warning in Junos XML Protocol Sessions
- Halt a Request in Junos XML Protocol Sessions
- Lock, Unlock, or Create a Private Copy of the Candidate Configuration Using the Junos XML Protocol
- Terminate a Junos XML Protocol Session
- End a Junos XML Protocol Session and Close the Connection
- Sample Junos XML Protocol Session
- play_arrow Junos XML Protocol Tracing Operations
- play_arrow Junos XML Protocol Operations
- play_arrow Junos XML Protocol Processing Instructions
- play_arrow Junos XML Protocol Response Tags
- play_arrow Junos XML Element Attributes
- active
- count
- delete
- inactive
- insert
- junos:changed
- junos:changed-localtime
- junos:changed-seconds
- junos:commit-localtime
- junos:commit-seconds
- junos:commit-user
- junos:group
- junos:interface-range
- junos:key
- junos:position
- junos:total
- matching
- protect
- recurse
- rename
- replace
- replace-pattern
- start
- unprotect
- xmlns
-
- play_arrow Request Operational and Configuration Information Using the Junos XML Protocol
- play_arrow Request Operational Information Using the Junos XML Protocol
- play_arrow Request Configuration Information Using the Junos XML Protocol
- Request Configuration Data Using the Junos XML Protocol
- Specify the Source for Configuration Information Requests in a Junos XML Protocol Session
- Specify the Output Format for Configuration Data in a Junos XML Protocol Session
- Request Commit-Script-Style XML Configuration Data Using the Junos XML Protocol
- Specify the Output Format for Configuration Groups and Interface Ranges Using the Junos XML Protocol
- Request Identifier Indicators for Configuration Elements Using the Junos XML Protocol
- Request Change Indicators for Configuration Elements Using the Junos XML Protocol
- Specify the Scope of Configuration Data to Return in a Junos XML Protocol Session
- Request the Complete Configuration Using the Junos XML Protocol
- Request a Configuration Hierarchy Level or Container Object Without an Identifier Using the Junos XML Protocol
- Request All Configuration Objects of a Specific Type Using the Junos XML Protocol
- Request a Specific Number of Configuration Objects Using the Junos XML Protocol
- Request Identifiers for Configuration Objects of a Specific Type Using the Junos XML Protocol
- Request a Single Configuration Object Using the Junos XML Protocol
- Request Subsets of Configuration Objects Using Regular Expressions
- Request Multiple Configuration Elements Using the Junos XML Protocol
- Retrieve a Previous (Rollback) Configuration Using the Junos XML Protocol
- Retrieve the Rescue Configuration Using the Junos XML Protocol
- Compare the Active or Candidate Configuration to a Prior Version Using the Junos XML Protocol
- Compare Two Previous (Rollback) Configurations Using the Junos XML Protocol
- Request an XML Schema for the Configuration Hierarchy Using the Junos XML Protocol
-
- play_arrow Junos XML Protocol Utilities
- play_arrow Develop Junos XML Protocol C Client Applications
-
- play_arrow Configuration Statements and Operational Commands
Commit a Configuration at a Specified Time Using the Junos XML Protocol
In a Junos XML protocol session with a device running Junos OS, to commit a
configuration at a specified time in the future, a client application encloses the
<at-time>
element in a
<commit-configuration>
and an
<rpc>
element:
<rpc> <commit-configuration> <at-time>time</at-time> </commit-configuration> </rpc>
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.
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 Using
the Junos XML Protocol and Logging a Message About a Commit Operation Using the Junos XML
Protocol.
The following example shows how to schedule a commit operation for 10:00 PM on the current day.
