Reply
New Member
Posts: 5
Registered: ‎02-04-2017
Kudos: 1

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

I had to rollback to 4.0.10 code which was stable and I can confirm that is it now working well. The codes 4.0.15 and 4.0.21 are affected but I have not tested 4.0.14 because I ran 4.0.10 for a while without any problems.
New Member
Posts: 17
Registered: ‎11-10-2016
Kudos: 3

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

Has anyone else seen sky high memory consumption rates on the new 4.0.21.9965?  Most of our v1 units have been disconnecting/failing since upgrading.

New Member
Posts: 1
Registered: ‎03-01-2016
Kudos: 4

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

We ecountered all of the community problems:

  • AP (mostly UAP-LR version 1) suddenly changing to 10HDX half-duplex
  • Sudden up and down on UAP-AP interfaces
  • Loss of signal strength on AC-PRO

We use

  • UAP-AC-PRO x30
  • UAP-LR x30

What we tried and mostly failed Man Happy

 

  1. Downgrade UAP-LR
    1. Via dashboard to 4.0.15 it doesn't work 
    2. Via TFTP to from 4.0.21
      1. 4.0.15 - we bricked UAP-LR
      2. 4.0.10 - we bricked UAP-LR
      3. 3.9.54 - we bricked UAP-LR
      4. To un-brick the AP we TFTP 4.0.21 and suddenly the AP started to working just fine

At this point I started to learn about 4.0.21 and this upgrade change partition-model of upgrade ???

I found that the all syswrapper.sh is just a dummy wrapper script for real command like fwupdate.real (sic!) cause fwupdate doesn't work - Ubiquity you should change it name to fwupdate.notreal Man Very Happy

Ok, back to point. If u try to downgrade via syswrapper like:

syswrapper.sh upgrade https://dl.ubnt.com/unifi/firmware/BZ2/4.0.15.9872/BZ.ar7240.v4.0.15.9872.181229.0259.bin

to 4.0.15 you probably ending with:

Invalid Image Layout!

Thats cause the syswrapper.sh do:

 fwupdate.real -c -d /tmp/fwupdate.bin
-c check
-d verbose (SIC!)

The fwupdate.real is failing on checking the image.

What is strange that if you check 4.0.21:

UBNT-BZ.v4.0.21# fwupdate.real -c -d /tmp/fwupdate.bin_4.0.21 
check = 1
verbose = 1
keep_running = 0
write_flash = 0
imagefile = /tmp/fwupdate.bin_4.0.21
Found mtd block: /dev/mtd0(u-boot)
Found mtd block: /dev/mtd1(u-boot-env)
Found mtd block: /dev/mtd2(kernel)
Found mtd block: /dev/mtd3(cfg)
Found mtd block: /dev/mtd4(EEPROM)
Got U-Boot variable: mtdparts = mtdparts=mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),7552k(kernel),256k(cfg),64k(EEPROM)
Adding U-Boot partition: u-boot 9F000000 00040000
Adding U-Boot partition: u-boot-env 9F040000 00010000
Adding U-Boot partition: kernel 9F050000 00760000
Adding U-Boot partition: cfg 9F7B0000 00040000
Adding U-Boot partition: EEPROM 9F7F0000 00010000
Calculating flash size:
Adding block: /dev/mtd0("u-boot") - size: 00040000
Adding block: /dev/mtd1("u-boot-env") - size: 00010000
Adding block: /dev/mtd2("kernel") - size: 00760000
Adding block: /dev/mtd3("cfg") - size: 00040000
Adding block: /dev/mtd4("EEPROM") - size: 00010000
Total flash size: 00800000
Flash start: 9F000000
Flash end: 9F800000
Header MAGIC 'UBNT'
Current: BZ.qca9342.v4.0.21.9965.190125.1623

New ver: BZ.ar7240.v4.0.21.9965.190125.1623
FW Part: "u-boot"(1), MAGIC: 'PART', Base: 0x9F000000, DLen: 0x0003AF04, PLen: 0x00040000
Adding adjusted FW partition:
name:	'u-boot'
flash_base:	0x9F000000
mem_base:	0xFFFFFFFF
size:		0x00040000
entry_point:	0xFFFFFFFF
data_len:	0x0003AF04
desc_cksum:	0x00000000
file_cksum:	0x00000000
===========================
FW Part: "kernel"(2), MAGIC: 'PART', Base: 0x9F050000, DLen: 0x006A9C99, PLen: 0x00760000
FW Part: "script"(3), MAGIC: 'EXEC', Base: 0x00000000, DLen: 0x00000155, PLen: 0x00000155
Adding adjusted FW partition:
name:	'kernel'
flash_base:	0x9F050000
mem_base:	0x80002000
size:		0x00760000
entry_point:	0x80002000
data_len:	0x006A9C99
desc_cksum:	0x00000000
file_cksum:	0x00000000
===========================
Signature MAGIC 'END.'
Pre-Check Script '/tmp/bin/precheck' success.
Working(1) with block: /dev/mtd0
Working(2) with block: /dev/mtd0
End check: 9F000000 + 00040000 <= 9F040000
Creating FIS partition: 0 =>
name:	'u-boot'
flash_base:	0x9F000000
mem_base:	0xFFFFFFFF
size:		0x00040000
entry_point:	0xFFFFFFFF
data_len:	0x0003AF04
desc_cksum:	0x00000000
file_cksum:	0x00000000
===========================
Working(1) with block: /dev/mtd0
Skipping: artificial: 0, unallocated: 0,writeable: 1024(WRITEABLE: 400, flags: C00), fw.flash_base: 9F050000 < blk->base: 9F000000 + blk->size: 40000
Working(1) with block: /dev/mtd1
Skipping: artificial: 0, unallocated: 0,writeable: 1024(WRITEABLE: 400, flags: C00), fw.flash_base: 9F050000 < blk->base: 9F040000 + blk->size: 10000
Copying FIS partition: 1 =>
name:	'u-boot-env'
flash_base:	0x9F040000
mem_base:	0xFFFFFFFF
size:		0x00010000
entry_point:	0xFFFFFFFF
data_len:	0x00010000
desc_cksum:	0xFFFFFFFF
file_cksum:	0xFFFFFFFF
===========================
Working(1) with block: /dev/mtd2
Working(2) with block: /dev/mtd2
End check: 9F050000 + 00760000 <= 9F7B0000
Creating FIS partition: 2 =>
name:	'kernel'
flash_base:	0x9F050000
mem_base:	0x80002000
size:		0x00760000
entry_point:	0x80002000
data_len:	0x006A9C99
desc_cksum:	0x00000000
file_cksum:	0x00000000
===========================
Working(3) with block: /dev/mtd3
Copying FIS partition: 3 <=
name:	'cfg'
flash_base:	0x9F7B0000
mem_base:	0xFFFFFFFF
size:		0x00040000
entry_point:	0xFFFFFFFF
data_len:	0x00040000
desc_cksum:	0xFFFFFFFF
file_cksum:	0xFFFFFFFF
===========================
Working(3) with block: /dev/mtd4
Copying FIS partition: 4 <=
name:	'EEPROM'
flash_base:	0x9F7F0000
mem_base:	0xFFFFFFFF
size:		0x00010000
entry_point:	0xFFFFFFFF
data_len:	0x00010000
desc_cksum:	0xFFFFFFFF
file_cksum:	0xFFFFFFFF
===========================
New FIS entries count 5

 It does ends normally

Now lets do this for 4.0.15 the previous one that you can downgrade from dashboard with a button and this option should be tested before issuing upgrade to public users

fwupdate.real -c -d /tmp/fwupdate.bin_4.0.15 
check = 1
verbose = 1
keep_running = 0
write_flash = 0
imagefile = /tmp/fwupdate.bin_4.0.15
Found mtd block: /dev/mtd0(u-boot)
Found mtd block: /dev/mtd1(u-boot-env)
Found mtd block: /dev/mtd2(kernel)
Found mtd block: /dev/mtd3(cfg)
Found mtd block: /dev/mtd4(EEPROM)
Got U-Boot variable: mtdparts = mtdparts=mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),7552k(kernel),256k(cfg),64k(EEPROM)
Adding U-Boot partition: u-boot 9F000000 00040000
Adding U-Boot partition: u-boot-env 9F040000 00010000
Adding U-Boot partition: kernel 9F050000 00760000
Adding U-Boot partition: cfg 9F7B0000 00040000
Adding U-Boot partition: EEPROM 9F7F0000 00010000
Calculating flash size:
Adding block: /dev/mtd0("u-boot") - size: 00040000
Adding block: /dev/mtd1("u-boot-env") - size: 00010000
Adding block: /dev/mtd2("kernel") - size: 00760000
Adding block: /dev/mtd3("cfg") - size: 00040000
Adding block: /dev/mtd4("EEPROM") - size: 00010000
Total flash size: 00800000
Flash start: 9F000000
Flash end: 9F800000
Header MAGIC 'UBNT'
Current: BZ.qca9342.v4.0.21.9965.190125.1623

New ver: BZ.ar7240.v4.0.15.9872.181229.0259
FW Part: "u-boot"(1), MAGIC: 'PART', Base: 0x9F000000, DLen: 0x0003B034, PLen: 0x00040000
Adding adjusted FW partition:
name:	'u-boot'
flash_base:	0x9F000000
mem_base:	0xFFFFFFFF
size:		0x00040000
entry_point:	0xFFFFFFFF
data_len:	0x0003B034
desc_cksum:	0x00000000
file_cksum:	0x00000000
===========================
FW Part: "kernel"(2), MAGIC: 'PART', Base: 0x9F050000, DLen: 0x000E1D74, PLen: 0x00100000
FW Part: "rootfs"(3), MAGIC: 'PART', Base: 0x9F150000, DLen: 0x005E0000, PLen: 0x00660000
FW Part: "script"(4), MAGIC: 'EXEC', Base: 0x00000000, DLen: 0x000005D5, PLen: 0x000005D5
Adding adjusted FW partition:
name:	'kernel'
flash_base:	0x9F050000
mem_base:	0x80002000
size:		0x00100000
entry_point:	0x80002000
data_len:	0x000E1D74
desc_cksum:	0x00000000
file_cksum:	0x00000000
===========================
Adding adjusted FW partition:
name:	'rootfs'
flash_base:	0x9F150000
mem_base:	0x9F150000
size:		0x00660000
entry_point:	0x00000000
data_len:	0x005E0000
desc_cksum:	0x00000000
file_cksum:	0x00000000
===========================
Signature MAGIC 'END.'
Pre-Check Script '/tmp/bin/precheck' success.
Invalid Image Layout!

At this point I'm clueless about what to do next. Can anyone help debug it further? 

New Member
Posts: 33
Registered: ‎08-20-2012

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

I wonder,does anyone of ubnt employees has something to say about the issue??

 

It's over 2 days now that almost 80% of unifi AP are not working right and we still have only the option to downgrade our v1 AP through the controller,which option does not work. Even though our v2 products (AC-PRO etc) are not working right also,there is no option to downgrade!!!

 

Come on guys,give us a solution!

New Member
Posts: 24
Registered: ‎12-01-2016
Kudos: 6

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

I cannot reset them to try the downgrade because 2 of them are at the roof of the factory at 20 meters height. 

 

CloudKey (1): v0.13.4.410e9b6.190213.1205 / Controller: 5.10.17-11638-1
UniFi USG(1): 4.4.36.5146617
US‑8‑60W (11): 4.0.21.9965
UniFi AP-LR,AC-Lite,AC-Pro (5): 4.0.15.9872
NanoBeam 5AC 19(2): XC.v8.5.8
New Member
Posts: 3
Registered: ‎02-14-2019
Kudos: 3

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

@BuckBuck

Thanks for this. I can confirm for anyone following along that punting 4.0.21 back to the UAP I bricked earlier trying to TFTP recover brought it back to life. Doesn't fix the overall problem but its a possible route to getting them back online and in the controller so I can play further.
Member
Posts: 114
Registered: ‎10-10-2013
Kudos: 51
Solutions: 4

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

[ Edited ]

Interesting to read about all the problems with gen 1 AP:s. I have been running 5 UAP Pro:s on 3 different sites (2 + 2 +1) for 20 days. In one of the sites (2 AP:s) I'm running 4 SSID:s on 3 different VLANS. As far as I know, zero problems... No diconnects, about 50 - 60% memory consumption. Not extreamly busy, at most about 20 concurrent clients on one AP give or take (hotspot + 3 diffrent WPA2 enterprise).

New Member
Posts: 2
Registered: ‎02-15-2019
Kudos: 1

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

hi all. i update to the latest controller and got the latest ac pro firmware.

 

I had connection problems... wifi experience jump from 0% - 100% ... ping timeouts etc.

 

 

i downgrade to the firmware before (4.0.15.9872) with gui and it worked again. downgradeacpro.JPG

New Member
Posts: 17
Registered: ‎11-10-2016
Kudos: 3

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

Just a quick note on the 10 HDX side effect... I watched the Cisco switch log closely and it never changed to 10 Mbps or HDX.  Whatever is going on there is an anomoly inside of the controller display.  Has anyone else tested this?

New Member
Posts: 3
Registered: ‎07-30-2016

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

I got caught with this upgrade as well, 2 x UniFi AP-Outdoor 5G both bricked after firmware upgrade. Have tried TFTP method but unresponsive just keeps flashing interminent orange or organge / green cannot ssh either. Any options to recover or are they going in the bin???

 

I saw the warning in the notes to late.... is there a way to stop pushing updates for older AP's ?

 

Downgrading others now as performance hit from upgrade awaiting a more stable release.

New Member
Posts: 4
Registered: ‎11-29-2017
Kudos: 1

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

Im getting this also updated to 4.0.21 and now my 3 aps connect at 10HDX randomly, i click down grade and this fails both in gui and in SSH with invalid invalid image layout in /var/log/messages so im stuck and cant downgrade

Member
Posts: 314
Registered: ‎02-20-2016
Kudos: 121
Solutions: 12

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

Could we get a "Known Issues" section for the stable firmware releases just like it is for controller releases?

New Member
Posts: 33
Registered: ‎04-22-2017
Kudos: 2

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

Hi there,

 

I’ve upgrade and am now seeing most of the issues listed here. I have LR APs (Gen 1) and since the upgrade internet access has been intermittent as has Sonos control etc. I also se the HDX issue. 

 

Ive tried to downgrade (as suggested by the controlled) using the GUI and it fails. I have also held the reset button for 10 seconds, adopted (but not applied any settings) before downgrading. This also failed. 

 

What else can I do?

 

Thanks in advance,

 

R

New Member
Posts: 35
Registered: ‎04-24-2015
Kudos: 10
Solutions: 1

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

Seems just like old times. Little has changed at Ubnt.

 

Crappy firmware, people take to the forums and guess what?

- Firmware for 1st gen UAP's is silently pulled

- Nobody from Ubnt adresses the complaints and there is no help for those who want to downgrade.

 

Happy I didn't do the upgrade. 

Cheers. 

New Member
Posts: 17
Registered: ‎11-10-2016
Kudos: 3

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

It seems that the disconnects and failures are minimal when the load is minimal.  I'm going to have to put the AC units in the high traffic areas until this issue gets fixed.

Emerging Member
Posts: 74
Registered: ‎02-24-2018
Kudos: 24
Solutions: 2

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable


@Arturo wrote:

Seems just like old times. Little has changed at Ubnt.

 

Crappy firmware, people take to the forums and guess what?

- Firmware for 1st gen UAP's is silently pulled

- Nobody from Ubnt adresses the complaints and there is no help for those who want to downgrade.

 

Happy I didn't do the upgrade. 

Cheers. 


Yeh, just pull the firmware and act like it was never in the "releases" in the first place.
No answers, no advice on how to down grade (UAP V1) and just leave their UAP V1 user base (and all their clients) to wallow in the mess.
I've used a lot of brands of routers over the last 30 years and NEVER have I come across a manufacturer which releases crap firmware time and time again.

Established Member
Posts: 880
Registered: ‎10-09-2010
Kudos: 107
Solutions: 7

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

so many issues with firmware 4.0.21.9965 devices disconnects, rstp blocking on poe 8 150 switch, 10hdx, and now cant downgrade . no help atall from ubnt 

Established Member
Posts: 880
Registered: ‎10-09-2010
Kudos: 107
Solutions: 7

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

[ Edited ]

i have one uap on wireless uplink . so i disable uplink 

 

uplink.jpg

 

now my stp blocking on switch ports stops so far, i dont see any 10 HDX so for,

but memory usage is still high, and uap disconnects still,

 

4.0.21 firmware for uaps causing this issue when there is uplink connectivity enable its flooding on all ports and causing switch to show rstp blocking and 10 HDX i guess

New Member
Posts: 36
Registered: ‎08-04-2016

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable

No help, no response..super-disappointing from UBNT! Downgraded to 4.0.15

Established Member
Posts: 880
Registered: ‎10-09-2010
Kudos: 107
Solutions: 7

Re: [FIRMWARE] 4.0.21.9965 for UAP/USW has been released | Stable


@mad1313 wrote:

No help, no response..super-disappointing from UBNT! Downgraded to 4.0.15


i couldnt able to downgrade in any means how did you do ?

Reply