Reply
Member
Posts: 167
Registered: ‎10-14-2009
Kudos: 62
Solutions: 1

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

[ Edited ]

To anyone who is having issues upgrading plain old regular Unifi APs from 4.0.14 to 4.0.15 in the controller with the upgrade button, we had to downgrade to 3.9.54 first, then do a custom upgrade to 'http://dl.ubnt.com/unifi/firmware/BZ2/4.0.15.9872/BZ.ar7240.v4.0.15.9872.181229.0259.bin' to finally get this hardware up to date. 

Emerging Member
Posts: 52
Registered: ‎08-03-2016
Kudos: 5
Solutions: 1

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

[ Edited ]

@anaptyx Yup, can't get this to work either. Tried via controller and SSH. The AP simply reboots - and remains on the same firmware. 

Ubiquiti Employee
Posts: 36
Registered: ‎01-24-2018
Kudos: 20

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

@StLouisWireless Sorry for the inconvenience. The 3.8.17 firmware should be compatible with the 5.6.40 Controller. I've tested an upgrade on an AP AC v2 (same firmware, etc.) from 3.8.16 -> 3.8.17 without any apparent issue. Are the AP AC in your network still showing disconnected? Let's chat via private message if you are still encountering issues.

Member
Posts: 104
Registered: ‎06-03-2014
Kudos: 3
Solutions: 2

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

@UBNT-charlie Thank you, I sent you over a PM. 

Ubiquiti Employee
Posts: 162
Registered: ‎06-14-2016
Kudos: 103
Solutions: 5

Re: [FIRMWARE] 4.0.15.9872 on Switch 24 No PoE issue being seen

Hi @MikelMD,

 

Can you check

1. The VLAN membership between your switch and DHCP server (on this Management VLAN).

2. DHCP server lease log, to make sure your switch get an IP. or check via switch console.

3. The routing setting on your controller.

 

Do you have any managed device using this Management VLAN?

New Member
Posts: 1
Registered: ‎06-22-2018
Kudos: 1

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

Thanks Graeme this worked perfectly, I have an AP-LR and an AP device bot had issues when attempting the upgrade .

Disabled auto upgrade and used the Custom upgrade using HTTP and it worked!
New Member
Posts: 1
Registered: ‎01-15-2019

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

[ Edited ]

When i try to upgrade AP-LR from 4.0.14 to 4.0.15 (no auto upgrade) it interrupts the proccess after upgrading (downloading) status, not moving to upgrading (writing). AP switches to connected status and is still with 4.0.14 firmware. Upgrade link becomes active again. Rebooting neither the controller, nor AP doesn't help. Manual upgrading to 4.0.15 via link or even downgrading to 3.9.54 (as suggested before) gives the same effect. Just rebooting and connected status again.

 

Edit:

Both caching the firmware in settings > maintenance or manual upgrading via http link (not https) helps.

New Member
Posts: 2
Registered: ‎01-15-2019

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

[ Edited ]

Same ping problem for us, also if no timeout occures, there is a high ping every 20 sec

 

Doesnt happen on the other AC AP Pros with 3.9.54.9373

 

Tested from Android and windows.

 

Ping wird ausgeführt für google.de [172.217.21.99] mit 32 Bytes Daten:
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=314ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=6ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=338ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=6ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=7ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=8ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=6ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=350ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57

New Member
Posts: 1
Registered: ‎09-19-2018

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

I have problem with UniFi AP-nanoHD and 4.0.15.9872 (same issue on older versions). I can't setup channel lower then 149. For example  - If I define in menu channel 36 AP did not chage it and stay on 149 channel. 

 

print_screen.png

Member
Posts: 167
Registered: ‎10-14-2009
Kudos: 62
Solutions: 1

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

@Cyr4x is your controller on site or hosted?

New Member
Posts: 19
Registered: ‎09-26-2014
Kudos: 6

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

This worked for me, Thanks.
New Member
Posts: 27
Registered: ‎01-07-2018
Kudos: 4

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

[ Edited ]

I apologise for this post.  I should have done some more testing before posting.

It appears the problem is with my laptop, or something there.  Testing rapid pings from lots of other Wifi connected devices show no problems.  I'm back on 4.0.15.9872 and can't see any issues (well, some, but they're isolated to my laptop, not all the other boxes)

 

I've had my share of odd issues with this version as well.

I have rolled back our home network consisting of two UAP-AC-LR's back to 3.9.54.9373

I've been seeing random ping spikes, and the odd dropped packet.

 

I spend all day in SSH and I've noticed of late my session hangs for 3-4 seconds about once an hour.  I left ping running in the background yesterday to the server I was SSH'd too (it's on the same LAN, not routed) and noticed the same time I'd see hangs that ICMP to the server would drop.

 

Other users on the network had also asked me if "something had changed" because they were seeing the odd drop/timeout issue with things, and "reloading the page/site" always fixes it.

 

A small datapoint, I'll update to let you know if the rollback has fixed the problem.

Member
Posts: 141
Registered: ‎03-10-2011
Kudos: 22
Solutions: 2

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

[ Edited ]

 

 


@litauer  escribió:

I think there is a network bug introduced with version 4.0.x, still existent in 4.0.15 regarding AC-Mesh-Pro:

If I install any 4.x version on my 4 UAP-AC-Mesh-Pro's every 8th ping packet takes about 2 seconds:

 

PING 141.26.131.250 (141.26.131.250): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 141.26.131.250: icmp_seq=0 ttl=64 time=2557.590 ms
64 bytes from 141.26.131.250: icmp_seq=3 ttl=64 time=0.350 ms
64 bytes from 141.26.131.250: icmp_seq=4 ttl=64 time=0.303 ms
64 bytes from 141.26.131.250: icmp_seq=5 ttl=64 time=0.383 ms
64 bytes from 141.26.131.250: icmp_seq=6 ttl=64 time=0.316 ms
64 bytes from 141.26.131.250: icmp_seq=7 ttl=64 time=0.397 ms
64 bytes from 141.26.131.250: icmp_seq=8 ttl=64 time=0.333 ms
Request timeout for icmp_seq 9
64 bytes from 141.26.131.250: icmp_seq=9 ttl=64 time=1935.335 ms
64 bytes from 141.26.131.250: icmp_seq=11 ttl=64 time=0.273 ms
64 bytes from 141.26.131.250: icmp_seq=12 ttl=64 time=0.334 ms
64 bytes from 141.26.131.250: icmp_seq=13 ttl=64 time=0.352 ms
64 bytes from 141.26.131.250: icmp_seq=14 ttl=64 time=0.380 ms
64 bytes from 141.26.131.250: icmp_seq=15 ttl=64 time=0.314 ms
64 bytes from 141.26.131.250: icmp_seq=16 ttl=64 time=0.328 ms
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
64 bytes from 141.26.131.250: icmp_seq=17 ttl=64 time=2313.222 ms
64 bytes from 141.26.131.250: icmp_seq=20 ttl=64 time=0.470 ms
64 bytes from 141.26.131.250: icmp_seq=21 ttl=64 time=0.388 ms
64 bytes from 141.26.131.250: icmp_seq=22 ttl=64 time=0.334 ms
64 bytes from 141.26.131.250: icmp_seq=23 ttl=64 time=0.346 ms
64 bytes from 141.26.131.250: icmp_seq=24 ttl=64 time=0.326 ms
64 bytes from 141.26.131.250: icmp_seq=25 ttl=64 time=0.373 ms
Request timeout for icmp_seq 26
64 bytes from 141.26.131.250: icmp_seq=26 ttl=64 time=1738.202 ms
64 bytes from 141.26.131.250: icmp_seq=28 ttl=64 time=0.326 ms
64 bytes from 141.26.131.250: icmp_seq=29 ttl=64 time=0.330 ms
64 bytes from 141.26.131.250: icmp_seq=30 ttl=64 time=0.351 ms
64 bytes from 141.26.131.250: icmp_seq=31 ttl=64 time=0.307 ms
64 bytes from 141.26.131.250: icmp_seq=32 ttl=64 time=0.348 ms
64 bytes from 141.26.131.250: icmp_seq=33 ttl=64 time=0.322 ms
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
64 bytes from 141.26.131.250: icmp_seq=34 ttl=64 time=2254.856 ms
64 bytes from 141.26.131.250: icmp_seq=37 ttl=64 time=0.306 ms

 

 

Downgrading to 3.9.42 or 3.9.54 fixes the problem. I tried 4.0.9, 4.0.10, 4.0.14 and 4.0.15. Reducing the ping intervall to 0.5 sec leads to a problem with every 16th packet. Seems to happen about every 8 secs.

 

 


 

 

Hi @litauer

It happen to me as well  only happend in UAP-AC-MESH-PRO and UAP-AC-PRO. I have a ticket since 4 months ago and still the bug.

 

I hope @UBNT-Corey solve this issue

Member
Posts: 141
Registered: ‎03-10-2011
Kudos: 22
Solutions: 2

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

[ Edited ]

@AndrKe  escribió:

Same ping problem for us, also if no timeout occures, there is a high ping every 20 sec

 

Doesnt happen on the other AC AP Pros with 3.9.54.9373

 

Tested from Android and windows.

 

Ping wird ausgeführt für google.de [172.217.21.99] mit 32 Bytes Daten:
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=314ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=6ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=338ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=6ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=4ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=7ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=8ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=6ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=350ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57
Antwort von 172.217.21.99: Bytes=32 Zeit=5ms TTL=57


 

It happend to me also. I´m still in 3.9.54 for UAP-AC-PRO and MESH-PRO

Member
Posts: 141
Registered: ‎03-10-2011
Kudos: 22
Solutions: 2

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

 

 


@smessinger  escribió:

I have observed similar behaviour with ping on my AC-Pros and AC-Mesh-Pros in the 4.0.x firmware. I discovered this when trying to troubleshoot intermittent increased response time, association issues and connectivity issues on connected devices shortly after I began trying to more widely roll out the 4.0.x firmware. The issue has been present on every AP that I have tested it on.


hi @smessinger

 

I have the same issue.  Only happen with UAP-AC-PRO and MESH PRO @UBNT-Corey still work on this

Established Member
Posts: 839
Registered: ‎10-13-2016
Kudos: 325
Solutions: 42

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


@anaptyx wrote:

To anyone who is having issues upgrading plain old regular Unifi APs from 4.0.14 to 4.0.15 in the controller with the upgrade button, we had to downgrade to 3.9.54 first, then do a custom upgrade to 'http://dl.ubnt.com/unifi/firmware/BZ2/4.0.15.9872/BZ.ar7240.v4.0.15.9872.181229.0259.bin' to finally get this hardware up to date. 


I didn't downgrade first, but custom update to http://dl.ubnt.com/unifi/firmware/BZ2/4.0.15.9872/BZ.ar7240.v4.0.15.9872.181229.0259.bin for an older "UniFi AP" worked to upgrade it to 4.0.15 - the normal "upgrade" button didn't work at all.

 

 

110+ sites / 100+ routers / 200+ switches / 300+ aps
UniFi / EdgeMAX / AirMAX / AirFiber
New Member
Posts: 23
Registered: ‎10-21-2016
Kudos: 2
Solutions: 1

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

Since upgrading our Mesh and Mesh POR from 4.01 to 4.015 we are receiving the following error constantly ({ "event_string" : "EVT_conntrack_full"} We receive hundreds ofthese notifications per night. Anyone know how to resolve this?

 

Note - our Outdoor + will not upgrade to this rev so we are putting tany further upgrades on hold until we resolve the issues of the event logs.

Ubiquiti Employee
Posts: 3,908
Registered: ‎01-11-2016
Kudos: 1160
Solutions: 29

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

@joebuck Can you get a tcpdump of the traffic flowing through that Mesh device? Most likely there is a client on your network that is creating tons of TCP connections.
Want to try out new features or fixes before they're released as Stable? Sign up for Beta here: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Signup-for-Beta-Access
Having connectivity issues? See: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
New Member
Posts: 2
Registered: ‎10-11-2018
Kudos: 1

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

Hello.

I can not update several AP models, for example UniFi AP-LR, from version 4.0.14.9736 to the latest 4.0.15.9872. I've tried it from the Upgrade button and from Custom upgrade, it does not work.

What I can do?.
New Member
Posts: 8
Registered: ‎07-31-2018
Kudos: 4
Solutions: 1

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

Do you have the ticket id?
Reply