Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

request system reboot

 

List of Syntax

Syntax

Syntax (EX Series Switches and EX Series Virtual Chassis)

Syntax (MX Series Routers and MX Series Virtual Chassis, EX9200 Switches and EX9200 Virtual Chassis)

Syntax (QFabric Systems)

Syntax (QFX Series Switches and QFX Series Virtual Chassis, Virtual Chassis Fabric)

Syntax (TX Matrix Router)

Syntax (TX Matrix Plus Router)

Syntax

Syntax (EX Series Switches and EX Series Virtual Chassis)

Syntax (MX Series Routers and MX Series Virtual Chassis, EX9200 Switches and EX9200 Virtual Chassis)

Syntax (QFabric Systems)

Syntax (QFX Series Switches and QFX Series Virtual Chassis, Virtual Chassis Fabric)

Syntax (TX Matrix Router)

Syntax (TX Matrix Plus Router)

Release Information

Command introduced before Junos OS Release 7.4.

Option other-routing-engine introduced in Junos OS Release 8.0.

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

Option partition changed to slice in Junos OS Release 10.0 for EX Series switches.

Option both-routing-engines introduced in Junos OS Release 12.1.

Description

Use this command to reboot the device software.

This command can be used on standalone devices and on devices supported in a Virtual Chassis, Virtual Chassis Fabric, or QFabric system.

Starting with Junos OS Release 15.1F3, the statement request system reboot reboots only the guest operating system on the PTX5000 with RE-PTX-X8-64G and, MX240, MX480, and MX960 with RE-S-X6-64G.

Starting with Junos OS Release 15.1F5, the statement request system reboot reboots only the guest operating system on the MX2010, and MX2020 with REMX2K-X8-64G.

Starting from Junos OS Release 17.2R1, PTX10008 routers do not support the request system reboot command. Starting from Junos OS Release 17.4R1, PTX10016 routers do not support the request system reboot command. Use the request vmhost reboot command instead of the request system reboot command on the PTX10008 and PTX10016 routers to reboot the Junos OS software package or bundle on the router. See request vmhost reboot.

On a QFabric system, to avoid traffic loss on the network Node group, switch mastership of the Routing Engine to the backup Routing Engine, and then reboot.

Options

The options described here are not all supported on every platform or release of Junos OS. Refer to the Syntax sections for the options commonly available on each type of platform.

none—Reboot the software immediately.
all-chassis—(Optional) On a TX Matrix router or TX Matrix Plus router, reboot all routers connected to the TX Matrix or TX Matrix Plus router, respectively.
all-lcc—(Optional) On a TX Matrix router or TX Matrix Plus router, reboot all line card chassis connected to the TX Matrix or TX Matrix Plus router, respectively.
all-members | local | member member-id—(Optional) Specify which member of the Virtual Chassis to reboot:

  • all-members—Reboots each switch that is a member of the Virtual Chassis.

  • local—Reboots only the local switch (switch where you are logged in).

  • member member-id—Reboots the specified member switch of the Virtual Chassis

at time—(Optional) Time at which to reboot the software, specified in one of the following ways:

  • now—Stop or reboot the software immediately. This is the default.

  • +minutes—Number of minutes from now to reboot the software.

  • yymmddhhmm—Absolute time at which to reboot the software, specified as year, month, day, hour, and minute.

  • hh:mm—Absolute time on the current day at which to stop the software, specified in 24-hour time.

both-routing-engines—(Optional) Reboot both Routing Engines at the same time.
hypervisor—(Optional) Reboot Junos OS, host OS, and any installed guest VMs.
in minutes—(Optional) Number of minutes from now to reboot the software. The minimum value is 1. This option is an alias for the at +minutes option.
in-service—(Optional) Enables you to reset the software state (no software version change) of the system with minimal disruption in data and control traffic.
junos—(Optional) Reboot from the Junos OS (main) volume.
lcc number——(Optional) Line-card chassis (LLC) number.

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.

media (compact-flash | disk | removable-compact-flash | usb)—(Optional) Use the indicated boot medium for the next boot.
media (external | internal)—(Optional) Use the indicated boot medium for the next boot:

  • external—Reboot the device using a software package stored on an external boot source, such as a USB flash drive.

  • internal—Reboot the device using a software package stored in an internal memory source.

message "text"—(Optional) Message to display to all system users before stopping or rebooting the software.
network—(Optional) Reboot using the Preboot Execution Environment (PXE) boot method over the network.
oam—(Optional) Reboot from the maintenance volume (OAM volume, usually the compact flash drive).
other-routing-engine—(Optional) Reboot the other Routing Engine from which the command is issued. For example, if you issue the command from the primary Routing Engine, the backup Routing Engine is rebooted. Similarly, if you issue the command from the backup Routing Engine, the primary Routing Engine is rebooted.
partition partition—(Optional) Reboot using the specified partition on the boot media. This option is equivalent to the slice option that is supported on some devices. Specify one of the following partition values:

  • 1—Reboot from partition 1.

  • 2—Reboot from partition 2.

  • alternate—Reboot from the alternate partition.

scc—(Optional) Reboot the Routing Engine on the TX Matrix switch-card chassis. If you issue the command from re0, re0 is rebooted. If you issue the command from re1, re1 is rebooted.
sfc number—(Optional) Reboot the Routing Engine on the TX Matrix Plus switch-fabric chassis. If you issue the command from re0, re0 is rebooted. If you issue the command from re1, re1 is rebooted. Replace number with 0.
slice slice—(Optional) Reboot using the specified partition on the boot media. This option was originally the partitiion option but was renamed to slice on EX Series and QFX Series switches. Specify one of the following slice values:

  • 1—Reboot from partition 1.

  • 2—Reboot from partition 2.

  • alternate—Reboot from the alternate partition (which did not boot the switch at the last bootup).

Note

The slice option is not supported on QFX Series switches that have no alternate slice when Junos OS boots as a Virtual Machine (VM). To switch to the previous version of Junos OS, issue the request system software rollback command.

usb—(Optional) Reboot from a USB device.

The following options are available only on QFabric Systems:

all—(Optional) Reboots the software on the Director group, fabric control Routing Engines, fabric manager Routing Engines, Interconnect devices, and network and server Node groups.
director-device name—(Optional) Reboots the software on the Director device and the default partition (QFabric CLI).
director-group—(Optional) Reboots the software on the Director group and the default partition (QFabric CLI).
fabric—(Optional) Reboots the fabric control Routing Engines and the Interconnect devices.
node-group name—(Optional) Reboots the software on a server Node group or a network Node group.
graceful—(Optional) Enables the QFabric component to reboot with minimal impact to network traffic. This sub-option is only available for the all, fabric, anddirector-group options.

Additional Information

Reboot requests are recorded in the system log files, which you can view with the show log command (see show log). Also, the names of any running processes that are scheduled to be shut down are changed. You can view the process names with the show system processes command (see show system processes).

On a TX Matrix or TX Matrix Plus router, if you issue the request system reboot command on the primary Routing Engine, all the primary Routing Engines connected to the routing matrix are rebooted. If you issue this command on the backup Routing Engine, all the backup Routing Engines connected to the routing matrix are rebooted.

Note

Before issuing the request system reboot command on a TX Matrix Plus router with no options or the all-chassis, all-lcc, lcc number, or sfc options, verify that primary Routing Engine for all routers in the routing matrix are in the same slot number. If the primary Routing Engine for a line-card chassis is in a different slot number than the primary Routing Engine for a TX Matrix Plus router, the line-card chassis might become logically disconnected from the routing matrix after the request system reboot command.

Note

To reboot a router that has two Routing Engines, reboot the backup Routing Engine (if you have upgraded it) first, and then reboot the primary Routing Engine.

Required Privilege Level

maintenance

Related Documentation

List of Sample Output

request system reboot

request system reboot (at 2300)

request system reboot (in 2 Hours)

request system reboot (Immediately)

request system reboot (at 1:20 AM)

request system reboot in-service

Output Fields

When you enter this command, you are provided feedback on the status of your request.

Sample Output

request system reboot

user@host> request system reboot

request system reboot (at 2300)

user@host> request system reboot at 2300 message ?Maintenance time!?

request system reboot (in 2 Hours)

The following example, which assumes that the time is 5 PM (17:00), illustrates three different ways to request the system to reboot in two hours:

user@host> request system reboot at +120 user@host> request system reboot in 120 user@host> request system reboot at 19:00

request system reboot (Immediately)

user@host> request system reboot at now

request system reboot (at 1:20 AM)

To reboot the system at 1:20 AM, enter the following command. Because 1:20 AM is the next day, you must specify the absolute time.

user@host> request system reboot at 06060120

request system reboot in-service

user@switch> request system reboot in-service