When the command utils dbreplication status is executed on the Cisco Unified Communications Manager CLI, which step should be taken next to check the database replication status?

When the command utils dbreplication status is executed on the Cisco Unified Communications Manager CLI, which step should be taken next to check the database replication status?
A. View the activelog file.
B. Run the same command on all nodes of the cluster.
C. Restart the Cisco CallManager service.
D. The command utils dbreplication runtimestate must be run on the publisher.
E. The command utils dbreplication runtimestate must be run on the subscriber.

cisco-exams

4 thoughts on “When the command utils dbreplication status is executed on the Cisco Unified Communications Manager CLI, which step should be taken next to check the database replication status?

  1. My initial thought was D as that is what I use to verify that replication is good in my cluster, even though I know that it states to check the active log file. Even Cisco TAC will have you use the runtimestate command.

    The key word in the question here is “Status” which is only shown using the file view activelog command.

    The output of view activelog [file path] shows the following categories:
    SERVER ID STATE STATUS QUEUE CONNECTION CHANGED

    The output of utils dbreplication runtimestate shows the following categories:
    PING DB/RPC/ REPL. Replication REPLICATION SETUP
    SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group ID (RTMT) & Details

    1. After you run the command, it actually tells you ” Please use: “File view active log, followed by the file path.

Leave a Reply

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


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