ASR903 packages.conf vs. asr900rsp3-universalk9.17.06.05.SPA.conf

[MATTHIAS SCHAERER]

Hi

The request platform software process creates two .conf files: one packages.conf and the other one asr900rsp3-universalk9.17.06.05.SPA.conf (or whatever SW version you use). The content seems to be slightly different but not that much.

The packages.conf is read during reload, what is the other one for and how is its content created? Furthermore the request platform software clean command deletes the asr900rsp3-universalk9.17.06.05.SPA.conf file per default. Does that create a problem for the next reload or the next SW upgrade?

Any hint is appreciated. 

[balaji.bandi]

if the upgrade fails you see those files - ( packages.conf is the file you need to use all the time).

if you look at the content of both the files :

 asr900rsp3-universalk9.17.06.05.SPA.conf  - this will point to 17.6.5 code packages.conf - if this is also point to same 17.6.5   (if this is different - then you can take backup packages.conf file and move  asr900rsp3-universalk9.17.06.05.SPA.conf  to packages.conf)

[MATTHIAS SCHAERER]

The way you describe it asr900rsp3-universalk9.17.06.05.SPA.conf would be the more trustful file than packages.conf. Do you happen to know if there is any reason why the "request platform software clean" process deletes this file by default if it is so important?

[balaji.bandi]

becuase if the upgrade works as expected you wont be seeing that file, that file will be packages.conf only

clean up clear all the un used files.

[Charlie Moreton]

Moving to the relevant forum

[Leo Laohoo · Accepted solution]

---

@MATTHIAS SCHAERER wrote:
The request platform software process creates two .conf files: one packages.conf and the other one asr900rsp3-universalk9.17.06.05.SPA.conf (or whatever SW version you use). 

---

The process does the following: 

1.  Creates the filename "asr900rsp3-universalk9.17.06.05.SPA.conf". 
2.  Renames packages.conf to packages.conf.00-
3.  Make a copy of asr900rsp3-universalk9.17.06.05.SPA.conf file and calls it "packages.conf". 

I am not familiar with the behaviour of this process with ASR9k, however, with ISR 1000, ASR 1k, switching and WLC, this process is not 100% foolproof.  I have witnessed where the process abruptly stops and steps 2 and 3 are not done.  (See picture below.)

The contents of either "asr900rsp3-universalk9.17.06.05.SPA.conf" &/or "packages.conf" can be examined by using the command "more bootflash:asr900rsp3-universalk9.17.06.05.SPA.conf".  The "first page" of the output is the "blah blah" page (can be ignored).  The interesting bits start from the "second page".