Rebooting Your System

You can reboot your system as a whole or select a single slot in the system to be rebooted. You can reboot your system immediately or in a designated interval of time, and can configure the system to prompt you if the modules are in a state that might lead to a loss of configuration data or an NVS corruption.

If you reboot the system before it has completely written configuration updates to NVS, the system starts with the last saved configuration. If you reboot the system after it has written the configuration updates to NVS, but before it has applied those updates to actual configuration data, the configuration update process resumes immediately following the reboot and completes before any application accesses its configuration data. For more information about stateful line module switchover, see Managing Stateful Line Module Switchover in the JunosE Services Availability Configuration Guide.

When stateful switchover for line modules is configured on a router and is activated, the line modules undergo a cold boot and, during this process, the secondary line module remains in the disabled or not online state. The primary line module returns to the online state. If the primary line module fails to become active within the specified timeout value (of less than 8.5 minutes), the secondary line module takes over as the primary and high availability is retained in the disabled state. All warm switchover processes are recorded in the reboot-history file on the currently active SRP module as warm restart.




reload slot

Rebooting When a Command Takes a Prolonged Time to Execute

Although some commands might take a relatively long time to execute, most do not. If the CLI displays no output other than “ Please wait...” for a prolonged period, you can press Ctrl+x to reset the system. Use Ctrl+x only as a last resort; if at all possible, wait until the command is completed, or attempt to connect to the system through a Telnet or SSH client through which you can use the reload command.

service ctrl-x-reboot

Configuration Caching

Configuration caching prevents the system from being partially configured with changes in the event of a reset. When a script or macro begins execution, the resulting configuration changes are automatically cached in system RAM rather than being committed to nonvolatile storage (NVS). When the script or macro completes execution, the cache is flushed as a background operation, saving the configuration changes to NVS.

If the SRP module resets during the script or macro execution, the system boots as though the script were never started because no NVS files have changed. If the SRP module resets during the flush operation, the system boots with factory defaults.

If you start another script or macro in the middle of an ongoing flush operation, the current flush is halted; now if the SRP module resets during the script, the system boots with factory defaults.

If you issue the reload command to manually reset the system, the system checks for an ongoing cache flush and warns you if a flush operation is discovered.