Removing Hotfixes; Hotfixes And Backup Settings; Hotfixes And Standby Srp Modules; Hotfixes And Line Modules - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

JUNOSe 11.1.x System Basics Configuration Guide
Hotfixes remain armed only for compatible releases. If you change the armed release
by issuing the boot system command, hotfixes that are not compatible with the new
release are no longer armed. However, if you subsequently rearm a compatible
release, the previously armed hotfixes for that release are automatically armed again.

Removing Hotfixes

You can deactivate, disarm, and delete hotfixes from a router. When you deactivate
a hotfix, any functionality that was added as part of the hotfix is automatically
removed (even though the .hfx file remains on the router).
You cannot deactivate a hotfix that is a dependency for other hotfixes until you
deactivate the dependent hotfixes. When a hotfix is no longer active, you can use
the delete command to remove the hotfix file from the flash card.

Hotfixes and Backup Settings

The boot backup command does not explicitly support hotfix files. When a system
reloads with the backup settings specified by the boot backup command, no armed
hotfixes are activated. However, the armed hotfix settings are retained in the event
that the system reverts to its normal (nonbackup) boot settings. If that happens,
these hotfixes are automatically rearmed and reactivated after a reload.

Hotfixes and Standby SRP Modules

Hotfixes are supported in redundant SRP module configurations. Hotfix files are
synchronized between the active and standby SRP modules by both automatic and
manual synchronization. Hotfix activation restrictions are enforced identically on
the active and standby SRP modules. A hotfix that is hot-patchable on the active
module is hot-patchable on the standby module. A hotfix that requires startup
activation on the active SRP module also requires startup activation on the standby
SRP module.
Hotfixes are synchronized from the active SRP module to the standby SRP module.
The standby SRP automatically activates the hotfixes that are armed as startup
hotfixes. However, if the synchronization reveals that the set of active hotfixes on
the standby SRP module is different from the set of armed hotfixes on the active
SRP module, then the standby SRP module automatically reboots. This action causes
the standby SRP module to activate the startup hotfixes. When you activate or arm
a hotfix for startup activation, compatibility and dependency checks are performed
independently on the active and standby SRP modules.

Hotfixes and Line Modules

For line modules, a hotfix consists of one or more image fixes specific to a particular
model of module or to a module type, depending on the fix. When a hotfix is
activated, each image fix contained in the hotfix is activated on all applicable modules
394
Updating the Router with JUNOSe Hotfix Files
displays a warning message if the line modules must be reloaded. If the warning
is confirmed, the SRP module reloads each line module. The flag applies to all
line modules targeted by the hotfix that are installed in the router.