Table of Contents
Advertisement
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:
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.
Dependency A hotfix that must be active or armed before another hotfix can
be activated or armed.
Safe With A list of hotfixes with which another hotfix is compatible and can
safely be concurrently armed or activated. This list applies only to hotfixes that
have some patched functionality in common and are armed or activated
concurrently.
Unsafe With A list of hotfixes with which another hotfix is not compatible and
cannot safely be concurrently armed or activated. The CLI displays a warning
message when you try to activate a hotfix that is unsafe with one or more active
or armed hotfixes.
Manual Activate [Active / Standby] Srp The name of a binary flag that indicates
whether manual activation of the hotfix is allowed on the active and standby
SRP modules. When the flag is set to false, you cannot manually activate the
hotfix; instead, the hotfix can only be activated as a startup hotfix. The CLI
displays a warning message when you try to activate a hotfix that cannot be
manually activated.
Manual Deactivate [Active / Standby] Srp The name of a binary flag that
indicates whether manual deactivation of the hotfix is allowed on the active and
standby SRP modules. When the flag is set to false, you cannot manually
deactivate the hotfix. You must disarm the hotfix and reload the router. The CLI
displays a warning message when you try to deactivate a hotfix that cannot be
manually deactivated.
Line card requires reload The name of a binary flag that indicates whether line
modules require a reload for the hotfix to become active on the module. The CLI
Chapter 6: Managing Modules
Updating the Router with JUNOSe Hotfix Files
393
Advertisement
Table of Contents
Troubleshooting
