Header Only - DO NOT REMOVE - Extreme Networks

How to downgrade an AP 3805 image from 10.01.04.1003 to 09.21.07.0007


I have to attach 3805 APs to a V2110 Controller running version 09.21.07.0007 (need v9 as I have still to support 2600 APs).

The config manager module is trying to downgrade the APs image from 10.01.04.1003 to 09.21.07.0007 which is failing.

Here the log entry:

"Wireless AP automatic software upgrade/downgrade has failed.
May be a corrupted image was selected as a default. Please select another default image. This alarm will repeat while the system is in automatic mode: Wireless AP SN 16xxxxx; failed image 09.21.07.0007."

How can I downgrade the APs to get them attached to the controller.

Any help is much appreciated


16 replies

Userlevel 4
Hi Christoph,

please try to set the AP to factory default .
ssh to the AP -> username :admin password:new2day
#cset f

Then try to downgrade the AP again.

Regards
Umut
Umut Aydin wrote:

Hi Christoph,

please try to set the AP to factory default .
ssh to the AP -> username :admin password:new2day
#cset f

Then try to downgrade the AP again.

Regards
Umut

It looks like the factory default image is 10.01.04.1003.
This was not working for me.
Userlevel 6
Christoph

You could also configure controlled upgrade mode in order to get the AP's connected on the code that they are running now https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-upgrade-Identifi-Wireless-AP-with-hotfix-firmware-via-controller-web-gui

Check that tftp is allowed on the path between the AP and the controller (firewall etc) and also check MTU is not a factor.

You can then try a manual upgrade of an AP once it is connected and up/stable.

-Gareth
Gareth Mitchell wrote:

Christoph

You could also configure controlled upgrade mode in order to get the AP's connected on the code that they are running now https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-upgrade-Identifi-Wireless-AP-with-hotfix-firmware-via-controller-web-gui

Check that tftp is allowed on the path between the AP and the controller (firewall etc) and also check MTU is not a factor.

You can then try a manual upgrade of an AP once it is connected and up/stable.

-Gareth

Hi Gareth,

this seams also to fail.
once I do the controlled upgrade mode it looks like it starts the upgrade, but the AP is again going into a boot loop.

Between the Controller and the APs there is no Firewall, as it is on the same L2 VLAN.
MTU size is correct.

Logfile is looking like this:

06/07/16 10:54:27 Info Config Manager Upgrading Wireless AP image: Serial 16160452085K0000, from 10.01.04.1003 to 09.21.07.0007

06/07/16 10:54:27 Info RU Session Manager Wireless AP registration and authentication succeeded. (AP SN 16160452085K0000 AP IP 10.49.4.110 (active tunnel), Certificate provided:None)

06/07/16 10:54:27 Info RU Manager Wireless AP authenticated. Serial Number: 16160452085K0000, IP: 10.49.4.110

06/07/16 10:54:27 Info RU Manager Wireless AP connects for registration. Serial number: 16160452085K0000, IP: 10.49.4.110

06/07/16 10:54:27 Info RU Manager Wireless AP registered. Serial number: 16160452085K0000

06/07/16 10:54:27 Info RU Manager Wireless AP connects for discovery. Serial Number: 16160452085K0000

-Christoph
Userlevel 6
Gareth Mitchell wrote:

Christoph

You could also configure controlled upgrade mode in order to get the AP's connected on the code that they are running now https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-upgrade-Identifi-Wireless-AP-with-hotfix-firmware-via-controller-web-gui

Check that tftp is allowed on the path between the AP and the controller (firewall etc) and also check MTU is not a factor.

You can then try a manual upgrade of an AP once it is connected and up/stable.

-Gareth

Christoph

If you are in controlled upgrade mode cancel any upgrades and do nothing more, does the AP stay up and provide service? You should see in AP>Bulk Configuration that the AP has a green band on it.

Try to reset to factory defaults as my colleague Umut suggested: https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-reset-an-IdentiFi-access-point-back-to-factory-defaults

-Gareth
Gareth Mitchell wrote:

Christoph

You could also configure controlled upgrade mode in order to get the AP's connected on the code that they are running now https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-upgrade-Identifi-Wireless-AP-with-hotfix-firmware-via-controller-web-gui

Check that tftp is allowed on the path between the AP and the controller (firewall etc) and also check MTU is not a factor.

You can then try a manual upgrade of an AP once it is connected and up/stable.

-Gareth

Hi Gareth,

The AP turns into green, when I register it (under AP>Bulk Configuration).
But it is still rebooting after about 3 minutes.

On the Menue AP > All I can assigne WLANs, also I can see the IP configuration (using DHCP).
But both Radio Modules showing "Curent Tx Power Level" OFF
"Admin Mode" is set to On.

I have now used another AP 3805 - to see if it might be a physical problem - but ist is the same issue.
Userlevel 6
Gareth Mitchell wrote:

Christoph

You could also configure controlled upgrade mode in order to get the AP's connected on the code that they are running now https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-upgrade-Identifi-Wireless-AP-with-hotfix-firmware-via-controller-web-gui

Check that tftp is allowed on the path between the AP and the controller (firewall etc) and also check MTU is not a factor.

You can then try a manual upgrade of an AP once it is connected and up/stable.

-Gareth

Christoph

I just tested this in my lab, using the same code and it works, the AP was also stable on 10.01.04.1003.

If your controlled upgrade has "upgrade to" empty and version is still 10.01.04.1003 and the AP doesn't stay up, I would suggest contacting GTAC so we can dig through the logs, if the AP stays up long enough, please get the AP trace file and a "tech support" from the controller.

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Collect-Access-Point-Logging-Information-Trace-Bundle

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Collect-a-Tech-Support-File-From-a-Wireless-Controller



-Gareth
Gareth Mitchell wrote:

Christoph

You could also configure controlled upgrade mode in order to get the AP's connected on the code that they are running now https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-upgrade-Identifi-Wireless-AP-with-hotfix-firmware-via-controller-web-gui

Check that tftp is allowed on the path between the AP and the controller (firewall etc) and also check MTU is not a factor.

You can then try a manual upgrade of an AP once it is connected and up/stable.

-Gareth

Hi Gareth,

I have it like in your screenshot.

On thing I have seen in the log:

Wireless AP automatic software upgrade/downgrade has failed. May be a corrupted image was selected as a default. Please select another default image. This alarm will repeat while the system is in automatic mode: Wireless AP SN 16160779085K0000; failed image 09.21.07.0007.

If the AP image on the controller is corrupt, do you think it is worth to change it with an other image / reimport the image to the controller?

Where can I get the image files for the controller - I did not found it under the downloads...

If this does not help I will raise a GTAC call than.

Thanks your your support on this.

Christoph
Userlevel 7
Is the AP on a remote network or in the local subnet of the controller ?
Ron wrote:

Is the AP on a remote network or in the local subnet of the controller ?

local sub net - layer 2
Userlevel 4
Hi,

did you set the AP to factory default?

Regarding new image..yes I saw it in the past that somehow the AP code was corrupted.
To test it with a different code would be good.

You can get the AP image only from the Controller itself.
It's not downloadable from the web.

You have to setup a V2110 if possible on your side
or call GTAC for the code.

The code in the Controller would be in /var/controller/images/AP/(ap Type ) and so on..

Regards

Umut
Hi Christoph,



you can extract the AP images from the controller SW.

For this please open the AC-MV-09.21.08.0013-1.bge with 7-Zip and then use the following path:

normal.tgz – normal.tar - . - var – controller – images – ap – AP3805

Then extract the AP3805-09.21.08.0013.img file.

The AP Image can be downloaded to the controller with FTP and installed using controlled upgrade.



Regards,

Andre
Andre Faupl wrote:

Hi Christoph,



you can extract the AP images from the controller SW.

For this please open the AC-MV-09.21.08.0013-1.bge with 7-Zip and then use the following path:

normal.tgz – normal.tar - . - var – controller – images – ap – AP3805

Then extract the AP3805-09.21.08.0013.img file.

The AP Image can be downloaded to the controller with FTP and installed using controlled upgrade.



Regards,

Andre



Hi all together,

I have to solve the same problem. Unfortunally I can't use the solution "controlled upgrade" because we use at about 20 AP3805 in a warehouse environment.
I tried to upgrade the AP manually via tftp and received the following message:
[i]##########
image_upgrade [i]
TFTP Filename in progress....
TFTP done.
core enabled
Error! Image file header not found!
No core files while upgrading
/usr/sbin/image_upgrade1: Clean up and exit with return value 12
############
I extracted the AP_FW-file from AC-MV-09.21.09.0004-1.bge as described by Gareth and Andre.
Yes I resetted the AP as described by Umut with cset f.

Is there a solution for manual upgrade/downgrade of the AP?

Regards

MIchael
Userlevel 6
Andre Faupl wrote:

Hi Christoph,



you can extract the AP images from the controller SW.

For this please open the AC-MV-09.21.08.0013-1.bge with 7-Zip and then use the following path:

normal.tgz – normal.tar - . - var – controller – images – ap – AP3805

Then extract the AP3805-09.21.08.0013.img file.

The AP Image can be downloaded to the controller with FTP and installed using controlled upgrade.



Regards,

Andre



Michael

Please call into the GTAC and open a case for this.

-Gareth
Hi all. Same problem here with a brand new 3805e arrived with firmware 10.01.04.1003 trying to register to a V2110 with 09.21.09.0004 firmware. Although I tried to stop the downgrade via the "controlled upgrade", the AP keeps trying downgrade every time it joins.

I also tried to do a manual firmware upgrade as indicated here:
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-upgrade-IdentiFi-Wireless-AP-firmwa...

In any case. from controller or manually, the firmware downgrade always seems to complete without problems:

Jun 16 07:22:14 cap: Kernel image upgraded.
Jun 16 07:22:14 cap: Image upgrade done.
Jun 16 07:22:14 cap: 00287:nvlog.c:543-send_to_user()-s=1175 tm=2016/06/16 07:20:15 UTC n=1 c=16 sv=MINOR e=Firmware upgraded to 09.21.09.0004
Jun 16 07:22:14 cap: No core files while upgrading
Jun 16 07:22:14 cap: /usr/sbin/image_upgrade2: Clean up and exit with return value 0
Jun 16 07:22:14 cap: Error in obtaining the tty, output will go to console
Jun 16 07:22:14 cap: 01059:logging.c:1021-show_one_alarm()-ALARM 1556 MAJOR: 06/16/16 07:22:14: AccessPoint software upgrade done with image AP3805/AP3805-09.21.09.0004.img.
Jun 16 07:22:16 cap: 01059:logging.c:1021-show_one_alarm()-ALARM 1557 CRITICAL(not acked): 06/16/16 07:22:16: AccessPoint Rebooting due to: Software Image Upgrade
Jun 16 07:22:16 kernel: ap_drv: watchdog re-armed
Jun 16 07:22:16 kernel: ap_drv: watchdog re-armed

But upon reboot, it shows the same 10.01.04.1003 firmware. It seems like the logic on the image_upgrade scripts on that firmware version doesn't activate the new firmware downloaded. Also I don't understand why the "controlled upgrade" logic is not followed by the AP.

I opened yesterday a GTAC case, but it its not assigned yet,

Regards.
Hi all,

there is a solution now from GTAC Support.

They have now a new release (09.21.10.0005) available to download.

Use this release to upgrade your controller and the 3805i APs are downgrading correct to the Version 09 Release.

(The Software file is not containing an AP image file in it forthe 3805 APs. This image file is created on the controller while updating the controller)

Reply