Re: [OSL | CCIE_Voice] CUCM DB Replication Issues

2010-05-17 Thread Kevin Damisch
Behalf Of Matthew Berry Sent: Monday, May 17, 2010 8:07 AM To: Phil G Cc: OSL Group Subject: Re: [OSL | CCIE_Voice] CUCM DB Replication Issues Ok! I'll chock that reading error up to sleep deprivation. :) Matthew Berry **Sent from my iPhone** Skype/Twitter: ciscovoiceguru Google Voice: +1 612 4

Re: [OSL | CCIE_Voice] CUCM DB Replication Issues

2010-05-17 Thread Matthew Berry
Ok! I'll chock that reading error up to sleep deprivation. :) Matthew Berry **Sent from my iPhone** Skype/Twitter: ciscovoiceguru Google Voice: +1 612 424 5044 On May 17, 2010, at 5:51 AM, Phil G wrote: > Your replication is OK. You do not have any server with status 3, > you have a server

Re: [OSL | CCIE_Voice] CUCM DB Replication Issues

2010-05-17 Thread Phil G
Your replication is OK. You do not have any server with status 3, you have a server with ID = 2 and one with ID = 3, STATE is for both active. The "3" you mean has nothing to do with a replication status. It is just an ID. Matthew Berry wrote: >Can someone explain this to me? > > Below is

Re: [OSL | CCIE_Voice] CUCM DB Replication Issues

2010-05-17 Thread Angel Perez
e name will be unregistered or rejected in UCM GUI If both names are the same your replication is working hth Date: Sun, 16 May 2010 21:07:07 -0500 From: ciscovoiceg...@gmail.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] CUCM DB Replication Issues Can someone explain

Re: [OSL | CCIE_Voice] CUCM DB Replication Issues

2010-05-16 Thread CCIETalk.com
You shouldn't have to reboot. Turn services off on the broken server Remove from the group Run repair all Turn on the services Add it to the group Is this the order you tried? On 5/16/10, Matthew Berry wrote: > Can someone explain this to me? > > Below is my output from "show dbreplcation status

[OSL | CCIE_Voice] CUCM DB Replication Issues

2010-05-16 Thread Matthew Berry
Can someone explain this to me? Below is my output from "show dbreplcation status" after I issued a "utils dbreplication repair all" and reboot the Pub then Sub. I always though a status of 3 meant replication was broken, but the explanation below says that no errors or mismatches were found.