On Fri, 14 Jan 2005, Brian Feeny wrote:
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.
Where I worked before, large service-affecting changes (code upgrade on
routers/switches, circuit re-grooms and the like) were discussed in a
semi-weekly change management meeting. The change was approved or not
approved by management and normally the engineer who scheduled the change
was the one who did the change. The standard maintenance window was 1 to
5 AM regardless of the day.
Smaller changes like new customer circuit turn-ups, static routes,
customer BGP changes, etc could be done on the fly in many cases.
As for the software, we has a homegrown app we wrote in PHP originally,
then the change management functionality was rolled into our existing
trouble ticket/case management system.
jms
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.
Thanks,
Brian
------------------------------------------------------------------------
------
Brian Feeny, CCIE #8036, CISSP e: sig...@shreve.net
Network Engineer p: 318.213.4709
ShreveNet Inc. f: 318.221.6612
5 messages in net.nether.puck.cisco-nsp[c-nsp] Change Management
