request system reboot
List of Syntax
SyntaxSyntax (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.
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
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.
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.
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.
1—Reboot from partition 1.
2—Reboot from partition 2.
alternate—Reboot from the alternate partition.
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).
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.
The following options are available only on QFabric Systems:
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.
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.
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 rebootrequest 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
Reboot the system ? [yes,no] (no)
request system reboot (at 2300)
user@host> request system reboot at 2300 message
?Maintenance time!?
Reboot the system ? [yes,no] (no) yes shutdown: [pid 186] *** System shutdown message from root@test.example.net *** System going down at 23:00
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 at 120 Reboot the system at 120? [yes,no] (no) yes
request system reboot in-service
user@switch> request system reboot in-service
Reboot the system ? [yes,no]
[Feb 22 02:37:04]:ISSU: Validating Image PRE ISSR CHECK: --------------- PFE Status : Online Member Id zero : Valid VC not in mixed or fabric mode : Valid Member is single node vc : Valid BFD minimum-interval check done : Valid GRES enabled : Valid NSR enabled : Valid drop-all-tcp not configured : Valid Ready for ISSR : Valid warning: Do NOT use /user during ISSR. Changes to /user during ISSR may get lost! Current image is jinstall-jcp-i386-flex-18.1.img [Feb 22 02:37:14]:ISSU: Preparing Backup RE Prepare for ISSR [Feb 22 02:37:19]:ISSU: Backup RE Prepare Done Spawning the backup RE Spawn backup RE, index 1 successful Starting secondary dataplane Second dataplane container started GRES in progress Waiting for backup RE switchover ready GRES operational Copying home directories Copying home directories successful Initiating Chassis In-Service-Upgrade for ISSR Chassis ISSU Started [Feb 22 02:42:55]:ISSU: Preparing Daemons [Feb 22 02:43:00]:ISSU: Daemons Ready for ISSU [Feb 22 02:43:05]:ISSU: Starting Upgrade for FRUs [Feb 22 02:43:15]:ISSU: FPC Warm Booting [Feb 22 02:44:16]:ISSU: FPC Warm Booted [Feb 22 02:44:27]:ISSU: Preparing for Switchover [Feb 22 02:44:31]:ISSU: Ready for Switchover Checking In-Service-Upgrade status Item Status Reason FPC 0 Online (ISSU) Send ISSR done to chassisd on backup RE Chassis ISSU Completed Removing dcpfe0 eth1 128.168.0.16 IP Bringing down bme00 Post Chassis ISSU processing done [Feb 22 02:44:33]:ISSU: IDLE Stopping primary dataplane Clearing ISSU states Console and management sessions will be disconnected. Please login again. device_handoff successful ret: 0 Shutdown NOW! [pid 14305] *** FINAL System shutdown message from root@sw-duckhorn-01 *** System going down IMMEDIATELY