Change management policy

All network managers are managing changes in their organization all the time. People come and go, access and security details change, and new hardware and software is being installed on a frequent basis. Most of us manage change on an ad hoc basis, perhaps documenting changes as we go – definitely not a best practice approach. It is better to create a set of policies and procedures that formalize change into a process that can be managed. Software that offers automated solutions for managing change in your organization often include the following features:

• Device discovery, enumeration, and documentation
• Inventory management
• A historical log of all changes made to your network and network devices
• Policy creation and management engine that controls who can make changes, when those changes can be made, and the rate of change.
• Software licensing

Your planning process should create a set of results and effects of any change along with an assessment of the risks involved. Risk mitigation is an important part of the change management methodology. You should also have a plan in place to roll back any change should the result not be what you wanted. For example, you should have a copy of your router tables in case they get corrupted in an upgrade. This methodology should also evaluate the level of benefi...

Digg This!     StumbleUpon     Del.icio.us

VIEW ALL IN THIS CATEGORY

RELATED CONTENT Network Management Common network errors and causes Network monitoring -- Best practices Networking Products of the Year 2004 Configuring HSRP and VRRP on Cisco routers Dust Auto-MDIX In search of... an affordable management platform The best of 2004 Network administrator documentation Reducing file sizes to save the network Network Management Green enterprise: Three networking investments that make a difference Distributed network management means no more hard NOCs Green data center networks: Smarter architecture, not expensive devices Internal cloud computing on the cheap: Free automated provisioning? With virtual OS and virtual applications, who needs virtual machines? Application switch testing: An easy RFP guide Virtualization: The next generation of application delivery challenges Improving the performance of Web traffic and application delivery The link between network management and application delivery How to align network usage information to business processes Network Performance Management Web gateway helps Texas manufacturer develop network user management Desktop virtualization network challenges: A primer Green enterprise: Three networking investments that make a difference Storage area networks change management primer CA-NetQoS deal: Network management = application performance Virtualization change and configuration management primer Network change and configuration management primer Distributed network management means no more hard NOCs WLAN QoS and SLA monitoring with 7/24 Wireless Quality Assurance costs Network management from a service-based perspective

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary baseboard management controller  (SearchNetworking.com) fault management  (SearchNetworking.com) loose coupling  (SearchNetworking.com) maximum segment size  (SearchNetworking.com) maximum transmission unit  (SearchNetworking.com) network coding  (SearchNetworking.com) packet loss  (SearchNetworking.com) phase-change cooling  (SearchNetworking.com) round-trip time  (SearchNetworking.com) throttled data transfer  (SearchNetworking.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

t achieved; reducing high-risk low benefit changes while stressing low risk high benefit ones. The principle goal is to avoid risk, and mitigate recovery.

Your management policy should include a protocol for all administrators to follow. Depending upon your management structure you may want to have each major change documented and approved by a senior technical manager/and or business manager; and emergency changes should be signed off on by a couple of senior managers. Minor changes might only require a more junior level permission, and -- for certain operations -- a system for simply documenting the change may be sufficient.

Here are three resources for you to read to learn more about change management:

• The University of Kentucky's Change Control FAQ.
• Cisco System's white paper.
• Alterpoint's RealTime Publishing's eBook.

Barrie Sosinsky is president of consulting company Sosinsky and Associates (Medfield MA). He has written extensively on a variety of computer topics. His company specializes in custom software (database and Web related), training and technical documentation.