UniFi Network Controller 5.10.12 Stable has been released

[AmazedMender16]

Hello @bsampsel,

Awesome, glad you're back up and running!

Regards,

Glenn R.

[AmazedMender16]

Hello @janth,

Looks like you either updated or restarting the USG.

Regards,

Glenn R.

[janth]

---

@AmazedMender16 wrote:

Hello @janth,

Looks like you either updated or restarting the USG.

Regards,

Glenn R.

---

Yes.  As I wrote I restarted USG.  And no. As I wrote i did not update firmware.  And the jump in memory consumption is much more dramatic than the normal restart jump.

[jms33]

A few weeks ago I successfully updated a ~50 site controller from 5.9.x to 5.10.  Currently running 5.10.12, Ubuntu 16.04.  The upgrade was smooth except that all APs provisioned after the upgrade - I knew this would happen and so I planned accordingly but it should be noted in the release notes.

Now I find that I am having an issue provioning new APs.

I'm trying to provision some AC-Pros.  They came out of the box on firmware 3.7.58.  On my office network I have a DNS entry for 'unifi' which points to my controller (L3 managed, not on the local network).  As expected, the AC-Pro shows up in the controller with the option to "Adopt & Upgrade" - I click this, the status on the AP changes to "Adopting (Update Required)" and gets stuck here.  The AP doesn't appear to be doing anything, and it will stay this way forever.  I've tried running the set-inform command on the AP to try to kick it along but this has no effect.  The APs themselves show as Connected:

BZ.v3.7.58# info

Model:       UAP-AC-Pro-Gen2
Version:     3.7.58.6385
MAC Address: b4:fb:e4:zz:zz:zz
IP Address:  192.168.254.63
Hostname:    UBNT
Uptime:      141 seconds

Status:      Connected (http://unifi:8080/inform)

I am then unable to remove the device from the controller, "There was an error removing [MAC]. Device busy." unless I disconnect the AP so it goes offline.

I haven't been able to find any way to adopt and upgrade new APs from the controller.  I have been having to manually upgrade (via SSH) the firmware on the AP, then adopt it.  This isn't the most painful thing for one or two but deploying a new site of APs would be very slow to have to SSH in and manually upgrade, and goes againt the ease in which the controller makes it in programming APs.

Is there a step I may be missing? 

[AmazedMender16]

Hello @janth,

It's normal to see a memory drop when you restart the USG.

Regards,

Glenn R.

[AmazedMender16]

Hello @jms33,

Upgrade the UAP manually.

I recommend the following upgrade path:

3.7.58 > 3.9.54 > 4.0.21

Regards,

Glenn R.

[jms33]

---

@AmazedMender16 wrote:

Hello @jms33,

Upgrade the UAP manually.

I recommend the following upgrade path:

3.7.58 > 3.9.54 > 4.0.21

Regards,

Glenn R.

---

Hi @AmazedMender16 ,

Thanks, that's what I've been doing, as indicated, but that's a cumbersome process if I'm deploying a new site of many APs - it's an OK work-around but I believe the controller should be able to upgrade APs on older firmware, no?

[jms33]

---

@jms33 wrote:

---

@AmazedMender16 wrote:

Hello @jms33,

Upgrade the UAP manually.

I recommend the following upgrade path:

3.7.58 > 3.9.54 > 4.0.21

Regards,

Glenn R.

---

Hi @AmazedMender16 ,

Thanks, that's what I've been doing, as indicated, but that's a cumbersome process if I'm deploying a new site of many APs - it's an OK work-around but I believe the controller should be able to upgrade APs on older firmware, no?

---

I should clarify.  After I upgaded the controller I still had (previously adopted) APs running older, pre-4.0.10 firmware, and the Controller was able to upgrade them without issue.  The issue I am having is only with APs that I am newly adopting.

[AmazedMender16]

Hello @jms33,

Haven’t been able to replicate this honestly.

Is the UAP able to resolve dl.ubnt.com?

Regards,

Glenn R.

[jms33]

---

@AmazedMender16 wrote:

Hello @jms33,

Haven’t been able to replicate this honestly.

Is the UAP able to resolve dl.ubnt.com?

Regards,

Glenn R.

---

Thanks for the help! Good question, yes it can.  I can run

upgrade https://dl.ubnt.com/unifi/firmware/U7PG2/4.0.21.9965/BZ.qca956x.v4.0.21.9965.190125.1623.bin

from the CLI and have it upgrade successfully.

[jms33]

Tailing the logs as I try to go through the procedure:

Feb 11 15:47:08 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #7, url=http://unifi:8080/inform

then I run the set-inform command manually using the FQDN of our controller (resolvable and pingable from the AP):

Feb 11 15:47:11 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #8, url=http://unifi.XYZ.com:8080/inform, rc=6

Then I click "Adopt + Upgrade" in the controller, and this is all that happens:

Feb 11 15:48:41 UBNT user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
Feb 11 15:48:41 UBNT user.info syslog: ace_reporter.reporter_handle_response(): cfgversion: ? -> 6e8b1748ab33686f
Feb 11 15:48:42 UBNT user.notice syswrapper: [busy] skipping: reload
Feb 11 15:48:42 UBNT user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED

Nothing more in the logs, and the controller continues to show "Adopting (Update Required)"

[AmazedMender16]

Hello @jms33,

Restart the controller.

Regards,

Glenn R.

[jms33]

---

@AmazedMender16 wrote:

Hello @jms33,

Restart the controller.

Regards,

Glenn R.

---

Gave it a try! You didn't specify if I should restart the service or the entire system - I restarted the whole system (Ubuntu 16.04).

No change.  I factory reset the AP to try again.   Logs:

Spoiler

Feb 11 16:02:21 UBNT user.err syslog: ace_reporter.reporter_fail(): Not Adopted (http://unifi:8080/inform)
Feb 11 16:02:21 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #2, url=http://unifi:8080/inform, rc=6
Feb 11 16:02:22 UBNT kern.info kernel: [   18.040000] br0: port 3(ath1) entered disabled state
Feb 11 16:02:28 UBNT kern.debug kernel: [   24.270000] br0: no IPv6 routers present
Feb 11 16:02:29 UBNT kern.debug kernel: [   25.060000] ath0: no IPv6 routers present
Feb 11 16:02:29 UBNT kern.debug kernel: [   25.060000] eth0: no IPv6 routers present
Feb 11 16:03:21 UBNT authpriv.info dropbear[1429]: Child connection from 192.168.254.46:56916
Feb 11 16:03:29 UBNT authpriv.notice dropbear[1429]: Password auth succeeded for 'ubnt' from 192.168.254.46:56916
Feb 11 16:03:51 UBNT user.err syslog: ace_reporter.reporter_fail(): Not Adopted (http://unifi:8080/inform)
Feb 11 16:03:51 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #3, url=http://unifi:8080/inform, rc=6
Feb 11 16:03:51 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url[0]=http://unifi:8080/inform
Feb 11 16:03:51 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): authkey=ba86f2bbe107c7c57eb5f2690775c712

-- at this point it shows up in the controller and so I click "Adopt and Upgrade" ---

Feb 11 16:05:21 UBNT user.err syslog: ace_reporter.reporter_fail(): Unable to resolve (http://unifi:8080/inform)
Feb 11 16:05:21 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #4, url=http://unifi:8080/inform, rc=1
Feb 11 16:05:21 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url[0]=http://unifi:8080/inform
Feb 11 16:05:21 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): authkey=ba86f2bbe107c7c57eb5f2690775c712
Feb 11 16:05:37 UBNT user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
Feb 11 16:05:37 UBNT user.info syslog: ace_reporter.reporter_handle_response(): cfgversion: ? -> f5190f97cd8bb63e
Feb 11 16:05:38 UBNT user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED

Then nothing more happens, the AP doesn't reboot or do anything, nothing more shows in the logs, and after 5 minutes or so it shows up as Disconnected in the controller.

[jms33]

For kicks, I upgraded the AP to 3.9.54 and factory reset it, then tried to Adopt & Upgrade from the controller again.  No change in behavior

Feb 11 16:19:27 UBNT user.err syslog: ace_reporter.reporter_fail(): Decrypt Error (http://unifi:8080/inform)
Feb 11 16:19:27 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #3, url=http://unifi:8080/inform, rc=8
Feb 11 16:19:27 UBNT user.info syslog: ace_reporter.reporter_next_inform_method(): next inform family: 10
Feb 11 16:19:34 UBNT user.err syslog: mcagent_data.data_decrypt(): header too small. size=0, should be=40
Feb 11 16:19:34 UBNT user.err syslog: ace_reporter.process_inform_response(): Failed to get the decrypted data from custom alert response
Feb 11 16:19:34 UBNT user.err syslog: ace_reporter.reporter_fail(): Decrypt Error (http://unifi.XYZ.com:8080/inform)
Feb 11 16:19:34 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #1, url=http://unifi.XYZ.com:8080/inform, rc=8
Feb 11 16:19:49 UBNT user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
Feb 11 16:19:49 UBNT user.info syslog: ace_reporter.reporter_handle_response(): cfgversion: ? -> 266d5cb6cd60dfa2
Feb 11 16:19:50 UBNT user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED

Then it goes Disconnected in the controller though the AP thinks it is connected:

UBNT-BZ.v3.9.54# info

Model:       UAP-AC-Pro-Gen2
Version:     3.9.54.9373
MAC Address: b4:fb:e4:43:zz:zz
IP Address:  192.168.254.63
Hostname:    UBNT
Uptime:      462 seconds

Status:      Connected (http://unifi.XYZ.com:8080/inform)

[AmazedMender16]

Hello @jms33,

Factory reset the UAP and forget it in the controllee, hn upgrade and adopt it.

Regards,

Glenn R.

[janth]

---

@AmazedMender16 wrote:

Hello @janth,

It's normal to see a memory drop when you restart the USG.

Regards,

Glenn R.

---

You dont seem to read what I write.  The jump is far bigger than a normal restart jump, and it continue to be low.  I would not have mentioned it if it was normal behaviour and in any case the message was to Ubiquity who asked for feedback on the statistics.

[jms33]

---

@AmazedMender16 wrote:

Hello @jms33,

Factory reset the UAP and forget it in the controllee, hn upgrade and adopt it.

Regards,

Glenn R.

---

Yes, that works fine when upgraded to 4.0.10 or above.  I'm hoping for it to work fine on any firmware - our techs take the APs out of the box, plug them into our network, and adopt and upgrade them from the controller.  It adds a lot if they need to manually upgrade them first.  I recognize the minimum requirements of the new controller, but I expect the adoption procedure to be as easy as it was before. I know you're not UBNT and I very much appreciate your help  

[AmazedMender16]

Hello @jms33,

Understood, I tried this just a minute ago and it worked fine for me.. for giggles could you click upgrade instead of adopt & upgrade 

Regards,

Glenn R.

[jms33]

---

@AmazedMender16 wrote:

Hello @jms33,

Understood, I tried this just a minute ago and it worked fine for me.. for giggles could you click upgrade instead of adopt & upgrade 

Regards,

Glenn R.

---

Aha! I only have the option to "Adopt & Upgrade" because it has not been adopted yet.  Are you trying with an AP-AC-Pro that has not yet been adopted into your controller? Is your controller on the same L2 network as the AP? Trying to figure out what's different between your setup and mine which would cause this.  Thanks!!

[AmazedMender16]

Hello @jms33,

The UAP was in factory default state, the controller is on the same L2 network.

Regards,

Glenn R.