Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual page 425

that are installed in the router. When existing line modules come online during startup
and when new line modules are inserted in the chassis, image fixes for that particular
line module are requested and activated during module startup.
Line module image hotfixes that have been armed as startup hotfixes are activated
before application configuration occurs on the line module.
Only image fixes contained in hotfixes that are active on the primary SRP module
can be activated on the line modules during startup. Hotfixes that are armed but not
active on the primary SRP module are not activated on line modules.
A hotfix can contain a combination of image fixes. System controller (SC) and interface
controller (IC) image fixes are cumulative and activated in the order in which they
were armed. For forwarding controller (FC) image fixes, the last one armed is the
only one applied.
NOTE: Because image fixes are activated in a particular order, we recommend that
you create a list of any hotfixes that you are currently running or intend to run with
a new FC image fix. JTAC can then provide you with the correct order of activation.
A hotfix cannot be partially activated on a router. If activation of any image hotfix
fails on any corresponding module, the entire activation fails for all applicable line
modules. Activation failure results in the generation of an appropriate log message.
E Series routers do not support activation of a hotfix on a per-slot basis or a
per-subsystem basis.
For example, suppose that a hotfix contains an image fix for the SRP module and
the GE-2 line module. The SRP image fix is successfully activated on the SRP module,
but the activation of the GE-2 image fix fails for some reason. In this case, the SRP
module image fix is deactivated and no further attempts are made to activate the
image fix on other GE-2 modules.
boot hotfix
Use to arm the specified hotfix as a startup hotfix that is automatically activated
the next time the SRP module reboots.
Arming fails if the specified hotfix depends on a hotfix that is not already armed.
In this event, the CLI displays an error message similar to the following:
% The hotfix, 975, requires the following hotfixes to be armed:
990
Arming fails if the hotfix is not compatible with the armed release. The CLI
displays the following error message:
% Hotfix is incompatible with armed release.
When a router reverts to its backup boot settings, as specified by the boot
backup command, no armed hotfixes are activated. The armed hotfix settings
are retained in the event the router reverts back to its normal boot settings.
Example
Chapter 6: Managing Modules
Updating the Router with JUNOSe Hotfix Files
395