137
Power off and then power on the device. This method might cause data loss, and is the
least-preferred method.
Using the CLI, you can reboot the device from a remote host.
Configuration guidelines
When you schedule a reboot, follow these guidelines:
The automatic reboot configuration takes effect on all member devices. It will be canceled if a
master/subordinate switchover occurs.
For data security purposes, the device does not reboot while it is performing file operations.
Rebooting devices immediately at the CLI
Execute the following command in user view:
device or
devices.
reboot
[
slot
slot-number ]
[
force
]
Use this command in user view
Scheduling a device reboot
The device supports only one device reboot schedule. If you configure the scheduler reboot at or
scheduler reboot delay command multiple times or configure both commands, the most recent
configuration takes effect.
To schedule a reboot, execute either of the following commands in user view:
and time.
scheduler reboot at
time [ date ]
By default, no reboot date or time is specified.
time.
scheduler reboot delay
time
By default, no reboot delay time is specified.
Scheduling a task
You can schedule the device to automatically execute a command or a set of commands without
administrative interference.
You can configure a non-periodic schedule or a periodic schedule. A non-periodic schedule is not
saved to the configuration file and is lost when the device reboots. A periodic schedule is saved to
the startup configuration file and is automatically executed periodically.
Configuration guidelines
Follow these guidelines when you schedule a task:
Make sure all commands in a schedule are compliant to the command syntax. The system does
not check the syntax when you assign a command to a job.
A schedule cannot contain any of these commands: telnet, ftp, ssh2, and monitor process.
To Next Page
Loading...
Need help?
General