Table Of Contents
Changing the IP Address, Hostname and Domain Name for Cisco Unified Presence Release 8.0, 8.5, and 8.6
Readiness Checklist
Modify Cluster IP Addresses for Servers Defined by IP Address
Modify Subscriber Servers Defined by IP Addresses
Modify Publisher Server Defined by IP Address
Modify Cluster IP Addresses for Servers Defined by Hostname/FQDN
Modify Subscriber Servers Defined by Hostname/FQDN
Modify Publisher Servers Defined by Hostname/FQDN
Modify Cluster Server Hostnames/FQDN
Modify Subscriber Server Hostname for Cisco Unified Presence Release 8.0
Modify Subscriber Server Hostname for Cisco Unified Presence Release 8.5 or 8.6
Modify Publisher Server Hostname
Post-Change Task List
Validating Cisco Unified Presence and MOC Interoperability after an IP Address Change
Modify the SIP Domain of a Cisco Unified Presence Cluster
Replace the Default Domain Value
Change the Domain Value
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Changing the IP Address, Hostname and Domain Name for Cisco Unified Presence Release 8.0, 8.5, and 8.6
May 16, 2012
This document provides the steps to change the IP address or hostname on a Cisco Unified Presence server. You may want to change this IP address for a variety of reasons, including moving the server from one cluster to another or resolving a duplicate IP address problem.
•
Readiness Checklist
•Modify Cluster IP Addresses for Servers Defined by IP Address
•Modify Cluster IP Addresses for Servers Defined by Hostname/FQDN
•Modify Cluster Server Hostnames/FQDN
•Post-Change Task List
•Validating Cisco Unified Presence and MOC Interoperability after an IP Address Change
•Modify the SIP Domain of a Cisco Unified Presence Cluster
•Obtaining Documentation, Obtaining Support, and Security Guidelines
Readiness Checklist
 |
Warning You must perform these procedures during a scheduled maintenance window.
|
Perform the following tasks to ensure that your system is prepared for a successful IP address or hostname change.
Caution If you do not receive the results that you expect when you perform these tasks, do not continue with this procedure until after you resolve any problems that you find.
Note If you use Domain Name System (DNS) in your network, ensure the following before you change the IP address:
•There is a forward and reverse lookup zone configured.
•The DNS is reachable and working.
Procedure
Step 1 List all servers in the cluster and note whether the nodes are defined by using IP addresses or hostnames.
•From Cisco Unified Presence Administration on the first node, navigate to System > Cluster Topology.
•Check the list of available servers in the left frame of the Cluster Topology Details window
•Capture the list of available servers for later reference.
Step 2 Ensure that you have saved a list of both the hostname and IP address of each node in your cluster.
Step 3 Ensure that all servers in the cluster are running and available by checking for any active ServerDown alerts. You can do this by entering the following command on the publisher node:
file search activelog syslog/CiscoSyslog ServerDown
Inspect the application even log after you run this command.
Step 4 Check the DB replication status on all Cisco Unified Presence nodes to ensure all servers are replicating database changes successfully. You can check by entering the following CLI command on the publisher node.
utils dbreplication runtimestate
Sample output is as follows:
DB and Replication Services: ALL RUNNING
Cluster Replication State: Replication status command started at: 2012-02-26-09-40
Replication status command COMPLETED 269 tables checked out of 269
No Errors or Mismatches found.
Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2012_02_26_09_40_34.out'
to see the details
DB Version: ccm8_6_3_10000_23
Number of replicated tables: 269
Cluster Detailed View from PUB (2 Servers):
PING REPLICATION REPL. DBver& REPL.
REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) RPC? STATUS QUEUE TABLES LOOP?
(RTMT) & details
----------- ------------ ------ ---- ----------- ----- ------- -----
-----------------
gwydla020218 10.53.46.130 0.038 Yes Connected 0 match Yes
(2) PUB Setup Completed
gwydla020220 10.53.46.133 0.248 Yes Connected 128 match Yes
(2) Setup Completed
It is important to verify that REPLICATION SETUP (RTMT) & details all report a state of 2. Anything other than 2 means that there is a problem with database replication.
Step 5 Check network connectivity and DNS server configuration. To do this, enter the CLI command that is shown in the following example:
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network : Passed
Step 6 Run a manual DRS backup and ensure that all nodes and active services are backed up successfully.
Step 7 Perform the appropriate action depending on the Cisco Unified Presence release you are using:
If you use:
|
Action
|
Cisco Unified Presence release 8.0
|
On the server that you are configuring the IP or hostname change, run the following CLI commands to stop the following Cisco Unified Presence services:
•utils service stop Cisco UP Config Agent
•utils service stop Cisco UP Intercluster Sync Agent
•utils service stop Cisco UP Client Profile Agent
•utils service stop Cisco UP Presence Engine
•utils service stop Cisco UP OAM Agent
•utils service stop Cisco UP SIP Proxy
•utils service stop Cisco UP Sync Agent
•utils service stop Cisco UP XCP Router
•utils service stop Cisco UP Presence Engine Database
|
Cisco Unified Presence release 8.5 or 8.6
|
1. If High Availability (HA) was enabled before the hostname and IP address change, disable HA. Select System > Cluster Topology in Cisco Unified Presence Administration. For more information on how to disable HA, see the Deployment Guide for Cisco Unified Presence.
2. On the server that you are configuring the IP or hostname change, run the following CLI commands to stop the following Cisco Unified Presence services:
•utils service stop Cisco UP Config Agent
•utils service stop Cisco UP Intercluster Sync Agent
•utils service stop Cisco UP Client Profile Agent
•utils service stop Cisco UP Presence Engine
•utils service stop Cisco UP OAM Agent
•utils service stop Cisco UP SIP Proxy
•utils service stop Cisco UP Sync Agent
•utils service stop Cisco UP XCP Router
•utils service stop Cisco UP Presence Engine Database
•utils service stop Cisco UP XCP Config Manager
3. On the peer server in the same subcluster that you are configuring the IP or hostname change, stop the following services:
•utils service stop Cisco UP Config Agent
•utils service stop Cisco Profile Config Agent
•utils service stop Cisco UP Presence Engine
•utils service stop Cisco UP SIP Proxy
•utils service stop Cisco UP Presence Engine Database
|
Cisco Unified Presence release 8.6(4) or later
|
1. If High Availability (HA) was enabled before the hostname and IP address change, disable HA. Select System > Cluster Topology in Cisco Unified Presence Administration. For more information on how to disable HA, see the Deployment Guide for Cisco Unified Presence.
2. On the server that you are configuring the IP or hostname change, run the following CLI commands to stop the following Cisco Unified Presence services:
•utils service stop Cisco UP Config Agent
•utils service stop Cisco UP Intercluster Sync Agent
•utils service stop Cisco Client Profile Agent
•utils service stop Cisco UP Presence Engine
•utils service stop Cisco UP OAM Agent
•utils service stop Cisco UP SIP Proxy
•utils service stop Cisco UP Sync Agent
•utils service stop Cisco UP XCP Router
•utils service stop Cisco UP Presence Datastore
•utils service stop Cisco UP SIP Registration Datastore
•utils service stop Cisco UP Login Datastore
•utils service stop Cisco UP Route Datastore
•utils service stop Cisco UP XCP Config Manager
3. On the peer server in the same subcluster that you are configuring the IP or hostname change, stop the following services:
•utils service stop Cisco UP Config Agent
•utils service stop Cisco Profile Config Agent
•utils service stop Cisco UP Presence Engine
•utils service stop Cisco UP SIP Proxy
•utils service stop Cisco UP Presence Datastore
•utils service stop Cisco UP SIP Registration Datastore
•utils service stop Cisco UP Login Datastore
•utils service stop Cisco UP Route Datastore
|
Troubleshooting Tip
Failure to properly shut down these services prior to changing the IP or hostname could potentially trigger erroneous alerts and core dumps during the renaming process. If you inadvertently skip this step, and an alarm or core is generated as a result, you will need to manually clear it and remove the core by using the following CLI command: file delete activelog core
Related Topic
Disaster Recovery System Guide for Cisco Unified Presence
Modify Cluster IP Addresses for Servers Defined by IP Address
This section describes how to change the cluster IP addresses for servers that are defined by IP addresses.
Caution Changing the IP address on any node in a Cisco Unified Presence cluster can interrupt presence services 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.
•Modify Subscriber Servers Defined by IP Addresses
•Modify Publisher Server Defined by IP Address
Modify Subscriber Servers Defined by IP Addresses
Use this procedure to change the IP address of a subscriber server if your cluster servers are defined by IP addresses. To successfully change the IP address, you must complete all steps in this procedure.
Before You Begin
Readiness Checklist
Caution If you need to change the gateway address, you must do so
before you change the IP address. If you change the IP address first, the Cisco Unified Presence server will restart immediately and you will not be able to change the gateway.
Procedure
Step 1 From Cisco Unified Presence Administration, perform the following tasks on the subscriber server:
a. Navigate to System > Cluster Topology.
b. Select Edit under the subscriber server in the Subclusters section.
c. Change the IP address of the Cisco Unified Presence server in the Node Configuration section.
Step 2 From Cisco Unified Communications Manager Administration, perform the following tasks to reflect the new IP address on the subscriber server:
a. Navigate to System > Application Server.
b. Select Find from the Find and List Servers window to display the subscriber server.
c. Select the subscriber server.
d. Change the IP address of the Cisco Unified Presence server under Application Server Information.
Note In Release 7.03 and later, Cisco Unified Presence attempts to change the IP address automatically. However, you must still verify the entry, and change it if the correct value is not automatically populated.
Step 3 Ensure that the IP address change is replicated to all the nodes in the cluster as follows:
If you use:
|
Action
|
Cisco Unified Presence Administration
|
From Cisco Unified Presence Administration, perform the following tasks.
a. Select System > Cluster Topology.
b. Select Edit under the subscriber server.
c. Check the IP address in the Node Configuration window.
|
CLI command
|
Enter the CLI command run sql select name,nodeid from ProcessNode
The following example shows the command output:
admin: run sql select name,nodeid from ProcessNode
================== ======
|
Step 4 Repeat Steps 1 to 3 on all subscriber nodes in the cluster, as required.
Step 5 Change the IP address of the subscriber server, and if necessary the default gateway, to the new address by performing the following tasks:
If you use:
|
Action
|
Troubleshooting Tips
|
Cisco Unified Operating System Administration
|
From Cisco Unified Operating System Administration, perform the following tasks.
a. Select Settings > IP > Ethernet.
b. Enter the new IP address.
c. If you are moving the server to a different subnet that requires a new default gateway address, enter the new default gateway address.
d. Select Save. The server restarts automatically.
|
When changing the IP address of more than one subscriber server, we recommend that you:
a. Change the IP address for one server at a time.
b. Restart all other servers in the cluster (including the publisher server) to update the local name resolution files including database related configuration files.
Caution! Do not change the IP address of more than one server at the same time because it can cause local name resolution files to be out of sync in the cluster.
|
CLI command
|
a. If you are moving the server to a different subnet that requires a new default gateway address, enter the CLI command set network gateway
The following output displays:
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
b. Enter yes and press Enter.
c. To change the IP address of the subscriber server, 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
under System -> Servers 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
d. Enter yes and press Enter.
|
Step 6 Verify the result of the database replication:
•If the changed IP address propagates correctly cluster-wide, return to Step 5 and complete the procedure on the next subscriber server.
•If the changed IP address does not propagate to the other servers in the cluster, enter the following command on the publisher node:
user utils dbreplication runtimestate
Verify that the new IP address is listed and that the replication state = 2 for all nodes in the cluster.
Troubleshooting Tips
•If you changed switches in addition to changing the gateway and IP address for the Cisco Unified Presence server, complete these steps while the server is automatically restarting. Otherwise, some of the Cisco Unified Presence scripts may fail network connectivity checks upon startup.
–watch the restart screen
–enter a ping -t on the old IP address
–when the pings are no longer successful, disconnect from the old switch and connect to the new switch
•The local name resolution files including database related configuration files are only updated during system startup. 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.
Related Topics
•Disaster Recovery System Guide for Cisco Unified Presence
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Post-Change Task List
Modify Publisher Server Defined by IP Address
Caution Changing the IP address of a publisher node may invalidate the server's software license for virtual servers.
Use this procedure to change the IP address of a publisher server if your cluster servers are defined by IP address.
Note You cannot use this procedure to change a publisher server of the subscriber host to another publisher server.
Before You Begin
•See the Readiness Checklist
•Ensure that the IP addresses of subscriber nodes are changed (if required) prior to changing publisher IP address.
Caution If you need to change the gateway address, you must do so
before you change the IP address. If you first change the IP address, the Cisco Unified Presence server will restart immediately and you will not be able to change the gateway.
Procedure
Step 1 From Cisco Unified Presence Administration, perform the following tasks on the publisher server:
a. Navigate to System > Cluster Topology.
b. Select Edit under the publisher server in the Subcluster section.
c. Change the IP address of the Cisco Unified Presence server under Node Configuration.
Step 2 From Cisco Unified Communications Manager Administration, perform the following tasks to reflect the new IP address on the publisher server:
a. Navigate to System > Application Server.
b. Select Find from the Find and List Servers window to display the subscriber server.
c. Select the subscriber server.
d. Change the IP address of the Cisco Unified Presence server under Application Server Information.
Note In Release 7.03 and later, Cisco Unified Presence attempts to change the IP address automatically. However, you must still verify the entry, and change it if the correct value is not automatically populated.
Step 3 Ensure that the IP address change is replicated to all subscriber nodes in the cluster by checking the following on each subscriber node:
If you want to use:
|
Action
|
Cisco Unified Presence Administration
|
From Cisco Unified Presence Administration, perform the following tasks.
a. Select System > Cluster Topology.
b. Select Edit under the subscriber server.
c. Check the IP address in the Node Configuration window.
|
CLI command
|
a. Enter the CLI command run sql select name,nodeid from ProcessNode
The following output displays:
admin: run sql select name,nodeid from ProcessNode
================== ======
|
Step 4 Change the IP address of the publisher server on each subscriber server in the cluster, by performing the following tasks:
If you want to use:
|
Action
|
Cisco Unified Operating System Administration
|
a. Open each subscriber server using this URL:
–http://subscriber_ip_address/cmplatform
b. Perform the following tasks in Cisco Unified Operating System Administration:
•Navigate to Settings > IP > Publisher.
•Change the IP address of the publisher server.
|
CLI command
|
a. Enter the following command:
set network cluster publisher ip. ip_address
b. Enter Yes and press Enter. The server restarts automatically.
|
Step 5 Change the IP address of the publisher server, and if necessary the default gateway, to the new address by performing the following tasks:
If you want to use:
|
Action
|
Cisco Unified Operating System Administration
|
From Cisco Unified Operating System Administration, perform the following tasks.
a. Select Settings > IP > Ethernet.
b. Enter the new IP address.
c. If you are moving the server to a different subnet that requires a new default gateway address, enter the new default gateway address.
d. Select Save. The server restarts automatically.
|
CLI command
|
a. If you are moving the server to a different subnet that requires a new default gateway address, enter the CLI command set network gateway
The following output displays:
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
b. Enter yes and press Enter.
c. To change the IP address of the publisher server, 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 under System -> Servers 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
d. Enter yes and press Enter.
|
Step 6 After the publisher server restarts automatically, restart all subscriber servers to update the local name resolution files including database related configuration files.
Troubleshooting Tips
•If you changed switches in addition to changing the gateway and IP address for the Cisco Unified Presence server, complete these steps while the server is automatically restarting. Otherwise, some of the Cisco Unified Presence scripts may fail network connectivity checks upon startup.
–watch the restart screen
–enter a ping -t on the old IP address
–when the pings are no longer successful, disconnect from the old switch and connect to the new switch
•The local name resolution files including database related configuration files, and services are only updated during system startup. 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.
Related Topics
•Disaster Recovery System Guide for Cisco Unified Presence
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Post-Change Task List
Modify Cluster IP Addresses for Servers Defined by Hostname/FQDN
Caution Be aware that when you take a DRS backup from a server with a particular hostname, it cannot be restored on a server (either a publisher or subscriber node) with a different hostname, even after you reinstall that node.
•Modify Subscriber Servers Defined by Hostname/FQDN
•Modify Publisher Servers Defined by Hostname/FQDN
Modify Subscriber Servers Defined by Hostname/FQDN
Use this procedure to change the IP address of a subscriber server if your cluster servers are defined by hostname. DNS servers comprise part of the network infrastructure. Cisco Unified Presence servers do not and cannot run DNS services.
Before you begin
Readiness Checklist
Procedure
Step 1 Perform the following actions:
a. Change the DNS record of the subscriber server to point to the new IP address.
b. Ensure that you correctly update both the forward (A) and reverse (PTR) records.
c. Refresh your DNS cache to ensure that the records are correctly updated.
Step 2 Change the IP address of the subscriber server, and if necessary the default gateway, to the new address by performing the following tasks:
If you want to use:
|
Action
|
Troubleshooting Tips
|
Cisco Unified Operating System Administration
|
From Cisco Unified Operating System Administration, perform the following tasks.
a. Select Settings > IP > Ethernet.
b. Enter the new IP address.
c. If you are moving the server to a different subnet that requires a new default gateway address, enter the new default gateway address.
d. Select Save. The server restarts automatically.
|
When changing IP address of more than one subscriber server, we recommend that you:
a. Change the IP address for one server at a time.
b. Restart all other servers in the cluster (including the publisher server) to update local name resolution files including database related configuration files.
Caution! Do not change the IP address of more than one server at the same time because it can cause local name resolution files to be out of sync in the cluster.
|
CLI command
|
a. If you are moving the server to a different subnet that requires a new default gateway address, enter the CLI command set network gateway
The following output displays:
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
b. Enter yes and press Enter.
c. To change the IP address of the subscriber server, 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
under System -> Servers 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
d. Enter yes and press Enter.
|
Step 3 Verify that the DNS change propagates to other nodes by using the utils network host and show tech network hosts CLI commands on all the cluster nodes:
admin:utils network host lg-sub-4
Hostname lg-sub-4 resolves to 14.86.13.11
admin:show tech network hosts
-------------------- show platform network --------------------
#This file was generated by the /etc/hosts cluster manager.
#It is automatically updated as nodes are added, changed, removed from the cluster.
14.87.10.10 lg-pub-1.lindermangroup.cisco.com lg-pub-1
14.87.10.11 lg-tftp-1.lindermangroup.cisco.com lg-tftp-1
14.87.10.12 lg-tftp-2.lindermangroup.cisco.com lg-tftp-2
14.87.11.10 lg-sub-1.lindermangroup.cisco.com lg-sub-1
14.87.11.11 lg-sub-3.lindermangroup.cisco.com lg-sub-3
14.86.13.10 lg-sub-2.lindermangroup.cisco.com lg-sub-2
14.86.13.11 lg-sub-4.lindermangroup.cisco.com lg-sub-4
14.87.11.12 lg-sub-5.lindermangroup.cisco.com lg-sub-5
14.87.11.13 lg-sub-7.lindermangroup.cisco.com lg-sub-7
14.86.13.12 lg-tftp-3.lindermangroup.cisco.com lg-tftp-3
14.87.20.20 lg-cups1.heroes.com lg-cups1
14.86.13.13 lg-sub-6.lindermangroup.cisco.com lg-sub-6
Step 4 Verify the result of the database replication, as follows:
a. Enter the following command: user utils dbreplication runtimestate
b. Verify that the new IP address is listed and that the replication state = 2 for all nodes in the cluster.
Step 5 Restart all other servers in the cluster (including the publisher server) to update the local name resolution files including database related configuration files.
Troubleshooting Tips
•If you changed switches in addition to changing the gateway and IP address for the Cisco Unified Presence server, complete these steps while the server is automatically restarting. Otherwise, some of the Cisco Unified Presence scripts may fail network connectivity checks upon startup.
–watch the restart screen
–enter a ping -t on the old IP address
–when the pings are no longer successful, disconnect from the old switch and connect to the new switch
•The local name resolution files including database related configuration files, and services are only updated during system startup. 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.
Related Topics
•Disaster Recovery System Guide for Cisco Unified Presence
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Post-Change Task List
Modify Publisher Servers Defined by Hostname/FQDN
Caution Changing the IP address of a publisher node may invalidate the server's software license for virtual servers.
Use this procedure to change the IP address of a publisher server if your servers are defined by hostname. DNS servers comprise part of the network infrastructure. Cisco Unified Presence servers do not and cannot run DNS services.
Note You cannot use this procedure to change a publisher server of the subscriber host to another publisher server.
Before you begin
Readiness Checklist
Procedure
Step 1 Perform the following actions:
a. Change the DNS record of the publisher server to point to the new IP address.
b. Ensure that you correctly update both the forward (A) and reverse (PTR) records.
Step 2 On each subscriber node in the cluster, access Cisco Unified Operating System Administration and perform the following tasks:
a. Navigate to Settings > IP > Publisher.
b. Change the IP address of the publisher server.
Step 3 Change the IP address of the publisher server, and if necessary the default gateway, to the new address by performing the following tasks:
If you want to use:
|
Action
|
Cisco Unified Operating System Administration
|
From Cisco Unified Operating System Administration, perform the following tasks.
a. Select Settings > IP > Ethernet.
b. Enter the new IP address.
c. If you are moving the server to a different subnet that requires a new default gateway address, enter the new default gateway address.
d. Select Save. The server restarts automatically.
|
CLI command
|
a. If you are moving the server to a different subnet that requires a new default gateway address, enter the CLI command set network gateway
The following output displays:
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
b. Enter yes and press Enter.
c. To change the IP address of the publisher server, 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 under System -> Servers 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
d. Enter yes and press Enter.
|
Step 4 After the publisher server restarts automatically, restart all subscriber servers to update the local name resolution files including database related configuration files, and services.
Step 5 Ensure that local resolution of the subscriber node also resolves to the new IP address by running the utils network host and show tech network hosts CLI commands:
admin:utils network host lg-sub-4
Hostname lg-sub-4 resolves to 14.86.13.11
admin:show tech network hosts
-------------------- show platform network --------------------
#This file was generated by the /etc/hosts cluster manager.
#It is automatically updated as nodes are added, changed, removed from the cluster.
14.87.10.10 lg-pub-1.lindermangroup.cisco.com lg-pub-1
14.87.10.11 lg-tftp-1.lindermangroup.cisco.com lg-tftp-1
14.87.10.12 lg-tftp-2.lindermangroup.cisco.com lg-tftp-2
14.87.11.10 lg-sub-1.lindermangroup.cisco.com lg-sub-1
14.87.11.11 lg-sub-3.lindermangroup.cisco.com lg-sub-3
14.86.13.10 lg-sub-2.lindermangroup.cisco.com lg-sub-2
14.86.13.11 lg-sub-4.lindermangroup.cisco.com lg-sub-4
14.87.11.12 lg-sub-5.lindermangroup.cisco.com lg-sub-5
14.87.11.13 lg-sub-7.lindermangroup.cisco.com lg-sub-7
14.86.13.12 lg-tftp-3.lindermangroup.cisco.com lg-tftp-3
14.87.20.20 lg-cups1.heroes.com lg-cups1
14.86.13.13 lg-sub-6.lindermangroup.cisco.com lg-sub-6
Step 6 Restart all other servers in the cluster (including the publisher) to update the local name resolution files including database related configuration files.
Troubleshooting Tips
•If you changed switches in addition to changing the gateway and IP address for the Cisco Unified Presence server, complete these steps while the server is automatically restarting. Otherwise, some of the Cisco Unified Presence scripts may fail network connectivity checks upon startup.
–watch the restart screen
–enter a ping -t on the old IP address
–when the pings are no longer successful, disconnect from the old switch and connect to the new switch
•The local name resolution files including database related configuration files and services are only updated during system startup. 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.
Related Topics
•Disaster Recovery System Guide for Cisco Unified Presence
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Post-Change Task List
Modify Cluster Server Hostnames/FQDN
•Modify Subscriber Server Hostname for Cisco Unified Presence Release 8.0
•Modify Subscriber Server Hostname for Cisco Unified Presence Release 8.5 or 8.6
•Modify Publisher Server Hostname
Modify Subscriber Server Hostname for Cisco Unified Presence Release 8.0
Use the following procedure to change the hostname of subscriber servers in a cluster for releases earlier than Release 8.5. DNS servers comprise part of the network infrastructure. Cisco Unified Presence servers do not and cannot run DNS services.
Before you begin
Readiness Checklist
Procedure
Step 1 For each cluster where the subscriber node being changed is an intercluster peer, remove the subscriber's cluster from the list of intercluster peers.
Step 2 Restart the Cisco UP Intercluster Sync Agent for all peer-cluster publisher nodes.
Step 3 If prompted, restart the Cisco UP XCP Router on nodes in the clusters.
Step 4 Perform the following actions:
a. Change the DNS record of the subscriber server to point to the new IP address.
b. Ensure that you correctly update both the forward (A) and reverse (PTR) records.
Step 5 Verify that the DNS change propagates to other nodes by using the following CLI commands on all the cluster nodes:
Command Line
|
Output / Result
|
utils network host
show tech network hosts
|
admin:utils network host lg-sub-4
Hostname lg-sub-4 resolves to 14.86.13.11
admin:show tech network hosts
--------------- show platform network --------------------
#This file was generated by the /etc/hosts cluster manager.
#It is automatically updated as nodes are added, changed,
removed from the cluster.
14.87.10.10 lg-pub-1.lindermangroup.cisco.com lg-pub-1
14.87.10.11 lg-tftp-1.lindermangroup.cisco.com lg-tftp-1
14.87.10.12 lg-tftp-2.lindermangroup.cisco.com lg-tftp-2
14.87.11.10 lg-sub-1.lindermangroup.cisco.com lg-sub-1
14.87.11.11 lg-sub-3.lindermangroup.cisco.com lg-sub-3
14.86.13.10 lg-sub-2.lindermangroup.cisco.com lg-sub-2
14.86.13.11 lg-sub-4.lindermangroup.cisco.com lg-sub-4
14.87.11.12 lg-sub-5.lindermangroup.cisco.com lg-sub-5
14.87.11.13 lg-sub-7.lindermangroup.cisco.com lg-sub-7
14.86.13.12 lg-tftp-3.lindermangroup.cisco.com lg-tftp-3
14.87.20.20 lg-cups1.heroes.com lg-cups1
14.86.13.13 lg-sub-6.lindermangroup.cisco.com lg-sub-6
Note Do not proceed if the change has not propagated to all nodes.
|
utils diagnose module validate_network
|
This diagnostics module checks that you configured DNS client services correctly, the server can connect to the DNS server, and Forward (A) and Reverse (PTR) records are present and match the server IP address and hostname.
Note Do not proceed if the change has not propagated to all nodes.
|
Step 6 Perform one of the following tasks:
•If the servers are defined by IP address and you are only changing the hostname of the server, skip to Step 10.
•If you are changing the IP address or the server is defined by hostname, continue with Step 7.
Step 7 From Cisco Unified Presence Administration, perform the following tasks on the publisher server:
a. Navigate to System > Cluster Topology.
b. Select Edit under the publisher server in the Subclusters section.
c. Change the hostname of the Cisco Unified Presence server under Node Configuration.
Step 8 You only need to complete this step for one server in the Cisco Unified Communications Manager cluster. From Cisco Unified Communications Manager Administration, perform the following tasks when you are changing either the subscriber or publisher:
a. Navigate to System > Application Server.
b. Select Find from the Find and List Servers window to display the server.
c. Select the server.
d. Change the hostname of the Cisco Unified Presence server under Application Server Information.
e. Select Save.
Note In Release 7.03 and later, Cisco Unified Presence attempts to change the hostname automatically. However, you must still verify the entry, and change it if the correct value is not automatically populated.
Step 9 Ensure that the hostname change is replicated to all the nodes in the cluster by performing the following tasks
If you want to use:
|
Action
|
Cisco Unified Presence Administration
|
From Cisco Unified Presence Administration, perform the following tasks.
a. Select System > Cluster Topology.
b. Select Edit under the subscriber server.
c. Check the hostname in the Node Configuration window.
|
CLI command
|
a. Enter the CLI command run sql select name,nodeid from ProcessNode
The following output displays:
admin: run sql select name,nodeid from ProcessNode
================== ======
|
:
Step 10 Change the hostname of the server by performing one or more of the following tasks:
If you want to:
|
Action
|
Change the hostname from Cisco Unified Operating System Administration
|
a. Navigate to Settings > IP > Ethernet.
b. Change the hostname and, if necessary, the default gateway.
c. Select Save, which automatically restarts this server with the changes.
Note Changing the hostname triggers an automatic, self-signed Certificate Regeneration. After the server restarts automatically, secure connections to this server will fail until the CTL client is rerun and the CTL file is updated.
|
Change the hostname via a CLI command
|
a. Enter the CLI command set network hostname hostname.
b. Enter Yes and press Enter. This will automatically restart this server with the new hostname.
Note Changing the hostname triggers an automatic, self-signed Certificate Regeneration. After the server restarts automatically, secure connections to this server will fail until the CTL client is rerun and the CTL file is updated.
|
Change the IP address and subnet via a CLI command
|
a. Change the server Default Gateway to the new address by using the set network gateway ipaddress CLI command.
b. When the default gateway is changing, ensure (prior to the next step) that the server is moved to the new subnet and has access to the default gateway prior to the next step.
c. If you also want to change the IP address of the server, perform the following tasks:
–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.
–Enter Yes and press Enter. This will automatically restart this server with the new IP address.
|
Step 11 Restart all other servers in the cluster to update the local name resolution files including database related configuration files.
Step 12 If you completed Step 1, add the cluster whose subscriber node hostname was changed to each peer-cluster publisher node.
Troubleshooting Tips
•If you changed switches in addition to changing the gateway and hostname for the Cisco Unified Presence server, complete these steps while the server is automatically restarting. Otherwise, some of the Cisco Unified Presence scripts may fail network connectivity checks upon startup.
–watch the restart screen
–enter a ping -t on the old IP address
–when the pings are no longer successful, disconnect from the old switch and connect to the new switch
•During Cisco Unified Presence server start up, the Verify Network script checks whether the server can access the default gateway. If the server cannot communicate with the default gateway at the time of startup, the Verify Network script will fail, and startup may be delayed. If you are using Manual DHCP configuration and the DHCP server is not reachable or not giving out an IP address to the server, the system will not boot and will instead continuously wait at the Verify Network startup phase.
•The local name resolution files including database related configuration files and services only update during startup time, and core network services such as Cisco DB and Cisco Tomcat need to be restarted after the files are updated. A restart of the servers ensures the proper update and service restart sequence for the hostname changes to take effect.
Related Topics
•Serviceability Configuration and Maintenance Guide for Cisco Unified Presence
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Post-Change Task List
Modify Subscriber Server Hostname for Cisco Unified Presence Release 8.5 or 8.6
Use the following procedure to change the hostname of subscriber servers in a cluster for Release 8.5 or 8.6. DNS servers comprise part of the network infrastructure. Cisco Unified Presence servers do not and cannot run DNS services.
Before You Begin
•Readiness Checklist
•In Cisco Unified Presence release 8.6(4) and later, the Single Sign-On (SSO) feature is available for Cisco Unified Presence interfaces, including the Real-Time Monitoring Tool (RTMT). The Cisco Unified Presence server hostname is a critical piece of information for SSO to function correctly. Cisco recommends that you disable SSO prior to changing the Cisco Unified Presence server hostname. After you change the hostname, you can re-enable SSO using the new hostname. For more information about SSO, see the "Single Sign-On Configuration" section of the Deployment Guide for Cisco Unified Presence.
Note Keep in mind that after you disable SSO, you will need to enter login credentials to access Cisco Unified Presence. Ensure that you remember your login credentials before disabling SSO, otherwise you may be locked out of Cisco Unified Presence applications.
Procedure
Step 1 For each cluster where the subscriber node being changed is an intercluster peer, remove the subscriber's cluster from the list of intercluster peers.
Step 2 Restart the Cisco UP Intercluster Sync Agent for all peer-cluster publisher nodes.
Step 3 If prompted, restart the Cisco UP XCP Router on nodes in the clusters.
Step 4 Perform the following actions:
a. Change the DNS record of the subscriber server to point to the new IP address.
b. Ensure that you correctly update both the forward (A) and reverse (PTR) records.
Step 5 Verify that the DNS change propagates to other nodes by using the following CLI commands on all the cluster nodes:
Command Line
|
Output / Result
|
utils network host
show tech network hosts
|
admin:utils network host lg-sub-4
Hostname lg-sub-4 resolves to 14.86.13.11
admin:show tech network hosts
--------------- show platform network --------------------
#This file was generated by the /etc/hosts cluster manager.
#It is automatically updated as nodes are added, changed,
removed from the cluster.
14.87.10.10 lg-pub-1.lindermangroup.cisco.com lg-pub-1
14.87.10.11 lg-tftp-1.lindermangroup.cisco.com lg-tftp-1
14.87.10.12 lg-tftp-2.lindermangroup.cisco.com lg-tftp-2
14.87.11.10 lg-sub-1.lindermangroup.cisco.com lg-sub-1
14.87.11.11 lg-sub-3.lindermangroup.cisco.com lg-sub-3
14.86.13.10 lg-sub-2.lindermangroup.cisco.com lg-sub-2
14.86.13.11 lg-sub-4.lindermangroup.cisco.com lg-sub-4
14.87.11.12 lg-sub-5.lindermangroup.cisco.com lg-sub-5
14.87.11.13 lg-sub-7.lindermangroup.cisco.com lg-sub-7
14.86.13.12 lg-tftp-3.lindermangroup.cisco.com lg-tftp-3
14.87.20.20 lg-cups1.heroes.com lg-cups1
14.86.13.13 lg-sub-6.lindermangroup.cisco.com lg-sub-6
Note Do not proceed if the change has not propagated to all nodes.
|
utils diagnose module validate_network
|
This diagnostics module checks that you configured DNS client services correctly, the server can connect to the DNS server, and Forward (A) and Reverse (PTR) records are present and match the server IP address and hostname.
Note Do not proceed if the change has not propagated to all nodes.
|
Step 6 Perform one of the following tasks:
•If the servers are defined by IP address and you are only changing the hostname of the server, skip to Step 10.
•If you are changing the IP address or the server is defined by hostname, continue with Step 7.
Step 7 From Cisco Unified Presence Administration, perform the following tasks on the publisher server:
a. Navigate to System > Cluster Topology.
b. Select Edit under the publisher server in the Subclusters section.
c. Change the hostname of the Cisco Unified Presence server under Node Configuration.
Step 8 You only need to complete this step for one server in the Cisco Unified Communications Manager cluster. From Cisco Unified Communications Manager Administration, perform the following tasks when you are changing either the subscriber or publisher:
a. Navigate to System > Application Server.
b. Select Find from the Find and List Servers window to display the server.
c. Select the server.
d. Change the hostname of the Cisco Unified Presence server under Application Server Information.
e. Select Save.
Note In Release 7.03 and later, Cisco Unified Presence attempts to change the hostname automatically. However, you must still verify the entry, and change it if the correct value is not automatically populated.
Step 9
If you want to use:
|
Action
|
Cisco Unified Presence Administration
|
From Cisco Unified Presence Administration, perform the following tasks.
a. Select System > Cluster Topology.
b. Select Edit under the subscriber server.
c. Check the hostname and IP address in the Node Configuration window.
|
CLI command
|
a. Enter the CLI command run sql select name,nodeid from ProcessNode
The following output displays:
admin: run sql select name,nodeid from ProcessNode
================== ======
|
Ensure that the hostname or IP address change is replicated to all the nodes in the cluster as follows:
Step 10 Repeat on all nodes in the cluster.
Step 11 Change the hostname of the server by performing one or more of the following tasks:
If you want to:
|
Action
|
Change the IP, hostname, or subnet gateway from Cisco Unified Operating System Administration
|
a. Navigate to Settings > IP > Ethernet.
b. Change IP address and, if necessary, the default gateway to the new address.
c. Select Save, which automatically restarts this server with the changes.
Note Changing the hostname triggers an automatic, self-signed Certificate Regeneration. After the server restarts automatically, secure connections to this server will fail until the CTL client is rerun and the CTL file is updated.
|
Change the hostname via a CLI command
|
a. Enter the CLI command set network hostname hostname.
b. Enter Yes and press Enter. This will automatically restart this server with the new hostname.
Note Changing the hostname triggers an automatic, self-signed Certificate Regeneration. After the server restarts automatically, secure connections to this server will fail until the CTL client is rerun and the CTL file is updated.
|
Change the IP address and subnet via a CLI command
|
a. Change the server Default Gateway to the new address by using the set network gateway ipaddress CLI command.
b. When the default gateway is changing, ensure (prior to the next step) that the server is moved to the new subnet and has access to the default gateway prior to the next step.
c. If you also want to change the IP address of the server, perform the following tasks:
–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.
–Enter Yes and press Enter. This will automatically restart this server with the new IP address.
|
Step 12 Reboot the publisher node in the cluster.
Step 13 Reboot the subscriber node (the node with the new host name).
Step 14 Restart all other servers in the cluster to update the local name resolution files including database related configuration files.
Step 15 On the publisher server, run utils dbreplication reset all to set up replication across the whole cluster again.
Step 16 If you completed Step 1, add the cluster whose subscriber node hostname was changed to each peer-cluster publisher node.
Step 17 If you disabled SSO prior to performing this procedure, you can enable it now. For information about how to enable SSO, see the "Single Sign-On Configuration" section of the Deployment Guide for Cisco Unified Presence.
Troubleshooting Tips
•If you changed switches in addition to changing the gateway and hostname for the Cisco Unified Presence server, complete these steps while the server is automatically restarting. Otherwise, some of the Cisco Unified Presence scripts may fail network connectivity checks upon startup.
–watch the restart screen
–enter a ping -t on the old IP address
–when the pings are no longer successful, disconnect from the old switch and connect to the new switch
•During Cisco Unified Presence server start up, the Verify Network script checks whether the server can access the default gateway. If the server cannot communicate with the default gateway at the time of startup, the Verify Network script will fail, and startup may be delayed. If you are using Manual DHCP configuration and the DHCP server is not reachable or not giving out an IP address to the server, the system will not boot and will instead continuously wait at the Verify Network startup phase.
•The local name resolution files including database related configuration files and services only update during startup time, and core network services such as Cisco DB and Cisco Tomcat need to be restarted after the files are updated. A restart of the servers ensures the proper update and service restart sequence for the IP address changes to take effect.
Related Topics
•Serviceability Configuration and Maintenance Guide for Cisco Unified Presence
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
•Deployment Guide for Cisco Unified Presence.
What To Do Next
Post-Change Task List
Modify Publisher Server Hostname
Caution Changing the hostname of a publisher node may invalidate the server's software license for virtual servers.
Use the following procedure to change the hostname of publisher servers in a cluster. DNS servers comprise part of the network infrastructure. Cisco Unified Presence servers do not and cannot run DNS services.
Before You Begin
•Readiness Checklist
•In Cisco Unified Presence release 8.6(4) and later, the Single Sign-On (SSO) feature is available for Cisco Unified Presence interfaces, including the Real-Time Monitoring Tool (RTMT). The Cisco Unified Presence server hostname is a critical piece of information for SSO to function correctly. Cisco recommends that you disable SSO prior to changing the Cisco Unified Presence server hostname. After you change the hostname, you can re-enable SSO using the new hostname. For more information about SSO, see the "Single Sign-On Configuration" section of the Deployment Guide for Cisco Unified Presence.
Note Keep in mind that after you disable SSO, you will need to enter login credentials to access Cisco Unified Presence. Ensure that you remember your login credentials before disabling SSO, otherwise you may be locked out of Cisco Unified Presence applications.
Procedure
Step 1 For each cluster where the publisher node being changed is an intercluster peer, remove the publisher's cluster from the list of intercluster peers.
Step 2 Restart the Cisco UP Intercluster Sync Agent for all peer-cluster publisher nodes.
Step 3 If prompted, restart the Cisco UP XCP Router on nodes in the clusters.
Step 4 Perform the following actions:
a. Change the DNS record of the publisher server to point to the new hostname.
b. If you intend for the IP address to change at the same time, make sure that it is also reflected on the DNS servers.
c. Ensure that you correctly update both the forward (A) and reverse (PTR) records.
Step 5 Verify that the DNS change propagates to other nodes by using the following CLI commands on all the cluster nodes:
Command Line
|
Output / Result
|
utils network host
show tech network hosts
|
admin:utils network host lg-sub-4
Hostname lg-sub-4 resolves to 14.86.13.11
admin:show tech network hosts
--------------- show platform network --------------------
#This file was generated by the /etc/hosts cluster manager.
#It is automatically updated as nodes are added, changed,
removed from the cluster.
14.87.10.10 lg-pub-1.lindermangroup.cisco.com lg-pub-1
14.87.10.11 lg-tftp-1.lindermangroup.cisco.com lg-tftp-1
14.87.10.12 lg-tftp-2.lindermangroup.cisco.com lg-tftp-2
14.87.11.10 lg-sub-1.lindermangroup.cisco.com lg-sub-1
14.87.11.11 lg-sub-3.lindermangroup.cisco.com lg-sub-3
14.86.13.10 lg-sub-2.lindermangroup.cisco.com lg-sub-2
14.86.13.11 lg-sub-4.lindermangroup.cisco.com lg-sub-4
14.87.11.12 lg-sub-5.lindermangroup.cisco.com lg-sub-5
14.87.11.13 lg-sub-7.lindermangroup.cisco.com lg-sub-7
14.86.13.12 lg-tftp-3.lindermangroup.cisco.com lg-tftp-3
14.87.20.20 lg-cups1.heroes.com lg-cups1
14.86.13.13 lg-sub-6.lindermangroup.cisco.com lg-sub-6
Note Do not proceed if the change has not propagated to all nodes.
|
utils diagnose module validate_network
|
This diagnostics module checks that you configured DNS client services correctly, the server can connect to the DNS server, and Forward (A) and Reverse (PTR) records are present and match the server IP address and hostname.
Note Do not proceed if the change has not propagated to all nodes.
|
Step 6 Perform one of the following tasks:
•If the servers are defined by IP address and you are only changing the hostname of the server, skip to Step 12.
•If you are changing the IP address or the server is defined by hostname, continue with Step 7.
Step 7 From Cisco Unified Presence Administration, perform the following tasks on the publisher server:
a. Navigate to System > Cluster Topology.
b. Select Edit under the publisher server in the Subcluster section.
c. Change the hostname of the Cisco Unified Presence server under Node Configuration.
d. Select Save.
Step 8 You need only complete this step for one server in the Cisco Unified Presence cluster. From Cisco Unified Communications Manager Administration, perform the following tasks when you are changing either the subscriber or publisher:
a. Navigate to System > Application Server.
b. Select Find from the Find and List Servers window to display the server.
c. Select the server.
d. Change the hostname of the Cisco Unified Presence server under Application Server Information.
e. Select Save.
Note In Release 7.03 and later, Cisco Unified Presence attempts to change the hostname automatically. However, you must still verify the entry, and change it if the correct value is not automatically populated.
Step 9 Ensure that the hostname change is replicated to all the nodes in the cluster as follows:
If you want to use:
|
Action
|
Cisco Unified Presence Administration
|
From Cisco Unified Presence Administration, perform the following tasks.
a. Select System > Cluster Topology.
b. Select Edit under the publisher server.
c. Check the hostname and IP address in the Node Configuration window.
|
CLI command
|
a. Enter the CLI command run sql select name,nodeid from ProcessNode
|
Step 10 Repeat on all nodes in the cluster.
Step 11 Change the IP address and/or hostname of the publisher server on each subscriber server in the cluster, by performing the following tasks:
If you want to use:
|
Action
|
Cisco Unified Operating System Administration
|
a. Open each subscriber server using this URL:
–http://subscriber_ip_address/cmplatform
b. Perform the following tasks in Cisco Unified Operating System Administration:
•Navigate to Settings > IP > Publisher.
•Change the hostname and/or IP address of the publisher server.
|
CLI command
|
Enter one of the following commands:
–set network cluster publisher ip
–set network cluster publisher hostname
|
Step 12 On the publisher server, change the hostname of the server by performing one or more of the following tasks:
If you want to:
|
Action
|
Change the IP, hostname, or subnet gateway from Cisco Unified Operating System Administration
|
a. Navigate to Settings > IP > Ethernet.
b. Change IP address and, if necessary, the default gateway to the new address.
c. Select Save, which automatically restarts this server with the changes.
Note Changing the hostname triggers an automatic, self-signed Certificate Regeneration. After the server restarts automatically, secure connections to this server will fail until the CTL client is rerun and the CTL file is updated.
|
Change the hostname via a CLI command
|
a. Enter the CLI command set network hostname hostname.
b. Enter Yes and press Enter. This will automatically restart this server with the new hostname.
Note Changing the hostname triggers an automatic, self-signed Certificate Regeneration. After the server restarts automatically, secure connections to this server will fail until the CTL client is rerun and the CTL file is updated.
|
Change the IP address and subnet via a CLI command
|
a. Change the server Default Gateway to the new address by using the set network gateway ipaddress CLI command.
b. When the default gateway is changing, ensure (prior to the next step) that the server is moved to the new subnet and has access to the default gateway prior to the next step.
c. If you also want to also change the IP address of the server, perform the following tasks:
–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.
–Enter Yes and press Enter. This will automatically restart this server with the new IP address.
|
Step 13 Restart all other servers in the cluster (including the publisher) to update local name resolution files including database related configuration files from the CLI or Cisco Unified Operating System Administration. You must restart the whole cluster after you change each node.
Step 14 If you completed Step 1, add the cluster whose publisher node hostname was changed to each peer-cluster publisher node.
Step 15 If you disabled SSO prior to performing this procedure, you can enable it now. For information about how to enable SSO, see the "Single Sign-On Configuration" section of the Deployment Guide for Cisco Unified Presence.
Troubleshooting Tips
•If you changed switches in addition to changing the gateway and IP address for the Cisco Unified Presence server, complete these steps while the server is automatically restarting. Otherwise, some of the Cisco Unified Presence scripts may fail network connectivity checks upon startup.
–watch the restart screen
–perform a ping -t on the old IP address
–when the pings are no longer successful, disconnect from the old switch and connect to the new switch
•During Cisco Unified Communications Manager server startup, the Verify Network script checks access to the default gateway. If the server cannot communicate to the default gateway at the time of startup, the Verify Network script will fail, and startup may be delayed. If you are using Manual DHCP configuration and the DHCP server is not reachable or not giving out an IP address to the server, the system will not boot and will instead continuously wait at the Verify Network startup phase.
•The local name resolution files including database related configuration files and services only update during startup time, and core network services such as Cisco DB and Cisco Tomcat need to be restarted after the files are updated. A restart of the servers ensures the proper update and service restart sequence for the IP address changes to take effect.
Related Topics
•Serviceability Configuration and Maintenance Guide for Cisco Unified Presence
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
•Deployment Guide for Cisco Unified Presence.
What To Do Next
Post-Change Task List
Post-Change Task List
Complete this procedure after you finish changing the IP addresses of your cluster.
Before You Begin
•Run a manual DRS backup and ensure that all nodes and active services are backed up successfully.
•If you change the hostname of the Cisco Unified Presence server and are federating with another enterprise, you must change the federation routing Full Qualified Domain Name (FQDN) parameter to point to the new server address. In Cisco Unified Presence Administration, perform the following tasks:
–Select System > Service Parameters
–Select the server.
–Select the Cisco UP SIP Proxy service.
–Change the clusterwide federation routing parameter (Federation Routing CUP FQDN) to the new FQDN.
Procedure
Step 1 Ensure that all servers in the cluster are running and available by checking for any active ServerDown alerts. You can check the application event log for ServerDown alerts by entering the following command in the Command Line Interface (CLI) on the publisher node:
file search activelog syslog/CiscoSyslog ServerDown
Step 2 Check the DB replication status on all the Cisco Unified Presence nodes in the cluster to ensure all servers are replicating database changes successfully. You can check by using either RTMT or a CLI command.
If you use:
|
Action
|
RTMT
|
Access the Database Summary and inspect the replication status as follows:
a. Select System > Performance > Open Performance Monitoring.
b. Check the values of these counters, that display under the "Number of Replicates Created and State of Replication" counter group:
–Number of Replicates Created
–Replicate_State
|
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
Note The number of replicates created must be the same on all nodes within the cluster
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 3 Run a manual DRS backup and ensure that all nodes and active services are backed up successfully.
Step 4 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 5 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.
•SIP trunks
•SFTP servers that are used for Cisco Unified Presence server trace collection or as a DRS backup destination
•Cisco Jabber
•Associated routers and gateways
•Third-party clients, such as IBM Lotus Sametime
Step 6 Perform the appropriate action depending on the Cisco Unified Presence release you are using:
If you are using:
|
Action
|
Cisco Unified Presence Release 8.0
|
On the server that you are configuring the IP or hostname change, verify that the previously stopped services are running. If the services are not running, run the following CLI commands to restart the Cisco Unified Presence services in the following order:
•utils service start Cisco UP Presence Engine Database
•utils service start Cisco UP XCP Router
•utils service start Cisco UP Sync Agent
•utils service start Cisco UP SIP Proxy
•utils service start Cisco UP OAM Agent
•utils service start Cisco UP Presence Engine
•utils service start Cisco UP Client Profile Agent
•utils service start Cisco UP Intercluster Sync Agent
•utils service start Cisco UP Config Agent
|
Cisco Unified Presence Release 8.5 or 8.6
|
1. On the server that you are configuring the IP or hostname change, verify that the previously stopped services are running. If the services are not running, run the following CLI commands to restart the Cisco Unified Presence services in the following order:
•utils service start Cisco UP XCP Config Manager
•utils service start Cisco UP Presence Engine Database
•utils service start Cisco UP XCP Router
•utils service start Cisco UP Sync Agent
•utils service start Cisco UP SIP Proxy
•utils service start Cisco UP OAM Agent
•utils service start Cisco UP Presence Engine
•utils service start Cisco UP Client Profile Agent
•utils service start Cisco UP Intercluster Sync Agent
•utils service start Cisco UP Config Agent
2. On the peer server in the same subcluster that you are configuring the IP or hostname change, verify that the previously stopped services are running. If the services are not running, run the following services CLI commands to restart the Cisco Unified Presence services in the following order:
•utils service stop Cisco UP Presence Engine Database
•utils service stop Cisco UP SIP Proxy
•utils service stop Cisco UP Presence Engine
•utils service stop Cisco Profile Config Agent
•utils service stop Cisco UP Config Agent
If High Availability (HA) was disabled before the hostname and IP address change, enable HA. Select System > Cluster Topology in Cisco Unified Presence Administration. For more information about how to enable HA, see the Deployment Guide for Cisco Unified Presence.
|
Cisco Unified Presence Release 8.6(4) or later
|
1. On the server that you are configuring the IP or hostname change, verify that the previously stopped services are running. If the services are not running, run the following CLI commands to restart the Cisco Unified Presence services in the following order:
•utils service start Cisco UP XCP Config Manager
•utils service start Cisco UP Route Datastore
•utils service start Cisco UP Login Datastore
•utils service start Cisco UP SIP Registration Datastore
•utils service start Cisco UP Presence Datastore
•utils service start Cisco UP XCP Router
•utils service start Cisco UP Sync Agent
•utils service start Cisco UP SIP Proxy
•utils service start Cisco UP OAM Agent
•utils service start Cisco UP Presence Engine
•utils service start Cisco Client Profile Agent
•utils service start Cisco UP Intercluster Sync Agent
•utils service start Cisco UP Config Agent
2. On the peer server in the same subcluster that you are configuring the IP or hostname change, verify that the previously stopped services are running. If the services are not running, run the following CLI commands to restart the Cisco Unified Presence services in the following order:
•utils service start Cisco UP Route Datastore
•utils service start Cisco UP Login Datastore
•utils service start Cisco UP SIP Registration Datastore
•utils service start Cisco UP Presence Datastore
•utils service stop Cisco UP SIP Proxy
•utils service stop Cisco UP Presence Engine
•utils service stop Cisco Profile Config Agent
•utils service stop Cisco UP Config Agent
If High Availability (HA) was disabled before the hostname and IP address change, enable HA. Select System > Cluster Topology in Cisco Unified Presence Administration. For more information about how to enable HA, see the Deployment Guide for Cisco Unified Presence.
|
Troubleshooting Tip
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 hostname. The post-change DRS file will include the new IP address or hostname.
Related Topics
•Disaster Recovery System Guide for Cisco Unified Presence
•Integration Guide for Configuring Cisco Unified Presence for Interdomain Federation
What To Do Next
Validating Cisco Unified Presence and MOC Interoperability after an IP Address Change
Validating Cisco Unified Presence and MOC Interoperability after an IP Address Change
Perform the steps in this procedure only if you change the hostname or IP address on a Cisco Unified Presence server that was previously integrated with Microsoft LCS/OCS. You need to do this to ensure the Microsoft Office Communicator (MOC) server and clients reflect the correct Cisco Unified Presence IP address and hostname (after your changes) and the new FQDN.
Before You Begin
Complete the Post-Change Task List.
Procedure
Step 1 Sign out of any existing MOC client session that you may have running.
Step 2 Sign in to the OCS or LCS server.
Step 3 Edit the Front End properties, in the following tabs on the OCS or LCS server:
Tab
|
Action
|
Routing Tab
|
a. Update the renamed Cisco Unified Presence server with its new FQDN and IP address.
b. Change the `Next Hop' IP address of the wild carded Cisco Unified Presence domain to be the new Cisco Unified Presence IP address.
|
Host Authorization Tab
|
Ensure that the new Cisco Unified Presence IP address and new FQDN is listed as follows:
•Outbound only - N
•Throttle As Server -Y
•Treat As Authenticated - Y
|
Step 4 Right-click on the LCS/OCS Users, and edit as follows:
a. Change the `Server URI' to be the new Cisco Unified Presence FQDN.
b. Select OK.
Step 5 Stop the OCS/LCS Front End Service.
Step 6 Restart the OCS/LCS Front End Service.
Step 7 Sign in to the MOC client, and confirm control of a Cisco device.
Related Topics
•Integration Note for Configuring Cisco Unified Presence with Microsoft OCS for MOC Call Control
•Post-Change Task List
Modify the SIP Domain of a Cisco Unified Presence Cluster
•Replace the Default Domain Value
•Change the Domain Value
Replace the Default Domain Value
The domain name specifies the DNS domain name of the Cisco Unified Presence server. Cisco Unified Presence automatically defaults to the domain name DOMAIN.NOT.SET. You must replace this default domain name with the DNS domain name in order for the SRM to initialize correctly in a High Availability deployment.
If you are not using DNS in your network, and you did not set the domain at install, you must replace this default value with the enterprise wide domain and ensure the node names are configured as IP addresses or Cisco Unified Presence will not function correctly.
Perform this configuration on all nodes in your Cisco Unified Presence cluster.
Procedure
Step 1 Perform the following steps to configure the new domain value:
a. Select Cisco Unified Presence Administration > System > Cluster Topology.
b. In the right pane, select Settings.
c. Configure the Domain Name value with the new domain.
a. Select Cisco Unified Presence Administration > System > Service Parameters, and select the Cisco UP SIP Proxy service.
b. Configure the Federation Routing Cisco Unified Presence FQDN with the new domain.
c. You will be prompted to confirm these configuration changes. Select OK for both prompts, and then select Save.
Step 2 Use this CLI command to set the new domain:
set network domain <new_domain>
This CLI command invokes a reboot of the server.
Step 3 Manually regenerate all certificates on the local Cisco Unified Presence server.
Note When you regenerate the Tomcat certificate, you must restart Tomcat. You can restart Tomcat after you regenerate all of the certificates on the local server. Use this CLI command to restart Tomcat: utils service restart Cisco Tomcat
Change the Domain Value
Follow this procedure if you want to change the domain value (from one valid domain value to another valid IP proxy domain value).
This procedure is applicable if you have a DNS or non-DNS deployment.
Note It is highly recommended that you use a DNS deployment. In order to be considered valid, the domain value must match the DNS domain name. Using a valid domain name ensures that the SRM initializes correctly in a High Availability deployment.
Procedure
Step 1 Stop the Cisco UP SIP Proxy, Presence Engine and XCP Router services on Cisco Unified Presence on all nodes in your cluster.
Step 2 On the publisher node, perform the following steps to configure the new domain value:
a. Select Cisco Unified Presence Administration > System > Cluster Topology.
b. In the right pane, select Settings.
c. Configure the Domain Name value with the new domain.
a. Select Cisco Unified Presence Administration > System > Service Parameters, and select the Cisco UP SIP Proxy service.
b. Configure the Federation Routing Cisco Unified Presence FQDN with the new domain.
c. You will be prompted to confirm these configuration changes. Select OK for both prompts, and then select Save.
Step 3 On all nodes in the cluster, use this CLI command to set the new domain:
set network domain <new_domain>
This CLI command invokes a reboot of the servers.
Step 4 On all nodes in the cluster, manually start the Cisco UP Presence Engine and Cisco UP XCP Router services after the reboot is complete (if required).
Step 5 Manually regenerate all certificates on each node in the cluster.
Note When you regenerate the Tomcat certificate, you must restart Tomcat. You can restart Tomcat after you regenerate all of the certificates on the local server. Use this CLI command to restart Tomcat: utils service restart Cisco Tomcat
Step 6 If you use DNS in your network, update the DNS configuration for the new domain. Update any host records and any DNS SRV records that you require for the new domain.
Step 7 Configure any XMPP clients with the new domain.
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
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
Further information regarding U.S. export regulations may be found at
http://www.access.gpo.gov/bis/ear/ear_data.html
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Copyright © 2012.Cisco Systems, Inc. All rights reserved.
Feedback
