Creating Core Dump And Debug Files Upon Device Crash - AudioCodes E-SBC User Manual

CHAPTER 60 Creating Core Dump and Debug Files upon Device Crash
60 Creating Core Dump and Debug Files upon
Device Crash
For debugging, you can configure the device to create a core dump file and/or debug file. The files
may assist you in identifying the cause of the crash. The core dump can either be included in or
excluded from the debug file, or alternatively, sent separately to a TFTP server. You can then
provide the files to AudioCodes support team for troubleshooting.
■ Core Dump File: You can enable the device to send a core dump file to a remote destination
upon a device crash. The core dump is a copy of the memory image at the time of the crash. It
provides a powerful tool for determining the root cause of the crash. When enabled, the core
dump file is sent to a user-defined TFTP server (IP address). If no address is configured, the
core dump file is saved to the device's flash memory (if it has sufficient memory) and can be
included in the debug file (see below). Each time the device crashes, the new core dump file
replaces the previous core dump file, if exists.
The core dump file is saved as a binary file with the following file name: "core_<device name>_
ver_<firmware version>_mac_<MAC address>_<date>_<time>". For example, core_
acDevice_ver_720-8-4_mac_00908F099096_1-02-2015_3-29-29.
■ Debug File: You can manually retrieve the debug file from the device (flash memory) and save
it to a folder on your local PC. The device creates the debug file when an exception occurs.
Each time the device creates a new debug file, it overwrites the existing file. The debug file
contains the following information:
● Exception information, indicating the specific point in the code where the crash occurred
and a list of up to 50 of the most recent SNMP alarms that were raised by the device
before it crashed.
● Latest syslog messages that were recorded prior to the crash.
● Core dump. The core dump is only included in the debug file if all the following conditions
are met:
◆
◆
◆
● The debug file may include additional application-proprietary debug information.
The debug file is saved as a zipped file with the following file name: "debug_<device name>_
ver_<firmware version>_mac_<MAC address>_<date>_<time>". For example, debug_
acDevice_ver_720-8-4_mac_00908F099096_1-03-2015_3-29-29.
The following procedure describes how to configure core dump file creation through the Web
interface.
➢
To enable core dump file generation:
1. (Optional) Set up a TFTP server to where you want to send the core dump file.
2. Open the Debug Files page (Troubleshoot menu > Troubleshoot tab > Debug folder >
Debug Files).
3. From the 'Enable Core Dump' drop-down list, select Enable.
You have enabled core dump generation (see below).
You have not configured an IP address to send the core dump to a remote server (see
below).
The device has sufficient memory on its flash memory.
Mediant 1000 Gateway & E-SBC | User's Manual
- 1058 -