cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
587
Views
8
Helpful
6
Replies

WLC 17.12.3 needs APSP 17.9.4?

Mkvts
Level 1
Level 1

Upgrading a WLC to version 17.12.3 but failed, needs a APSP from 17.9.4?

Improper State./bootflash/C9800-CL-universalk9.17.09.04.CSCwh64998.SPA.apsp.bin not present.

After providing the file installing was succesfull but just for me to know why we need to provide a APSP that has already been installed earlier in version 17.09.04?

Is this because the service pack is applied again or the bug is still present in current version?

 

1 Accepted Solution

Accepted Solutions

I'm curious to hear what TAC have to say about it.  I've addressed this on previous threads.  The only safe way to do the upgrade is to remove each SMU and APSP individually before upgrade but then you have APs downloading and WLC reloading which is obviously a problem.  The quick fix is:
https://community.cisco.com/t5/wireless/9800-issu-behavior/m-p/4905112/highlight/true#M259614
which clears all SMU and APSP from the install database and reloads the WLC (then APs will try to download the non-APSP code so you might want to shut the AP management interface till the upgrade is complete)!
After that upgrade is clean but this is a very irritating bug in the install scripts!

View solution in original post

6 Replies 6

Leo Laohoo
Hall of Fame
Hall of Fame

This is a known bug feature. 

install remove file bootflash:C9800-CL-universalk9.17.09.04.CSCwh64998.SPA.apsp.bin

 

JPavonM
VIP
VIP

I'm hitting this defect also, but mine when adding APSP1 over 17.9.5 it asked for APSP3 from 17.9.3, and then asking for the same APSP3 from 17.9.3 when adding APSP5 over 17.9.5+APSP1 some time after the first APSP.

Weirdly this is happening only to one WLC out of 7. I've a TAC case open to investigate and clarify how to proceed, and why this happen.

I have no access to TAC for this weird behaviour, could you update if you have any news from TAC?

Thank you.

This behaviour has long existed as early as 16.12.4.  

The only way to see if the IOS-XE upgrade process has removed old SMU/APSP/APDP is to watch the bootup using the console cable.  

Developers have no interest in fixing this because it has not (yet) reached of "catastrophic" level, i.  e.  not one of Cisco's very, very large customers are affected.  

I'm curious to hear what TAC have to say about it.  I've addressed this on previous threads.  The only safe way to do the upgrade is to remove each SMU and APSP individually before upgrade but then you have APs downloading and WLC reloading which is obviously a problem.  The quick fix is:
https://community.cisco.com/t5/wireless/9800-issu-behavior/m-p/4905112/highlight/true#M259614
which clears all SMU and APSP from the install database and reloads the WLC (then APs will try to download the non-APSP code so you might want to shut the AP management interface till the upgrade is complete)!
After that upgrade is clean but this is a very irritating bug in the install scripts!

jasonm002
Level 1
Level 1

FYI this was a long standing issue in IOS XE, affects both switch and WLC, even though this is not an exact match it should be the issue basically: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwj73014

If you're not on a fixed release then in a maintenance window (do not do this during business hours):

configure terminal

service internal

end

*write the config*

in privileged exec mode do: "clear install state"

reload the box and then never again do "install remove inactive" if you have ever installed an APSP or SMU. I haven't tested this on a fixed release, supposedly in one of the fixed releases they will remove rollback points on boot that are missing the SMU in flash. The core issue is IOS XE had a design flaw where software rollback points could exist with inactive SMUs that were missing the SMU file in flash and other install operations would require those SMUs to be on flash to proceed, and "install remove inactive" would very unhelpfully remove all the inactive SMUs.

 

Also avoid 17.12.4 unless you get the APSP1 for it from TAC. It's not yet available on the downloads page publicly but TAC should be able to get it to you. It contains a fix for an annoying crash bug affecting almost all the ax APs.

Review Cisco Networking for a $25 gift card