Filter
Top Products
8-25
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Chapter 8 Archiving Configurations and Managing Them Using Archive Management
Understanding Configuration Retrieval and Archival
Manual Updates (Sync Archive function)
This feature allows the RME user to force the configuration archive to check specified devices for
changes to the running configuration file only. Use Sync Archive if you need it to synchronize quickly
with the running configuration.
You can also poll the device and compare the time of change currently on the device with the time of last
archival of the configuration to determine whether the configuration has changed on a device.
The Startup configuration is not retrieved during manual update archive operation. However, you can
retrieve the Startup configuration by enabling the Fetch startup Config option while scheduling Sync
Archive job.
See Scheduling Sync Archive Job for further details.
Using Version Summary
You can trigger a configuration file retrieval by clicking on the Running or Startup configuration in the
Configuration Version Summary report.
After a configuration file is fetched from the device, as described above, RME submits the configuration
file for archival.
See Viewing the Configuration Version Summary for further details.
Timestamps of Configuration Files
These are timestamps of a running configuration file, or the change time (in change audit), indicate the
time at which RME system archived the configuration file.
This is not the time at which the configuration actually changed on the device. If changes are detected
immediately using Syslog messages, the timestamp should be very close to the actual configuration
change time on the device.
Startup configurations are handled differently by RME. Startup configs are simply saved into the system,
as they are retrieved from the device (unlike running configurations, which are compared and saved in
versioned archives, if different).
The timestamps of Startup Configuration files are just the archival times, and do not indicate the change
time.
In the version summary reports, the Running and Startup are links, which when clicked will retrieve in
real time, the respective configuration from the device. This column does not have a timestamp
associated with it.
In the Out-Of-Sync report, the Startup configuration column indicates the last archived startup
configuration along with its timestamp, and the Running configuration column indicate the last archived
running config along with its timestamp.
How Running Configuration is Archived
The workflow for archiving the Running configuration is:
1. If RME detects an effective change, the new configuration is queued for Archival.
2. The archiver, calculates the exact effective changes, assigns a new version number for the newly
collected archive, and archives it in the system.
3. The archiver, at the end, logs a change audit record that the configuration of the device has changed,
along with other Audit information.