Updating CPE first?  Mike, you secretly started drinking the Ubuiquiti
koolaid?  You of all people are going to let them get away with shoddy QA?
It's okay if new cpe are deployed one at a time are at or newer, but when
doing a system wide upgrade, no f'n way.  The damn things should be able to
be newer or older and just connect and just work regardless.

A stone-cold reliable updating process should be number one on their list.
I just updated some scabby old canopy network we acquired a couple weeks
ago from versions 6-10 years old and it just worked, no BS.  Did the AP
first.  Then brought up a handful of CPE.  Then the whole works.  We don't
even have addresses for all these locations so really didn't want to truck
roll.  But I trust that update system.

A primary/secondary firmware loading system ought to get on their to-do
list at the very least.  If people can't trust the damn things to work
without truck rolls, then people won't update firmware.  Period.

On Wed, Dec 21, 2016 at 12:09 PM, Mike Hammett <wispaubntus...@ics-il.net>
wrote:

> I think the clients should always be at equal or greater version than the
> AP, regardless of the platform.
>
>
>
> -----
> Mike Hammett
>
> Intelligent Computing Solutions <http://www.ics-il.com/>
> <https://www.facebook.com/ICSIL>
> <https://plus.google.com/+IntelligentComputingSolutionsDeKalb>
> <https://www.linkedin.com/company/intelligent-computing-solutions>
> <https://twitter.com/ICSIL>
>
> Midwest Internet Exchange <http://www.midwest-ix.com/>
> <https://www.facebook.com/mdwestix>
> <https://www.linkedin.com/company/midwest-internet-exchange>
> <https://twitter.com/mdwestix>
>
> The Brothers WISP <http://www.thebrotherswisp.com/>
> <https://www.facebook.com/thebrotherswisp>
> <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg>
> ------------------------------
> *From: *"Rory Conaway" <r...@triadwireless.net>
> *To: *"Ubiquiti Users Group" <ubnt_users@wispa.org>
> *Sent: *Wednesday, December 21, 2016 2:08:38 PM
>
> *Subject: *Re: [Ubnt_users] Firmware Releases
>
> I just test it with an XM Rocket 5M.  All clients on beta 15.  41 users
> online.  After installation, 18 users came up.  Went back to Beta, 41 users
> online again.  I'm not sure if I have to make all the clients 6.0 first but
> I do know that this is exactly what we saw with RC3 and we had to go to a
> lot of houses to unload it when they wouldn't reconnect.  We refer to that
> as hell week.
>
> Rory
>
> -----Original Message-----
> From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org]
> On Behalf Of Nick Bright
> Sent: Wednesday, December 21, 2016 10:08 AM
> To: ubnt_users@wispa.org
> Subject: Re: [Ubnt_users] Firmware Releases
>
> On 12/20/2016 9:43 AM, Kevin Lamothe wrote:
> > My experiences so far:
> >
> > 8.0 is stable
> >
> > 6.0 is stable running on 5GHz only. 2.4GHz and 900MHz AP/cpes will
> > randomly disconnect or goto sleep. Downgrading it back to 5.6.9 fixed
> > it for us.
> >
> > Ubiquiti is reviewing some support files I sent em.
> Remember kids: Just say no to dot-oh. :D
>
> --
> -----------------------------------------------
> -  Nick Bright                                -
> -  Vice President of Technology               -
> -  Valnet -=- We Connect You -=-              -
> -  Tel 888-332-1616 x 315 <(888)%20332-1616> / Fax 620-331-0789
> <(620)%20331-0789>  -
> -  Web http://www.valnet.net/                 -
> -----------------------------------------------
> - Are your files safe?                        -
> - Valnet Vault - Secure Cloud Backup          -
> - More information & 30 day free trial at     -
> - http://www.valnet.net/services/valnet-vault -
> -----------------------------------------------
>
> This email message and any attachments are intended solely for the use of
> the addressees hereof. This message and any attachments may contain
> information that is confidential, privileged and exempt from disclosure
> under applicable law. If you are not the intended recipient of this
> message, you are prohibited from reading, disclosing, reproducing,
> distributing, disseminating or otherwise using this transmission. If you
> have received this message in error, please promptly notify the sender by
> reply E-mail and immediately delete this message from your system.
>
> _______________________________________________
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
> _______________________________________________
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
> _______________________________________________
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>
_______________________________________________
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Reply via email to