Post-Change Tasks Cisco Unified Communications Manager Nodes
Perform all post-change tasks to ensure that your changes are properly implemented in your deployment.
If you do not receive the results that you expect when you perform these tasks, do not continue until you have resolved the issue.
If you have DNS configured anywhere on the Cisco Unified Communications Manager servers, ensure that a forward and reverse lookup zone has been configured and that the DNS is reachable and working.
Check for any active ServerDown alerts to ensure that all servers in the cluster are up and available. Use either the Cisco Unified Real-Time Monitoring Tool (RTMT) or the command line interface (CLI) on the first node.
Check the database replication status on all nodes in the cluster to ensure that all servers are replicating database changes successfully.
For IM and Presence Service, check the database replication status on the database publisher node using the CLI if you have more than one node in your deployment.
Use either Unified RTMT or the CLI. All nodes should show a status of 2.
Enter the CLI command
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 admin:
If you are performing the pre-change system health checks, you are done; otherwise, continue to perform the post-change verification steps.
Verify that the new hostname or IP address appears on the Cisco Unified Communications Manager server list. In Cisco Unified Communications Manager Administration, select .
Verify that changes to the IP address, hostname, or both are fully implemented in the network. Enter the CLI command
The output should contain the new IP address or hostname of the node.
admin:show network cluster 10.63.70.125 hippo2.burren.pst hippo2 Subscriber cups DBPub authenticated 10.63.70.48 aligator.burren.pst aligator Publisher callmanager DBPub authenticated using TCP since Wed May 29 17:44:48 2013
Verify that changes to the hostname are fully implemented in the network. Enter the CLI command
The output should confirm that the new hostname resolves locally and externally to the IP address.
admin:utils network host hippo2 Local Resolution: hippo2.burren.pst resolves locally to 10.63.70.125 External Resolution: hippo2.burren.pst has address 10.63.70.125
For security-enabled clusters (Cluster Security Mode 1 - Mixed), update the CTL file and then restart all nodes in the cluster before you perform the system health checks and other post-change tasks.
For more information, see the Certificate and ITL Regeneration for Multi-Server Cluster Phones section.
If you enabled cluster security using Certificate Trust List (CTL) files and USB eTokens, you must regenerate the Initial Trust List (ITL) file and the certificates in the ITL if you changed the IP address or hostname for Release 8.0 or later nodes. Skip this step if you have not enabled cluster security using Certificate Trust List (CTL) files and USB eTokens.
Run a manual DRS backup and ensure that all nodes and active services back up successfully.
For more information, see the Administration Guide for Cisco Unified Communications Manager .
Update all relevant IP phone URL parameters.
Update all relevant IP phone services using Cisco Unified Communications Manager Administration. Choose.
Update Unified RTMT custom alerts and saved profiles.
If you are using the integrated DHCP server that runs on Cisco Unified Communications Manager, update the DHCP server.
Check and make any required configuration changes to other associated Cisco Unified Communications components.