We are using admin. TAC had me reboot the server. I didn't want to do this as we have had this problem before and I knew this would resolve it. I was hoping that before we rebooted we could find a root cause.

After rebooting, web access was available. Here is the CLI output after rebooting showing some form of db replication error.

First issued this command:

admin:utils dbreplication status

******************************************************************************** ********************

This command reads and writes database information from all machines and will ta ke quite some time...please be patient.

******************************************************************************** ********************

-------------------- utils dbreplication status --------------------

Error returned -1 at 1321

Error returned -1 at 802

command failed -- General Error (-1) (-1)

Output is in file cm/trace/dbl/sdi/ReplicationStatus.083700.out

admin:

Then issued the following command with the name of the file *.out:

admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.083700.out

SERVER ID STATE STATUS QUEUE CONNECTION CHANGED

-----------------------------------------------------------------------

g_cucm_ccm 2 Active Local 0

g_cucm_subscriber_ccm 3 Active Connecting 5640359

-------------------------------------------------

utils dbreplication status output

To determine if replication is suspect, look for the following:

(1) Number of rows in a table do not match on all nodes.

(2) Non-zero values occur in any of the other output columns for a table

(3) ***** PLEASE IGNORE MISMATCHES IN ReplicationDynamic TABLE *****

First a summary of replication servers and their server status is provided

options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 20 of 23)

Error returned -1 at 1321

Error returned -1 at 802

command failed -- General Error (-1) (-1)

end of the file reached

options: q=quit, n=next, p=prev, b=begin, e=end (lines 21 - 23 of 23)