Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

show chassis routing-engine

Syntax

Syntax (ACX Series, PTX Series, and MX104 Universal Routing Platforms.)

Syntax (EX Series Switches)

Syntax (QFX Series)

Syntax (MX Series Routers)

Syntax (MX204 and MX10003 Universal Routing Platforms)

Syntax (TX Matrix Routers)

Syntax (TX Matrix Plus Routers)

Syntax (Junos OS Evolved)

Description

Display the status of the Routing Engine.

Options

none

Display information about one or more Routing Engines. On a TX Matrix router, display information about all Routing Engines on the TX Matrix router and its attached T640 routers. On a TX Matrix Plus router, display information about all Routing Engines on the TX Matrix Plus router and its attached routers.
all-members

(MX Series routers only) (Optional) Display Routing Engine information for all members of the Virtual Chassis configuration.
bios

(Optional) Display the (BIOS) firmware version.

errors

(Optional) Display routing engine errors.
hard-disk-test

(Junos OS Evolved only) (Optional) Display the health of the hard disk. Use disk /dev/disk-name status to display the status of a particular disk.
interconnect-device number

(QFabric systems only) (Optional) Display Routing Engine information for a specified Interconnect device.

lcc number

(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router, display Routing Engine information for a specified T640 router (line-card chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, display Routing Engine information for a specified router (line-card chassis) that is connected to the TX Matrix Plus router.

Replace number with the following values depending on the LCC configuration:

  • 0 through 3, when T640 routers are connected to a TX Matrix router in a routing matrix.

  • 0 through 3, when T1600 routers are connected to a TX Matrix Plus router in a routing matrix.

  • 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.

  • 0, 2, 4, or 6, when T4000 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.
local

(MX Series routers only) (Optional) Display Routing Engine information for the local Virtual Chassis member.
member member-id

(MX Series routers only) (Optional) Display Routing Engine information for the specified member of the Virtual Chassis configuration. For an MX Series Virtual Chassis, replace member-id with a value of 0 or 1.
node-device number

(QFabric systems only) (Optional) Display Routing Engine information for a specified Node device.

satellite [slot-id slot-id |device-alias alias-name]

(Junos Fusion only) (Optional) Display Routing Engine information 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 Routing Engine information for the TX Matrix router (switch-card chassis).

sfc number

(TX Matrix Plus routers only) (Optional) Display Routing Engine information for the TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.

slot

(Systems with multiple Routing Engines) (Optional) Display information for an individual Routing Engine. Replace slot with 0 or 1. For QFX3500 switches, there is only one Routing Engine, so you do not need to specify the slot number.

Required Privilege Level

view

Output Fields

Table 1 lists the output fields for the show chassis routing-engine command. Output fields are listed in the approximate order in which they appear.

Table 1: show chassis routing-engine Output Fields

Field Name

Field Description

Slot

(Systems with single and multiple Routing Engines) Slot number.

Current state

(Systems with multiple Routing Engines) Current state of the Routing Engine: Master, Backup, or Disabled.

Election priority

(Systems with multiple Routing Engines) Election priority for the Routing Engine: Master or Backup.

Temperature

Temperature of the air flowing past the Routing Engine.

CPU Temperature

Temperature of the CPU.

DRAM

Total DRAM available to the Routing Engine's processor.

Note:

When the chassis has two Routing Engines, the amount of DRAM should be the same on both. A DRAM size mismatch error can result when the Routing Engines have different amounts of DRAM.

Starting with Junos OS Release 12.3R1, the DRAM field displays both available memory and installed memory.

Memory utilization

Percentage of Routing Engine memory being used.

Note:

For platforms running Junos OS with upgraded FreeBSD, the way memory utilization is calculated has changed. Starting in Junos OS Release 15.1R1, inactive memory is no longer included in calculating memory utilization. Inactive memory is considered as free. The value for used memory decreases and results in more memory to be available for other processes. For platforms that run Junos OS with upgraded FreeBSD, see Release Information for Junos OS with Upgraded FreeBSD.

CPU utilization

Information about the Routing Engine's CPU utilization:

  • User—Percentage of CPU time being used by user processes.

  • Background—Percentage of CPU time being used by background processes.

  • Kernel—Percentage of CPU time being used by kernel processes.

  • Interrupt—Percentage of CPU time being used by interrupts.

  • Idle—Percentage of CPU time that is idle.

5 sec CPU Utilization

Information about the Routing Engine's CPU utilization in the past 5 seconds:

  • User—Percentage of CPU time being used by user processes.

  • Background—Percentage of CPU time being used by background processes.

  • Kernel—Percentage of CPU time being used by kernel processes.

  • Interrupt—Percentage of CPU time being used by interrupts.

  • Idle—Percentage of CPU time that is idle.

1 min CPU Utilization

Information about the Routing Engine's CPU utilization in the past 1 minute:

  • User—Percentage of CPU time being used by user processes.

  • Background—Percentage of CPU time being used by background processes.

  • Kernel—Percentage of CPU time being used by kernel processes.

  • Interrupt—Percentage of CPU time being used by interrupts.

  • Idle—Percentage of CPU time that is idle.

5 min CPU Utilization

Information about the Routing Engine's CPU utilization in the past 5 minutes:

  • User—Percentage of CPU time being used by user processes.

  • Background—Percentage of CPU time being used by background processes.

  • Kernel—Percentage of CPU time being used by kernel processes.

  • Interrupt—Percentage of CPU time being used by interrupts.

  • Idle—Percentage of CPU time that is idle.

15 min CPU Utilization

Information about the Routing Engine's CPU utilization in the past 15 minutes:

  • User—Percentage of CPU time being used by user processes.

  • Background—Percentage of CPU time being used by background processes.

  • Kernel—Percentage of CPU time being used by kernel processes.

  • Interrupt—Percentage of CPU time being used by interrupts.

  • Idle—Percentage of CPU time that is idle.

Model

Routing Engine model number.

Serial ID

(Systems with multiple Routing Engines) Identification number of the Routing Engine in this slot.

Start time

Time at which the Routing Engine started running.

Uptime

How long the Routing Engine has been running.

Routing Engine BIOS Version

BIOS version being run by the Routing Engine.

Last reboot reason

Reason for last reboot, including:

  • power cycle/failure—Halt of the Routing Engine using the halt command, powering down using the power button on the chassis or any other method (such as removal of the control board or Routing Engine), and then powering back the Routing Engine. A halt of the operating system also occurs if you enter the request system halt command. You can enter this command to halt the system operations on the chassis or specific Routing Engines. To restart the software, press any key on the keyboard.

  • watchdog—Reboot due to a hardware watchdog. A watchdog is a hardware monitoring process that examines the health and performance of the router to enable the device to recover from failures. A watchdog checks for problems at certain intervals, and reboots the routing engine if a problem is encountered.

  • reset-button reset—(Not available on the EX Series switch) Reboot due to pressing of the reset button on the Routing Engine.

  • power-button hard power off—Reboot due to pressing of the power button on the chassis. A powering down of the software also occurs if you enter the request system power-off command. You can enter this command to power down the chassis or specific Routing Engines; you can then restart the software.

  • misc hardware reason—Reboot due to miscellaneous hardware reasons.

  • thermal shutdown—Reboot due to the router or switch reaching a critical temperature at which point it is unsafe to continue operations.

  • hard disk failure—Reboot due to a hard disk or solid-state drive (SSD) failure.

  • reset from debugger—Reboot due to reset from the debugger.

  • chassis control reset—Restart the chassis process that manages PICs, FPCs, and other hardware components. The chassis control module that runs the Routing Engine performs management and monitoring functions, and it provides a single access point for operational and maintenance functions. A reset of the chassis management process occurs when you enter the restart chassis-control command.

  • bios auto recovery reset—Reboot due to a BIOS auto-recovery reset.

  • could not be determined—Reboot due to an undetermined reason.

  • Router rebooted after a normal shutdown—Reboot due to a normal shutdown. This reason is displayed if the Routing Engine is powered down by pushing and holding the online/offline button on the Routing Engine faceplate for 30 seconds, and then powered back. A reboot of the software also occurs if you enter the request system reboot command. You can enter this command to reboot the chassis or specific Routing Engines.

  • Low battery detected This reason is displayed if the Routing Engine is powered down due to detection of low battery and powered back when battery is charged.
  • Catastrophic error This reason is displayed if the Routing Engine is powered down due to catastrophic error (for example, link failure between FPC line card and PFE(packet forwarding engine)) and powered back.

QFX5700 displays the following additional reboot reasons:

  • FPGA reset Reboot due to FPGA reset.
  • MSMI error/hw misc Reboot due to hardware MSMI (Microsoft Mail Connector interchange) Service Returned Service-Specific error.
  • swizzle reset Reboot due to swizzle reset, power off and turning back on.
  • PCH cold reset Reboot due to complete removal of power and restart of Intel PCH (Platform Controller Hub).
  • software reboot Reboot of system due to software reboot process.
  • Straight to s5 reset Reboot due to system in S5 state and does not retain memory state.
  • iTCO watchdog Linux TCO hardware watchdog reboots the system automatically when there is a systems pause.

Load averages

Routing Engine load averages for the last 1, 5, and 15 minutes.

Sample Output

The sample outputs for show chassis routing engine are as follows:

show chassis routing-engine (MX Series Routers)

show chassis routing-engine (QFX5700 Switches) (Junos OS Evolved Release)

show chassis routing-engine (QFX5230-64CD devices with logical FPC and PIC) (Junos OS Evolved Release)

Usage

The show chassis routing-engine and show chassis feb commands can be used to find the memory allocated for each RE (Routing Engine) and Packet Forwarding Engine components.

Release Information

Command introduced before Junos OS Release 7.4.

sfc option introduced in Junos OS Release in 9.6 for the TX Matrix Plus router.

5 sec CPU Utilization, 1 min CPU Utilization, 5 min CPU Utilization, and 15 min CPU Utilization output fields introduced in Junos OS Release 11.3R1.

satellite option introduced in Junos OS Release 14.2R3.

Related Documentation