Package management: install commit?

[simone.c]

Hi all,

I'm trying to understand what is the purpose/importance of performing a install commit after having installed couple of packages in my ASR9906. I noticed that if I perform a reload without committing, the packages will still be available after the reload. So what is really accomplished with install commit? I found this explanation which I can't really understand:

When a package is activated, it becomes part of the current running configuration. To make the package activation persistent across designated secure domain router shelf controller (DSDRSC) reloads, enter the install commit command. On startup, the DSDRSC of the SDR loads this committed software set.

Any clarification would be really appreciated!

Thanks,

Simone

[tkarnani · Accepted solution]

Install commit is writing the boot string.

for example.

router is running 6.1.1, you perform the install add for 6.3.3 and activate the code.

lets assume you did not "install commit". when you reload the router it will come back with 6.1.1 running.

the idea behind it is to allow you to verify services and if you have any issues you can quickly roll back to the older code.

thanks

[simone.c]

Thanks for your quick reply, tkarnani!

So based on your statement, and given that each package (e.g. MPLS, EIGRP, ISIS) is specific to the version, the install commit does not affect anyhow the aforementioned packages, it affects only the boot image. Did I get it right?

Simone

[tkarnani]

Hi Simone,

install commit will affect all packages on the device at the time.

here is an example from our lab.

show install active summary, will display all the currently running packages

RP/0/RSP0/CPU0:ASR-9001-C#show install active summary
Fri May 29 22:58:05.670 EDT
Default Profile:
  SDRs:
    Owner
  Active Packages:
    disk0:asr9k-services-infra-6.5.3
    disk0:asr9k-video-px-6.5.3
    disk0:asr9k-services-px-6.5.3
    disk0:asr9k-optic-px-6.5.3
    disk0:asr9k-mpls-px-6.5.3
    disk0:asr9k-mini-px-6.5.3
    disk0:asr9k-mgbl-px-6.5.3
    disk0:asr9k-mcast-px-6.5.3
    disk0:asr9k-li-px-6.5.3
    disk0:asr9k-k9sec-px-6.5.3
    disk0:asr9k-fpd-px-6.5.3
    disk0:asr9k-doc-px-6.5.3
    disk0:asr9k-bng-px-6.5.3
    disk0:asr9k-9000v-nV-px-6.5.3
    disk0:asr9k-px-6.5.3.sp3-1.0.0

RP/0/RSP0/CPU0:ASR-9001-C#

show install committed summary.

if the router were to reload/power cycle, these are the packages that will be running when the router comes back up

RP/0/RSP0/CPU0:ASR-9001-C#show install committed summary
Fri May 29 22:59:03.417 EDT
Default Profile:
  SDRs:
    Owner
  Committed Packages:
    disk0:asr9k-services-infra-6.5.3
    disk0:asr9k-video-px-6.5.3
    disk0:asr9k-services-px-6.5.3
    disk0:asr9k-optic-px-6.5.3
    disk0:asr9k-mpls-px-6.5.3
    disk0:asr9k-mini-px-6.5.3
    disk0:asr9k-mgbl-px-6.5.3
    disk0:asr9k-mcast-px-6.5.3
    disk0:asr9k-li-px-6.5.3
    disk0:asr9k-k9sec-px-6.5.3
    disk0:asr9k-fpd-px-6.5.3
    disk0:asr9k-doc-px-6.5.3
    disk0:asr9k-bng-px-6.5.3
    disk0:asr9k-9000v-nV-px-6.5.3
    disk0:asr9k-px-6.5.3.sp3-1.0.0

RP/0/RSP0/CPU0:ASR-9001-C#

i do not have a recent image upgrade to show you the difference. however if we were to just do an upgrade and the router come up with the new image. install active summary would be different from install committed summary

thanks

[simone.c]

Hi,

I've tested this on my ASR9906, version 6.6.2. If I issue a reload without having committed the activated packages, the device will come back with the exact same active packages it had before the reload.

[tkarnani]

Hi Simone,

that seems weird. can you please post

"show install active summary" " show install committed"

thank you

[simone.c]

Hi!

RP/0/RSP0/CPU0:LAB-ASR#show install active summary
Sat May 30 06:31:57.803 UTC
Active Packages: 7
asr9k-xr-6.6.2 version=6.6.2 [Boot image]
asr9k-k9sec-x64-2.1.0.0-r662
asr9k-mpls-x64-2.0.0.0-r662
asr9k-mcast-x64-2.0.0.0-r662
asr9k-bng-x64-1.0.0.0-r662
asr9k-mgbl-x64-2.0.0.0-r662
asr9k-eigrp-x64-1.0.0.0-r662

RP/0/RSP0/CPU0:LAB-ASR#show install committed
Sat May 30 06:32:01.685 UTC
Node 0/RSP0/CPU0 [RP]
Boot Partition: xr_lv1
Committed Packages: 2
asr9k-xr-6.6.2 version=6.6.2 [Boot image]
asr9k-k9sec-x64-2.1.0.0-r662

Node 0/RSP1/CPU0 [RP]
Boot Partition: xr_lv1
Committed Packages: 2
asr9k-xr-6.6.2 version=6.6.2 [Boot image]
asr9k-k9sec-x64-2.1.0.0-r662

Node 0/0/CPU0 [LC]
Boot Partition: xr_lv1
Committed Packages: 2
asr9k-xr-6.6.2 version=6.6.2 [Boot image]
asr9k-k9sec-x64-2.1.0.0-r662

Node 0/1/CPU0 [LC]
Boot Partition: xr_lv1
Committed Packages: 2
asr9k-xr-6.6.2 version=6.6.2 [Boot image]
asr9k-k9sec-x64-2.1.0.0-r662

I think this behaviour might be related to a redundat RSP setup. I issued the reload command yesterday, but it seems to me that it just caused a switch of the active RSP... and the activated packages remain available.

RP/0/RSP0/CPU0:LAB-ASR#sh vers
Sat May 30 06:33:25.127 UTC
Cisco IOS XR Software, Version 6.6.2
Copyright (c) 2013-2019 by Cisco Systems, Inc.

Build Information:
Built By : ahoang
Built On : Fri Apr 26 16:54:14 PDT 2019
Built Host : iox-ucs-032
Workspace : /auto/srcarchive16/prod/6.6.2/asr9k-x64/ws
Version : 6.6.2
Location : /opt/cisco/XR/packages/

cisco ASR9K () processor
System uptime is 11 weeks 1 day 16 hours 18 minutes

RP/0/RSP0/CPU0:LAB-ASR#show redundancy
Sat May 30 06:33:32.948 UTC
Redundancy information for node 0/RSP0/CPU0:
==========================================
Node 0/RSP0/CPU0 is in ACTIVE role
Partner node (0/RSP1/CPU0) is in STANDBY role
Standby node in 0/RSP1/CPU0 is ready
Standby node in 0/RSP1/CPU0 is NSR-ready

Reload and boot info
----------------------
A9K-RSP5-32G reloaded Tue Mar 10 12:17:10 2020: 11 weeks, 3 days, 18 hours, 16 minutes ago
Active node booted Thu Mar 12 14:14:38 2020: 11 weeks, 1 day, 16 hours, 18 minutes ago
Last switch-over Fri May 29 14:24:51 2020: 16 hours, 8 minutes ago

[tkarnani · Accepted solution]

Hi Simone,

yes that would make more sense. thanks for confirming