[cisco-voip] DB Replication State on CUCM 6.1.1a

[Justin Steinberg]

check the sqlhosts file within the same cm database status report.  Do you
see any stale records in this file?  If so, this could be contributing to
your problem.  This file seems to be the master record for the informix
replication process and It seems like if there is a bad record in this file,
it can prevent proper replication between CM nodes.

In my case, I had to open a TAC case and they had to root in and edit the
file.  After editing the file, I had to run the utils dbreplcation
clusterreset command.


On Tue, Mar 25, 2008 at 3:11 PM, Adam <cisco at adman.net> wrote:

> I installed a new subscriber into a cluster and the DB replication state
> is "4 - Setup Failed" the number of replicates is correct across all three
> node and changes seem to be replicated between nodes just fine. I tried
> doing a "utils dbreplication stop nodex" and "utils dbreplication reset
> nodex" but the status is still stuck at 4. Any suggestions?
>
> As an extra piece of information this node was originally installed with
> DNS enabled, whereas it is disabled on the two original nodes. This seemed
> to cause some issues so I reinstalled the new subscriber with DNS disabled.
> I now have some extra entries on the Rhosts file on one of the servers so
> the "Unified CM Database Status" report shows an error for Rhosts as well as
> the replication state error.
>
> -Adam
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080325/8e725769/attachment-0001.html