Showing results for 
Search instead for 
Did you mean: 
Step-by-Step Configuration and Troubleshooting Best Practices for the NGFW, NGIPS and AMP Technologies A Visual Guide to the Cisco Firepower Threat Defense (FTD)

ASA 5510 upgrade 8.2(1) coredump.cfg created

After upgrading from 8.0(2) to 8.2(1) I noticed that a directory named coredumpinfo, containing a file coredump.cfg was created. The file size of coredump.cfg is 43 bytes.

Is this normal? The ASA functions normally after the upgrade.

Thanks in advance,

-- Bill

Frequent Contributor

Re: ASA 5510 upgrade 8.2(1) coredump.cfg created

by default the ASA creates the coredump files as snapshots and unless you enables the feature, it would not do anything. The Coredump is a system-wide snapshot of the ASA code at the time when a crash occurs. Coredumps are saved to disk allowing the user to export it later for off-site analysis by Cisco TAC . The Coredump was created since the current traceback information saved on the ASA after a crash, doesn't always provide enough information to determine the root cause of the problem. For ASA systems running Linux, the goal here is to take advantage of the built in LINUX OS functionality which, when configured, dumps core when unrecoverable problems are encountered.

In other words, a Coredump is the recorded state of the working memory of a computer program at a specific time, generally when the program has terminated abnormally (i.e. crashed). In practice, other key pieces of program state are usually dumped at the same time, including the processor registers, which may include the program counter and stack pointer, memory management information, and other processor and operating system flags and information. Coredumps can then be analyzed to diagnose or debug errors incomputer programs.

In order to disable this feature, you can issue the following command:

ciscoasa(config)# no coredump enable

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards