From the syslogs I don't see what happened before the reboot, except one message, that the certificate has expired on one of the nodes in the cluster.
Mar 20 21:00:00 ndc1cm001 local7 0 : 311: Mar 20 10:00:00.60 UTC : %CCM_UNKNOWN-CERT-0-CertExpiryEmergency: Certificate Expiry EMERGENCY_ALARM Message:Certificate expiration Notification. Certificate name:CAPF-962c702a Unit:CallManager-trust Type:trust-cert Expiration:Mon Oct 29 App ID:Cisco Certificate Monitor Cluster ID: Node ID:ndc1cm001
After this the only message is that the call manager has booted, where the service manager is starting up. this is the first service to start.
Mar 21 08:58:37 ndc1cm001 local7 6 : 0: Mar 20 21:58:37.317 UTC : %CCM_SERVICEMANAGER-GENERIC-6-ServiceStarted: Service started. Service Name:Service Manager Process ID:6959 App ID:Cisco Service Manager Cluster ID: Node ID:ndc1cm001
I would suggest checking the server for any core dumps that have been created. That would indicate a service crash, causing a reboot.
Another thing that you can look at would be the tomcat catalina.out log to see if that may have been a cause.
Yes, CUCM ver 7.1.5 is affected and as per the bug workaround "Rebuild the server if there is a non-graceful shutdown regardless if the recovery disk was required. As any non-graceful shutdown can cause file system corruption even if no symptoms are seen immediately."
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...