Maybe you want a system that enforces configuration workflow, such as LMS. There, you can comment each work order with *why* this is to be done. You have to enforce to have this documented before the changes are done, otherwise the operators will fail to comment ex-post, with increasing probability over time :)
-- deejay > -----Original Message----- > From: [email protected] [mailto:cisco-nsp- > [email protected]] On Behalf Of Jeff Wojciechowski > Sent: Tuesday, August 17, 2010 4:18 PM > To: [email protected] > Subject: [c-nsp] Network Change Management > > 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. > > Can anyone out there make recommendations on what change management > tools they use or have used that might fit this bill? > > We are open to either open source or something modestly priced. > > Thanks, > > Jeff Wojciechowski > LAN, WAN and Telephony Administrator > Midland Paper Company > 101 E Palatine Rd > Wheeling, IL 60090 > * tel: 847.777.2829 > * fax: 847.403.6829 > e-mail: > [email protected]<mailto:jeff.wojciechow...@midlandpap > er.com> > http://www.midlandpaper.com > > > > > ________________________________ > 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. > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
