- request system halt
- <at time>
- <both-routing-engines>
- <other-routing-engine>
- <in minutes>
- <media (compact-flash | disk | removable-compact-flash
| usb)>
- <message "text">
- request system halt
- <all-lcc | lcc number | scc>
- <at time>
- <both-routing-engines>
- <other-routing-engine>
- <in minutes>
- <media (compact-flash | disk)>
- <message "text">
Command introduced before JUNOS Release 7.4.
other-routing-engine option introduced in JUNOS Release 8.0.
Stop the router software.
none — Stop the router software immediately.
all-lcc — (Optional) (Routing matrix only) Halt all T640 routing nodes (or line-card chassis) connected to the TX Matrix platform.
lcc number — (Optional) (Routing matrix only) Halt a T640 routing node that is connected to the TX Matrix platform. Replace number with a value from 0 through 3.
scc — (Optional) (Routing matrix only) Halt only the master Routing Engine or the backup Routing Engine on the TX Matrix platform (or switch-card chassis). If you issue the command from the master Routing Engine, the master SCC is halted. If you issue the command from the backup Routing Engine, the backup SCC is halted.
at time — (Optional) Time at which to stop the software, specified in one of the following ways:
both-routing-engines — (Optional) Halt both Routing Engines at the same time.
other-routing-engine — (Optional) Halt 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 halted. Similarly, if you issue the command from the backup Routing Engine, the master Routing Engine is halted.
in minutes — (Optional) Number of minutes from now to stop the software. This option is an alias for the at +minutes option.
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 routing platform only.)
message "text" — (Optional) Message to display to all system users before stopping the software.
On the M7i router, the request system halt command does not immediately power down the Packet Forwarding Engine. The power-down process can take as long as 5 minutes.On a routing matrix, if you issue the request system halt command on the TX Matrix master Routing Engine, all the master Routing Engines connected to the routing matrix are halted. If you issue this command on the backup Routing Engine, all the backup Routing Engines connected to the routing matrix are halted. If you issue the request system halt both-routing-engines command on the TX Matrix, all the Routing Engines on the routing matrix are halted.
![]() |
Note: If you have a router with two Routing Engines and you want to shut the power off to the router or remove a Routing Engine, you must first halt the backup Routing Engine (if it has been upgraded), then halt the master Routing Engine. To halt a Routing Engine, issue the request system halt command. You can also halt both Routing Engines at the same time by issuing the request system halt both-routing-engines command. |
maintenance
When you enter this command, you are provided feedback on the status of your request.
user@host> request system halt
Halt the system ? [yes,no] (no) yes *** FINAL System shutdown message from root@section2 *** System going down IMMEDIATELY Terminated ... syncing disks... 11 8 done The operating system has halted. Please press any key to reboot.
The following example, which assumes that the time is 5 PM (1700), illustrates three different ways to request the system to stop 2 hours from now:
user@host> request system halt at +120user@host> request system
halt in 120user@host> request system halt at 19:00
user@host> request system halt at
now
To stop 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 halt at yymmdd120
request system halt at 120 Halt the system at 120? [yes,no] (no) yes