I recently installed new tomcat certificates on my cluster. After installing the certificates, I restarted the Cisco Tomcat service on every node, and deleted all the old certificates from the tomcat-trust store.
Even though I'm sure I've purged all the old certificiates, I'm still getting RMT alerts for certificates about to expire. Sure enough, when I go back to CUCM, I see the old certificates that I'd replaced & deleted have re-appeared.
I've re-restarted the Cisco Tomcat service, but still no joy.
How are these Tomcat certificates managing to rise from the dead? And how do I kill these Zombies?
This describes what has to be done, https://tools.cisco.com/bugsearch/bug/CSCto86463. In summary the Certificate Change Notification Service has to be stopped on all nodes before deleting the certificates. Once the old tomcat certificate has been deleted from all nodes you can start the Certificate Change Notification Service again and the certificate should no longer re-appear.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...