Set Up Device Configuration File Management
Make Sure Devices Are Configured Correctly
Before you start using the Configuration Archive features, make sure devices are configured according to the settings in Configure Devices So They Can Be Modeled and Monitored.
Control How Archiving is Triggered
By default, Cisco EPN Manager saves device configuration files to the archive when:
-
A new device is added to Cisco EPN Manager
-
When a device change notification is received
-
Archive collection is not carried out in case of full or granular sync.
Note
If there is an event occurrence, archive data is collected after the period of configured hold off timer.
Users with Administrator privileges can change these settings.
Procedure
Step 1 |
Choose , then choose . |
||||||
Step 2 |
Adjust the archiving settings depending on the following criteria.
|
||||||
Step 3 |
To schedule regular archiving for groups of devices (or single devices):
|
Set Up Event-Triggered Archiving
By default, Cisco EPN Manager backs up a device’s configuration file whenever it receives a change notification event. This function will work only if devices are configured properly; see How Is Inventory Collected?. For example, for devices running Cisco IOS XR and Cisco IOS XE, the following setting must be configured:
logging server-IP
When Cisco EPN Manager receives a configuration change event, it waits 10 minutes (by default) before archiving in case more configuration change events are received. This prevents multiple collection processes from running at the same time. To check or change this setting, choose , then choose and adjust the Hold Off Timer.
Note |
The Hold Off Timer may be set to a shorter period for certain events, called expedited events. For more information, see Change the Behavior of Expedited Events. |
To turn off event-triggered archiving, choose Archive configuration on receiving configuration change events? check box.
, then choose and uncheck theSpecify Items to be Excluded When Configuration Files Are Checked for Changes
Some lines in device configuration files should be excluded when Cisco EPN Manager compares different versions to identify changes. Cisco EPN Manager excludes some lines by default, such as clock settings for routers and switches. If you have Administrator privileges, you can check which lines are excluded, and add more lines to be excluded.
Procedure
Step 1 |
Choose , then choose . |
Step 2 |
Click the Advanced tab. |
Step 3 |
In the Product Family list, choose the devices or groups to which you want to apply the command exclusions. |
Step 4 |
In the Command Exclude List, enter a comma-separated list of configuration commands you want to exclude for that selection. These are the parameters Cisco EPN Manager will ignore when checking devices for configuration changes. |
Step 5 |
Click Save. |
Control the Timeouts for Configuration Archive Operations
The Configuration Archive task uses the Device CLI Timeout value for each fetch activity. A single Configuration Archive task entails 1 to 5 files. Consequently, the overall job timeout value is determined using the following logic:Overall job timeout = Number of files*Device CLI Timeout
To configure a CLI timeout value, choose Telnet/SSH option, and then enter a value in the Timeout field.
, click the edit device icon, select theNote |
You must increase the Device CLI timeout value if the Configuration Archive task fails due to CLI timeout. |
Control How Often Alarms are Triggered
By default, Cisco EPN Manager saves device configuration files to the archive based on the configured settings. However, when these jobs fail, you can choose to generate an alarm notification.
When a Configuration Archive job fails, Cisco EPN Manager waits for 7 days or for more than 5 (by default) configuration files before triggering an alarm. The alarm has information about the cause for the trigger of the alarm and other related details associated with the configuration archives. To change the default settings for how often the alarms are generated, choose , then choose , and adjust the Alarm Threshold parameter for maximum number of configuration files (exceeding which an alarm is generated) and the number of days to wait before the alarm is triggered.
Control When Device Configuration Files are Purged from the Database
Device configuration files cannot be automatically deleted from the database (you can manually delete the files); they can be periodically purged by Cisco EPN Manager based on your settings. Users with Administrator privileges can adjust when configuration files are purged as follows. If you do not want any configuration files purged, follow this procedure but leave both fields blank.
Note |
For a description of how to manually delete a configuration file, see Delete Archived Device Configuration Files. |
Procedure
Step 1 |
Choose , then choose . |
||||||
Step 2 |
Adjust the archiving settings depending on the following criteria.
|