<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-7" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000066">
<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>
Anthony Kouloglou<br>
<br>
Wes Sisk wrote:
<blockquote cite="mid:48D91CF8.2020702@cisco.com" type="cite">
<meta content="text/html;charset=ISO-8859-7" http-equiv="Content-Type">
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 cite="mid:48D78D0D.1040004@dataways.gr" 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 wrap=""><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</blockquote>
</body>
</html>