Firmware 3.2

[henrik_lodel]

Hi !

I have some problems with my vsz after upgrading to 3.2.

Now when I try to upgrade firmware on the accesspoints it fail ́s in the download process.

The accesspoints are R300 and R500.

The logs from the AP ́s looks like this.
Nov 10 10:09:03 RuckusAP daemon.notice Firmware Daemon[612]: failed|control file download problemNov 10 10:09:04 RuckusAP daemon.notice Firmware Daemon[612]: working|looking up control server IP
Nov 10 10:09:04 RuckusAP daemon.notice Firmware Daemon[612]: working|reading control file
Nov 10 10:09:25 RuckusAP daemon.notice Firmware Daemon[612]: failed|control file download problem
Nov 10 10:09:26 RuckusAP daemon.notice Firmware Daemon[612]: working|looking up control server IP
Nov 10 10:09:26 RuckusAP daemon.notice Firmware Daemon[612]: working|reading control file
Nov 10 10:09:47 RuckusAP daemon.notice Firmware Daemon[612]: failed|control file download problem
Nov 10 10:09:48 RuckusAP daemon.notice Firmware Daemon[612]: working|looking up control server IP
Nov 10 10:09:48 RuckusAP daemon.notice Firmware Daemon[612]: working|reading control file

I have tested both internal and external.

Any idea whats wrong?


Thanks in advance!

[paddy_naughton_]

Had a similar problem here when we upgraded from 3.0 to 3.1 and found a workaround by moving the APs into the staging zone and then back to their correct zone. Try it and see does it help.

[henrik_lodel]

Thanks for the tip but unfortunately that did not help 😞 Still "Firmware Upgrade Failed".

[dionis_taveras]

There is a new port that needs to be opened for this to work.  You likely have port 91, 22 and 443, please add port 11443 for the transfer to take place.  This is new in firmware 3.2 and is used for firmware upgrade using HTTPS instead of FTP.

Let me know if this helps.

Regards,

[michael_brado]

Yes, and it looks like I need to write the KBA asap.