This document describes factors that should be considered when IP addresses are changed for an entire Cisco Intelligent Contact Management (ICM) network.
A. When IP addresses are changed for the entire Cisco ICM network, consider the following:
Network Modification
Change the IP address of the network router interface if the IP address change affects the network or the subnet part. This new IP address serves as the default gateway for all of the ICM computers on the same subnet.
If the Domain Name Server (DNS) is part of the name resolve process, replace the old IP addresses of all the ICM servers with the new IP addresses in the DNS database.
Peripheral Configuration Modification
Review all of the peripheral configurations to see if there are any hardcoded IP addresses that refer to the affected ICM servers.
ICM Modification
Change the IP address of each NIC on the ICM server. See How to Change the IP Address of One or More Cisco ICM NT Servers for the procedure.
Reboot the ICM server, and stop all ICM services.
Use ping and tracert to verify all ICM servers communicate with each other.
Verify that all peripherals can reach its partner ICM server.
Log on to the Primary Domain Controller (PDC), LoggerA.
Modify both the hosts and lmhosts file with the new IP addresses on the LoggerA.
Run sendall.bat command from the LoggerA. See How to Update ICM Node Host Files Using the Sendall.bat Command for the procedure.
Run setup on all the ICM servers and replace all the hardcoded IP addresses with the new IP addresses.
Start all ICM services in the following order:
LoggerA
CallRouterA
CallRouterB
LoggerB
All the other ICM servers
From an ICM function point of view, use the appropriate tools, such as rttest, opctest, to verify all ICM servers run properly.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
25-Oct-2005 |
Initial Release |