Rolling Back To A Previous Or Rescue Configuration; Creating, Modifying, Or Deleting Configuration Elements - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Rolling Back to a Previous or Rescue Configuration

Creating, Modifying, or Deleting Configuration Elements

Copyright © 2010, Juniper Networks, Inc.
Client Application
<rpc>
<load-configuration action="override" url="/tmp/new.conf"/>
</rpc>
The routing, switching, or security platform stores a copy of the most recently committed
configuration and up to 49 additional previous configurations. To replace the candidate
configuration or private copy with a previously committed configuration, a client
application includes the
rollback="index"
is the numerical index of the appropriate previous configuration. The index for the
index
most recently committed configuration is
previous configuration is 49
<rpc>
<load-configuration rollback="index">
</rpc>
To replace the configuration with the rescue configuration, include the
attribute in the
<load-configuration/>
<rpc>
<load-configuration rescue="rescue"/>
</rpc>
For more information about rollback and rescue configurations, see the Junos CLI User
Guide.
In addition to replacing the entire configuration (as described in "Replacing the Entire
Configuration" on page 108), a client application can create, modify, or delete one or more
configuration elements (hierarchy levels and configuration objects) in the candidate
configuration or a private copy.
To use Junos XML tag elements to represent an element, the application includes the
tag elements representing all levels in the configuration hierarchy from the root
(represented by the
<configuration>
element. Which attributes and child tag elements are included depends on the operation
being performed on the element. The syntax applies both to the contents of a file and
to a data stream. In the following, the identifier tag element is called
<configuration>
<!-- opening tag for each parent of the element -->
<container-tag [operation-attribute="value"]>
<name>identifier</name> <!-- if the element has an identifier -->
<!-- other child tag elements --> <!-- if appropriate for the operation -->
</container-tag>
<!-- closing tag for each parent of the element -->
</configuration>
Chapter 5: Changing Configuration Information
Junos XML Protocol Server
<rpc-reply xmlns:junos="URL ">
<load-configuration-results>
<load-success/>
</load-configuration-results>
</rpc-reply>
attribute in the
0 (zero), and the index for the oldest possible
.
tag.
tag element) down to the element's container tag
tag, where
<load-configuration/>
rescue="rescue"
:
<name>
109