Jeff, We need to clean up and scrub the source code a bit before we put it online. We will work on this and let you know where to download it.
Regards, Mark On 8/18/2010 3:13 PM, Jeff Wojciechowski wrote: > Thanks all! > > -Jeff > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Mark Meijerink > Sent: Tuesday, August 17, 2010 11:13 AM > Cc: [email protected] > Subject: Re: [c-nsp] Network Change Management > > We have written an PHP page for running rancid for a certain device and > adding CVS comments just like John noted in the e-mail before. By using this > method you can make your configuration changes and afterwards run rancid and > add comments to the config changes. This should help with adding the why > factor to the configuration changes. > > Regards, > Mark > > On 8/17/2010 5:51 PM, john heasley wrote: >> Tue, Aug 17, 2010 at 09:18:28AM -0500, Jeff Wojciechowski: >>> All: >>> >>> I know there are tools out there like RANCID that help manage configuration >>> changes but we want something that will be able to be able to have a system >>> that will not only be able to document what changes were made, but to also >>> document why. >> >> not the most efficient method and requires discipline, but one could >> annotate the CVS or SVN versions (cvs admin -m rev:msg file or >> svnadmin setlog -r rev file) generated by rancid SCM commits for >> documentation. >> you can also tag or branch to create named sets, such as replace_foundry. >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > This electronic mail (including any attachments) may contain information that > is privileged, confidential, or otherwise protected from disclosure to anyone > other than its intended recipient(s). Any dissemination or use of this > electronic mail or its contents (including any attachments) by persons other > than the intended recipient(s) is strictly prohibited. If you have received > this message in error, please delete the original message in its entirety > (including any attachments) and notify us immediately by reply email so that > we may correct our internal records. Midland Paper Company accepts no > responsibility for any loss or damage from use of this electronic mail, > including any damage resulting from a computer virus.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
