Write a change request
Plan a real change, such as a router firmware update, through a proper change management process: impact analysis, test plan, backout plan and maintenance window.
Environment
A document or spreadsheet.
Before you start
- Read Change Management Programs (p.385), Change Management Concepts (p.386) and Restarts, Dependencies, and Downtime (p.388).
You will
- Complete a change request
- Identify dependencies and downtime
- Write a backout plan
Steps
-
1
Pick a change: updating your router firmware, or upgrading your laptop's operating system.
-
2
Fill in: requester, owner, description, reason, and change type (standard, normal or emergency).
-
3
Impact analysis: which devices, services and people are affected, and for how long? What depends on this device?
-
4
Test plan: how will you confirm it worked (internet access, Wi-Fi settings kept, VPN still working)?
-
5
Backout plan: how you'll roll back if it fails (keep the old firmware file, export the current configuration first).
-
6
Choose a maintenance window when nobody needs the network, and note who must approve.
-
7
After the change, update your documentation and inventory, as in the version control section on p.390.
Check your understanding
- ?Why is a backout plan required before approval rather than after a failure?
- ?Which changes might be 'standard' (pre-approved)?
- ?What documentation should you update afterwards?