DB Rep status =2 but report shows servers not RTMT reachable
i have a cluster of 5 servers.
All 5 when running the CLI Command "utils dbreplication runtimestate" Show a DB Replication state of 2 (good)
When i run the unified CM Database status report from the GUI on the publisher i get the following; It reports all subscribers are not contactable via RTMT, however - everything else is good (CMhosts good Rhosts good connectivity check good ping good, CM SQL hosts good all is good!)
When i run the same report from any of the subscribers, they only list the publisher as being unreachable from RTMT. All other servers are reachable from RTMT just fine, and all other things (CM Rhosts etc) are also good. This happened after i upgraded from CM 184.108.40.2060-26 to 220.127.116.1100-5 to get around the cosmetic bug "the onconfig file does not match the publisher" when running this same report.
Now the onconfig file matches but apparently RTMT connection does not work!
The RTMT reporter servlet is up and started just fine, and I have rebooted all servers in the cluster twice already since the upgrade to try and fix this.
admin:utils dbreplication runtimestate
DB and Replication Services: ALL RUNNING
Cluster Replication State: Replication status command started at: 2011-11-01-15-31 Replication status command COMPLETED 530 tables checked out of 530 No Errors or Mismatches found.
Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2011_11_01_15_31_27.out' to see the details
DB Version: ccm8_5_1_13900_5 Number of replicated tables: 530
Please help, im not sure where to go with this? One of my friends suggested doing a dbreplication stop across the whole cluster and then dropadmindb and rebuild replication but to me this is not a replication issue but an RTMT one?
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...