Active and Committed pkg are different on A9K

[Rps-Cheers]

Hello Friends.

I have a question about the A9K package. The contents of Active and Committed pkgs on A9K devices are different, such as the following states:

Active Packages:
    disk0:asr9k-px-4.3.4.CSCut30136-1.0.0
    disk0:asr9k-bng-px-4.3.4
    disk0:asr9k-doc-px-4.3.4
    disk0:asr9k-fpd-px-4.3.4
    disk0:asr9k-k9sec-px-4.3.4
    disk0:asr9k-li-px-4.3.4
    disk0:asr9k-mcast-px-4.3.4
    disk0:asr9k-mgbl-px-4.3.4
    disk0:asr9k-mini-px-4.3.4
    disk0:asr9k-mpls-px-4.3.4
    disk0:asr9k-optic-px-4.3.4
    disk0:asr9k-px-4.3.4.CSCug75299-1.0.0
    disk0:asr9k-px-4.3.4.CSCuh93866-1.0.0
    disk0:asr9k-px-4.3.4.CSCui28202-1.0.0
    disk0:asr9k-px-4.3.4.CSCui67212-1.0.0
    disk0:asr9k-px-4.3.4.CSCui94441-1.0.0
    disk0:asr9k-px-4.3.4.CSCuj83661-1.0.0
    disk0:asr9k-px-4.3.4.CSCul39674-1.0.0
    disk0:asr9k-px-4.3.4.CSCul58246-1.0.0
    disk0:asr9k-px-4.3.4.CSCul66510-1.0.0

  Committed Packages:
    disk0:asr9k-px-4.3.4.CSCut30136-1.0.0
    disk0:asr9k-bng-px-4.3.4
    disk0:asr9k-doc-px-4.3.4
    disk0:asr9k-fpd-px-4.3.4
    disk0:asr9k-k9sec-px-4.3.4
    disk0:asr9k-li-px-4.3.4
    disk0:asr9k-mcast-px-4.3.4
    disk0:asr9k-mgbl-px-4.3.4
    disk0:asr9k-mini-px-4.3.4
    disk0:asr9k-mpls-px-4.3.4
    disk0:asr9k-optic-px-4.3.4
    disk0:asr9k-px-4.3.4.CSCug75299-1.0.0
    disk0:asr9k-px-4.3.4.CSCuh93866-1.0.0
    disk0:asr9k-px-4.3.4.CSCui09934-1.0.0
    disk0:asr9k-px-4.3.4.CSCui15435-1.0.0
    disk0:asr9k-px-4.3.4.CSCui28202-1.0.0
    disk0:asr9k-px-4.3.4.CSCui67212-1.0.0
    disk0:asr9k-px-4.3.4.CSCui94441-1.0.0
    disk0:asr9k-px-4.3.4.CSCuj01579-1.0.0
    disk0:asr9k-px-4.3.4.CSCuj83661-1.0.0
    disk0:asr9k-px-4.3.4.CSCul39674-1.0.0
    disk0:asr9k-px-4.3.4.CSCul58246-1.0.0
    disk0:asr9k-px-4.3.4.CSCul66510-1.0.0
    disk0:asr9k-px-4.3.4.CSCum03261-1.0.0
    disk0:asr9k-px-4.3.4.CSCum26074-1.0.0
    disk0:asr9k-px-4.3.4.CSCum27065-1.0.0
    disk0:asr9k-px-4.3.4.CSCum43188-1.0.0
    disk0:asr9k-px-4.3.4.CSCum44940-1.0.0
    disk0:asr9k-px-4.3.4.CSCum51429-1.0.0
    disk0:asr9k-px-4.3.4.CSCum70202-1.0.0
    disk0:asr9k-px-4.3.4.CSCum97742-1.0.0
    disk0:asr9k-px-4.3.4.CSCun09478-1.0.0
    disk0:asr9k-px-4.3.4.CSCun15934-1.0.0
    disk0:asr9k-px-4.3.4.CSCun19764-1.0.0
    disk0:asr9k-px-4.3.4.CSCun26020-1.0.0
    disk0:asr9k-px-4.3.4.CSCun32418-1.0.0
    disk0:asr9k-px-4.3.4.CSCun75418-1.0.0
    disk0:asr9k-px-4.3.4.CSCuo16209-1.0.0
    disk0:asr9k-px-4.3.4.CSCuo17130-1.0.0

Will it cause the standby RSP to fail to synchronize with the Active RSP when replacing the standby engine?

If I want Active Packages to be the same as Committed Packages, what should I do? Is it possible to use ‘admin install commit’? Does this command have any effect on the device?

In addition, I see that there are Superceded Packages on the device. There are many of the same Packages. Will this affect the synchronization of the standby RSP?

 Superceded Packages:
    disk0:asr9k-px-4.3.4.CSCui09934-1.0.0 
    disk0:asr9k-px-4.3.4.CSCui15435-1.0.0 
    disk0:asr9k-px-4.3.4.CSCui36695-1.0.0 
    disk0:asr9k-px-4.3.4.CSCui36695-1.0.0 
    disk0:asr9k-px-4.3.4.CSCui36695-1.0.0 
    disk0:asr9k-px-4.3.4.CSCui36695-1.0.0 
    disk0:asr9k-px-4.3.4.CSCui36695-1.0.0 
    disk0:asr9k-px-4.3.4.CSCui36695-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj01579-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj95304-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj95304-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj95304-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj95304-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj95304-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj95304-1.0.0 
    disk0:asr9k-px-4.3.4.CSCuj95304-1.0.0 
    disk0:asr9k-px-4.3.4.CSCul93777-1.0.0 
    disk0:asr9k-px-4.3.4.CSCul93777-1.0.0 
    disk0:asr9k-px-4.3.4.CSCul93777-1.0.0 
    disk0:asr9k-px-4.3.4.CSCul93777-1.0.0 
    disk0:asr9k-px-4.3.4.CSCul93777-1.0.0 
    disk0:asr9k-px-4.3.4.CSCul93777-1.0.0 
    disk0:asr9k-px-4.3.4.CSCul93777-1.0.0 
<snip>

Thanks

[tkarnani]

Hi,

your committed package list is a lot longer than active.

it looks like a few packages have been deactivated since they were active.

you can run "admin install commit" this will save the list of active packages as committed. this is not impacting.

having this mismatch does not stop the RSP from synchronizing.

however what can happen. if the router were to reload, the system will boot with the committed packages rather than active.

the superceded packages are those that have been installed, however a newer smu has the fix plus additional fixes so it moves to superceded. it will not hurt anything or stop the RSP from synchronizing.

you can run this command "admin install remove inactive" this will remove the packages listed in "show install inactive summary" you will save some disk space or you can leave it as is

Thanks

[Rps-Cheers]

HI tkarnani ，

Thank you for your patience, but our inactive pkg does not have any file package.

  Inactive Packages:
    No packages.

At this time, when we replaced the STANDBY RSP, the following error occurred:
asr9k-fwding-4.3.4.CSCuo91149-1.0.0 ---This pkg synchronization failed

Note: Because the Active and Committed pkg lists are too long, I haven't completed the output before, but I am sure that the committed pkg lists are more than Active. The SMU that cannot be synchronized is in the Committed pkg list and not in the Active pkg list.

So I don't know what the problem is, do you have any suggestions?

Thanks

[tkarnani]

Hi

Can we check if there are any errors in "admin install verify packages"

Thanks

[Rps-Cheers]

Thanks for your reply.

Will this command affect the business?

Thanks

[tkarnani]

This command is non-impacting.  it is just checking for errors with the install

Thank you

[Rps-Cheers]

I tried the "admin install verify packages" command on the test device and found that it would take a long time to wait. I was worried about the impact on the business on the device. You may not be able to try this command right away.