5 messages in net.nether.puck.cisco-nsp[c-nsp] Change Management
FromSent OnAttachments
Brian FeenyJan 14, 2005 3:35 pm 
John NeibergerJan 14, 2005 3:48 pm 
Justin M. StreinerJan 14, 2005 4:14 pm 
Serge VondandamoJan 15, 2005 1:20 am 
Michael MarkstallerJan 17, 2005 11:47 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] Change ManagementActions...
From:John Neiberger (John@efirstbank.com)
Date:Jan 14, 2005 3:48:54 pm
List:net.nether.puck.cisco-nsp

Brian Feeny <sig@shreve.net> 1/14/05 1:36:55 PM >>>

Can some of you all share how you handle Change Management on your networks? Everything from serious changes to something mundane like changing a

customer IP address.

I would hope there is some good open source tools for this purpose.

BTW, we already use "configuration management" tools like RANCID, but I am needing something that people can use to log a change, who did it, why, when, etc, so its accounted for BEFORE it happens.

I'm interested in this, as well. We use Device Authority for configuration management but our change control process is a bit...er...manual, i.e. fill out request form, sign it, hand it to manager for approval, get form back from manager, make changes, sign form, give form to someone else for verification, they sign the form...you know how it goes. It works but it's sluggish and I'd prefer a more streamlined approach.

John