<change> (XSLT)
Usage
<change rollback="index"/>
<change url="url" [action="(merge | override | replace | update)"] />
<change [action="(merge | override | replace | update)"] ]>
<!-- tag elements representing configuration statements to load -->
</change>
Release Information
Statement introduced in Junos OS Release 7.4.
Description
Request that the Junos XML protocol server load configuration data into the candidate configuration. Provide the data to load in one of three ways:
- Set the empty <change/> element’s rollback attribute to the numerical index of a previous configuration. The device stores a copy of the most recently committed configuration and up to 49 previous configurations. The specified previous configuration completely replaces the current configuration.
- Set the empty <change/> element’s url attribute to the pathname of a file that resides on the device and contains the Junos XML-encoded configuration data.
- Enclose the configuration data within an opening <change> tag and closing </change> tag. Inside the <change> element, include the configuration data as Junos XML tag elements.
action—Specifies how to load the configuration data, particularly when the candidate configuration and loaded configuration contain conflicting statements. The following are acceptable values:
- merge—Combines the data in the loaded configuration with the candidate configuration. If statements in the loaded configuration conflict with statements in the candidate configuration, the loaded statements replace the candidate ones. This is the default behavior if the action attribute is omitted.
- override—Discards the entire candidate configuration and replaces it with the loaded configuration. When the configuration is later committed, all system processes parse the new configuration.
- replace—Substitutes each hierarchy level
or configuration object defined in the loaded configuration that has
the replace="replace" attribute for the corresponding level
or object in the candidate configuration.
Also set the replace attribute to the value replace on the opening tag of the container tag element that represents the hierarchy level or object to replace. For more information, see the Junos XML Management Protocol Guide.
- update—Compares the loaded configuration and candidate configuration. For each hierarchy level or configuration object that is different in the two configurations, the version in the loaded configuration replaces the version in the candidate configuration. When the configuration is later committed, only system processes that are affected by the changed configuration elements parse the new configuration.
rollback—Specifies the numerical index of the previous configuration to load. Valid values are 0 (zero, for the most recently committed configuration) through one less than the number of stored previous configurations (maximum is 49).
url—Specifies the full pathname of the file that contains the configuration data to load. The file must reside on the device’s local disk.
Usage Guidelines
See Overview of Generating Persistent or Transient Configuration Changes and Overview of Creating Custom Configuration Syntax with Macros.
Hide Navigation Pane
Show Navigation Pane
Download
SHA1