When I used the msan certificate option for tomcat on the cucm publisher if the publisher imp node ever restarted Cisco sync agent would never start again. It appears to be an axl problem between imp and cucm. Tac was not able to resolve. As a workaround if I generated self signed certificates for tomcat on the cluster sync agent would start again. I could then re apply the msan cert and it would fine until the next time the node was rebooted. Ugh. I think if you generate a single cert for every node and not use the msan option for the cluster it will be fine.
Getting Started
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:
