Table Of Contents
You must perform these procedures during a scheduled maintenance window.
Perform the tasks in the following procedure to ensure that your system is prepared for a successful IP address, hostname or domain change.
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.
Step 1 If you have more than one Cisco Unified Presence node in your deployment, check the database replication status to ensure that all servers are replicating database changes successfully. Enter 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
Note 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 and that you need to reset replication.
If replication is not set up, complete the following troubleshooting steps:
a. Reset replication by entering the following command on the publisher node:
utils dbreplication reset all
b. Run the following command again on the publisher node to check the replication status:
utils dbreplication runtimestate
Step 2 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
Note Steps 1 and 2 check the health of your deployment. The remainder of the tasks in this procedure are preconfiguration tasks that you must complete before you change an IP address, hostname, domain name or node name.
Step 3 Run a manual Disaster Recovery System backup and ensure that all nodes are backed up successfully.
Step 4 Disable High Availability (HA) on all subclusters. For more information about how to disable HA, see the Deployment Guide for Cisco Unified Presence.
Step 5 If you have intercluster peers configured in your deployment, complete the following steps:
a. For each cluster where the publisher node that you are changing is an intercluster peer, remove the publisher's cluster from the list of intercluster peers.
For example, ClusterA, ClusterB and ClusterC are all intercluster peers. You want to change the hostname on the publisher node of ClusterA. You must first remove the ClusterA publisher node from the list of intercluster peers on both ClusterB and ClusterC.
b. Restart the Cisco Intercluster Sync Agent on the publisher and subscriber nodes of the first subcluster in each cluster.
Step 6 If you are changing the Cisco Unified Presence server hostname for Release 8.6(4) or later, disable single sign-on (SSO). For more information about SSO, see the "Single Sign-On Configuration" section of the Deployment Guide for Cisco Unified Presence.
Step 7 Compile a list of all services that are currently activated:
a. To view the list of activated network services, log in to Cisco Unified Serviceability and select Tools > Control Center - Network Services.
b. To view the list of activated feature services, log in to Cisco Unified Serviceability and select Tools > Control Center - Feature Services.
You can refer to this list later when you need to reactivate services.
Step 8 Stop all feature services by selecting Tools > Control Center - Feature Services from the Cisco Unified Serviceability GUI. The order in which you stop feature services is not important.
Step 9 Stop all network services that are listed under the CUP Services group. To do this, select Tools > Control Center - Network Services from the Cisco Unified Serviceability GUI. You must stop the CUP Services network services in the following order:
1. Cisco UP Config Agent
2. Cisco UP Intercluster Sync Agent
3. Cisco Client Profile Agent
4. Cisco UP OAM Agent
5. Cisco UP XCP Config Manager
6. Cisco UP XCP Router
7. Cisco UP Presence Datastore
8. Cisco UP SIP Registration Datastore
9. Cisco UP Login Datastore
10. Cisco UP Route Datastore
11. Cisco UP Server Recovery Manager
12. Cisco UP Replication Watcher