[cisco-voip] Publisher - Subscriber syncing

[Scott Voll]

I would bring up the sub and see if they automagically work.  check the
status.

then if it does not sync up them utils dbreplication stop on the sub -->
utils dbreplication reset sub on the pub and then check status.  remember it
could take some time to get sync'd up.

Scott

On Wed, Sep 24, 2008 at 12:59 AM, Anthony Kouloglou <akoul at dataways.gr>wrote:

> Hi Wes and Scott and thanks a lot for the replies.
>
> So, correct if i am wrong. When, the subscriber is not connected for some
> time in the cluster, when you plan to put it back:
>
> 1. before you connect the subscriber, issue the command: *utils
> dbreplication stop* on both servers
> 2. Connect the subscriber in the network and issue *utils dbreplication
> reset all *only on the subscriber; this should start the replication on
> all nodes. (I hope, data of the publisher only will replicate to the
> publisher and not vice versa!!)
> 3. Check with       *utils dbreplication status* the status of the
> replication.
>
> Thanks in advance
>
> Regards,
> Anthony Kouloglou
>
>
> Wes Sisk wrote:
>
> it depends, but most likely not.  even though you don't change anything
> there are still automated changes happening in the backend.  'utils
> dbreplication reset' will get you and going if replication has stopped.
> Scott's post is accurate on how to check replication state. You can also use
> the CLI command 'utils dbreplication status'
>
> admin:utils dbreplication ?
>       utils dbreplication clusterreset
>       utils dbreplication dropadmindb
>       utils dbreplication repair
>       utils dbreplication reset
>       utils dbreplication setrepltimeout
>       utils dbreplication status
>       utils dbreplication stop
>
> admin:help utils dbreplication reset
>
> utils dbreplication reset help:
> usage: utils dbreplication reset [nodename]|all
> Reset tears down and rebuilds replication. Use when replication setup has
> failed after install/upgrade
> You must execute "utils dbreplication stop" before using this command. If
> reset all, stop replication on all nodes first.
> If using reset <nodename>, stop replication on that node first.
>
> /Wes
>
> On 9/22/2008 8:18 AM, Anthony Kouloglou wrote:
>
> Hi, i have a 6.1(2) CUCM cluster.
> For some reasons, subscriber was out of the network for a couple of days
> (but none change occured to it).
> We changed some things in the publisher : added some phones, edited some
> others.
> As soon as i plugged in the subscriber in the network will it sync with the
> publisher and get the latest changes?
> How can i monitor the process and know it has finished?
>
> Chears,
> Anthony
>
> ------------------------------
>
> _______________________________________________
> cisco-voip mailing listcisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> 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/20080924/b1b60f7d/attachment.html>