Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

show system errors

date_range 19-Nov-23

Syntax

content_copy zoom_out_map
show system errors
<cb slot| ccg slot | fan slot | fpc slot | psm slot | re slot | sib slot>

Description

Display information about faults in the system. You can display all errors or the errors for one system component. Use this command to understand about faults and their correlation with other events. First, top level root causes are listed, with board level faults followed by component level faults. Next, details for affected faults are listed.

The show output represents five faults, F1 through F5. F4 and F5 are top level faults, where F4 is affected by F1, F2, and F3; and F3 is affected by F1 and F2. The lowest level (leaf) faults, F1, F2, and F5, have no affected events.

Note:

For Junos OS Evolved, only the QFX5200 supports this command. For all other Junos OS Evolved platforms, use the show system errors active, show system errors count, show system errors error-id, show system errors fru, or show system errors inactive command.

Options

This command has no options.

Required Privilege Level

view

Output Fields

Table 1 lists the output fields for the show system errors command. Output fields are listed in the approximate order in which they appear.

Table 1: show system errors Output Fields

Field Name

Field Description

Top level root causes

Display of the top level faults with board level faults followed by component level faults.

Fx

Fault number F1 to Fn, where F1 is the first fault and n is the last fault generated by the system.

(module, error-id, board-name, component-name)

Information about the fault. Component level faults include the component name.

Group

Fault severity level is Fatal, Major, or Minor.

Scope

Affected scope of fault is System, Component, Board, or Link.

Corr-enabled

Correlation with fault is always enabled, Y.

Time

Time in the format yyyy-mm-dd hh:nn:ss.lll TMZ, where nn is minutes, lll is milliseconds, and TMZ is time zone.

Desc

Description of the fault.

Actions

List of errors that caused the fault.

Root-causes

List of faults that caused this error.

Affected

List of faults that correlate to this root cause.

Details for affected errors

Display the affected errors listed in top level faults.

Sample Output

show system errors

content_copy zoom_out_map
user@host> show system errors
Top level root-causes:
F4: {pciesw, 1, fpc0} Group: Fatal Scope: Board Corr-enabled: Y
Time: “2017-02-22 16:37:47.456 PST”
Desc: PCIe Switch Fatal AER Errors
Actions: Alarm: FPC_FATAL_ERRORS + FRU_FAULT
Root-causes: None
Affected:
F3: {hwd, 1, fpc0}
F1: {pechip, 1, fpc0, pechip0}
F2: {pechip, 1, fpc0, pechip3}
F5: {pfchip, 3, sib0, pfchip5} Group: Major Scope: Component Corr-enabled: Y
Time: “2017-02-22 18:37:47.456 PST”
Desc: Midplane link errors
Actions: Alarm: ASIC_FABRIC_LINK_ERRORS
Affected: None
Details for Affected Errors:
F3: {hwd, 1, fpc0}, Group: Fatal Scope: Board Corr-enabled: Y
Time: “2017-02-22 16:37:47.856 PST”
Desc: FPC Fault
Root-causes: F4 : { pciesw, 1, fpc0}
Affected:
F1: {pechip, 1, fpc0, pechip0}
F2: {pechip, 1, fpc0, pechip3}
F1: {pechip, 3, fpc0, pechip0}, Group: Fatal Scope: Component Corr-enabled: Y
Time: “2017-02-22 16:37:48.500 PST”
Desc: PIO Fault
Root-causes:
F4 : {pciesw, 1, fpc0}
Affected: None
F2: {pechip, 3, fpc0, pechip1}, Group: Fatal Scope: Component Corr-enabled: Y
Time: “2017-02-22 16:37:48.600 PST”
Desc: PIO Fault
Root-causes:
F4 : {pciesw, 1, fpc0}
Affected: None

show system errors fpc 0

content_copy zoom_out_map
user@host> show system errors fpc 0
Top level root-causes:	
F4: {pciesw, 1, fpc0} Group: Fatal   Scope: Board  Corr-enabled: Y
  Time:    “2017-02-22 16:37:47.456 PST”
  Desc:    PCIe Switch Fatal AER Errors
    Actions: Alarm: FPC_FATAL_ERRORS + FRU_FAULT
    Root-causes: None
    Affected:
      F3:    {hwd, 1, fpc0}
      F1:    {pechip, 1, fpc0, pechip0}
      F2:    {pechip, 1, fpc0, pechip3}

Details for Affected Errors:
F3: {hwd, 1, fpc0}, Group: Fatal   Scope: Board  Corr-enabled: Y
    Time: “2017-02-22 16:37:47.856 PST”
  Desc:    FPC Fault
  Root-causes: F4 : { pciesw, 1, fpc0}
  Affected:
      F1:    {pechip, 1, fpc0, pechip0}
      F2:    {pechip, 1, fpc0, pechip3}

F1: {pechip, 3, fpc0, pechip0}, Group: Fatal   Scope: Component  Corr-enabled: Y
    Time: “2017-02-22 16:37:48.500 PST”
    Desc: PIO Fault
  Root-causes: 
      F4 :   {pciesw, 1, fpc0}
  Affected: None
F2: {pechip, 3, fpc0, pechip1}, Group: Fatal   Scope: Component  Corr-enabled: Y
    Time: “2017-02-22 16:37:48.600 PST”
    Desc: PIO Fault
  Root-causes: 
      F4 :   {pciesw, 1, fpc0}
  Affected: None

show system errors sib 0

content_copy zoom_out_map
user@host> show system errors sib 0
Top level root-causes:	
F5: {pfchip, 3, sib0, pfchip5} Group: Major   Scope: Component  Corr-enabled: Y
  Time:    “2017-02-22 18:37:47.456 PST”
  Desc:    Midplane link errors
    Actions: Alarm: ASIC_FABRIC_LINK_ERRORS
    Affected: None

Release Information

Command introduced in Junos OS Evolved Release 18.3R1.

footer-navigation