Removing Hotfixes; Hotfixes And Backup Settings - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual

JunosE 11.3.x System Basics Configuration Guide

Removing Hotfixes

Hotfixes and Backup Settings

380
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 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.
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.
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.
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.
Copyright © 2010, Juniper Networks, Inc.