- play_arrow Configuration Statements and Operational Commands
System Troubleshooting
Saving Core Files Generated by 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 /var/tmp/process-name.core.core-number.tgz. The contextual information includes the configuration and system log message files.
To disable the saving of core files and associated context information:
content_copy zoom_out_map[edit system] no-saved-core-context;
To save the core files only:
content_copy zoom_out_map[edit system] saved-core-files number;
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:
content_copy zoom_out_map[edit system] saved-core-context;
Viewing Core Files from Junos OS Processes
When an internal Junos OS process generates a core file, you can find the output at /var/crash/ and /var/tmp/. For Junos OS Evolved, you can find the output core files at /var/core/ for Routing Engine core files and /var/lib/ftp/in/ for FPC core files. Using these directories provides a quick method of finding core issues across large networks.
Use the CLI command show system core-dumps to view core files.
root@host> show system core-dumps -rw------- 1 root wheel 268369920 Jun 18 17:59 /var/crash/vmcore.0 -rw-rw---- 1 root field 3371008 Jun 18 17:53 /var/tmp/rpd.core.0 -rw-r--r-- 1 root wheel 27775914 Jun 18 17:59 /var/crash/kernel.0
