giantqosa.blogg.se

I got 15.3(3)JF release.įirst, put the downloaded archive on the server accessible from subnet where access point gets its IP address from. You can download the firmware from, but you need valid service contract assigned to your CCO profile. You can perform manual firmware upgrade in such situation loading either up-to-date version or any close to this. That is not an uncommon problem in Cisco we saw this on ASA already. I could see this when I listed available images in WLCĪnother possible reason was that the download or image verification process changes significantly and access point was not able to verify the new image. In my case, I suspect one of the possible reasons why automatic firmware upgrade did not work is that for Cisco Aironet 3700 with release 15.3(3)JF has changed the platform code from ap3g2 to c3700. As we can see the 15.3(3)JA1 is compatible with controller firmware release 8.0.110.0 – both released in 2014. My access point out-of-box had preinstalled firmware 15.3(3)JA1, the latest vWLC version 8.6.101.0 requires the 15.3(3)JG1. The FailureCode:3 does not point to a reason. The access point joined the controller successfully and attempted to download the current archive from the controller, but the whole operation failed. Downloading image from Controller.ĮRROR: Image is not a valid IOS image archive.ĭownload image failed, notify controller!!! From:8.0.110.0 to 0.0.0.0, FailureCode:3

*Dec 17 16:39:40.251: %CAPWAP-6-AP_IMG_DWNLD: Required image not found on AP. *Dec 17 16:39:40.227: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.1.205perform archive download capwap:/ap3g2 tar file More answers you will get from the access point console However, this does not answer the question what exactly the problem is.

What are the symptoms that you cannot upgrade your access point automatically? On the web dashboard, you will see the access point reappearing with Operational Status set to Downloading. My lightweight access point image is too old Sometimes you need to perform a manual lightweight access point firmware upgrade procedure which is not well documented. Is it working? Yes, usually, but not always. The idea is that access point upgrades its firmware when it registers to WLC.

It has been on the market for years, evolved from LWAPP to CAPWAP model, is supporting a wide range of access point models. The Cisco lightweight access point managed by the wireless controller is not a new product.