Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

request system reboot

Syntax

request system reboot <at time><both-routing-engines><in minutes><media (compact-flash | disk | removable-compact-flash | usb)> <message "text"><other-routing-engine>

Syntax (EX Series Switches)

request system reboot <all-members><at time> <both-routing-engines><in minutes><local><media (external | internal)><member member-id><message "text"><other-routing-engine><slice slice>

Syntax (TX Matrix Router)

request system reboot <all-chassis | all-lcc | lcc number | scc><at time><both-routing-engines><in minutes> <media (compact-flash | disk)><message "text"> <other-routing-engine>

Syntax (TX Matrix Plus Router)

request system reboot <all-chassis | all-lcc | lcc number | sfc number><at time><both-routing-engines><in minutes> <media (compact-flash | disk)><message "text"> <other-routing-engine><partition (1 | 2 | alternate)>

Syntax (MX Series Router)

request system reboot <all-members><at time> <both-routing-engines><in minutes><local><media (external | internal)><member member-id><message "text"><other-routing-engine>

Release Information

Command introduced before Junos OS Release 7.4.

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

Command introduced in Junos OS Release 9.0 for EX Series switches.

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

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

Description

Reboot the software.

Options

none
—

Reboot the software immediately.

all-chassis
—

(TX Matrix routers and TX Matrix Plus routers only) (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
—

(TX Matrix routers andTX Matrix Plus routers only) (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
—

(EX4200 switches and MX Series routers only) (Optional) Reboot the software on all members of the Virtual Chassis configuration.

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.

in minutes
—

(Optional) Number of minutes from now to reboot the software. This option is an alias for the at +minutes option.

lcc number
—

—(TX Matrix routers and TX Matrix Plus routers only) (Optional) Line-card chassis 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.
local
—

(EX4200 switches and MX Series routers only) (Optional) Reboot the software on the local Virtual Chassis member.

media (compact-flash | disk | removable-compact-flash | usb)
—

(Optional) Boot medium for next boot. (The options removable-compact-flash and usb pertain to the J Series routers only.)

media (external | internal)
—

(EX Series switches and MX Series routers only) (Optional) Reboot the boot media:

  • external—Reboot the external mass storage device.
  • internal—Reboot the internal flash device.
member member-id
—

(EX4200 switches and MX Series routers only) (Optional) Reboot the software on the specified member of the Virtual Chassis configuration. For EX4200 switches, replace member-id with a value from 0 through 9. For an MX Series Virtual Chassis, replace member-id with a value of 0 or 1.

message "text"
—

(Optional) Message to display to all system users before stopping or rebooting the software.

other-routing-engine
—

(Optional) Reboot the other Routing Engine from which the command is issued. For example, if you issue the command from the master Routing Engine, the backup Routing Engine is rebooted. Similarly, if you issue the command from the backup Routing Engine, the master Routing Engine is rebooted.

partition
—

(TX Matrix Plus routers only) (Optional) Reboot using the specified partition on the boot media. This option has the following suboptions:

  • 1—Reboot from partition 1.
  • 2—Reboot from partition 2.
  • alternate—Reboot from the alternate partition.
scc
—

(TX Matrix routers only) (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
—

(TX Matrix Plus routers only) (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
—

(EX Series switches only) (Optional) Reboot a partition on the boot media. This option has the following suboptions:

  • 1—Power off partition 1.
  • 2—Power off partition 2.
  • alternate—Reboot from the alternate partition.

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 master Routing Engine, all the master 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 master Routing Engine for all routers in the routing matrix are in the same slot number. If the master Routing Engine for a line-card chassis is in a different slot number than the master 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 master 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)

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@berry.network.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

Published: 2013-03-14

Previous Page Next Page