I checked the DBReplication Status of my 5.1.1 cluster (1 pub and 2 subs), and though it took a long time to create the file, there was no output in it. I then performed a "utils dbreplaction stop" on the sub and a "util dbreplication reset <subscriber2>" and let it run through. Ever since that point I have been getting a "IDSReplicationFailure class_id : CDR DEFINE SERVER command failed on the subscriber class_msg : replstate = 3 specific_msg : We are in the svc routine of ReplTask trying to setup replication on Subscriber AppID : Cisco Database Layer Monitor ClusterID : UofLCCM NodeID : <subscriber2> " If someone can tell me what I have done wrong and how to get replication working againj through my cluster that would be awesome. This all precipitated from an attemot to upgrade from 5.1.1 to 5.1.3, the publisher could see the patch file, but the subscribers couldn't. I had read that if replication has failed that it can cause this to happen. Any help would be greatly appreciated.
The upgrade from 5.1.1 to 5.1.3 needs to be carried out initially on the Publisher before any subscriber, once the Publisher has been upgraded the Subscriber should then be able to see the upgrade image.
Can you confirm what the DB status is within RTMT, does is show the status of all nodes or only the Publisher and what the states are?
The sqlhosts file is present on each server and contains a reference for each Cisco Unified Communication Manager node in the cluster.
If those sqlhosts files are out of sync, the SQL replication fails. Use the show tech dbstateinfo CLI command in each subscriber in order to check the local sqlhosts at the
bottom of the output for any mismatch on each node.
If there are mismatches within this file these can only be modified through root access by TAC.