Community change administration is a course of that goals to cut back the danger of a failed change. This course of entails a number of steps that guarantee profitable adjustments.
Plane pilots use well-defined processes to make sure protected flying. Equally, community groups can use outlined processes to cut back the danger of failed community adjustments that create unplanned outages. Nonetheless, organizations typically discover that adjustments do not go as deliberate, resulting in community outages. Some disruptions are because of a course of failure, whereas others consequence from unintended penalties of complicated configurations.
This text discusses the fundamental working ideas of community change administration, akin to the next:
- Scope dedication and danger evaluation.
- Peer evaluate.
- Pre-deployment testing and validation.
- Implementation and testing.
- Documentation updates.
Earlier than coming into the change administration course of, community groups should set up the change particulars, akin to new configurations, system connection info and documentation.
1. Scope and danger evaluation
Step one within the community change administration course of is to guage the scope of a proposed change. Decide which providers is likely to be affected and the stakeholders who use these providers. Contemplate the blast radius of a change for its potential scope and impact, together with any attainable unfavorable outcomes.
Groups ought to measure the scope by way of the next two elements:
- The variety of endpoints affected by a change.
- The significance of the providers a change may have an effect on.
As soon as groups determine the scope, they need to carry out a danger evaluation of the change. Is it one thing that has been accomplished many occasions earlier than and is nicely understood? Is it absolutely automated, or is it attainable that human error will alter the change in an surprising method? Is the expertise concerned nicely understood, or is there an opportunity of one thing surprising occurring?
The scope of a change figures into the danger. A change to the infrastructure on which key enterprise processes run poses a larger danger to the enterprise than a change to a small department website.
Community groups can assess danger by assigning values to key parameters. By averaging the values from the next instance parameters, they’ll decide the general danger degree.
The larger the danger, the extra cautious groups must be through the the rest of the change administration course of. Groups ought to have clear change management documentation in place, detailing the rationale for any adjustments, rollback procedures and scope.
2. Peer evaluate
The following step is to conduct a peer evaluate. Groups can carry out this step earlier than the danger evaluation, however it’s higher to make use of the danger degree to drive the thoroughness of a peer evaluate. Whereas all peer critiques must be comparably thorough, it is possible that groups conduct cursory critiques for routine adjustments, akin to entry management checklist adjustments or digital LAN modifications. Automated testing and deployment of routine adjustments can assist mitigate the danger of cursory peer critiques.
Sometimes, inner workers who’re accustomed to the community conduct the peer critiques. If a change is out of the unusual, nevertheless, it is smart to have an professional from the tools vendor carry out the evaluate. Findings from the critiques ought to feed again to the danger evaluation part and replace the technical danger measurements.
Peer reviewers ought to look at a number of elements throughout a evaluate, together with the next:
- Configuration scripts.
- {Hardware} and software program compatibility.
- Rollback procedures.
- Change rationale.
- Enterprise wants.
- Community safety and compliance.
- Templates and documentation.
3. Pre-deployment testing and validation
Ideally, all adjustments undergo a pre-deployment testing and validation part. Contemplate automating low-risk, repetitive duties and adjustments to take away the temptation to skip testing for adjustments that groups understand as low danger. The larger the scope and danger, the extra vital it’s to correctly take a look at and validate the proposed change.
The prevalence of digital router and swap OS situations makes it simpler to automate the creation of take a look at community topologies with out costly {hardware} investments. Use community labs and sandboxes to construct automation workflows inside a digital community topology that groups can tear down after the assessments are efficiently accomplished.
Pre-deployment testing consists of a number of steps groups ought to comply with to guage a proposed change:
- Confirm that the take a look at community works as meant previous to the change.
- Implement the change in a take a look at infrastructure to verify that the change ends in the specified closing state. Groups ought to use automated processes to keep away from human error and cut back the time to validate the change. If validation within the take a look at setting fails, decide the explanation. Did it fail as a result of the change was incorrect, or was it as a result of the take a look at community did not precisely symbolize the actual community?
- Take a look at the backout change course of so it is simple to revert to the earlier state if one thing goes incorrect. The rollback ought to return the community to the beginning state, which groups can validate by repeating Step 1.
4. Implementation and testing
Deployment and post-deployment testing and validation ought to comply with Steps 1 and a pair of of pre-deployment testing. If groups have accomplished a great job of pre-deployment testing and validation, nothing surprising ought to occur. If post-change testing detects an surprising drawback, groups ought to again out the change and confirm service restoration.
Some community protocols take longer to converge after adjustments to giant networks. As such, post-change verification ought to incorporate delays or convergence assessments, which pre-deployment testing in a small take a look at setting would not want.
Many organizations automate community configuration adjustments emigrate to a DevOps tradition primarily based on infrastructure as code. The target is to undertake a steady integration/steady supply course of for low-risk adjustments.
5. Documentation and community administration updates
Ideally, groups create and replace paperwork through the change creation course of, enabling them to evaluate the documentation and community administration adjustments together with particulars of the change. As soon as groups have carried out and verified the change, they’ll incorporate the documentation adjustments right into a community documentation system.
Groups also needs to replace the community administration system as wanted. Most community administration techniques have APIs that allow automated processes to make the adjustments.
If the change validation step is automated, it may be included into periodic community validation checks. These periodic checks can detect failures in extremely redundant and resilient networks. Over time, groups construct a library of community validation checks that cowl many elements of the community.
The ideas of fine community change administration present steering to cut back unplanned community outages because of failed adjustments. Groups ought to create a course of that works for his or her group and work towards making that course of extremely environment friendly.
Editor’s be aware: This text was initially written by Terry Slattery and up to date by Informa TechTarget editors to enhance the reader expertise.
Terry Slattery is an impartial guide who makes a speciality of community administration and community automation. He based Netcordia and invented NetMRI, a community evaluation equipment that gives visibility into the problems and complexity of contemporary router- and switch-based IP networks.
