Filter
Top Products
10-30
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Chapter 10 Editing and Deploying Configurations Using Config Editor
What Happens During Configuration Deployment in Overwrite and Merge Modes
• ALLOW—false
What Happens During Configuration Deployment in Overwrite
and Merge Modes
Overwrite Mode
Config Editor assumes that the latest archived version is the same as the running configuration on the
device.
Before Config Editor downloads the archived configuration on the device, it compares the archived
version (which you have modified) with the latest version. The application then overwrites the running
configuration on the device with the archived version. This means, after the configuration is successfully
deployed, the selected configuration and the running configuration on the device are the same.
For example, assume that the archived version contains commands a, b, c, and d; and that the latest
running version, contains commands a, b, e, f, and g. After the archived configuration has been restored,
the currently running configuration on the device, will contain commands a, b, c, and d.
Ensure that all the required commands are in the archived version. You can review the work order and
make necessary changes by editing the archived version, if required.
This is the default mode for the configuration deployment.
Merge Mode
The configuration that you have selected is deployed on to the device as is. This means, the existing
running configuration of the device is updated incrementally with the commands in the selected
configuration.
The selected running configuration is not compared with the running configuration in the Configuration
Archive.
We recommend that you use this mode on newly deployed devices. This is because, the Merge option
effectively deploys the entire configuration from the archive, on to the device.
Overview: Downloading a Configuration File
To download a configuration file to the device and to the archive, you must:
• Start creating a download job.
• Select the configuration file on which the job will run.
• Configure the job properties.
• Set the job approvers.
• Review the job work order.
When a job starts to download, the users on the job approver list are notified by e-mail. At least one
approver must approve the job before it can run. Make sure that an approver list with the approvers you
want exists.
If there is no approver list but you have the correct access privileges, you must modify or create approver
lists, using the Job Approval option (Select RME> Admin> Approval). Otherwise, contact your system
administrator.