Saving Core Files from Junos OS Processes

By default, when an internal Junos OS process generates a core file, the file and associated context information are saved for debugging purposes in a compressed tar file named process-name.core.core-number.tgz in the /var/tmp/ and /var/crash/ directories. For Junos OS Evolved, the output is saved in the /var/core/ directory for Routing Engine core files and /var/lib/ftp/in/ for FPC core files. The contextual information includes the configuration and system log message files.

Junos OS Evolved has a number of interrelated processes. For these process pairs, when one process stops responding and generates a core file, the system also generates a live core for the related process by default, in releases that support this feature. As a result, the system provides more complete diagnostic data at the time of the failure, which enables you to perform a more thorough root cause analysis and resolve issues faster.

To disable the saving of core files and associated context information, include the no-saved-core-context statement at the [edit system] hierarchy level.

To save the core files only, include the saved-core-files statement at the [edit system] hierarchy level and specify the number of files to save:

where number is the number of core files to save and can be a value from 1 through 10.

To save the core files along with the contextual information, include the saved-core-context statement at the [edit system] hierarchy level. This is the default.

On Junos OS Evolved, to disable the feature that generates a live core for a process when its related process generates a core file, configure the no-livecore-dump-on-crash statement. You can configure the statement for an individual process or for all processes that support the feature.