Automated Configuration Backup

Any change made to the device configuration in a network carries the possibility of an error. An erroneous

configuration change

can cause network issues ranging from performance degradation to network outage. This is particularly true for those network devices that are crucial for the infrastructure. Any change in such devices should be detected and the

configuration file

of the device has to be backed up.
Such provision of

automated configuration backup

enables

change detection

and triggers configuration backup. Network Configuration Manager detects the changes through the syslog messages received from the devices.
  • Syslog based change detection
  • Automated configuration backup
  • Enable change detection
Here's how

automated configuration backup

works in Network Configuration Manager:
  • When an admin, operator or user logs in and out of a network device, the device generates a syslog message.
  • These syslog messages reach the built-in syslog server in NCM which looks out for the 'log out' message.
  • Upon receiving a log out message, NCM triggers the configuration backup of that network device. This is because whenever someone logs out of a device, there is a possibility that person has made a change in the config file of that device.
  • This backed up

    configuration file

    is then compared to the latest config version of that device in NCM and is checked for any new changes.
  • If any change is detected, the backed up

    configuration file

    is encrypted and stored in NCM's database.
  • If no change is detected, the backed up file is discarded.