- play_arrow Overview
- play_arrow NETCONF XML Management Protocol Overview
- play_arrow NETCONF and Junos XML Tags Overview
- XML and Junos OS Overview
- XML Overview
- XML and NETCONF 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 NETCONF Configuration Response Tag Elements in NETCONF Requests and Configuration Changes
-
- play_arrow Manage NETCONF Sessions
- play_arrow NETCONF Session Overview
- play_arrow Manage NETCONF Sessions
- Establish an SSH Connection for a NETCONF Session
- NETCONF Sessions over Transport Layer Security (TLS)
- NETCONF and Shell Sessions over Enhanced Outbound HTTPS
- NETCONF Sessions over Outbound HTTPS
- NETCONF Call Home Sessions
- NETCONF Sessions
- Sample NETCONF Session
- How Character Encoding Works on Juniper Networks Devices
- Configure RFC-Compliant NETCONF Sessions
- NETCONF Monitoring
- NETCONF Event Notifications
- play_arrow NETCONF Tracing Operations
- play_arrow NETCONF Protocol Operations and Attributes
- play_arrow NETCONF Request and Response Tags
- play_arrow Junos XML Protocol Elements Supported in NETCONF Sessions
- <abort/>
- <abort-acknowledgement/>
- <checksum-information>
- <close-configuration/>
- <commit-configuration>
- <commit-results>
- <commit-revision-information>
- <database-status>
- <database-status-information>
- <end-session/>
- <get-checksum-information>
- <get-configuration>
- <load-configuration>
- <load-configuration-results>
- <lock-configuration/>
- <open-configuration>
- <reason>
- <request-end-session/>
- <routing-engine>
- <unlock-configuration/>
- <xnm:error>
- <xnm:warning>
- play_arrow Junos XML Protocol Element Attributes Supported in NETCONF Sessions
-
- play_arrow Manage Configurations Using NETCONF
- play_arrow Change the Configuration Using NETCONF
- Edit the Configuration Using NETCONF
- Upload and Format Configuration Data in a NETCONF Session
- Set the Edit Configuration Mode in a NETCONF Session
- Handle Errors While Editing the Candidate Configuration in a NETCONF Session
- Replace the Candidate Configuration Using NETCONF
- Roll Back Uncommitted Changes in the Candidate Configuration Using NETCONF
- Delete the Configuration Using NETCONF
- Change Individual Configuration Elements Using NETCONF
- Merge Configuration Elements Using NETCONF
- Create Configuration Elements Using NETCONF
- Delete Configuration Elements Using NETCONF
- Replace Configuration Elements Using NETCONF
- Replace Patterns in Configuration Data Using the NETCONF or Junos XML Protocol
- play_arrow Commit the Configuration Using NETCONF
- play_arrow Ephemeral Configuration Database
- Understanding the Ephemeral Configuration Database
- Unsupported Configuration Statements in the Ephemeral Configuration Database
- Enable and Configure Instances of the Ephemeral Configuration Database
- Commit and Synchronize Ephemeral Configuration Data Using the NETCONF or Junos XML Protocol
- Managing Ephemeral Configuration Database Space
- Example: Configure the Ephemeral Configuration Database Using NETCONF
-
- play_arrow NETCONF Utilities
- play_arrow NETCONF Perl Client
- play_arrow Develop NETCONF Perl Client Applications
- Write NETCONF Perl Client Applications
- Import Perl Modules and Declare Constants in NETCONF Perl Client Applications
- Connect to the NETCONF Server in Perl Client Applications
- Collect Parameters Interactively in NETCONF Perl Client Applications
- Submit a Request to the NETCONF Server in Perl Client Applications
- Example: Request an Inventory of Hardware Components Using a NETCONF Perl Client Application
- Example: Change the Configuration Using a NETCONF Perl Client Application
- Parse the NETCONF Server Response in Perl Client Applications
- Close the Connection to the NETCONF Server in Perl Client Applications
-
- play_arrow YANG
- play_arrow YANG Overview
- Understanding YANG on Devices Running Junos OS
- Understanding Junos YANG Modules
- YANG Modules Overview
- Understanding the YANG Modules That Define the Junos OS Configuration
- Understanding the YANG Modules for Junos Operational Commands
- Junos Genstate YANG Data Models
- Understanding the Junos DDL Extensions YANG Module
- YANG Metadata Annotations for Junos Devices
- Use Juniper Networks YANG Modules
- play_arrow Create and Use Non-Native YANG Modules
- Understanding the Management of Nonnative YANG Modules on Devices Running Junos OS
- Manage YANG Packages, Modules, and Scripts on Junos Devices
- Managing YANG Packages and Configurations During a Software Upgrade or Downgrade
- Create Translation Scripts for YANG Configuration Models
- Disable and Enable YANG Translation Scripts on Devices Running Junos OS
- Commit and Display Configuration Data for Nonnative YANG Modules
- Create Custom RPCs in YANG for Devices Running Junos OS
- Create Action Scripts for YANG RPCs on Junos Devices
- Use Custom YANG RPCs on Devices Running Junos OS
- Example: Use a Custom YANG RPC to Retrieve Operational Information on Junos Devices
- Understanding Junos OS YANG Extensions for Formatting RPC Output
- Customize YANG RPC Output on Devices Running Junos OS
- Define Different Levels of Output in Custom YANG RPCs for Junos Devices
- Display Valid Command Option and Configuration Statement Values in the CLI for Custom YANG Modules
- Configure a NETCONF Proxy Telemetry Sensor in Junos
-
- play_arrow OpenDaylight Integration
- play_arrow Configure OpenDaylight Integration
-
- play_arrow Configuration Statements and Operational Commands
Retrieve a Previous (Rollback) Configuration Using NETCONF
In a NETCONF session with a device running Junos OS, to request a previously committed
(rollback) configuration, a client application emits the Junos XML
<get-rollback-information>
tag element and its child
<rollback>
tag element in an <rpc>
tag element. This operation is equivalent to the show system
rollback
operational mode command. The
<rollback>
tag element specifies the index number of the
previous configuration to display; its value can be from 0 (zero, for the most
recently committed configuration) through 49.
To request Junos XML-tagged
output, the application either includes the <format>
tag
element with the value xml
or omits the
<format>
tag element (Junos XML tag elements are the
default):
<rpc> <get-rollback-information> <rollback>index-number</rollback> </get-rollback-information> </rpc> ]]>]]>
The
NETCONF server encloses its response in <rpc-reply>
,
<rollback-information>
, and
<configuration>
tag elements. The
<ok/>
tag is a side effect of the implementation and does
not affect the results. For information about the attributes in the opening
<configuration>
tag, see Specify the Source for Configuration Information Requests Using NETCONF.
<rpc-reply xmlns="URN" xmlns:junos="URL"> <rollback-information> <ok/> <configuration attributes> <!-- tag elements representing the complete previous configuration --> </configuration> </rollback-information> </rpc-reply> ]]>]]>
To
request formatted ASCII output, the application includes the
<format>
tag element with the value
text
.
<rpc> <get-rollback-information> <rollback>index-number</rollback> <format>text</format> </get-rollback-information> </rpc> ]]>]]>
The
NETCONF server encloses its response in <rpc-reply>
,
<rollback-information>
,
<configuration-information>
, and
<configuration-output>
tag elements. For more information
about the formatted ASCII notation used in Junos OS configuration statements, see
the CLI User
Guide.
<rpc-reply xmlns="URN" xmlns:junos="URL"> <rollback-information> <ok/> <configuration-information> <configuration-output> /* previous configuration in formatted ASCII*/ </configuration-output> </configuration-information> </rollback-information> </rpc-reply> ]]>]]>
Starting
in Junos OS Release 16.1, to request a previously committed (rollback) configuration
in JSON format, the application includes the <format>
tag
element with the value json
in the
<get-rollback-information>
element. Prior to Junos OS
Release 16.1, JSON-formatted data is requested by including the
format="json"
attribute in the opening
<get-rollback-information>
tag.
<rpc> <get-rollback-information> <rollback>index-number</rollback> <format>json</format> </get-rollback-information> </rpc> ]]>]]>
When
you use the format="json"
attribute to specify the format, the
NETCONF server encloses its response in an <rpc-reply>
element, the field name for the top-level JSON member is
"rollback-information"
, and the emitted configuration data uses
an older implementation for serialization. When you use the
<format>json</format>
element to request
JSON-formatted data, the NETCONF server encloses its response in
<rpc-reply>
,
<rollback-information>
,
<configuration-information>
, and
<json-output>
tag elements, the field name for the
top-level JSON member is "configuration"
, and the emitted
configuration data uses a newer implementation for serialization.
<rpc-reply xmlns="URN" xmlns:junos="URL"> <rollback-information> <ok/> <configuration-information> <json-output> <!-- JSON data for the complete previous configuration --> </json-output> </configuration-information> </rollback-information> </rpc-reply> ]]>]]>
The following example shows how to request Junos XML-tagged output for the rollback configuration that has an index of 2. In actual output, the Junos-version variable is replaced by a value such as 20.4R1 for the initial version of Junos OS Release 20.4.

Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
<format>
tag element with the value json
in the <get-rollback-information>
element. Prior to Junos
OS Release 16.1, JSON-formatted data is requested by including the format="json"
attribute in the opening <get-rollback-information>
tag.