Merging Configuration Elements - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide

Merging Configuration Elements

110
To use formatted ASCII text to represent an element, the application includes the
complete statement path, starting with a statement that can appear directly under the
[edit] hierarchy level. The attributes and child statements to include depend on the
operation being performed on the element. The set of statements is enclosed in a
tag element when the application provides a data stream. When
<configuration-text>
saving statements to a file for later loading, omit the
<configuration-text>
/* statements for parent levels of the element */
operation-to-perform: # if appropriate
element identifier { # if the element has an identifier
/* child statements */ # if appropriate for the operation
}
/* closing braces for parent levels for the element */
</configuration-text>
When loading formatted ASCII text, the application includes the
in the
<load-configuration/>
For more information about the source and formatting for configuration elements, see
"Specifying the Source and Format of New Configuration Data" on page 105.
For information about the operations a client application can perform on configuration
elements, see the following sections:
Merging Configuration Elements on page 110
Replacing Configuration Elements on page 113
Creating New Configuration Elements on page 114
Replacing Configuration Elements Only If They Have Changed on page 115
Deleting Configuration Elements on page 116
By default, the Junos XML protocol server merges loaded configuration data into the
candidate configuration according to the following rules. (The rules also apply to a private
copy of the configuration, but for simplicity the following discussion refers to the candidate
configuration only.)
A configuration element (hierarchy level or configuration object) that exists in the
candidate but not in the loaded configuration remains unchanged.
A configuration element that exists in the loaded configuration but not in the candidate
is added to the candidate.
If a configuration element exists in both configurations, the semantics are as follows:
If a child statement of the configuration element (represented by a child tag element)
exists in the candidate but not in the loaded configuration, it remains unchanged.
If a child statement exists in the loaded configuration but not in the candidate, it is
added to the candidate.
If a child statement exists in both configurations, the value in the loaded configuration
replaces the value in the candidate.
<configuration-text>
tag or opening
<load-configuration>
Copyright © 2010, Juniper Networks, Inc.
tag element.
attribute
format="text"
tag.