01-25-2019 06:54 AM - edited 03-19-2019 01:40 PM
Dear Team,
I have a problem recently between Cisco Publisher and Subscriber when I try to reach the subscriber from the serviceability list
I got below message :
![]() |
Connection to the Server cannot be established(Certificate Exception) |
When I try to navigate below in CLI on Publisher I got below:utils dbreplication runtimestate
(-) DB Active-Error
Even there is no reachibility between subscriber and publisher eventhough the two are on same network
01-25-2019 08:13 AM
. Hi Tanios,
Can you check the DB replication status by issue the command - utils dbreplication status to get updated data.
you probably need to repair the DB replication first and ensure that you have good DB replication between the nodes if you get the same error again when you run the command utils dbreplication runtimestate.
meanwhile, check the tomcat certificate expiry - If expired, regenerate the Tomcat certificate and restart the Tomcat service.
Regards,
Shalid
01-27-2019 10:56 PM
will this affect the anything running?
01-28-2019 08:04 AM
01-28-2019 08:15 AM
Which certificates I should check if expired?
Can you provide with detailed technique to regenerate the certificate?
Will it affect the live environement in any way?
01-29-2019 03:37 AM - edited 01-29-2019 03:39 AM
Shalid mentioned this above:
"Meanwhile, check the Tomcat certificate expiry - If expired, regenerate the Tomcat certificate and restart the Tomcat service."
And here is a link to information on regenerating certificates:
CUCM Certificate Regeneration/Renewal Process
Maren
01-29-2019 04:29 AM
Hi there
There could be multiple reasons why you are getting this error. Also please check the below link and the associated workarounds.
Hope this Helps
Cheers
Rath!
***Please rate helpful posts***
02-01-2019 03:07 AM
how can I bind the hostname to an IP address in CUCM CLI as I can reach from publisher the IM and Presence and Unity but cannot reach the subscriber how can add hostname of subscriber and bind it to the IP of the subscriber
02-01-2019 09:10 AM
Hey
Please try out this and let me know
Workaround
Log in to each CUCM node separately in order to access Serviceability and Activate/Deactivate services.
Solution
This known defect is documented in Cisco bug ID CSCup10995.
Hope this helps
Cheers
Rath!
***Please rate helpful posts***
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: