HOWEVER, if you don't want your configurations on the wire in the clear, where a sniffer could snag them, they will need to be encrypted. Although Cisco::CopyConfig can use SNMPv3, which is encrypted if you specify a privacy option, it uses TFTP to transfer the configuration to the backup server. TFTP is never encrypted.
Many people instead take backups of their Ciscos through SSH, using the Rancid package to keep CVS archives. The archives let you see the changes made to your configs, and you can use something like cvsweb to provide a (heavily secured) web site to browse the archives.
The distributed version of rancid does a "show running-config" which doesn't work properly for accounts with limited privileges. This Cisco technical note describes the problem. However, it is trivial to patch Rancid's source code to do an "enable 5" and then a "show startup-config" instead. Then rancid's login only needs enough privilege to do the show startup-config command, which can be set up on the router with "privilege exec level 5 show startup-config".
In reply to Re: Backups Cisco Router with Net::SNMP in PERL
by quester
in thread Backups Cisco Router with Net::SNMP in PERL
by TELCO
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |