Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual page 146

Junos 10.3 Junos XML Management Protocol Guide
124
The renaming operation is not available when formatted ASCII text is used to represent
the configuration data.
The attribute can be combined with the
rename
or reactivate the configuration element as it is renamed. For more information, see
"Changing a Configuration Element's Activation State Simultaneously with Other Changes"
on page 127.
The following example shows how to change the name of a firewall filter from
to
access-control new-access-control
configuration mode command:
[edit firewall family inet]
user@host# rename filter access-control to filter new-access-control
Client Application
<rpc>
<load-configuration>
<configuration>
<firewall>
<family>
<inet>
<filter rename="rename" name="new-access-control">
<name>access-control</name>
</filter>
</inet>
</family>
</firewall>
</configuration>
</load-configuration>
</rpc>
The following example shows how to change the identifiers for an OSPF virtual link
(defined at the
[edit protocols ospf area area]
and to
transit-area 1.1.1.1 neighbor-id 192.168.0.7
equivalent to the following configuration mode command (which appears on two lines
for legibility only):
[edit protocols ospf area area]
user@host# rename filter virtual-link neighbor-id 192.168.0.3 transit-area \
1.1.1.1 to virtual-link neighbor-id 192.168.0.7 transit-area 1.1.1.5
or
inactive active
. This operation is equivalent to the following
Junos XML Protocol Server
<rpc-reply xmlns:junos="URL ">
<load-configuration-results>
<load-success/>
</load-configuration-results>
</rpc-reply>
hierarchy level) from
and
transit-area 1.1.1.5
Copyright © 2010, Juniper Networks, Inc.
attribute to deactivate
neighbor-id 192.168.0.3
. This operation is