Hello Hesham, You can be running into this bug : http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtb59167
Can you please send me the output for the command utils dbreplication runtimestate ? On Mon, Apr 22, 2013 at 5:53 AM, Hesham Abdelkereem < heshamcentr...@gmail.com> wrote: > > > ---------- Forwarded message ---------- > From: Hesham Abdelkereem <heshamcentr...@gmail.com> > Date: 22 April 2013 01:52 > Subject: Re: [OSL | CCIE_Voice] Subscriber failure > To: William Bell <b...@ucguerrilla.com> > > > Hi Bill, > > In Reference to this e-mail I have changed the ip address of the Pub and > Sub and followed this steps > > > http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/ipchange/ipchg712.html#wp42070 > > as well as and I followed your steps mentioned earlier in this e-mail > below. > > However when I have done utils dbreplication forcedatasyncsub all > I got this error message attached in the attachment. > However , I have tried the following solutions > > utils network host cucm7sub from publisher and subscriber it gives the > correct names with addresses > > I have done that also on pub and sub > > run sql select name,nodeid from ProcessNode > and it shows correct and proper new ip addresses > > > when I have performed the test > > utils diagnose module validate_network > it return Primary DNS server Failed. > > Actually , there is no DNS reliance , I killed the instances of DNS > everywhere and I don't know why it shows that error. > > So , I still have DB replication issues following the above and below > steps. > > Your kind help would be highly appreciated. > > Thanks, > Hesham > On 3 April 2013 09:10, William Bell <b...@ucguerrilla.com> wrote: > >> You definitely have a replication issue. You cannot go by the Unified >> Reporting or by the perf counters (RTMT or from the CLI) as a valid >> indication of replication health. I know that sucks but it's true. >> >> I recommend using the CLI command: "utils dbreplication status all" from >> the Publisher >> >> In practice (and in the real lab) I use the following approach since NTP >> seams to be where replication could fall apart on you: >> >> >> 1. Make sure that if you are using HQ, BR1, BR2 or some other device you >> "control" in the lab as the NTP source for CUCM that that NTP server is >> associated to a valid NTP clock source and is synchronized. Very important >> step. >> >> 2. Set the NTP server on the Pub as you normally would >> >> 3. SSH to Pub and use "utils ntp status" command to ensure that time in >> synchronized. If it does not sync then look at step 1 and you will need to >> restart NTP on the pub. >> >> 4. SSH to Sub (after Pub is sync'd) and use the "utils ntp restart" >> command to restart NTP. You could check status beforehand if you want but >> you'll need to restart NTP 99.999% of the time. >> >> 5. Use "utils ntp status" on Sub to verify sync status. Once sync'd, >> proceed to 6. >> >> 6. Use "utils dbreplication status all" from Publisher to check >> replication status. >> >> >> If you see a db replication issue, I'd recommend fixing it. Various >> methods exist. The method I use for this lab: >> >> 1. Subscriber: utils dbreplication stop >> >> 2. Publisher: utils dbreplication stop >> >> 3. Once publisher has stopped replicating: utils dbreplication >> forcedatasyncsub all >> >> 4. Reload Subscriber >> >> This all takes 10 - 15 minutes, so try to avoid stupid mistakes and also >> try to catch dbreplication issues early on >> >> >> -Bill >> >> >> -- >> William Bell >> blog: http://ucguerrilla.com >> twitter: @ucguerrilla >> >> >> >> On Apr 2, 2013, at 1:14 PM, Hesham Abdelkereem wrote: >> >> > Dear Experts, >> > >> > I was working yesterday on one of the online Rack Rentals. >> > I have registered all Phones , Gateways and everything to the >> Subscriber. >> > Something is very odd. >> > I was unable to make any calls from the phone at all and the calls were >> not reaching the gateway. >> > I have deleted the SLRG and Recreated, Delete all Route Patterns and >> then Recreated them again. >> > Deleted all Route Groups and recreated them again. >> > Disassociated LRG from Device Pool and Recreated them Again never >> worked. >> > Restarted all Device Pool , Phones and Gateways never worked. >> > However, When I shut down the subscriber and when it was restarting and >> everything fails over on Publisher then everything works perfectly and as >> soon as the Subscriber comes back everything is ruined. >> > However , NTP Server is configured properly , Checked DB replication in >> Unified Reporting and it's good status. >> > All Endpoints shows registered successfully but I am unable to perform >> calls. >> > All Devices are configured with the correct Device Pool and Correct CSS. >> > So what's likely other problem that makes the subscriber fail? >> > I restarted it and as soon as it comes back nothing works. >> > >> > Thanks a lot for your great efforts. >> > >> > Hesham >> > _______________________________________________ >> > For more information regarding industry leading CCIE Lab training, >> please visit www.ipexpert.com >> > >> > Are you a CCNP or CCIE and looking for a job? Check out >> www.PlatinumPlacement.com <http://www.platinumplacement.com/> >> >> > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > -- Rafael Chavantes
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
