Table of Contents
Advertisement
Scope
Any proposed change should include a complete technical definition, and the intent or purpose
of the change. The change should also include information that describes what business units,
user groups, servers, and applications might be affected, both during the change period and
after deployment. Generally, most changes fall into one of the following categories:
Network expansion
Addition of LAN segments at existing sites
Addition of new sites
Connection to existing networks
Connection to the Internet
Corporate mergers and acquisitions
Design and feature enhancements
Software release upgrade
Host software
Distributed client software
Configuration changes
Support for additional protocol(s)
Implementation of enhanced features
Risk assessment
Every network change has an associated risk level that can be assessed by modeling the
change in a laboratory environment or with a network modeling tool. It might be helpful to assign
one of the following risk categories to each change request:
High risk. These network changes have the highest impact on user groups or particular
environments, and might affect an entire site. Backing out of the change can be time
consuming and difficult. Research high-risk changes using the available tools, and
implement the change in conjunction with Avaya Services personnel. Ensure that
management is aware of the change and its implications, and notify all users.
Moderate-risk. These network changes can have a critical impact on user environments
or affect an entire site, but backing out of the change is a reasonably attainable scenario.
You should research moderate-risk changes the Avaya Support Centre Web site, and
possibly review the change with Avaya Services personnel. Avaya recommends notifying
all users of a moderate-risk change.
High-Level process flow
Issue 3.4.1 June 2005
373
Advertisement
Table of Contents
