Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CUCM PUB and SUB Replication Issue!!!

Hello All,

I have attached a file to explain everything. I have even tried deleting the Sub and reinstalling it. The reinstall goes fine but replication still fails. Weird!!! Help! Also followed the Solution below with no luck.

Solution

After you add a new subscriber to the cluster, the replication agreements and the actual replication are initiated only after the first reboot of each subscriber. So make sure you reboot the subscribers after you add them to the cluster. If you add many subscribers, reboot them one at a time in order to avoid overloading the publisher with the database replication.

Note:

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.

Procedure

If the replication status is shown as 4, which indicates that the replication is not setup correctly, complete these steps:

  1. Double check the current status of the publisher in order to ensure it can establish the agreement. For this you can export and provide the database report from http://<pub>/cucreports > System Reports > Unified CM Database Replication Debug or download the report from http://<pub>/cucreports > System Reports > Unified CM Database Status > Download report .
  2. Re-initiate the agreement for each subscriber, then wait and verify the status. When the nodes start to communicate, you can reset the replication per node. In order to reset the replication in each subscriber, complete these steps:
    1. Execute the utils dbreplication stop command on all subscribers.
      Note: Ensure that you had finished Step 2a on all subscribers and then only run the command mentioned in Step 2b on the publisher.
    2. Execute the utils dbreplication stop command on the publisher.
    3. Execute the utils dbreplication clusterreset command on the publisher.
      Note: This command resets database replication on an entire cluster. If there is replication issue with only one subscriber there is no need to execute the command. You may skip Step 2d and perform Step 2e.
    4. If all subscriber servers need to be reset, issue the utils dbreplication reset all command.
    5. At the publisher server, issue the utils dbreplication reset <hostname> CLI command where <hostname> is the hostname of the subscriber server that needs to be reset.
    Now verify that the database replication status is changed to 2, which means the replication setup is complete and working.


Performed on Sub first Sub

admin:utils dbreplication stop
********************************************************************************
This command will delete the marker file(s) so that automatic replication setup
It will also stop any replication setup currently executing
********************************************************************************

Deleted the marker file, auto replication setup is stopped

Service Manager is running
Commanded Out of Service
A Cisco DB Replicator[NOTRUNNING]
Service Manager is running
A Cisco DB Replicator[STARTED]

Completed replication process cleanup

Please run the command 'utils dbreplication runtimestate' and make sure all nodes are
RPC reachable before a replication reset is executed


Performed on Pub after Sub


admin:utils dbreplication stop
********************************************************************************************
This command will delete the marker file(s) so that automatic replication setup is stopped
It will also stop any replication setup currently executing
********************************************************************************************

Deleted the marker file, auto replication setup is stopped

Service Manager is running
Commanded Out of Service
A Cisco DB Replicator[NOTRUNNING]
Service Manager is running
A Cisco DB Replicator[STARTED]

Completed replication process cleanup

Please run the command 'utils dbreplication runtimestate' and make sure all nodes are
RPC reachable before a replication reset is executed

Performed on Pub Last


admin:utils dbreplication clusterreset

******************************************************************************** ************
This command will repair replication on all nodes in the cluster
Before running, execute dbreplication stop <server> on all subscribers
then execute dbreplication stop on the publisher
After clusterreset, "utils dbreplication reset all" should be executed
followed by the reboot of all subscribers
******************************************************************************** ************

This command can take considerable amount of time, and will tear down replicatio n and build it back again.
Are you sure you want to continue? (y/n):y

Repairing of replication is in progress.
You may tail /cm/trace/dbl/sdi/clusterReset_20120416205446.out to observe progre ss

admin:utils dbreplication reset all

This command will try to start Replication reset and will return in 1-2 minutes.

Background repair of replication will continue after that for 1 hour.

Please watch RTMT replication state. It should go from 0 to 2. When all subs

have an RTMT Replicate State of 2, replication is complete.

If Sub replication state becomes 4 or 1, there is an error in replication setup.

Monitor the RTMT counters on all subs to determine when replication is complete.

Error details if found will be listed below

OK [10.3.3.151]

OK [10.3.3.150]

1 REPLY
Silver

CUCM PUB and SUB Replication Issue!!!

Hello!

Need the following:

1. Call Manager Version

2. Topology, connectivity between call manager servers.

3. Screen shot of CM data base status report from the unified reporting page.

Check the following post as well:

https://supportforums.cisco.com/message/3183491#3183491

Once you post the above requested info, we can move forward accordingly..

HTH

Kunal

3762
Views
0
Helpful
1
Replies