Table of Contents
Advertisement
JUNOSe 11.1.x System Basics Configuration Guide
boot force-backup
NOTE: Even if you request the normal release/configuration, the boot logic still checks
the reboot history file. It may force the backup mode regardless of your request. To
guarantee that the boot logic does not override your request to use the normal
release/configuration, do either of the following:
boot revert-tolerance
boot revert-tolerance never
512
Configuring Your System for Booting
You can require the system to reboot from the factory default configuration. On
subsequent reboots, the system will use the running configuration current at the
time of that reboot:
host1(config)#boot config factory-defaults
This command does not reboot the system.
Use the no version to clear a previous request to reboot in a specified manner.
See boot config.
Use to force the system to use the backup release/configuration on the next boot.
This command does not reboot the system.
Example
host1(config)#boot force-backup mysafe.rel mysafe.cnf
Delete the reboot history file after issuing the no boot force-backup command.
Do not configure a backup release or configuration file.
Use the no version to set the system to return to its normal release/configuration
on the next boot.
See boot force-backup.
Use to set the reversion tolerances that the boot logic uses to determine whether
to use normal or backup settings.
The default settings tolerate up to three resets in 30 minutes.
This command does not reboot the system when high availability is not enabled.
Issuing this command when high availability is enabled results in the system
cold-restarting the router and using the backup settings if the tolerance settings
are met.
Example
host1(config)#boot revert-tolerance 2 60
Use the no version to restore the default values, 3 and 1800.
See boot revert-tolerance.
Advertisement
Table of Contents
Troubleshooting
