Cisco Unified Presence, Release 7.x -- Post-Change Task List
Main page: Cisco Unified Presence, Release 7.x
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 FQDN parameter to point to the new server address. In Cisco Unified Presence Administration, perform the following tasks:
- Choose System > Service Parameters > Cisco UP SIP Proxy.
- Change the clusterwide federation routing parameter (Federation Routing CUP FQDN) to the new FQDN
1. Run this command to restart all nodes in the cluster:
- run utils dbreplication reset all
2. Ensure that all servers in the cluster are running 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.
If you use: Action
Access Alert Central and check for ServerDown alerts.
Enter the following command and inspect the application event log:
- file search activelog syslog/CiscoSyslog ServerDown
3. 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
Access the Database Summary and inspect the replication status as follows:
- Select System > Performance in the RTMT.
- Check the values of these counters, that display under "Number of Replicates Created and State of Replication":
- Number of Replicates Created
Enter the command that is shown in the following example:
admin: show perf query class "Number of Replicates Created and State of Replication"
==>query class :
- - 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.
4. Run a manual DRS backup and ensure that all nodes and active services are backed up successfully.
5. 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.
6. 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/H.323 trunks
- SFTP servers that are used for Cisco Unified Presence server trace collection or as a DRS backup destination
- Cisco Unified Personal Communicator
- Associated routers and gateways
- Third-party clients, such as IBM Lotus Sametime
- 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.