[Contents] [Prev] [Next] [Index] [Report an Error]

# Replacing Parts of the Configuration

A replace operation searches for replace attributes in the specified file, deletes the existing statements of the same name, if any, and replaces them with the incoming configuration. If there is no existing statement of the same name, the replace operation adds to the configuration the statements marked with the replace attribute. You can also use create, delete, and merge attributes in the file.

If you are performing a replace operation and the file you specify does not contain any replace attributes, the replace operation is effectively equivalent to a merge operation. This type of operation might be useful if you are running automated scripts and cannot know in advance whether the scripts need to perform a replace or a merge operation. The scripts can use the replace operation to cover either case.

You can merge a configuration from files in XML or text format. The examples in this section use files in XML format.

You can replace all of the configuration, or the configuration at a specified hierarchy level. For information about loading a configuration at a specified hierarchy level, see Loading a Configuration at a Specified Hierarchy Level.

To replace portions of a configuration:

1. Make sure that the incoming configuration file has replace attributes in place for each part of the configuration to be replaced.

   See About SRC Configuration Files in XML Format.

2. In configuration mode, specify the load replace command. For example:

   user@host# load replace newcfg.xml format xml

The following example shows part of the existing configuration, the configuration in the file to be loaded, and the resulting configuration. In the resulting configuration, bold text indicates the configuration that changed.

For an example of a file snippet that shows how to replace a number a values within a hierarchy, see About SRC Configuration Files in XML Format.

Existing configuration:

`

<configuration>
. . .
<system>
. . .
<host-name>myhost</host-name>
<name-server>192.2.2.10</name-server>
<name-server>192.2.2.20</name-server>
<domain-search>mydomain.juniper.net</domain-search>
<domain-search>juniper.net</domain -search>
. . .
</system>
. . .
</configuration>

`

Configuration in the file to be loaded:

`

<configuration>
. . .
<system>
. . .
<host-name>myhost</host-name>
< name-server operation=” replace” >192.2.2.10</name-server>
<name-server>192.2.2.30
</name-server>
<domain-search>mydomain.juniper.net</domain-search>
<domain-search>mydomain.juniper.net
</domain-search>
<domain-search>juniper.net</domain -search>
. . .
</system>
. . .
</configuration>

`

Resulting configuration:

`

<configuration>
. . .
<system>
. . .
<host-name>myhost</host-name>
<name-server>192.2.2.10</name-server>
<name-server>192.2.2.30</name-server>
<domain-search>mydomain.juniper.net</domain-search>
<domain-search>juniper.net</domain -search>
. . .
</system>
. . .
</configuration>

`

#### Related Topics

- Replacing the Current Configuration with the Default SRC Configuration
- Merging the Active Configuration with Another Configuration
- Replacing the Configuration
- Adding a Configuration Through Configuration Mode Commands
- Reverting to a Previous SRC Configuration

[Contents] [Prev] [Next] [Index] [Report an Error]