AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 951 / 1248

Version 7.2 951 Mediant 500 MSBR
User's Manual 65. Creating Core Dump and Debug Files upon Device Crash
65 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). 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_acMediant_ver_700-8-4_mac_00908F099096_1-02-2015_3-29-29 .

Debug File: You can manually retrieve the debug file from the device and save it to a
folder on your local PC. 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 log messages that were recorded prior to the crash.
•
Core dump. The core dump is included only if core dump generation is enabled,
no IP address has been configured, and the device has sufficient memory on its
flash memory.
•
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_acMediant_ver_700-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. 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 ).
Figure 65-1: Debug Files Page
3. From the 'Enable Core Dump' drop-down list, select Enable .
4. (Optional) In the 'Core Dump Destination IP' field, enter an IP address of the remote
server to where you want the file to be sent.
5. Click Apply , and then reset the device with a save-to-flash for your settings to take
effect.