<rpc-reply xmlns:junos="URL"> <commit-results>
<!-- 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>
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.
Child element included in a Junos XML protocol
<commit-results> response element
to return information about the old and new configuration request
identifiers on a particular Routing Engine. The configuration request
identifier is used by network management server (NMS) applications,
such as Junos Space, to determine whether the synchronization (sync)
status of a device that the NMS application manages is out-of-sync
Out-of-band configuration changes are configuration changes
made to a device outside of the network management server (NMS) application,
such as Junos Space. For example, configuration changes can be performed
on a device using the device CLI, using the device Web-based management
interface (the J-Web interface or Web View), or using the Junos Space
Network Management Platform configuration editor. As a result, there
is a requirement for a configuration revision identifier to determine
whether the configuration settings on devices being managed by an
NMS application is in sync with the CLI of devices running Junos OS.
A configuration revision identifier might not be necessary if the
NMS application is the only utility that is used to modify the configuration
of a device. However, in a real- world network deployment, out-of-band
configuration commits might occur on a device, such as during a maintenance
window for support operations. In such cases, the NMS application
might not detect these out-of-band commits. To solve this problem,
starting in Junos OS Release 16.1, the
<commit-revision-information> element containing a configuration revision identifier string is
enclosed within the
<routing-engine> tags. The configuration
revision identifier is a string (for example, re0-1365168149-1), which
has the following format:
<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.
<revision-id>—Unique identifier of the revision made to the configuration in the database, which contains the name of the Routing Engine on which the commit operation was performed.