my attachment show replication status after deleting node server and then restarting the cluster. we can see that g_idgn2ucmsub03 still exist in Cisco Unified Reporting and make the other server to try connecting to.
Note that if replication is bad and you reboot the cluster, it can take up to an hour or more (depending on DB size and other factors - such as hardware, etc) before replication fully completes and changes state. However, there is no harm in running the DB repair command from CLI; however, make sure you follow instructions on how to do this. If I remember correctly, you should issue a stop comand on each server before running the repair. From there, you should watch replication via RTMT and remember that it will take some time for the cluster to repair itself.
Out of curiousity, when you removed the server from the cluster - did you delete the server and CM configuration within the CCM Admin page as well?
Before doing the dbreplication reset. Do the following on each cucm node:
From the CLI on each server:
1. "run sql select name from processnode"
2. "show network cluster"
3. "show tech network hosts"
4. "utils diagnose module validate_network"
Look for inconsistencies in output data across each cluster node. Look for any data values in the output of each command that disagrees with other commands. Look for anything you weren't expecting or think is erroneous. Look for any failures in "validate_network". You are likely to see a failure related to the CUCM node that you removed. Any errors outside of that?
If you prefer, post the output but make sure you include all nodes.
A dbreplication reset may be necessary (sounds likely). You will want to validate_network (see above, command 4). A dbreplication stop on non-publisher nodes may be necessary but I have found mixed guidance from cco docs on this. Certainly it wouldn't hurt. Make sure you read up on the "utils dbreplication " commands first.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...