Which three steps will resolve the replication problem?

Refer to the exhibit. Users on a four-node CUCM cluster are reporting call problems when attempting to call out to internal extension and PSTN. An engineer troubleshooting issue found a replication of the cluster is in status 4.
Which three steps will resolve the replication problem? (Choose Three)


A. run the command utils dbreplication dropadmindb on all subscribers
B. run the command utils dbreplication repairable all from the publisher
C. run the command utils dbreplication stop on the publisher
D. run the command utils dbreplication reset all from the publisher
E. run the command utils dbreplication repair all from the publisher
F. run the command utils dbreplication stop on all subscribers

cisco-exams

2 thoughts on “Which three steps will resolve the replication problem?

  1. C, A, D
    Step 8. Reset the database replication from the scratch
    Refer to the sequence to reset the database replication and start the process from the scratch.
    utils dbreplication stop all (Only on the publisher)
    utils dbreplication dropadmindb (First on all the subscribers one by one then the publisher)
    utils dbreplication reset all ( Only on the publisher )

    1. The cluster is a 5 node cluster.
      The publisher is in Replication State = 3
      All subscribers in the cluster are in Replication State = 4
      We check in the report for Replication Server List and only the publisher shows local as connected. This verifies to us that based on our descriptions the servers are indeed in the states listed above.
      We now do some other checks to prepare to fix replication. We verify in the report that all of the hosts files look correct. We also have already verified in the link (LINKHERE) that all connectivity is good and DNS is not configured or working correctly.

      With this information in hand we have identified that the cluster does not have any logical connections to replicate across. Thus the recommendation to the customer would be to follow the most basic process that fixes about 50 percent of replication cases. Below are these steps.

      utils dbreplication stop on all subscribers. This command can be run on all subscribers at the same time but needs to complete on all subscribers prior to being run on the publisher. The amount of time this command takes to return is based on your cluster’s repltimeout. This can be seen through the Command show tech repltimeout and by default is 300 seconds or 5 minutes. At the end of this document I will provide a calculation for determining what you should set your repltimeout (via utils dbreplication setrepltimeout) in your cluster and how this value affects replication. (If utils dbreplication stop all is available (7.X and later) then step 1 and step 2 can be accomplished in this one command)
      utils dbreplication stop on publisher. Again this command can be done through the utils dbreplication stop all if available. This also will wait the repltimeout as said above.
      utils dbreplication reset all – This command will take an hour to complete or longer depending on your cluster. You can monitor the status through the utils dbreplication runtimestate or through the procedure following the examples portion of this document.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.