This example presents several aspects of hotfix use. In this example, 6-0-1p0-5.rel is the currently armed and active release. Hotfix hf63035.hfx is compatible with this release and is currently activated and armed as a startup hotfix.
host1# dir
Active System Controller:
unshared in
file size size date (UTC) use
------------------------- --------- --------- ------------------- ---
reboot.hty 596288 596288 03/07/2005 19:35:52
system.log 6762 6762 03/07/2005 17:30:08
haIpSetup.mac 4874 4874 03/24/2004 10:02:08
6-0-1p0-5.rel 125987342 125987342 02/30/2005 18:17:32 !
6-1-0.rel 148489185 148489185 02/28/2005 20:19:20
hf63035.hfx 30445 30445 03/07/2005 14:04:02 !
hf63036.hfx 27445 27445 03/07/2005 16:12:05
hf63037.hfx 28324 28324 03/07/2005 16:13:25
host1# show hotfix detail
name id active armed requires
----------- -------- ------ ----- -----------
hf63035.hfx 12343035 X X
hf63036.hfx 23453036
hf63037.hfx 34563037 23453036
name synopsis
----------- --------------------------------------------
hf63035.hfx Fix for CQ63035, bgp crash, out of resources
hf63036.hfx Fixed show version formatting issue
hf63037.hfx Increased max session limit on ERX310 to 32,000
host1(config)# boot hotfix hf63037.hfx
% The hotfix, 34563037, requires the following hotfix(es) to be armed:
23453036
The hf63036.hfx hotfix must be armed as a startup hotfix:
host1(config)# boot hotfix hf63036.hfx
This command succeeds because hf63036.hfx is compatible with the currently armed release, 6-1-0.rel, and has no dependencies on other hotfixes.
Now the attempt to arm hf63037.hfx succeeds because its dependency on hf63036.hfx has been met.
host1(config)# boot hotfix hf63037.hfx
Now suppose the user reloads the router:
host1# reload
As the router loads the armed release, 6-1-0.rel, the hotfix loader discovers three armed startup hotfixes, hf63035.hfx, hf63036.hfx, and hf63037.hfx. Only hf63036.hfx and hf63037.hfx are activated. Hotfix hf63035.hfx is disarmed because it is incompatible with the new running release. The router therefore becomes operational running 6-1-0.rel with hf63036.hfx and hf63037.hfx activated.
host1# dir unshared in
file size size date (UTC) use
------------------------- --------- --------- ------------------- ---
reboot.hty 596288 596288 03/07/2005 19:35:52
system.log 6762 6762 03/07/2005 17:30:08
haIpSetup.mac 4874 4874 03/24/2004 10:02:08
6-0-1p0-5.rel 125987342 125987342 02/30/2005 18:17:32
6-1-0.rel 148489185 148489185 02/28/2005 20:19:20 !
hf63035.hfx 30445 30445 03/07/2005 14:04:02
hf63036.hfx 27445 27445 03/07/2005 16:12:05 !
hf63037.hfx 28324 28324 03/07/2005 16:13:25 !
host1#show hotfix
name active armed requires
----------- ------ ----- --------
hf63035.hfx
hf63036.hfx X X
hf63037.hfx X X 23453036
Now suppose the user attempts to deactivate hf63036.hfx:
host1#no hotfix activate hf63036.hfx
The hotfix, 23453036, has the following active dependents which must be deactivated first:
34563037
% De-activation failed.
The command fails because hf63037.hfx is dependent on hf63036.hfx. Interdependent hotfixes must be deactivated and disarmed in the reverse order that they were activated.
When 6-0-1p0-5.rel is re-armed and the router reloaded, the hotfix loader determines that the startup hotfixes, hf63036.hfx and hf63037.hfx, are incompatible with the release. It disarms these hotfixes. The user decides to delete the now unnecessary hotfixes from the router.
host1# delete hf63036.hfx
host1# delete hf63037.hfx
host1# dir
Active System Controller:
unshared in
file size size date (UTC) use
------------------------- --------- --------- ------------------- ---
reboot.hty 596288 596288 03/07/2005 19:35:52
system.log 6762 6762 03/07/2005 17:30:08
haIpSetup.mac 4874 4874 03/24/2004 10:02:08
6-0-1p0-5.rel 125987342 125987342 02/30/2005 18:17:32 !
6-1-0.rel 148489185 148412851 02/28/2005 20:19:20
hf63035.hfx 30445 30445 03/07/2005 14:04:02 !
host1# show hotfix detail
name active armed requires
----------- ------------ ----- --------
hf63035.hfx X X ---