CHAPTER 58 Syslog and Debug Recording
●
●
■
Device's CLI: The device sends error messages (e.g., Syslog messages) to the CLI as well
as to the configured destination.
●
To start debug recording:
debug log
●
To stop debug recording:
no debug log
●
To stop all debug recording:
no debug log all
■
Wireshark: Third-party, network protocol analyzer (http://www.wireshark.org).
When debug recording is enabled and Syslog messages are also included in the debug
recording, to view Syslog messages using Wireshark, you must install AudioCodes'
Wireshark plug-in (acsyslog.dll). Once the plug-in is installed, the Syslog messages are
decoded as "AC SYSLOG" and displayed using the "acsyslog" filter (instead of the
regular "syslog" filter). For more information on debug recording, see
■
Third-party, Syslog Server: Any third-party, Syslog server program that enables filtering of
messages according to parameters such as priority, IP sender address, time, and date.
Syslog Message Description for CPU Overload
Whenever the devicedetects a CPU overload, it sends a Syslog message that shows CPU
utilization of the different processes (tasks) per core. This information can help in identifying the
cause of the overload. When the devicedetects a CPU overload, it sends a Syslog message every
10 seconds until it returns to normal state.
You can also view CPU utilization through the CLI, by using the following command:
show system utilization
The figure below shows an example of a Syslog message generated because of a CPU overload.
CPU utilization information is shown under the "CPUUtilMonitor" section (shown in pink). The
subsequent table describes the displayed information.
It's not recommended to keep a Message Log session open for a prolonged period.
This may cause the device to overload. For prolonged (and detailed) debugging,
use an external Syslog server.
The Message Log page provides limited Syslog server functionality.
Mediant 1000 Gateway & E-SBC | User's Manual
- 1051 -
Debug
Recording.