Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Working with the event logs
Cisco TelePresence MCU Version 4.2 Printable online help
Page 220 of 252
Working with the event logs
If you are experiencing complex issues that require advanced troubleshooting, you may need to
collect information from the MCU logs. Typically, you will be working with Customer support who can
help you obtain these logs.
collect information from the MCU logs. Typically, you will be working with Customer support who can
help you obtain these logs.
Event log
The last 2000 status messages generated by the MCU are displayed in the Event log page (Logs >
Event log). In general these messages are provided for information, and occasionally Warnings or
Errors may be shown in the Event log. The presence of such messages is not cause for concern
necessarily; if you are experiencing a specific problem with the operation or performance of the MCU,
Customer support can interpret logged messages and their significance for you.
Event log). In general these messages are provided for information, and occasionally Warnings or
Errors may be shown in the Event log. The presence of such messages is not cause for concern
necessarily; if you are experiencing a specific problem with the operation or performance of the MCU,
Customer support can interpret logged messages and their significance for you.
You can:
Change the level of detail collected in the traces by editing the
Capture filter page. You should not
modify these settings unless instructed to do so by Customer support.
Display the log as text: go to
Logs > Event log and click
Download as text
.
Change which of the stored Event log entries are displayed by editing the
Display filter page
Send the event log to one or more syslog servers on the network for storage or analysis. The
servers are defined in the
servers are defined in the
Syslog page. For more information, refer to
Empty the log by clicking
Clear log
.
Event capture filter
The Event capture filter allows you to change the level of detail to collect in the Event log traces.
NOTE: You should not modify these settings unless instructed to do so by Customer support.
Modifying these settings can impair the performance of your MCU.
Modifying these settings can impair the performance of your MCU.
Normally, the capture filter should be set to the default of Errors, warnings and information for all
logging sources. There is no advantage in changing the setting of any source without advice from
Customer support. There is a limited amount of space available to store logged messages and
enabling anything other than Errors, warnings and information could cause the log to become full
quickly.
logging sources. There is no advantage in changing the setting of any source without advice from
Customer support. There is a limited amount of space available to store logged messages and
enabling anything other than Errors, warnings and information could cause the log to become full
quickly.
Event display filter
The Event display filter allows you to view or highlight stored Event log entries. Normally, you should
not need to view or modify any of the settings on this page.
not need to view or modify any of the settings on this page.
Syslog
You can configure the MCU to send event messages to up to four syslog servers. To add or remove a
syslog server, go to Logs > Syslog and make the changes you require. See
syslog server, go to Logs > Syslog and make the changes you require. See
H.323/SIP log
The H.323/SIP log page records every H.323 and SIP message received or transmitted from the
MCU. The log can be exported in an .xml file by clicking Download as XML.
MCU. The log can be exported in an .xml file by clicking Download as XML.
By default the H.323/SIP log is disabled because it affects performance, but Customer support may
ask you to enable it if there is a problem with an MCU in your network. To do this, click Enable
H323/SIP logging.
ask you to enable it if there is a problem with an MCU in your network. To do this, click Enable
H323/SIP logging.