<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
'utils ntp status' on both servers will give you the current time and timezone. The sub should be using the pub as an NTP server and if for some reason the times are not sync'd replication will fail.<div><br><div> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">-Ryan</font></p> </div><br><div><div>On Feb 6, 2009, at 4:22 AM, l brahmam wrote:</div><br class="Apple-interchange-newline">Hi<br><br>Kindly find the attachment for timezones configured on both. Let me know the command different to check and change the timezone.<br><br>Thanks<br>Brahmam<br><br><div class="gmail_quote">On Fri, Feb 6, 2009 at 7:24 AM, Samuel Womack <span dir="ltr"><<a href="mailto:womacksamuel@gmail.com">womacksamuel@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="">And be extremely PATIENT....<div>Seriously, Be PATIENT...</div><div><div></div> <div class="Wj3C7c"><div><br></div><div><br><div><div>On Feb 5, 2009, at 7:50 PM, Jason Burns wrote:</div><br><blockquote type="cite">Sorry for the confusion. Here is what step 3 should read:<br><br>3. In the SSH Admin CLI of the Publisher server run the following command<br> <br>utils dbreplication reset <name of the problem subscriber><br><br><br> <br><div class="gmail_quote">On Wed, Feb 4, 2009 at 6:03 AM, James Buchanan <span dir="ltr"><<a href="mailto:jbuchanan@ctiusa.com" target="_blank">jbuchanan@ctiusa.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div link="blue" vlink="purple" lang="EN-US"> <div><p><span style="font-size: 11pt; color: rgb(31, 73, 125);">I had this same issue recently. NTP had failed on the Publisher and the Publisher had the wrong time. The Subscriber had close to the right time. The servers were an hour apart from each other. Once we got the time the same on the two servers synchronization would work.</span></p> <div><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span><br></div> <div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;"><p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>l brahmam<br> <b>Sent:</b> Wednesday, February 04, 2009 1:29 AM<br> <b>To:</b> Scott Voll<br> <b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br> <b>Subject:</b> Re: [cisco-voip] cucm 6.1 replication problem</span></p> </div><div><div></div><div><div> <br></div> <div><p style="margin-bottom: 12pt;">Hi <br> <br> I have executed <br> <br> <span style="color: rgb(84, 141, 212);">1. Run "utils dbreplication stop" on the subscriber - wait for this to finish<br> 2. Run "utils dbreplication stop" on the publisher - wait for this to finish<br> 3. Run "utils dbreplication reset" on the subscriber as its not allowing me to run on publisher.<br> <br> Kindly find below for output of commands and suggest me how can i make replication works fine.<br> <br> </span>[root@lurtz ~]# ssh <a href="mailto:admin@192.168.101.21" target="_blank">admin@192.168.101.21</a><br> <a href="mailto:admin@192.168.101.21" target="_blank">admin@192.168.101.21</a>'s password:<br> Last login: Mon Jan 5 00:57:32 2009 from 10.1.2.80<br> <br> Welcome to the Platform Command Line Interface<br> <br> Uptime : 05:14:07 up 201 days, 6 min, 1 user,<br> Load average : 0.13, 0.10, 0.09<br> Platform OS version : UCOS 3.0.0.0-56<br> HW model : 7825H3<br> <br> admin:exit<br> <br> <br> <br> Copyright Cisco Systems 2006<br> Connection to 192.168.101.21 closed.<br> [root@lurtz ~]# ssh <a href="mailto:admin@192.168.101.20" target="_blank">admin@192.168.101.20</a><br> <a href="mailto:admin@192.168.101.20" target="_blank">admin@192.168.101.20</a>'s password:<br> Last login: Mon Dec 22 01:56:05 2008 from 10.1.2.80<br> <br> Welcome to the Platform Command Line Interface<br> <br> Uptime : 06:15:18 up 19 days, 18:12, 1 user,<br> Load average : 1.15, 0.66, 0.59<br> Platform OS version : UCOS 3.0.0.0-56<br> HW model : 7825H3<br> <br> admin:utils dbreplication stop<br> ********************************************************************************************<br> This command will delete the marker file(s) so that automatic replication setup is stopped<br> It will also stop any replication setup currently executing<br> ********************************************************************************************<br> <br> Deleted the marker file, auto replication setup is stopped<br> <br> Service Manager is running<br> A Cisco DB Replicator[STOPPING]<br> A Cisco DB Replicator[STOPPING]<br> Commanded Out of Service<br> A Cisco DB Replicator[NOTRUNNIG]<br> Service Manager is running<br> A Cisco DB Replicator[STARTED]<br> Completed replication process cleanup<br> admin:exit<br> <br> <br> <br> Copyright Cisco Systems 2006<br> Connection to 192.168.101.20 closed.<br> You have new mail in /var/spool/mail/root<br> [root@lurtz ~]# ssh <a href="mailto:admin@192.168.101.21" target="_blank">admin@192.168.101.21</a><br> <a href="mailto:admin@192.168.101.21" target="_blank">admin@192.168.101.21</a>'s password:<br> Last login: Tue Feb 3 05:14:07 2009 from 10.1.2.1<br> <br> Welcome to the Platform Command Line Interface<br> <br> Uptime : 05:31:36 up 201 days, 23 min, 1 user,<br> Load average : 0.06, 0.10, 0.09<br> Platform OS version : UCOS 3.0.0.0-56<br> HW model : 7825H3<br> <br> admin:utils dbreplication stop<br> ********************************************************************************************<br> This command will delete the marker file(s) so that automatic replication setup is stopped<br> It will also stop any replication setup currently executing<br> ********************************************************************************************<br> <br> Deleted the marker file, auto replication setup is stopped<br> <br> Service Manager is running<br> A Cisco DB Replicator[STOPPING]<br> A Cisco DB Replicator[STOPPING]<br> Commanded Out of Service<br> A Cisco DB Replicator[NOTRUNNIG]<br> Service Manager is running<br> A Cisco DB Replicator[STARTED]<br> Completed replication process cleanup<br> admin:utils dbreplication reset IndiaCCM61-Prim<br> You have entered nodename as publisher node. You must enter subscriber node name.<br> <br> Executed command unsuccessfully<br> <br> admin:utils dbreplication reset IndiaCCM61-Sec<br> Repairing of replication is in progress.<br> Background repair of replication will continue after that for 30 minutes..<br> <br> admin:<br> <br> Thanks<br> Brahmam.<br> <br> i could be see the status on both servers as 2. currently i have hostnames seperately on server. Kindly let me know does it cause any issue.<br> <br> </p> <div><p>On Fri, Sep 26, 2008 at 9:25 PM, Scott Voll <<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>> wrote:</p> <div> <div><p>I believe Jason is correct that your replication is in deed broke.</p> </div> <div><div> <br></div> </div> <div><p>but as an FYI you might not see these with both server with a 2. I had the same problem and host names (even though they could ping each) it didn't fix until I changed the host names to IP addresses.</p> </div> <div><div> <br></div> </div> <div><p style="margin-bottom: 12pt;"><span style="color: rgb(136, 136, 136);">Scott</span></p> </div> <div> <div> <div><p>On Wed, Sep 24, 2008 at 2:56 PM, Jason Burns <<a href="mailto:burns.jason@gmail.com" target="_blank">burns.jason@gmail.com</a>> wrote:</p> <div><p>Your replication is indeed broken.<br> <br> 1. Run "utils dbreplication stop" on the subscriber - wait for this to finish<br> 2. Run "utils dbreplication stop" on the publisher - wait for this to finish<br> 3. Run "utils dbreplication reset" on the publisher<br> <br> After that churns for a while you should see your replication status go back to 2 (as long as you don't have any network connectivity problems between the servers).<br> <span style="color: rgb(136, 136, 136);"><br> -Jason</span> </p> <div> <div><div style="margin-bottom: 12pt;"> <br></div> <div><p>On Wed, Sep 24, 2008 at 4:09 AM, l brahmam <<a href="mailto:lbrahmam@gmail.com" target="_blank">lbrahmam@gmail.com</a>> wrote:</p> <div><p>Kindly find the attachment for the current status of my CUCM and suggest me if i can run dbreplication reset command on both publisher and subscriber.<br> <br> Thanks<br> <span style="color: rgb(136, 136, 136);">Brahmam</span> </p> <div> <div><div style="margin-bottom: 12pt;"> <br></div> <div><p>On Tue, Sep 23, 2008 at 5:34 PM, Jason Burns <<a href="mailto:burns.jason@gmail.com" target="_blank">burns.jason@gmail.com</a>> wrote:</p> <div><p style="margin-bottom: 12pt;"> Brahmam,<br> <br> You can run<br> <br> utils dbreplication status<br> <br> on the publisher, or view the Unified Reporting Tool pages, or RTMT to check your replication status.<br> <br> Here is an article with the procedure for resetting replication:<br> <br> <a href="http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00809643e8.shtml" target="_blank">http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00809643e8.shtml</a><br> <br> This was the first article that came up when I ran a Google search for<br> <br> cisco callmanager 6.1 database replication<br> <span style="color: rgb(136, 136, 136);"><br> -Jason</span></p> <div> <div> <div><p>On Tue, Sep 23, 2008 at 5:24 AM, l brahmam <<a href="mailto:lbrahmam@gmail.com" target="_blank">lbrahmam@gmail.com</a>> wrote:</p> </div> </div> <blockquote style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204); border-width: medium medium medium 1pt; padding: 0in 0in 0in 6pt; margin-left: 4.8pt; margin-right: 0in;"> <div> <div> <div> <div><p>Hi </p> </div> <div><div> <br></div> </div> <div><p>We have CUCM 6.1 publisher and subscriber, if i add a device to publisher its not reflecting at subscriber. I hope problem with db replication. Kindly help me and provide the information to fix the same.</p> </div> <div><div> <br></div> </div> <div><p>Thanks</p> </div> <div><p>Brahmam</p> </div> <div><div> <br></div> </div> </div><div> <br></div> </div> </div> <div><p style="margin-bottom: 12pt;">_______________________________________________<br> cisco-voip mailing list<br> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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></p> </div> </blockquote> </div><div> <br></div> </div> </div><div> <br></div> </div> </div> </div> </div><div> <br></div> </div> </div> </div><p style="margin-bottom: 12pt;"><br> _______________________________________________<br> cisco-voip mailing list<br> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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></p> </div><div> <br></div> </div> </div> </div> </div><div> <br></div> </div> </div></div><p><span style="font-size: 10pt;">No virus found in this incoming message.<br> Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br> Version: 8.0.233 / Virus Database: 270.10.17/1932 - Release Date: 02/03/09 07:57:00</span></p> </div> </div> <br>_______________________________________________<br> cisco-voip mailing list<br> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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> _______________________________________________<br>cisco-voip mailing list<br> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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> </blockquote></div><br></div></div></div></div></blockquote></div><br><br clear="all"><br>-- <br>--<br> \\\||///<br> \\ - - //<br> ( @ @ )<br>-oOo--( )--oOo-------------------------------------------------------<br> <span><publishertime.jpg></span><span><subscribertime.jpg></span><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">cisco-voip mailing list</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div> </div><br></div></body></html>