[nsp] Suggestions on Versioning Control

[Adam Debus]

We use RANCID (http://www.shrubbery.net/rancid/), which works very well for
us.

Thanks,

Adam Debus
Network Engineer, ReachONE Internet
adam at reachone.com
----- Original Message ----- 
From: "Joel M Snyder" <Joel.Snyder at Opus1.COM>
To: <cisco-nsp at puck.nether.net>
Sent: Tuesday, November 18, 2003 9:43 AM
Subject: [nsp] Suggestions on Versioning Control


>
> > Does anyone have any good suggestions on a system for versioning for
> > config files? I don't particularly see anything that cisco can do to
> > make it work, but i think maybe some custom perl scripts + cvs might
> > work pretty well, but I wish I could have it track every change rather
> > than daily changes. Any ideas?
>
> I'm surprised that no one has mentioned CiscoWorks.  It does a pile of
> stuff, most of which we ignore, but it also handles this task very very
> well.  It sucks down configs periodically all on its own, plus it
> listens to your SYSLOGs and pulls configs whenever someone changes them.
>   It's good at watching uptime and general system health.
>
> There are a bunch of other features, like the ability to execute
> configuration commands on a bunch of devices simultaneously (want to
> change your NTP server everywhere...).
>
> They have Unix (Solaris, I think) and Windows versions, and we run it on
> a retarded Windows box which is too small to be marketable to customers.
>
> One of the nice things about it is a blame feature: you can see who made
> what diffs, assuming you hand out usernames, and then see who to blame
> when something breaks.
>
> I strongly recommend it.
>
> jms
>
> -- 
> Joel M Snyder, 1404 East Lind Road, Tucson, AZ, 85719
> Phone: +1 520 324 0494 (voice)  +1 520 324 0495 (FAX)
> jms at Opus1.COM    http://www.opus1.com/jms    Opus One
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>