Reply
New Member
Posts: 7
Registered: ‎03-14-2017
Kudos: 1

Documentation of the upgrade process?

Hello!

 

Is there a document that describes the upgrade process?

I'm unsure how this all works, because the documentation is lacking this informations.

 

This is what I found:

 

  1. On one hand we have the "Settings -> Automatically upgrade firmware" checkbox.

    What does this do?

    Does it automatically update all AccessPoints or only grab the latest Firmware from the download server? Or both?

  2. Then we have the "Devices -> Upgrade" button.

    Triggering this button, where did it load the firmware from?

    The best method would from the controller, because not any AccessPoint would have Internet access. But it's nowhere documented...

    Looking in the log file, it seems to send the official download URL "http://dl.ubnt.com/unifi/firmware/..." to the accesspoint, but it's only a guess. If so, why it's not using the local server (controller)?
  3. And we have the "Devices -> Properties -> Configuration -> Manage Device -> Custom Upgrade" Upload.

    When should I use this? Only for unusal firmware updates?

    Can I specify a local server here?

  4. And at last we have the possibility to upgrade the firmware on the accesspoint itself (SSH/SCP).

    I think this in only needed in problem cases...?!

 

Ubiquiti, if there is no document already, please create one!

 

Regards

 Sven

 

SuperUser
Posts: 41,748
Registered: ‎06-23-2009
Kudos: 8519
Solutions: 1411

Re: Documentation of the upgrade process?

I believe some of this is documented in the Ubiquiti

manual; have you read it?

 

You seem concerned, and I'm not sure why.

 

1> both

2> from the Ubiquiti fileserver; an access point may not

    have Internet access, but the controller PC must have,

    and the access point must be connected to the controller

    at initial install, the controller will have a firmware build

    for that level software; later updates must be from Ubiquiti

3> yes: if you want to update an access point beyond

     what is currently offered, you paste the URL of the new

     firmware in this field; the access point will download it

     and update; of course, this is for one access point only

4> please read 3>

 

Dave


> HQ in Seacoast region New Hampshire U.S.A.
> Ubiquiti Certified Trainer [UCT] for:
     UBWA [AirMax] / UEWA [UniFi] / UBRSS [routers]
UBNT.NH@gmail.com
New Member
Posts: 7
Registered: ‎03-14-2017
Kudos: 1

Re: Documentation of the upgrade process?

Dave-D wrote:

I believe some of this is documented in the Ubiquiti manual; have you read it?

 

Yes I read it, but it's not very detailed. Regarding point 1 I only found the following:

 

"Automatic Upgrade": When enabled, the UniFi Controller will automatically upgrade your firmware when an update is available.

 

You seem concerned, and I'm not sure why.

 

Because it does not work as expected and now I try to understand the logic...

 

1> both

 

Ok, In which interval is this done? How long do I have to wait when testing it?

 

2> from the Ubiquiti fileserver; an access point may not have Internet access, but the controller PC must have, and the access point must be connected to the controller at initial install, the controller will have a firmware build for that level software; later updates must be from Ubiquiti.

 

Hmm, but it does not seem to work. I tested it with the Controller version 5.4.11.

The access points still have version 3.7.17. The controller offers version 3.7.37, but if I hit the "UPGRADE" button I see in the log the following line:

 

[2017-03-14 17:05:07,757] <inform-138> INFO inform - <<< [upgrade] dev[80:2a:a8:63:22:30] { "_type" : "upgrade" , "md5sum" : "3cf1214b59ff1076ececb4d1fe673d24" , "server_time_in_utc" : "1489507507757" , "url" : "http://dl.ubnt.com/unifi/firmware/U7PG2/3.7.47.6194/BZ.qca956x.v3.7.47.6194.170310.1133.bin" , "version" : "3.7.47.6194"}

 

Why do I see the version 3.7.47 here instead of the provided 3.7.37?

 

Every time I hit the button, the access point goes offline for a while and after a reset it still has the old version.

 

Any further tips?

 

3/4> yes: if you want to update an access point beyond what is currently offered, you paste the URL of the new firmware in this field; the access point will download it and update; of course, this is for one access point only.

 

Ok, this is clear and it seems to work...

 

Thanks for the anwers so far...

 

Regards

 Sven

SuperUser
Posts: 41,748
Registered: ‎06-23-2009
Kudos: 8519
Solutions: 1411

Re: Documentation of the upgrade process?

Sven, the Ubiquiti server only offers the latest

released firmware; I can't explain why the version

that you see planned for update is different than

the one the server provides. For all I know there

may be a small glitch in the display.

 

Often test or newer firmware is offered in the beta

forums separately from the release server; that

firmware can only be installed using the manual

update--or by installing a beta controller software.   Dave


> HQ in Seacoast region New Hampshire U.S.A.
> Ubiquiti Certified Trainer [UCT] for:
     UBWA [AirMax] / UEWA [UniFi] / UBRSS [routers]
UBNT.NH@gmail.com
New Member
Posts: 7
Registered: ‎03-14-2017
Kudos: 1

Re: Documentation of the upgrade process?

Sven, the Ubiquiti server only offers the latest released firmware; I can't explain why the version

that you see planned for update is different than the one the server provides. For all I know there

may be a small glitch in the display.

 

I think the output is clear. It uses an external URL.

What does your system output here, if you trigger an upgrade?

 

I read another forum post where someout has a similar problem.

What controller version are you running?

 

Do you know what the automatic upgrade interval is set to?

Can I trigger the "automatic upgrade" to do it instantly?

This would be handy to test this functionality...

 

Regards

 Sven

 

SuperUser
Posts: 41,748
Registered: ‎06-23-2009
Kudos: 8519
Solutions: 1411

Re: Documentation of the upgrade process?

Sven, all I can say is: 'don't worry'.

 

If you have firmware that works for you and there

are no special issues, you can keep using it. 


> HQ in Seacoast region New Hampshire U.S.A.
> Ubiquiti Certified Trainer [UCT] for:
     UBWA [AirMax] / UEWA [UniFi] / UBRSS [routers]
UBNT.NH@gmail.com
New Member
Posts: 7
Registered: ‎03-14-2017
Kudos: 1

Re: Documentation of the upgrade process?


@Dave-D wrote:

Sven, all I can say is: 'don't worry'.

 

If you have firmware that works for you and there

are no special issues, you can keep using it. 


That isn't really helpful.

I'm testing the upgrade process for one of our customers and currently it does not

work as expected...

 

Can anybody please answer this question and possibly give hints in which versions (controller and firmware) it does work and which versions may be problematic?!

 

Regards

 Sven

 

 

New Member
Posts: 7
Registered: ‎03-14-2017
Kudos: 1

Re: Documentation of the upgrade process?

Ok, I experimented and analysed the update process a little further.

 

I seems, that the controller updates the firmware information from the internet. But only the latest firmware version number, not the firmware images itself.

 

So the controller sends the newest available firmware version to the accesspoint even if the accesspoint does not have any internet access.

 

I think this is a bug and could be fixed in two ways:

 

1. Make an automatic update of the firmware images on the controller.

    (I read in an old post from last year that this in planned... Is this correct?)

 

2. Fall back or force the accesspoint to update only to the firmware provided by the controller.

 

It would still be nice to have some more documentation. So I found the "rolling updates" feature, the automatic updates interval cannot be found anywhere and it's not clear what the "Settings->Maintenance->Services->Device Firmware Update->CHECK FIRMWARE UPDATE" button does. Moreover it would be nice to schedule the "rolling updates".

 

 

Regards

 Sven

 

SuperUser
Posts: 41,748
Registered: ‎06-23-2009
Kudos: 8519
Solutions: 1411

Re: Documentation of the upgrade process?

I agree in general that documentation could be improved;

it's a long discussion on that.

 

And some have requested more control over update time--

for example, delaying updates until early morning.

 

But neither of these is a 'bug', and I don't understand what

your need or issue is:

   "So the controller sends the newest available firmware version to

the accesspoint even if the accesspoint does not have any internet access."

 

I think I answered that one, but why is it a bug? And if you

want to change [upgrade or downgrade] firmware for an

access point, the manual feature provides that option.    Dave


> HQ in Seacoast region New Hampshire U.S.A.
> Ubiquiti Certified Trainer [UCT] for:
     UBWA [AirMax] / UEWA [UniFi] / UBRSS [routers]
UBNT.NH@gmail.com
New Member
Posts: 7
Registered: ‎03-14-2017
Kudos: 1

Re: Documentation of the upgrade process?


@Dave-D wrote:

But neither of these is a 'bug', and I don't understand what

your need or issue is:

   "So the controller sends the newest available firmware version to

the accesspoint even if the accesspoint does not have any internet access."

 

I think I answered that one, but why is it a bug? And if you

want to change [upgrade or downgrade] firmware for an

access point, the manual feature provides that option.    Dave


It's a bug:

I cannot upgrade the accesspoints because they do not have an internet connection and the controller sends the wrong URL.

 

If I would have only one or two accesspoints, I could update these manually, but this does not work for 100 or more accesspoints.

I can upload the newest firmware to the controller and adapt the bundles.json file, but this cannot be the correct solution. The correct solution would be, if the controller sends the correct URL.

 

Regards

 Sven

 

 

 

 

SuperUser
Posts: 41,748
Registered: ‎06-23-2009
Kudos: 8519
Solutions: 1411

Re: Documentation of the upgrade process?

Ok, so this statement isn't true?

 

   "So the controller sends the newest available firmware version to

the accesspoint even if the accesspoint does not have any internet access."

 

You seem to say that the controller does not send the newest

available firmware but something else. I believe the correct

behavior would be to send the latest--not some other version.

 

Trust me: I'm not trying to drag this out...only to understand.   Dave


> HQ in Seacoast region New Hampshire U.S.A.
> Ubiquiti Certified Trainer [UCT] for:
     UBWA [AirMax] / UEWA [UniFi] / UBRSS [routers]
UBNT.NH@gmail.com
New Member
Posts: 7
Registered: ‎03-14-2017
Kudos: 1

Re: Documentation of the upgrade process?


@Dave-D wrote:

Ok, so this statement isn't true?

 

   "So the controller sends the newest available firmware version to

the accesspoint even if the accesspoint does not have any internet access."

 

You seem to say that the controller does not send the newest

available firmware but something else. I believe the correct

behavior would be to send the latest--not some other version.


Ok, to clarify:

The controller only sends the URL for the update. The accesspoint then tries to downloads the firmware from this URL.

The problem is now, that the controller sends an URL pointing to the external resource "http://dl.ubnt.com/unifi/firmware/..." because the controller knows it has not the newest firmware itself. But he does not know, that the accesspoint does not have the same internet access rules. So the accesspoint tries to download the firmware and fails.

Instead the controller should only send the local URL, because that could be accessed by the accesspoint.

As long as you upgrade the controller and do the upgrade of the accesspoints at the same time you have no problem, but if some time passes and you want to upgrade the accesspoints after a newer version of the firmware (as provided by the controller) exists, you run into this problem.

 

For the right correction see the my previous posting...

 

I hope it's clearer now?!

 

Regards

 Sven

 

 

SuperUser
Posts: 41,748
Registered: ‎06-23-2009
Kudos: 8519
Solutions: 1411

Re: Documentation of the upgrade process?

[ Edited ]

Got it.

 

I believe the designers felt it's reasonable to

expect that if the controller has Internet access,

so do the the access points--which are on the

same LAN. I understand there could be very

rare exceptions to that.

 

If on the other hand, the controller had to maintain

a local repository of multiple firmware images

[there are currently different ones for various access

point types/versions], the controller would also have to

manage its available storage space in a complex way.

It's not assured in a small device [such as a Cloud

Key] there would always be enough space.

 

If you 'fix' one issue that impacts very few people,

you create another one that could have wide effects.

 

Do you have a solution in mind?    Dave


> HQ in Seacoast region New Hampshire U.S.A.
> Ubiquiti Certified Trainer [UCT] for:
     UBWA [AirMax] / UEWA [UniFi] / UBRSS [routers]
UBNT.NH@gmail.com
Highlighted
SuperUser
Posts: 9,419
Registered: ‎01-10-2012
Kudos: 5852
Solutions: 385

Re: Documentation of the upgrade process?

[ Edited ]

@Dave-D wrote:

 

If on the other hand, the controller had to maintain

a local repository of multiple firmware images

[there are currently different ones for various access

point types/versions], the controller would also have to

manage its available storage space in a complex way.

It's not assured in a small device [such as a Cloud

Key] there would always be enough space.

 


Eventually they are going to have to do this anyway.  As for managing storage, on the firmware management screen just show me the available disk space, and for firmware files their size.  When I select a bunch of firmware files to download, warn me if I don't have enough disk space.

 

The newer cloud keys have greatly increased disks - and not all of us run the controller on a cloud key too.  For an "enterprise" solution, better firmware management is essential at larger sites where again, the cloud key is likely to be less of an issue.

 

@SvenA - it may not be obvious, but if you get the firmware to a URL the AP's can access you can go into group edit mode on the AP screen, select multiple APs and then custom upgrade them all at once.  Of course they will all reboot at once to so there is that.

 

Right now the best way is to probaly modify the firmware files and bundle.json on the controller.  Yup, it's ugly but it's where we are today.  I have a site where the APs don't have Internet access either - Internet access is tightly controlled. I copy the firmware to the controller manually (but I'm pretty sure the last time I just cheated and renamed the file and didn't mess with the .json).

When you receive a solution to your question/issue, don't forget to mark your thread as solved and to give kudo's to the people who have helped you out!

Having wifi problems? Take a look here first: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Reply