Table Of Contents
Changing the IP Address for Cisco Unified Communications Manager 5.x and 6.x Servers
Readiness Checklist
Changing the Cluster IP Addresses for Servers That Are Identified by IP Addresses
Changing the Cluster IP Addresses for Subscriber Servers That Are Identified by IP Addresses
Changing the Cluster IP Address for the Publisher Server That Is Identified by IP Address
Changing the Cluster IP Addresses for Servers That Are Identified by Host Names
Changing the Cluster IP Addresses for Subscriber Servers That Are Identified by Hostname
Changing the Cluster IP Addresses for Publisher Servers That Are Identified by Hostname
Post-Change Task List
Obtaining Documentation, Obtaining Support, and Security Guidelines
Changing the IP Address for Cisco Unified Communications Manager 5.x and 6.x Servers
This document provides the steps to change the IP address on a Cisco Unified Communications Manager server. You may want to change this IP address for a variety of reasons, including moving the server from one segment to another or resolving a duplicate IP address problem.
This document contains the following main sections:
•
Readiness Checklist
•Changing the Cluster IP Addresses for Servers That Are Identified by IP Addresses
•Changing the Cluster IP Addresses for Servers That Are Identified by Host Names
•Post-Change Task List
•Obtaining Documentation, Obtaining Support, and Security Guidelines
Readiness Checklist
Perform the following tasks to ensure that your system is prepared for a successful IP address change.
Procedure
Step 1 List all servers in the cluster and note whether the nodes are defined by using IP addresses or host names.
•From Cisco Unified Communications Manager Administration on the first node, navigate to System > Server and click Find. A list of all servers in the cluster displays.
•Capture this list of servers for later reference.
Step 2 Ensure that you have saved an inventory of both the host name and IP address of each node in your cluster.
Step 3 Ensure that all servers in the cluster are up and available by checking for any active ServerDown alerts. You can check by using either the Real Time Monitoring Tool (RTMT) or the Command Line Interface (CLI) on the first node.
•To check by using RTMT, access Alert Central and check for ServerDown alerts.
•To check by using the CLI on the first node, enter one of the following commands and inspect the application event log:
–For Cisco Unified Communications Manager 5.x systems
file search activelog syslog/CallManager ServerDown
–For Cisco Unified Communications Manager 6.x systems
file search activelog syslog/CiscoSyslog ServerDown
Note For Cisco Unified Communications Manager 5.1(3) and 6.1(1), you can check status of all servers by generating the Cisco Unified CM Cluster Overview report in Cisco Unified Reporting.
Step 4 Check the DB replication status on all the Cisco Unified Communications Manager nodes in the cluster to ensure that all servers are replicating database changes successfully. You can check by using either RTMT or a CLI command.
•To check by using RTMT, access the Database Summary and inspect the replication status.
•To check by using the CLI, enter the command that is shown in the following example:
admin: show perf query class "Number of Replicates Created and State of Replication"
- Perf class (Number of Replicates Created and State of Replication)
has instances and values:
ReplicateCount -> Number of Replicates Created = 344
ReplicateCount -> Replicate_State = 2
Be aware that the Replicate_State object shows a value of 2 in this case. The following list shows the possible values for Replicate_State:
–0—Replication Not Started. Either no subscribers exist, or the Database Layer Monitor service is not running and has not been running since the subscriber was installed.
–1—Replicates have been created, but their count is incorrect.
–2—Replication is good.
–3—Replication is bad in the cluster.
–4—Replication setup did not succeed.
Step 5 Run a manual DRS backup and ensure that all nodes and active services get backed up successfully. For more information, refer the Disaster Recovery System Administration Guide for your release.
Step 6 For security-enabled clusters (Cluster Security Mode 1 - Mixed), update the Certificate Trust List (CTL) file.
Note All IP phones that support security always download the CTL file, which includes the IP address of the TFTP servers with which the phones are allowed to communicate. If you change the IP address of one or more TFTP servers, you must first add the new IP addresses to the CTL file first, so the phones can communicate with their TFTP server.
Caution To avoid unnecessary delays, you must update the CTL file with the new IP address of your TFTP servers before you change the IP address of the TFTP servers. If you do not perform this step, you will have to update all secure IP phones manually.
For detailed instructions on updating and managing the CTL file, including adding a new TFTP server to an existing CTL file, refer to one of the following documents:
•For 5.x releases, refer to the Cisco Unified CallManager Release 5.1(1) New and Changed Information Guide.
•For 6.x releases, refer to the Cisco Unified Communications Manager Security Guide Release 6.1(1).
You can find both documents at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Changing the Cluster IP Addresses for Servers That Are Identified by IP Addresses
This section describes how to change the cluster IP addresses for servers that are identified by IP addresses. For information about changing cluster IP addresses for servers that are identified by host names, see the "Changing the Cluster IP Addresses for Servers That Are Identified by Host Names" section.
Caution Changing the IP address on any node in a Cisco Unified Communications Manager cluster can interrupt call processing and other system functions. Also, changing the IP address can cause the system to generate certain alarms and alerts, such as ServerDown and SDLLinkOSS, and automatic failover to a backup server may not operate. Because of this potential impact to the system, you must perform IP address changes during a planned maintenance window.
This section contains the following procedures:
•Changing the Cluster IP Addresses for Subscriber Servers That Are Identified by IP Addresses
•Changing the Cluster IP Address for the Publisher Server That Is Identified by IP Address
Changing the Cluster IP Addresses for Subscriber Servers That Are Identified by IP Addresses
Use this procedure to change the IP address of a a subscriber server if your cluster servers are identified by IP address.
Procedure
Step 1 From the Cisco Unified Communications Manager Administration window, perform the following tasks:
a. Navigate to System > Server.
b. Change the IP address of the subscriber server.
Step 2 Ensure that the IP address change is replicated to the subscriber server database by entering the CLI command run sql select name,nodeid from ProcessNode on all nodes in the cluster. The following example shows the command output:
admin: run sql select name,nodeid from ProcessNode
================== ======
Step 3 If you are moving the server to a different subnet that requires a new default gateway address, change the default gateway by using the set network gateway CLI command, as shown in the following example:
admin:set network gateway 10.3.90.2
This will cause the system to temporarily lose network connectivity
Do you want to continue ?
Enter "yes" to continue or any other key to abort
Step 4 Change the IP address of the subscriber server by performing the following tasks:
a. Enter the CLI command set network ip eth0 ip_address netmask
where ip_address specifies the new server IP address and netmask specifies the new server network mask.
The following output displays:
admin: set network ip eth0 10.3.90.21 255.255.254.0
If there are IP addresses (not hostnames)
configured in CallManager Administration
then you must change the IP address there BEFORE
changing it here or call processing will fail.
This will cause the system to restart
=======================================================
Note: To recognize the new IP address all nodes within
the cluster will have to be manually rebooted.
=======================================================
Enter "yes" to continue and restart or any other key to abort
b. Enter yes and press Enter.
Note You can also change the IP address of the default gateway and the server by using the Cisco Unified Communications Operating System. From Cisco Unified Communications Operating System Administration, choose Settings > IP > Ethernet.
Step 5 Reboot all other servers in the cluster, including the publisher node, to update the local name resolution files, such as hosts, rhosts, sqlhosts, and services.
Note These files get updated only during system startup, and the system needs to restart core network services, such as Cisco DB and Cisco Tomcat, after the files are updated. Restarting the servers ensures the proper update and service-restart sequence for the IP address changes to take effect.
Changing the Cluster IP Address for the Publisher Server That Is Identified by IP Address
Use this procedure to change the IP address of a a publisher server if your cluster servers are identified by IP address.
Procedure
Step 1 From the Cisco Unified Communications Manager Administration window, perform the following tasks:
a. Navigate to System > Server.
b. Change the IP address of the publisher server.
Step 2 Ensure that the IP address change is replicated to the subscriber server database by entering the CLI command run sql select name,nodeid from ProcessNode on all nodes in the cluster. The following example shows the command output:
admin: run sql select name,nodeid from ProcessNode
================== ======
Step 3 From the Cisco Unified Communications Operating SystemAdministration window (http://subscriber_ip_address/cmplatform) of each subscriber server in the cluster, perform the following tasks:
a. Navigate to Settings > IP > Publisher.
b. Change the IP address of the publisher server.
Step 4 If you are moving the server to a different subnet that requires a new default gateway address, change the default gateway by using the set network gateway CLI command, as shown in the following example:
admin:set network gateway 10.3.90.2
This will cause the system to temporarily lose network connectivity
Do you want to continue ?
Enter "yes" to continue or any other key to abort
Step 5 Change the IP address of the publisher server by using the CLI by performing the following tasks:
a. Enter the CLI command set network ip eth0 ip_address netmask
where ip_address specifies the new server IP address and netmask specifies the new server network mask.
The following output displays:
admin: set network ip eth0 10.3.90.21 255.255.254.0
If there are IP addresses (not hostnames)
configured in CallManager Administration
then you must change the IP address there BEFORE
changing it here or call processing will fail.
This will cause the system to restart
=======================================================
Note: To recognize the new IP address all nodes within
the cluster will have to be manually rebooted.
=======================================================
Enter "yes" to continue and restart or any other key to abort
b. Enter yes and press Enter.
Note You can also change the IP address of the default gateway and the server by using the Cisco Unified Communications Operating System. From Cisco Unified Communications Operating System Administration, choose Settings > IP > Ethernet.
Step 6 After the publisher server reboots automatically as a result of the set network ip command, reboot all subscriber servers to update the local name resolution files, such as hosts, rhosts, sqlhosts, and services.
Note These files get updated only during system startup, and the system needs to restart core network services, such as Cisco DB and Cisco Tomcat, after the files are updated. Restarting the servers ensures the proper update and service-restart sequence for the IP address changes to take effect.
Step 7 Run a manual DRS backup and ensure that all nodes and active services get backed up successfully. For more information, refer the Disaster Recovery System Administration Guide for your release.
Changing the Cluster IP Addresses for Servers That Are Identified by Host Names
This section describes how to change the cluster IP addresses for servers that are identified by host names. For information about changing cluster IP addresses for servers that are identified by IP address, see the "Changing the Cluster IP Addresses for Servers That Are Identified by IP Addresses" section.
Note Prior to Cisco Unified Communications Manager Release 6.1(2), you cannot change the host name of either the publisher node or subscriber node after it is installed. If you must apply a new host name to a server, you can delete the server from Cisco Unified Communications Manager Administration (System > Server) and then reinstall the server with a new hostname. Also, be aware that a DRS backup that you take from a server with a particular hostname cannot be restored on a server (either a publisher or subscriber node) with a different hostname, even after you reinstall that node.
This section contains the following procedures:
•Changing the Cluster IP Addresses for Subscriber Servers That Are Identified by Hostname
•Changing the Cluster IP Addresses for Publisher Servers That Are Identified by Hostname
Changing the Cluster IP Addresses for Subscriber Servers That Are Identified by Hostname
Use this procedure to change the IP address of a a subscriber server if your cluster servers are identified by hostname.
Procedure
Step 1 Change the DNS record of the subscriber server to point to the new IP address. Ensure that you correctly update both the forward (A) and reserve (PTR) records.
Step 2 Verify that the DNS change propagates to other nodes by using the utils network host CLI command on all the cluster nodes. Look for the External Resolution Results. Local Resolution update occurs after the nodes are rebooted. The following example shows running of this command:
admin: utils network host rdu-sub-1
rdu-sub-1.cisco.com resolves locally to 10.3.90.6
rdu-sub-1.cisco.com has address 10.3.90.21
Step 3 If you are moving the server to a different subnet that requires a new default gateway address, change the default gateway by using the set network gateway CLI command, as shown in the following example:
admin:set network gateway 10.3.90.2
This will cause the system to temporarily lose network connectivity
Do you want to continue ?
Enter "yes" to continue or any other key to abort
Step 4 Change the IP address of the subscriber server by performing the following tasks:
a. Enter the CLI command set network ip eth0 ip_address netmask
where ip_address specifies the new server IP address and netmask specifies the new server network mask.
The following output displays:
admin: set network ip eth0 10.3.90.21 255.255.254.0
If there are IP addresses (not hostnames)
configured in CallManager Administration
then you must change the IP address there BEFORE
changing it here or call processing will fail.
This will cause the system to restart
=======================================================
Note: To recognize the new IP address all nodes within
the cluster will have to be manually rebooted.
=======================================================
Enter "yes" to continue and restart or any other key to abort
b. Enter yes and press Enter.
Note You can also change the IP address of the default gateway and the server by using the Cisco Unified Communications Operating System. From Cisco Unified Communications Operating System Administration, choose Settings > IP > Ethernet.
Step 5 Reboot all other servers in the cluster, including the publisher server, to update the local name resolution files, such as hosts, rhosts, sqlhosts, and services.
Note These files only get updated during system startup, and you need to restart core network services, such as Cisco DB and Cisco Tomcat, after the files are updated. Restarting the servers ensures that the proper update and service-restart sequence for the IP address changes take effect.
Step 6 Ensure that local resolution of the subscriber server also resolves to the new IP address by using the utils network host CLI command. This example shows the command output:
admin: utils network host rdu-sub-1
rdu-sub-1.cisco.com resolves locally to 10.3.90.21
rdu-sub-1.cisco.com has address 10.3.90.21
Step 7 Run a manual DRS backup and ensure that all nodes and active services get backed up successfully. For more information, refer the Disaster Recovery System Administration Guide for your release.
Changing the Cluster IP Addresses for Publisher Servers That Are Identified by Hostname
Use this procedure to change the IP address of a publisher server if your servers are identified by hostname.
Procedure
Step 1 Change the DNS record of the subscriber server to point to the new IP address. Ensure that you correctly update both the forward (A) and reserve (PTR) records.
Step 2 Verify that the DNS changes propagate to other nodes by using the utils network host CLI command on all the cluster nodes. Look for the External Resolution Results. Local Resolution update occur after the nodes are rebooted. The following example shows running this command:
admin: utils network host rdu-sub-1
rdu-sub-1.cisco.com resolves locally to 10.3.90.6
rdu-sub-1.cisco.com has address 10.3.90.21
Step 3 From the Cisco Unified Communications Operating SystemAdministration window (http://subscriber_ip_address/cmplatform) of each subscriber server in the cluster, perform the following tasks:
a. Navigate to Settings > IP > Publisher.
b. Change the IP address of the publisher server.
Step 4 If you are moving the server to a different subnet that requires a new default gateway address, change the default gateway by using the set network gateway CLI command, as shown in the following example:
admin:set network gateway 10.3.90.2
This will cause the system to temporarily lose network connectivity
Do you want to continue ?
Enter "yes" to continue or any other key to abort
Step 5 Change the IP address of the publisher server by using the CLI by performing the following tasks:
a. Enter the CLI command set network ip eth0 ip_address netmask
where ip_address specifies the new server IP address and netmask specifies the new server network mask.
The following output displays:
admin: set network ip eth0 10.3.90.21 255.255.254.0
If there are IP addresses (not hostnames)
configured in CallManager Administration
then you must change the IP address there BEFORE
changing it here or call processing will fail.
This will cause the system to restart
=======================================================
Note: To recognize the new IP address all nodes within
the cluster will have to be manually rebooted.
=======================================================
Enter "yes" to continue and restart or any other key to abort
b. Enter Yes and press Enter.
Note You can also change the IP address of the default gateway and the server by using the Cisco Unified Communications Operating System. From Cisco Unified Communications Operating System Administration, choose Settings > IP > Ethernet.
Step 6 After the publisher server reboots automatically as a result of the set network ip command, reboot all subscriber servers to update the local name resolution files, such as hosts, rhosts, sqlhosts, and services.
Note These files only get updated during system startup, and you need to restart core network services, such as Cisco DB and Cisco Tomcat, after the files are updated. Restarting the servers ensures that the proper update and service-restart sequence for the IP address changes take effect.
Step 7 Ensure that local resolution of the subscriber node also resolves to the new IP address, as shown in this example:
admin: utils network host rdu-pub-1
rdu-pub-1.cisco.com resolves locally to 10.3.90.20
rdu-pub-1.cisco.com has address 10.3.90.20
Step 8 From the Cisco Unified Communications Manager Administration window, navigate to System > Enterprise Parameters.
Step 9 Under Phone URL Parameters, change all URLs that contain the old IP address to reflect the new IP address.
Step 10 Run a manual DRS backup and ensure that all nodes and active services get backed up successfully. For more information, refer the Disaster Recovery System Administration Guide for your release.
Post-Change Task List
After you finish changing the IP addresses of your cluster, complete the following tasks:
Procedure
Step 1 For security-enabled clusters (Cluster Security Mode 1 - Mixed), update the CTL file.
For detailed instructions on updating and managing the CTL file, including adding a new TFTP server to an existing CTL file, refer to one of the following documents:
•For 5.x releases, refer to the Cisco Unified CallManager Release 5.1(1) New and Changed Information Guide.
•For 6.x releases, refer to the Cisco Unified Communications Manager Security Guide Release 6.1(1).
You can find both documents at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
Step 2 After you finish updating the CTL file, restart all nodes in the cluster.
Step 3 Ensure that all servers in the cluster are up and available by checking for any active ServerDown alerts. You can check by using either the Real Time Monitoring Tool (RTMT) or the Command Line Interface (CLI) on the first node.
•To check by using RTMT, access Alert Central and check for ServerDown alerts.
•To check by using the CLI on the first node, enter one of the following commands and inspect the application event log:
–For Cisco Unified Communications Manager 5.x systems
file search activelog syslog/CallManager ServerDown
–For Cisco Unified Communications Manager 6.x systems
file search activelog syslog/CiscoSyslog ServerDown
Note For Cisco Unified Communications Manager 5.1(3) and 6.1(1), you can check status of all servers by generating the Cisco Unified CM Cluster Overview report in Cisco Unified Reporting.
Step 4 Check the DB replication status on all the Cisco Unified Communications Manager nodes in the cluster to ensure all servers are replicating database changes successfully. You can check by using either RTMT or a CLI command.
•To check by using RTMT, access the Database Summary and inspect the replication status.
•To check by using the CLI, enter the command that is shown in the following example:
admin: show perf query class "Number of Replicates Created and State of Replication"
- Perf class (Number of Replicates Created and State of Replication)
has instances and values:
ReplicateCount -> Number of Replicates Created = 344
ReplicateCount -> Replicate_State = 2
Be aware that the Replicate_State object shows a value of 2 in this case. The following list shows the possible values for Replicate_State:
–0—Replication Not Started. Either no subscribers exist, or the Database Layer Monitor service is not running and has not been running since the subscriber was installed.
–1—Replicates have been created, but their count is incorrect.
–2—Replication is good.
–3—Replication is bad in the cluster.
–4—Replication setup did not succeed.
Step 5 In Cisco Unified Reporting, generate the Unified CM Database Status report. Look for any errors or warnings in this report.
Step 6 In Cisco Unified Reporting, generate the Unified CM Cluster Overview report. Look for any errors or warnings in this report.
Step 7 Reconfigure the netdump server and clients by using the utils netdump CLI commands. For more information, see Appendix A in the Cisco Unified Communications Operating System Administration Guide.
Step 8 Run a manual DRS backup and ensure that all nodes and active services get backed up successfully. For more information, refer the Disaster Recovery System Administration Guide for your release.
Note You must run a manual DRS backup after you change the IP address of a node, because you cannot restore a node with a DRS file that contains a different IP address or host name. The post-change DRS file will include the new IP address or host name.
Step 9 Update all relevant IP phone URL parameters in Cisco Unified Communications Manager Administration under System > Enterprise Parameters.
Step 10 Update all relevant IP phone services.
Step 11 Update IPSec tunnels that terminate to the Cisco Unified Communications Manager.
Step 12 Update RTMT custom alerts and saved profiles:
•RTMT custom alerts that are derived from performance counters include the hard-coded server IP address. You must delete and reconfigure these custom alerts.
•RTMT saved profiles that have performance counters include the hard-coded server IP address. You must delete and re-add these counters and then save the profile to update it to the new IP address.
Step 13 Update the DHCP server that runs on Cisco Unified Communications Manager.
Step 14 Check and make any required configuration changes to other associated Cisco Unified Communications components, including the following ones:
Note Consult the documentation for your product to determine how to make any required configuration changes.
•Cisco Unity
•Cisco Unity Connection
•Cisco Unity Express
•SIP/H.323 trunks
•IOS Gatekeepers
•Cisco Unified MeetingPlace
•Cisco Unified MeetingPlace Express
•Cisco Unified Contact Center Enterprise
•Cisco Unified Contact Center Express
•DHCP Scopes for IP phones
•SFTP servers that are used for Cisco Unified Communications Manager trace collection, CDR export, or as a DRS backup destination
•IOS hardware resources (conference bridge, media termination point, transcoder, RSVP agent) that are registered with Cisco Unified Communications Manager
•IPVC video MCUs that are registered or integrated with Cisco Unified Communications Manager
•Cisco Emergency Responder
•Cisco Unified Application Environment
•Cisco Unified Presence
•Cisco Unified Personal Communicator
•Associated routers and gateways
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R)
Copyright © 2008.Cisco Systems, Inc. All rights reserved.
