Change control
380 Avaya Application Solutions IP Telephony Deployment Guide
Test evaluation of change
Testing and verification can be critical to a successful change. You should identify testing steps
after defined change checkpoints and final change completion. In addition, allocate sufficient
time for testing, both during and following the implementation and backout, if necessary. In
some cases, you can do testing prior to the change when new service is involved, such as new
circuits or links that are not currently in production. The following additional testing and
verification procedures may be pertinent to a network change:
●
Extended pings for connectivity and performance (may require many to many)
●
Traceroutes
●
End-user station network and application testing
●
Test calls or traffic generation for performance-related changes
●
Bit error rate tester (BERT) for new circuits
●
Display errors
●
Log file verification
●
List trace verification
●
Display or status command verification
●
Network management station availability and verification
After achieving some level of comfort with the change, evaluate what was accomplished:
●
Does the change make sense?
●
Did the change address the network problem?
●
What should be done differently the next time that a change is warranted?
Network management update
Operational readiness requires that you update all network management tools, device
configuration, and DNS to reflect the change. Your organization might also have tools for fault
management, configuration management, availability measurement, inventory management,
billing, and security that require updates. The following are some typical network management
update requirements following change:
●
Removal of DNS entries and network management system (NMS) management for
devices that were removed from the network.
●
Standard SNMP configuration entered on devices, including community string, location,
support contact, syslog server, trap server, and SNMP server host.
●
Trap source, syslog source, and SNMP source configured for loopback.
Summary of Contents for Application Solutions
Page 1: ...Avaya Application Solutions IP Telephony Deployment Guide 555 245 600 Issue 3 4 1 June 2005 ...
Page 20: ...About This Book 20 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 21: ...Issue 3 4 1 June 2005 21 Section 1 Avaya Application Solutions product guide ...
Page 22: ...22 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 106: ...Call processing 106 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 124: ...Avaya LAN switching products 124 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 139: ...Issue 3 4 1 June 2005 139 Section 2 Deploying IP Telephony ...
Page 140: ...140 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 186: ...Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 204: ...Security 204 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 228: ...Avaya Integrated Management 228 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 274: ...Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 275: ...Issue 3 4 1 June 2005 275 Section 3 Getting the IP network ready for telephony ...
Page 276: ...276 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 356: ...Network recovery 356 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 366: ...Network assessment offer 366 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 367: ...Issue 3 4 1 June 2005 367 Appendixes ...
Page 368: ...Appendixes 368 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 394: ...Access list 394 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 414: ...DHCP TFTP 414 Avaya Application Solutions IP Telephony Deployment Guide ...