close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

show system core-dumps

date_range 19-Nov-23

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
show system core-dumps 
<re0>
<re1>
<routing-engine>
<satellite [fpc-slot-id |device-alias  alias-name]>

Syntax (SRX Series)

content_copy zoom_out_map
show system core-dumps

Syntax (Junos OS Evolved)

content_copy zoom_out_map
show system core-dumps

Syntax (EX Series Switches)

content_copy zoom_out_map
show system core-dumps 
<all-members>
<local>
<member member-id>

Syntax (TX Matrix Router)

content_copy zoom_out_map
show system core-dumps 
<all-chassis | all-lcc | lcc number | scc> 

Syntax (TX Matrix Plus Router)

content_copy zoom_out_map
show system core-dumps 
<all-chassis | all-lcc | lcc number | sfc number>

Syntax (QFX Series and OCX Series)

content_copy zoom_out_map
show system core-dumps 
<component (UUID | serial number | all)>
<display-period (hours | minutes | seconds)>
<display-order>
<kernel-crashinfo component (UUID | serial number)>
<repository (core | log)>

Description

Show core files on all routers or switches running Junos OS. You can use the show system core-dumps command to show a list of system core files created when the router or switch has failed. This command can be useful for diagnostic purposes. Each list item includes the file permissions, number of links, owner, group, size, modification date, and path and filename. If dual Routing Engines are present, you can view core-dump files for either routing engine or both routing engines together. On a QFabric system, you can view core-dump files on individual QFabric system devices as well as on the entire QFabric system.

For Junos OS, all cores files are stored at /var/core/re. For Junos OS Evolved, a core file created during early bootup is stored in /var/core/re. But a core file created later in the bootup, for example, after the Routing Engine slot number can be determined, is stored in /var/core/re0 or /var/core/re1. The command show system core-dumps continues to show all cores generated.

The core files are placed in the /var/tmp/corefiles on the SPC3 cards. Each PIC of the SPC3 card has five core files quota on the RE. When no more than five core files from one SPC3 PIC are on the RE, and the RE hard drive has more than 5 GB capacity, core file from the specific PIC is saved at the time it arrives. When there are already five core files from one SPC3 PIC on the RE, the newly arrived core file from the specific PIC replaces the last core file created by that PIC on the RE. When 5 GB capacity limit is reached, core file is not copied onto the RE. Only a zero sized shadow file with the same file name suffixed by “.shadow” is created. The core file is reached on the specific SPC3 PIC.

On vSRX Virtual Firewall, the srxpfe process might stop if you perform a reboot or an upgrade. You might observe core files whn you execute the show system core-dump command.

Options

none	Display a list of all existing core-dump files. Note: If dual Routing Engines are present, then only the core-dump files for the active Routing Engine are listed. For Junos OS Evolved, core-dump files for all Routing Engines are listed.
all-chassis	(TX Matrix and TX Matrix Plus routers only) (Optional) On a routing matrix based on a TX Matrix router, display system core files for the TX Matrix router switch-card chassis [SCC] and all the T640 routers [LCCs] connected to the TX Matrix router. On a routing matrix based on a TX Matrix Plus router, display system core files for the TX Matrix Plus router (switch-fabric chassis [SFC]) and all the T1600 routers [LCCs] connected to the TX Matrix Plus router.
<all-lcc \| lcc `number`>	(TX Matrix and TX Matrix Plus routers only) (Optional) On a routing matrix based on the TX Matrix router, display core dump files for all T640 routers (line-card chassis [LCCs]) or a specific T640 router [LCC] connected to the TX Matrix router. On a routing matrix based on the TX Matrix Plus router, display logging information for all T1600 routers (line-card chassis [LCCs]) or a specific T1600 router (LCC) connected to the TX Matrix Plus router. When using the `lcc number` option, replace `number` with a value from `0` through `3`. Note: The `all-chassis` option displays system core files for the SCC or SFC and the LCCs connected to the SCC or SFC in the routing matrix while the `all-lcc` option only displays system core files for the LCCs in the routing matrix.
all-members	(EX4200 switches) (Optional) Display system core files on all members of the Virtual Chassis configuration.
component (`UUID` \| `serial number` \| `all`)	(QFabric systems only) (Optional) Display a list of core-dump files located on individual QFabric system device or on the entire QFabric system.
display-order (timestamp-sort \| alphanumeric-sort)	(QFabric systems only) (Optional) Display list of debug artifacts generated within the specified period—for example, within the last hour, within the last 20 minutes, or within the last 32 seconds—or according to their filename.
display-period (`hours` \| `minutes` \| `seconds`)	(QFabric systems only) (Optional) Display core-dump files generated within the specified period—for example, within the last hour, within the last 20 minutes, or within the last 32 seconds.
kernel-crashinfo component (`UUID` \| `serial number`)	(QFabric systems only) (Optional) Display kernel crash information from the EEPROM on a QFabric system device.
local	(EX4200 switches only) (Optional) Display system core files on the local Virtual Chassis member.
member `member-id`	(EX4200 switches only) (Optional) Display system core files on the specified member of the Virtual Chassis configuration. Replace `member-id` with a value from 0 through 9.
node `node-name`	(Optional) (Junos OS Evolved only) Display system core files generated on the specified node.
re0	(Dual Routing Engines only) Display the core-dump files on re0.
re1	(Dual Routing Engines only) Display the coredump files on re1.
repository (core \| log)	(QFabric systems only) (Optional) Specify either the core or log repository in which to view core-dump files.
routing-engine (backup \| both \| local \| master \| other)	(Dual routing engines only) Display a list of core-dump files for either the backup, local, primary, or other routing engine or both routing engines.
satellite [`fpc-slot-id` \| device-alias `alias-name`]	(Junos Fusion only)(Optional) Display system core files for the specified satellite device in a Junos Fusion, or for all satellite devices in the Junos Fusion if no satellite devices are specified.
scc	(TX Matrix routers only) (Optional) Display system core files on the TX Matrix router (or switch-card chassis).
sfc	(TX Matrix Plus routers only) (Optional) Display system core files on the TX Matrix Plus router (or switch-fabric chassis).

Required Privilege Level

view

Output Fields

Table 1 describes the output fields for the show system core-dumps command. Output fields are listed in the approximate order in which they appear.

Table 1: show system core-dumps Output Fields
Field Name	Field Description
`Permissions`	Read/write permissions for the file named.
`Links`	Number of links to the file.
`Owner`	Name of the file owner.
`Group`	Name of the group with file access.
`File size`	File size in bytes.
`Modified`	Last file modification date and time.
`Path/filename`	File path where the file resides and the filename. (MX Series routers only) When you display the core files for an MX Series Virtual Chassis, the `show system core-dumps` command does not display information about files pertaining to the relayd process.
`Repository scope:`	Repository where core-dump files and log files are stored. The core-dump files are located in the `core` repository, and the log files are located in the `log` repository. The default `Repository scope` is shared since both the `core` and `log` repositories are shared by all of the QFabric system devices.
`Repository head:`	Path to the top-level repository location.
`Repository name:`	Name of the repository: `core` or `log`.
`List of nodes for core repository:`	List of core-dump files associated with a particular QFabric system device located in the core repository.
`Node Group`	Name of the QFabric system device.
`Node Identifier`	UUID or serial number of the QFabric system device.
`Num`	Number of core-dump and log files.
`Model`	Model number of the QFabric system device.
`Usage`	Usage of the repository in megabytes.
`Total usage of core repository:`	Total usage of core-dump files associated with a particular QFabric system device located in the core repository. Usage is specified in megabytes and as a percentage.
`Total usage of log repository:`	Total usage of log files associated with a particular QFabric system device located in the log repository. Usage is specified in megabytes and as a percentage.
`List of nodes for core repository:`	List of core-dump files associated with a particular QFabric system device located in the core repository.
`List of nodes for log repository:`	List of log files associated with a particular QFabric system device located in the log repository.
`Filename`	Name of the core-dump file.
`Date`	Last core-dump file modification date and time.
`Size`	Size of the core-dump file.
`Core filename`	Filename of the core-dump file.
`Process name`	Name of the process that is generating a core-dump file or log file.
`Release`	Junos OS release.
`Build server`	Junos OS build server.
`Build date`	Junos OS build date.
`Stack trace`	Stack trace of the core-dump file.

Sample Output

show system core-dumps
show system core-dumps
show system core-dumps routing-engine both
show system core-dumps (SRX Series)
show system core-dumps (TX Matrix Plus Router)
show system core-dumps (QFX3500 Switch)
show system core-dumps (QFabric Systems)
show system core-dumps component serial number display-order alphanumeric-sort repository core (QFabric Systems)
show system core-dumps display-period (QFabric Systems)
show system core-dumps kernel-crashinfo component serial number (QFabric Systems)
show system core-dumps repository core (QFabric Systems)
show system core-dumps repository log (QFabric Systems)