Juniper JUNOSE 11.3, Configuration Manual

Page: 409 / 632

Although most hotfixes can also be manually activated without reloading the router,
some hotfixes cannot. You can configure any hotfix to be activated automatically when
the router reloads.
A hotfix consists of a .hfx file and possibly other supporting files. The .hfx file manages
the associated files in much the same way that a .rel file manages supporting files
associated with a release image.
To use a hotfix, you must use the copy command to download the file from a network
host to the router. You cannot copy the hotfix to an FTP file server. You can use file system
commands such as
dir , rename , and delete with the hotfix. After a hotfix is copied to the
local flash card, it remains there until you explicitly delete it.
Hotfixes must be activated to take effect. A startup hotfix is automatically activated
during system initialization. A hot-patchable hotfix does not require a reload to become
active; it takes effect immediately if compatibilities and dependencies are correctly met.
You can manually install hot-patchable hotfixes with the
hotfix activate command.
Hot-patchable hotfixes can also be configured to be activated as a startup hotfix.
Arming a hotfix prepares it for activation after a system reload. You can configure hotfixes
in several ways with the
boot hotfix and hotfix activate commands, as in the following
examples:
•
Activated immediately on an active router but not armed as a startup hotfix. In this
case, the hotfix is activated only until the SRP module reloads. If the SRP module
reloads, then you must manually activate the hotfix again (if desired) with the
hotfix
activate command.
•
Activated immediately on an active router and armed as a startup hotfix. In this case
the hotfix is automatically activated after every reload.
• Armed as a startup hotfix with the boot hotfix command but not immediately activated.
In this case the hotfix is activated when the SRP module reloads.
When a system reloads with the backup settings specified by the boot backup command,
no armed hotfixes are activated. The currently armed hotfix settings are retained in the
event that the router reverts back to its normal boot settings.
Hotfix Compatibility and Dependency
Hotfixes can have compatibility and dependency requirements. A given hotfix is
compatible with one or more releases. It can be dependent on one or more other hotfixes
being active. Compatibility and dependency requirements are stored as part of the hotfix.
The requirements are enforced at the time of arming or activation. If the software installed
and active on the router does not match the requirements specified in the hotfix, then
activation of the hotfix fails. Such a failure generates appropriate error and log messages.
The following restrictions can apply to a hotfix:
379 Copyright © 2010, Juniper Networks, Inc.
Chapter 6: Managing Modules