Configuring Your System for Booting

Juniper Networks delivers your E Series router already set up with a factory default configuration and a software release (.rel) file. You can, however, create a new configuration file (.cnf) and select a different software release file to use in future reboots of your router. When you reboot your router, you can use:

In addition, you can configure the system to load a different software release file on its next reboot. Use the boot system command to do this. If you do not configure your system with a backup release, it reverts to the release and configuration it had before the crash.

You can use the boot backup command to specify a software release and configuration for the system to use in case the system resets too many times in a given period.

The boot subsystem command enables you to override the system release setting for a given subsystem—for example, OC3.

Booting the GE-2 Line Module

The GE-2 line module can now detect whether it supports the software release installed on the primary SRP module in an E Series router. When the GE-2 line module is booting and it detects that it supports the software release on the SRP module, the line module boots successfully with that software release. However, if the GE-2 line module detects that it does not support the software release on the SRP module, the module does not boot successfully and the following messages appear in the system log:

ERROR 05/04/2005 06:09:05 system (slot 13): Line card failed diags in slot 13 with status: Autoboot disabledERROR 05/04/2005 06:09:05 system (slot 13): board failed diagnostics

boot backup

boot config

boot force-backup

boot revert-tolerance

boot revert-tolerance never

boot subsystem

boot system

Caution: This command attempts to reprogram the SRP boot PROMs, if necessary. The SRP has a primary and, typically, a backup boot PROM. If the boot system command is executed on an SRP with no backup boot PROM, the following message is displayed: “ Write to Backup Boot ROM failed.” In this instance, this message is correct, and you can ignore it.