hotfix activate
•
Use to manually activate the specified hotfix.
•
Each image fix contained in the hotfix is downloaded from the local flash card to the
SRP module and any corresponding line module, and then activated on the modules.
•
When a new line module is inserted in the router, all applicable image fixes are activated
during initialization of the module. Activation is performed by the line module
operational image before application configuration takes place on the module.
•
An activation failure for any image fix on its corresponding line module causes the
entire activation to fail. The image fix is then deactivated on any modules on which it
was successfully activated.
•
Activation fails if the specified hotfix is incompatible with the running release, In this
event, an error message similar to the following is displayed:
% Hotfix is incompatible with running release.
•
Activation fails if the specified hotfix depends on other hotfixes that have not been
activated. The CLI displays an error message similar to the following:
The hotfix, 975, requires the following hotfixes to be activated:
990
% Activation failed
•
Startup hotfixes cannot be manually activated. If you attempt to manually activate a
startup hotfix, the operation fails and generates the following error message:
% Manual activation not allowed
•
Example
host1#
hotfix activate hf63037.hfx
•
Use the
no
version to manually deactivate the specified hotfix. Deactivation restores
the system to the state that existed before the hotfix was activated. You can specify
the
all
keyword to deactivate all active hotfixes.
When you deactivate hotfixes that have dependencies, you must deactivate them in
the reverse sequence from which they were armed. However, if you have issued the
all
keyword, the disarming automatically takes place in the correct order.
•
See hotfix activate.
Monitoring Hotfixes
Several commands provide information about hotfixes that have been loaded on the
router. You can use the
show hotfix
command to discover the armed and activation
status of all hotfixes or a specific hotfix. The output lists the hotfix by name and a unique
ID number, which is useful if the filename has been changed. This command also displays
dependencies for each hotfix; that is, other hotfixes that must be activated before that
hotfix can be activated. For more usage details and sample output, see “show hotfix” on
page 385.
383
Copyright © 2010, Juniper Networks, Inc.
Chapter 6: Managing Modules
Summary of Contents for JUNOSE 11.3
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 3 x System Basics Configuration Guide...
Page 24: ...Copyright 2010 Juniper Networks Inc xxiv JunosE 11 3 x System Basics Configuration Guide...
Page 32: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 3 x System Basics Configuration Guide...
Page 146: ...Copyright 2010 Juniper Networks Inc 116 JunosE 11 3 x System Basics Configuration Guide...
Page 166: ...Copyright 2010 Juniper Networks Inc 136 JunosE 11 3 x System Basics Configuration Guide...
Page 432: ...Copyright 2010 Juniper Networks Inc 402 JunosE 11 3 x System Basics Configuration Guide...
Page 488: ...Copyright 2010 Juniper Networks Inc 458 JunosE 11 3 x System Basics Configuration Guide...
Page 524: ...Copyright 2010 Juniper Networks Inc 494 JunosE 11 3 x System Basics Configuration Guide...
Page 554: ...Copyright 2010 Juniper Networks Inc 524 JunosE 11 3 x System Basics Configuration Guide...
Page 566: ...Copyright 2010 Juniper Networks Inc 536 JunosE 11 3 x System Basics Configuration Guide...
Page 588: ...Copyright 2010 Juniper Networks Inc 558 JunosE 11 3 x System Basics Configuration Guide...
Page 613: ...PART 3 Index Index on page 585 583 Copyright 2010 Juniper Networks Inc...
Page 614: ...Copyright 2010 Juniper Networks Inc 584 JunosE 11 3 x System Basics Configuration Guide...
Page 632: ...Copyright 2010 Juniper Networks Inc 602 JunosE 11 3 x System Basics Configuration Guide...