10-19-2011 07:51 AM - edited 03-19-2019 03:48 AM
Hello,
Any one please could help with the below error i'm facing on CUPS 8.5.2
It's always in Initialization mode
And notification tells nothing
Solved! Go to Solution.
10-10-2012 10:41 AM
I was able to resolve this issue. I rebuilt the Subscriber on recommendation from TAC and I ran a utils dbreplication dropadmindb and a utils dbreplication reset and this fixed it.
Thanks for the suggestions.
10-14-2012 03:11 PM
1
I rebuilt the subscriber
I still had the issue... then..
2 I Disable HA
Then Reboot the servers(starting with the Publisher, wait until this server is completely up and running before the restart of the Sub)
Then re-enable HA
And everything was fine after.
06-04-2012 07:28 AM
Hi Osama,
We are facing the exact same problem.
Did you found a solution ?
Thanks in advance
07-01-2012 01:32 AM
Did you get any resolution or direction on this issue as I have run into the same problem. I am running CUPS 8.6.4 with my CUPS servers in different subnets across a 1 ms "wan" (in different parts of the same city over dwdm fiber ring).
09-25-2012 05:44 AM
Was there any update on this? I am running into something similar with CUPS 8.6.4 where all my services on the secondary node are in STARTING. I have given time for replication, but it's been like this for days.
09-25-2012 06:01 AM
All,
Being stuck in the "initializing" state typically has to do with name resolution of the other server (especially in different subnets). I haven't narrowed down the EXACT requirements, but I believe it to be one of the following is required:
1)
2)
Where domain is the domain configured on the underlying linux system and can be found via the command "show network eth0 detailed". SIPProxy domain is the instant message domain that all the users have. This can be found under System -> Cluster topology -> Settings. While you are in this menu and your CUPS nodes are in different subnets please ensure the routing mechanism is changed to "router to router" and restart the XCP Router.
You can verify the 2 lines above can be resolved from the CUPS node CLI by the command: "utils network host
Regards,
Jason
09-25-2012 07:14 AM
Thanks for the response.
I tried all of this. Also made sure to put both servers in the same domain (They were in seperate domains, seperate subnets) and also tried changing the server names in the cluster to IP only. No luck with any of it. I am able to do forward and reverse lookups from both servers and both dns servers that I have specified. The proxy domain is the same as the domain set on the servers.
09-28-2012 03:56 PM
Set the server recovery manager service to debug tracing level, bounce the service and collect the logs.
That should give you some clues as to what the issue is. As Jason said, more often than not it's a name resolution issue (or reverse)
HTH,
Christos
10-10-2012 10:01 AM
Anyone have an update on this issue ? I have the same problem here
10-10-2012 10:37 AM
Hi Philippe,
You can set the logs as per my post above
That should normally tell you what's wrong
Thanks,
Christos
10-10-2012 10:41 AM
I was able to resolve this issue. I rebuilt the Subscriber on recommendation from TAC and I ran a utils dbreplication dropadmindb and a utils dbreplication reset and this fixed it.
Thanks for the suggestions.
10-14-2012 03:11 PM
1
I rebuilt the subscriber
I still had the issue... then..
2 I Disable HA
Then Reboot the servers(starting with the Publisher, wait until this server is completely up and running before the restart of the Sub)
Then re-enable HA
And everything was fine after.
10-03-2014 07:22 AM
For reference, the CUPS high availibility settings in 10 and 10.5 are in CUCM Admin, under System > Presence Redundancy Groups.
Reference: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/10_5_1/CUP0_BK_CE43108E_00_config-admin-guide-imp-105/CUP0_BK_CE43108E_00_config-admin-guide-imp-105_chapter_00.html#CUP0_RF_P97794C4_00
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide