ON THIS PAGE
<commit-revision-information>
Usage
<rpc-reply xmlns:junos="URL">
<commit-results>
<routing-engine>
<!-- configuration with commit revision identifier -->
<commit-revision-information>
<old-db-revision>old-revision-id</old-db-revision>
<new-db-revision>new-revision-id</new-db-revision>
</commit-revision-information>
</routing-engine>
</commit-results>
</rpc-reply>Description
Child element included in a Junos XML protocol server
<commit-results> response element to return information
about the old and new configuration revision identifiers (CRI) on a particular
Routing Engine. The CRI is a unique string (for example, re0-1365168149-1) that is
associated with a committed configuration.
Network management system (NMS) applications, such as Junos Space, can use the configuration revision identifier to determine if the NMS's known configuration for a Junos device is identical to the device's current configuration. The NMS can detect if out-of-band commits were made to the device by comparing the CRI associated with the NMS's last commit to the CRI of the configuration on the device.
Contents
<old-db-revision> |
Indicates the old configuration revision identifier, which is the identifier of the configuration prior to the previously successfully committed configuration. |
<new-db-revision> |
Indicates the new configuration revision identifier, which is the identifier of the last successfully committed configuration. |
Release Information
This is a Junos XML management protocol response tag. It is supported in Junos XML protocol sessions, and it is supported as a Juniper Networks proprietary extension in NETCONF sessions on devices running Junos OS that identify the URI http://xml.juniper.net/netconf/junos/1.0 in the capabilities exchange.
Element introduced in Junos OS Release 16.1.