A network administrator submits a Request for Change (RFC) to perform a major firmware upgrade on the central distribution switches servicing a corporate office. The submission details the business justification, target maintenance window, affected VLANs, and post-installation validation tests. However, the Change Advisory Board (CAB) rejects the RFC during review. Which of the following critical components was most likely missing from the RFC submission?
- A comprehensive rollback plan specifying exact steps and triggers to revert to the previous software version if validation failsAnswer
- BA plan to implement alternative fixes on production switches before establishing a probable cause for potential issues
- CA directive to downgrade switch management interfaces to unencrypted SNMPv2c for monitoring during the upgrade
- DA configuration change to update connected client default gateways from the HSRP virtual IP to physical interface IPs
Answer
A comprehensive rollback plan specifying exact steps and triggers to revert to the previous software version if validation fails
A formal Request for Change (RFC) submitted to a Change Advisory Board (CAB) must contain a documented rollback (backout) plan. This plan outlines explicit steps, backout time windows, and threshold triggers for reverting network devices to their baseline configuration and software version if post-change validation fails.
Step-by-Step Solution
Key Concept
Essential elements of a Request for Change (RFC) and Rollback Planning