Table Of Contents

Post-Change Task List

Post-Change Task List

---

November 28, 2012

Complete this procedure after you finish changing the IP address, hostname or domain of your cluster.

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 IM and Presence nodes in the cluster to ensure all servers are replicating database changes successfully. You can check by using the following CLI command.

utils dbreplication runtimestate 

---

Note The REPLICATION SETUP (RTMT) & details value for all nodes must be 2.

---

Step 3 If you completed Step 9 in the Readiness Checklist, add the cluster whose publisher/subscriber hostname/IP address was changed to each peer-cluster publisher node.

Step 4 If you disabled SSO prior to performing a 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 IM and Presence Service on Cisco Unified Communications Manager.

Step 5 Run a manual DRS backup and ensure that all nodes and active services are backed up successfully.

Step 6 If the IP address for the server has been changed, 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 7 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 IM and 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 8 On all nodes, verify that services are running. If you need to start services, use the following commands to start the IM and Presence services in the following order:

•utils service start Cisco XCP Config Manager

•utils service start Cisco Route Datastore

•utils service start Cisco Login Datastore

•utils service start Cisco SIP Registration Datastore

•utils service start Cisco Presence Datastore

•utils service start Cisco XCP Router

•utils service start Cisco Sync Agent

•utils service start Cisco SIP Proxy

•utils service start Cisco OAM Agent

•utils service start Cisco Presence Engine

•utils service start Cisco Client Profile Agent

•utils service start Cisco Intercluster Sync Agent

•utils service start Cisco Config Agent

Step 9 If High Availability (HA) was disabled before the hostname or IP address change, enable HA on all subclusters. Select System > Cluster Topology in Cisco Unified CM IM and Presence Administration. For more information about how to enable HA, see the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager.

Step 10 You must run a manual DRS backup after you change the IP address or hostname 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

•Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager