McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 9

↗ View in doc context
page
9
source
cucm/v15/troubleshoot-db-replication/troubleshoot-db-replication.md
chunk_id
cucm::v15::troubleshoot-db-replication::troubleshoot-db-replication::7

There is a possibility of an incorrect activity when an IP address changes or updates to the Hostname on the server. Refer to this link in order to change IP address to the Hostname for the CUCM. IP Address and Hostname Changes Restart these services from the CLI of the publisher server and check if the mismatch is cleared. If yes, go to Step 8. If no, contact Cisco TAC. Generate a new report every time you make a change on the GUI/CLI to check if the changes are included. Cluster Manager ( utils service restart Cluster Manager) A Cisco DB ( utils service restart A Cisco DB) The Rhosts files are mismatched: If the Rhosts files are mismatched along with the host files, follow the steps mentioned under The Hosts files are mismatched. If only the Rhosts files are mismatched, run the commands from the CLI: A Cisco DB ( utils service restart A Cisco DB ) Cluster Manager ( utils service restart Cluster Manager) Generate a new report and check if the Rhost files are equivalent on all the servers. If yes, go to Step 8. If no, contact Cisco TAC. The Sqlhosts are mismatched: If the Sqlhosts are mismatched along with the host files, follow the steps mentioned under The Hosts files are mismatched. If only the Sqlhosts files are mismatched, run the command from the CLI: utils service restart A Cisco DB Generate a new report and check if the Sqlhost files are equivalent on all the servers. If yes, go to Step 8. If no, contact Cisco TAC Ensure that the Database Layer Remote Procedural Call (DBL RPC) hello is successful, as shown in this image. •

Page 9 content