[cisco-voip] cucm 6.1 replication problem

Scott Voll svoll.voip at gmail.com
Fri Sep 26 11:55:57 EDT 2008


I believe Jason is correct that your replication is in deed broke.

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.

Scott

On Wed, Sep 24, 2008 at 2:56 PM, Jason Burns <burns.jason at gmail.com> wrote:

> Your replication is indeed broken.
>
> 1. Run "utils dbreplication stop" on the subscriber  - wait for this to
> finish
> 2. Run "utils dbreplication stop" on the publisher - wait for this to
> finish
> 3. Run "utils dbreplication reset" on the publisher
>
> 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).
>
> -Jason
>
>
> On Wed, Sep 24, 2008 at 4:09 AM, l brahmam <lbrahmam at gmail.com> wrote:
>
>> 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.
>>
>> Thanks
>> Brahmam
>>
>>
>> On Tue, Sep 23, 2008 at 5:34 PM, Jason Burns <burns.jason at gmail.com>wrote:
>>
>>> Brahmam,
>>>
>>> You can run
>>>
>>> utils dbreplication status
>>>
>>> on the publisher, or view the Unified Reporting Tool pages, or RTMT to
>>> check your replication status.
>>>
>>> Here is an article with the procedure for resetting replication:
>>>
>>>
>>> http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00809643e8.shtml
>>>
>>> This was the first article that came up when I ran a Google search for
>>>
>>> cisco callmanager 6.1 database replication
>>>
>>> -Jason
>>>
>>>   On Tue, Sep 23, 2008 at 5:24 AM, l brahmam <lbrahmam at gmail.com> wrote:
>>>
>>>>   Hi
>>>>
>>>> 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.
>>>>
>>>> Thanks
>>>> Brahmam
>>>>
>>>>
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://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/20080926/b684fb66/attachment.html>


More information about the cisco-voip mailing list