[c-nsp] Network Change Management

[Mark Meijerink]

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  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20100817/608a12af/attachment.bin>