request system reboot (Junos OS Evolved)
Syntax
request system reboot <at time> <in minutes> <message "text">
Syntax (QFX Series)
request system reboot <at time> <hitless> | <hitless no-confirm> <in minutes> <message "text">
Syntax (UfiSpace)
request system reboot <at time> <in minutes> <message "text">
request system reboot onie (install | update | rescue | embed) <at time> <in minutes> <message "text">
Description
Reboot the entire system (all nodes).
To reboot a single node, use the request node reboot command instead.
Options
| none |
Reboot the software immediately. |
||||||||
| at time |
(Optional) Time at which to reboot the software, specified in one of the following ways:
|
||||||||
| hitless |
(Optional) Perform a hitless graceful reboot to minimize traffic loss and prevent interface flapping. You will be prompted to continue and the hitless reboot will only begin if you respond with "yes". |
||||||||
| hitless no-confirm |
(Optional) Perform a hitless graceful reboot immediately without prompting the user. |
||||||||
| in minutes |
(Optional) Number of minutes from now to reboot the software. The minimum value is 1.
This option is an alias for the |
||||||||
| message "text" |
(Optional) Message to display to all system users before stopping or rebooting the software. |
||||||||
| onie | Reboot into the specified ONIE bootloader mode:
|
Additional Information
Starting in Junos OS Evolved 23.4R1, when rebooting a system with this command, the Layer 2
applications l2ald, l2ald-agent, l2cpd,
and l2cpd-agent are initialized and started only if any of the following
configuration hierarchy levels contain any configuration statements:
-
[edit interface interface-name unit number family ethernet-switching] -
[edit vlans] -
[edit routing-instance instance-name instance-type virtual-switch] -
[edit routing-instance instance-name instance-type mac-vrf] -
[edit protocols l2-learning]
Additionally, l2cpd, and l2cpd-agent are initialized and
started if the [edit protocols lldp] hierarchy level contains any
configuration statements.
As a result of this change, if your configuration already contains these configuration statements and you then delete all of the above configuration statements, these Layer 2 applications stop running.
Required Privilege Level
maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
- request system reboot
- request system reboot at 23:00
- request system reboot at 202607011200
- request system reboot in 1
- request system reboot (in 2 Hours)
- request system reboot (Immediately)
- request system reboot hitless
- request system reboot hitless no-confirm
- request system reboot onie install
request system reboot
user@host-re0> request system reboot The entire system (all nodes) will reboot causing traffic loss, do you wish to continue? [yes,no] (no) yes *** System shutdown message from root@host-re0 *** reboot the system at Tue Dec 6 13:32:24 2022 System going down IMMEDIATELY
request system reboot at 23:00
user@host-re0> request system reboot at 23:00 The entire system (all nodes) will reboot causing traffic loss, do you wish to continue? [yes,no] (no) yes *** System shutdown message from root@host-re0 *** reboot the system at Mon Dec 5 23:00:00 2022
request system reboot at 202607011200
user@host-re0> request system reboot at 202607011200 The entire system (all nodes will reboot causing traffic loss, do you wish to continue? [yes,no] (no) yes *** System shutdown message from root@host-re0 *** reboot the system at Wed Jul 1 12:00:00 2026
request system reboot in 1
user@host-re0> request system reboot in 1
The entire system (all nodes) will reboot causing traffic loss, do you wish to continue? [yes,no] (no) yes
*** System shutdown message from root@host-re0 ***
reboot the system at Mon Dec 5 15:08:00 2022request 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-re0> request system reboot at +120 user@host-re0> request system reboot in 120 user@host-re0> request system reboot at 19:00
request system reboot (Immediately)
user@host-re0> request system reboot at now The entire system (all nodes) will reboot causing traffic loss, do you wish to continue? [yes,no] (no) yes
request system reboot hitless
user@host-re0> request system reboot hitless Do you want to proceed with kernel hitless warm reboot? [yes,no] yes Starting hitless kernel warm reboot... App config validation succeeded for current version ----- Impact report for kernel warm reboot ----- Actions prior to warm reboot: *** Applications that need prep to warm reboot *** rpdagent *** Applications that need prep to warm reboot final *** agentd arpd evo-pfemand l2cpd-agent ndp picd rpdagent Actions post warm reboot: *** Applications that need sw sync *** evo-pfemand *** Applications that need hw sync *** evo-pfemand *** Applications that need unprep to warm reboot *** agentd arpd evo-pfemand l2cpd-agent ndp picd rpdagent Sending prepare notification to app rpdagent on node re0 Prepare to warm reboot succeeded for app rpdagent on node re0 Sending prepare final notification to app agentd on node re0 Sending prepare final notification to app arpd on node re0 Sending prepare final notification to app evo-pfemand on node re0 Sending prepare final notification to app l2cpd-agent on node re0 Sending prepare final notification to app ndp on node re0 Sending prepare final notification to app picd on node re0 Sending prepare final notification to app rpdagent on node re0 Prepare to warm reboot succeeded for app arpd on node re0 Prepare to warm reboot succeeded for app picd on node re0 Prepare to warm reboot succeeded for app agentd on node re0 Prepare to warm reboot succeeded for app evo-pfemand on node re0 Prepare to warm reboot succeeded for app rpdagent on node re0 Prepare to warm reboot succeeded for app l2cpd-agent on node re0 Prepare to warm reboot succeeded for app ndp on node re0 Saving system snapshot and rebooting. See /var/log/warm_reboot.log for warm reboot logs
request system reboot hitless no-confirm
user@host-re0> request system reboot hitless no-confirm Starting hitless kernel warm reboot... App config validation succeeded for current version ----- Impact report for kernel warm reboot ----- Actions prior to warm reboot: *** Applications that need prep to warm reboot *** rpdagent *** Applications that need prep to warm reboot final *** agentd arpd evo-pfemand l2cpd-agent ndp picd rpdagent Actions post warm reboot: *** Applications that need sw sync *** evo-pfemand *** Applications that need hw sync *** evo-pfemand *** Applications that need unprep to warm reboot *** agentd arpd evo-pfemand l2cpd-agent ndp picd rpdagent Sending prepare notification to app rpdagent on node re0 Prepare to warm reboot succeeded for app rpdagent on node re0 Sending prepare final notification to app agentd on node re0 Sending prepare final notification to app arpd on node re0 Sending prepare final notification to app evo-pfemand on node re0 Sending prepare final notification to app l2cpd-agent on node re0 Sending prepare final notification to app ndp on node re0 Sending prepare final notification to app picd on node re0 Sending prepare final notification to app rpdagent on node re0 Prepare to warm reboot succeeded for app agentd on node re0 Prepare to warm reboot succeeded for app picd on node re0 Prepare to warm reboot succeeded for app rpdagent on node re0 Prepare to warm reboot succeeded for app ndp on node re0 Prepare to warm reboot succeeded for app arpd on node re0 Prepare to warm reboot succeeded for app evo-pfemand on node re0 Prepare to warm reboot succeeded for app l2cpd-agent on node re0 Saving system snapshot and rebooting. See /var/log/warm_reboot.log for warm reboot logs
request system reboot onie install
user@host-re0> request system reboot onie install The entire system (all nodes) will reboot causing traffic loss, do you wish to continue? [yes,no] (no) yes user@host-re0> *** System shutdown message from user@host-re0 *** System going down IMMEDIATELY
Release Information
Command introduced in Junos OS Evolved Release 18.3R1.
Option to set a future date and time introduced in Junos OS Evolved Release 25.2R1.
hitless and hitless no-confirm options introduced in
Junos OS Evolved release 25.4R1 for QFX Series devices.
onie options introduced in Junos OS Evolved Release 25.4R1 for UfiSpace
devices.