Table of Contents
Advertisement
Target system name and location
User group contact (if available)
Lab tested (yes or no)
Description of how the change was tested
Test plan
Backout plan
If successful, will the change migrate to other locations (yes or no)
Prerequisites of other changes to make this change successful
The technical description of the change is an important aspect of the change request, and may
include the following: current topology and configuration, physical rack layouts, hardware and
hardware modules, software versions, software configuration, cabling requirements, logical
maps with device connectivity or VLAN connectivity, port assignments and addressing, device
naming and labeling, DNS update requirements, circuit identifiers and assignments, network
management update requirements, out-of-band management requirements, solution security,
and change procedures.
In addition, a change request should reference any standards within your organization that
apply to the change. This helps to ensure that the change conforms to current architecture or
engineering design guidelines or constraints. Standards can include the following: device and
interface naming conventions, DNS update requirements, IP addressing requirements, global
standard configuration files, labeling conventions, interface description conventions, design
guidelines, standard software versions, supported hardware and modules, network
management update requirements, out-of-band management requirements, and security
requirements.
Change controller
A key element to the change process is the change controller. The change controller is usually
an individual within your IT organization who acts as a coordinator for all change process
details. Normal job functions of the change controller include:
Accepting and reviewing all change requests for completeness and accuracy
Running periodic (weekly or biweekly) change review meetings with change review board
personnel
Presenting complete change requests to the change review board for business impact,
priority, and change readiness review
Preventing potential conflict by maintaining a change schedule or calendar
High-Level process flow
Issue 3.4.1 June 2005
377
Advertisement
Table of Contents
