Wireless Access

If you get a console cable, we might be able to fix it with that...

EDIT: I think I figured it out. I had to clear both os paritions (0 and 1) to make enough space. AP is now up on my cluster with latest image.

Think I'm having a similar issue. Had to factory reset an AP-325 (which has 6.4.4.0 by default). Current production is at 8.10.0.2.

I keep getting errors like:
ERROR: File size exceeded 14680064 bytes
Flash Image upgrade failed: Result code 255

Via console access Ive tried factory_reset and purgeenv - no luck. Then factory_reset and purgeenv and tftpboot - no luck.

Is there a different order of commands to try? Or am I at the point of RMAing this AP?

If you get a console cable, we might be able to fix it with that...

I have had to open a case about this as well. We've had to move up in code to accommodate the newer AP models like some of the 500 series, but also still have AP 105s that need to be upgraded before certain clusters can move up in code. I found out about this issue after trying to repurpose bunch of our 325 APs from 8.7 to 8.6 so these APs were working. However, our procedure is to factory reset the AP before sending it back out into the field which of course puts some of them back to code 6.4.4.0. If I recall the lowest magical code that will work on the 8.7 version that we are running is 6.4.4.8 or something very close to that.

There was a version of code that was released where you could run a command on the MM or MD not sure at the moment that supposedly put whatever version of code running on the MM on the APs backup partition (can be found in the release notes of 8.7.1.9). In our case we have found this command does not work hence the case I've opened. We currently have about 500+ AP325 that will fall into this category and would really like to upgrade them before taking them offline and factory resetting them.

The solution we have been using is to manually install the code on the AP once it has been factory reset. I've found that this version of code works the best for all our APs that need their OS upgraded - ArubaInstant_Hercules_8.3.0.15_79362. I've added this version of code to the flash on one of the controllers so that while the AP is booting I can break the boot cycle to push the code to it using - upgrade os 1 (ip of controller):

Basically, this is what we are dealing with, but I really want to ask everyone here is has anyone been able to get this command to work for them? Here is the information that was released in 8.7.1.9 

Starting from ArubaOS 8.7.1.9, the following CLI commands have been enhanced:
apflash command
The ap31x-ap32x backup partition parameter has been added to the apflash command to upgrade the backup
partition of Aruba 310 Series and 320 Series access points running ArubaOS 6.4.x or earlier versions to the
ArubaOS version running on the Mobility Master.
(host) [mynode] #apflash ap31x-ap32x backup partition

A

EDIT: I think I figured it out. I had to clear both os paritions (0 and 1) to make enough space. AP is now up on my cluster with latest image.

Think I'm having a similar issue. Had to factory reset an AP-325 (which has 6.4.4.0 by default). Current production is at 8.10.0.2.

I keep getting errors like:
ERROR: File size exceeded 14680064 bytes
Flash Image upgrade failed: Result code 255

Via console access Ive tried factory_reset and purgeenv - no luck. Then factory_reset and purgeenv and tftpboot - no luck.

Is there a different order of commands to try? Or am I at the point of RMAing this AP?

If you get a console cable, we might be able to fix it with that...

I have had to open a case about this as well. We've had to move up in code to accommodate the newer AP models like some of the 500 series, but also still have AP 105s that need to be upgraded before certain clusters can move up in code. I found out about this issue after trying to repurpose bunch of our 325 APs from 8.7 to 8.6 so these APs were working. However, our procedure is to factory reset the AP before sending it back out into the field which of course puts some of them back to code 6.4.4.0. If I recall the lowest magical code that will work on the 8.7 version that we are running is 6.4.4.8 or something very close to that.

There was a version of code that was released where you could run a command on the MM or MD not sure at the moment that supposedly put whatever version of code running on the MM on the APs backup partition (can be found in the release notes of 8.7.1.9). In our case we have found this command does not work hence the case I've opened. We currently have about 500+ AP325 that will fall into this category and would really like to upgrade them before taking them offline and factory resetting them.

The solution we have been using is to manually install the code on the AP once it has been factory reset. I've found that this version of code works the best for all our APs that need their OS upgraded - ArubaInstant_Hercules_8.3.0.15_79362. I've added this version of code to the flash on one of the controllers so that while the AP is booting I can break the boot cycle to push the code to it using - upgrade os 1 (ip of controller):

Basically, this is what we are dealing with, but I really want to ask everyone here is has anyone been able to get this command to work for them? Here is the information that was released in 8.7.1.9

Starting from ArubaOS 8.7.1.9, the following CLI commands have been enhanced:
apflash command
The ap31x-ap32x backup partition parameter has been added to the apflash command to upgrade the backup
partition of Aruba 310 Series and 320 Series access points running ArubaOS 6.4.x or earlier versions to the
ArubaOS version running on the Mobility Master.
(host) [mynode] #apflash ap31x-ap32x backup partition

A

EDIT: I think I figured it out. I had to clear both os paritions (0 and 1) to make enough space. AP is now up on my cluster with latest image.

Think I'm having a similar issue. Had to factory reset an AP-325 (which has 6.4.4.0 by default). Current production is at 8.10.0.2.

I keep getting errors like:
ERROR: File size exceeded 14680064 bytes
Flash Image upgrade failed: Result code 255

Via console access Ive tried factory_reset and purgeenv - no luck. Then factory_reset and purgeenv and tftpboot - no luck.

Is there a different order of commands to try? Or am I at the point of RMAing this AP?

If you get a console cable, we might be able to fix it with that...