[j-nsp] Config archive subtleties

[Jensen Tyler]

RANCID? - http://www.shrubbery.net/rancid/

Works for us and you can monitor multiple vendors gear.

Jensen Tyler
Sr Engineering Manager
Fiberutilities Group, LLC

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.



-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Phil Mayers
Sent: Wednesday, August 07, 2013 11:03 AM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] Config archive subtleties

All,

For several years, we've used "system archival configuration" in "on-commit" mode, to backup each commit to a separate file on an sftp/scp server, then check them individually into subversion.

Recently this fell apart on us, as the SSH key on the server changed and the archival transfers started to silently[1] fail.

While trying to write a nagios check for outstanding archive transfers, I then discovered that in some circumstances, the archival config will give up and discard a file - I had assumed it would queue them forever, but apparently not in some cases (e.g. 3 successive failures with bad username/password).

All of which has me wondering if the feature is more trouble than it's worth.

What do other people do? It seems like it would be a nice feature to preserve the commits and so forth, but if it's not robust, maybe it's just misleading.

Cheers,
Phil

[1] It did log en entry into /var/log/messages, but TBH JunOS logs so much crap there, we don't do anything with those logs...
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp