CallManager Archive Trace Logs

[Chi Fai Leung]

Hi,

I have a customer to complain the CallManager always cannot capture the Trace Logs for the TAC troubleshooting. It is because it was overtime to capture the logs.

The User-A opened a helpdesk case about his IP-Phone on 3:00pm today and claimed his IP-Phone suddently reset on 2:00pm today.
The IPT Admin cannot find out the reason and root cause, so opened a TAC case. Finally, the TAC replied cannot capture the Trace Logs, because it was overtime to capture the logs.

The customer is asking how to keep the Trace Logs on 24 hours. As I know, that is only one way to capture the trace logs, which is the debug level logging. We can set the schedule to capture the Trace Logs to local / FTP/ SFTP, through RTMT, that is the Java client program. <--- That is not stable to capture the Trace Logs on 24 hours.

Third-party IPUC monitor software, which only can capture the SNMP trap / Syslog on CallManager? Event level only?

Any look like the EEM (Embedded Event Manager) to write a script on IOS Router to capture the debug logs?

[Andrew Skelly]

We are using the log capture via RTMT and have not had an issue.  While RTMT is a Java application, it is not actually RTMT that is doing the offloading of logs to a SFTP server.  CUCM is doing the offloading of the logs.  RTMT is merely a GUI portal for accessing certain functions of CUCM from a reporting and monitoring standpoint.  We setup our SFTP server to store logs for 7 calendar days as we have also run in to issues with logs being over-written and Cisco not asking for common logs for days on end.