Cisco Unified Presence, Release 7.x -- Readiness Checklist
Main page: Cisco Unified Presence, Release 7.x
Perform the following tasks to ensure that your system is prepared for a successful IP address 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.
1. List all servers in the cluster and note whether the nodes are defined by using IP addresses or host names.
- From Cisco Unified Presence Administration on the first node, navigate to System > Topology.
- Check the list of available servers in the left frame of the Topology window, and capture this list for later reference.
2. Ensure that you have saved an inventory of both the host name and IP address of each node in your cluster.
3. 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
4. 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
1.Access the Database Summary and inspect the replication status as follows:
- Select System > Performance in the RTMT.
2. 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"
- - 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.
5. To check network connectivity and DNS server configuration, 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
- Diagnostics Completed
6. Run a manual DRS backup and ensure that all nodes and active services are backed up successfully.
What To Do Next