<div dir="ltr"><div>I would bring up the sub and see if they automagically work. check the status.</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Wed, Sep 24, 2008 at 12:59 AM, Anthony Kouloglou <span dir="ltr"><<a href="mailto:akoul@dataways.gr">akoul@dataways.gr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div text="#000066" bgcolor="#ffffff"><font face="Times New Roman">Hi Wes and Scott and thanks a lot for the replies.<br><br>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:<br>
<br>1. before you connect the subscriber, issue the command: </font><i>utils dbreplication stop</i> on both servers<br>2. Connect the subscriber in the network and issue <i>utils dbreplication reset all </i>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!!)<br>
3. Check with <i>utils dbreplication status</i> the status of the replication.<br><br>Thanks in advance<br><br>Regards,<br><font color="#888888">Anthony Kouloglou</font>
<div>
<div></div>
<div class="Wj3C7c"><br><br>Wes Sisk wrote:
<blockquote type="cite">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'<br>
<br>admin:utils dbreplication ?<br> utils dbreplication clusterreset<br> utils dbreplication dropadmindb<br> utils dbreplication repair<br> utils dbreplication reset<br> utils dbreplication setrepltimeout<br>
utils dbreplication status<br> utils dbreplication stop<br><br>admin:help utils dbreplication reset<br><br>utils dbreplication reset help:<br>usage: utils dbreplication reset [nodename]|all<br>Reset tears down and rebuilds replication. Use when replication setup has failed after install/upgrade<br>
You must execute "utils dbreplication stop" before using this command. If reset all, stop replication on all nodes first.<br>If using reset <nodename>, stop replication on that node first.<br><br>/Wes<br><br>
On 9/22/2008 8:18 AM, Anthony Kouloglou wrote:
<blockquote type="cite"><font face="Times New Roman">Hi, i have a 6.1(2) CUCM cluster.<br>For some reasons, subscriber was out of the network for a couple of days (but none change occured to it).<br>We changed some things in the publisher : added some phones, edited some others.<br>
As soon as i plugged in the subscriber in the network will it sync with the publisher and get the latest changes?<br>How can i monitor the process and know it has finished?<br><br>Chears,<br>Anthony<br></font><pre><hr width="90%" size="4">
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre></blockquote></blockquote></div></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>