Archive is a way to store multiple copies of the config in a sequential fashion and roll back configs if needed to a previous version. Use Cisco's Archive functionality for configuration management. So the command used in the scheduler is show run | redirect tftp://$SERVERIP/$PATH/$FILE (Unless you've turned off file prompt confirmation, however I don't recommend it as a normal setting.) Redirecting does not require confirmation. As you pointed out, copy run tftp requires file prompt confirmation. This will allow you to execute predefined commands on a scheduled basis. Use Cisco's Kron functionality for command scheduling. (Especially in GNS3.) The below options are available to you for automating confirguation backup, however I would not recommend doing so every 1 minute. Some older devices/IOS loads will have different capabilities.)ĮDIT: You are asking about doing this every one minute, which as you found out in our chat about this question, will bog down your router. (Which one you use depends on your needs and sometimes on the device and IOS load.
You could also use a hardcoded name within the configuration, the solution above probably better.You have several options to get this type of functionality on a Cisco device. $currentFile = ::Format("D:\prtg\router-config-backups\",$backupFileName) $date = (Get-Date -Format "ddMMyyyy-HH.mm.ss")
Make sure that the sensor name matches the configuration file:
For every configuration, create a file sensor that triggers upon file content changes.Make sure it points to your PRTG server:Ĭopy system:running-config tftp:/directory]/filename] Setup kron to execute the following command.Install a TFTP server on your PRTG server and configure it accordingly.It should be even easier, since you can use kron on the Cisco appliance to run commands on a schedule. Cacti and Nagios are both using plugins and it's the same way for PRTG.
0 kommentar(er)
