Unifi users - how often do you find yourself needing to restart APs?

Hey gang!

I’m especially curious if other Unifi users find themselves needing to reboot access points from time to time. It seems like a few of ours tend to get used more, and over time…they seem to slow down.

A quick restart from the Unifi console gets them back to their snappy usual selves, but I’m wondering if we can address the problem somewhere else in the admin console? I’ve been experimenting with load balancing within wlan groups but I can’t tell if it’s helping or not :slight_smile:

Configuration tips welcome!

-Alex

···

The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

I’m seeing something similar, although I don’t have enough data to really offer much to the conversation. I know one of our APs keeps dropping down to 100Mbps so I think it has a bad cable. I also see a fair amount of channel switching going on. I’ve left things on auto hoping it will figure out the best settings, but I might need to pin them down.

Jacob

···

On Thu, Apr 23, 2015 at 11:55 AM, Alex Hillman [email protected] wrote:

Hey gang!

I’m especially curious if other Unifi users find themselves needing to reboot access points from time to time. It seems like a few of ours tend to get used more, and over time…they seem to slow down.

A quick restart from the Unifi console gets them back to their snappy usual selves, but I’m wondering if we can address the problem somewhere else in the admin console? I’ve been experimenting with load balancing within wlan groups but I can’t tell if it’s helping or not :slight_smile:

Configuration tips welcome!

-Alex


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.

Not something we've seen yet since we're new but it's certainly something I'll keep an eye out for now that you've mentioned it.

What's you typical load per AP? Or the APs that seem to slow down?

It seems to be less about the number of devices currently connected (can be anywhere between 20 and 50 on a normal day) and how many devices have been connected in recent days/weeks. I can’t prove that to be 100% true, that’s my instinct.

-Alex

···

On Sunday, April 26, 2015, Jacques Paquin [email protected] wrote:

Not something we’ve seen yet since we’re new but it’s certainly something I’ll keep an eye out for now that you’ve mentioned it.

What’s you typical load per AP? Or the APs that seem to slow down?

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]com.

For more options, visit https://groups.google.com/d/optout.


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

We’ve been using Unifi for awhile now and started having the same issues after a few months of usage. I did a lot of the load balancing stuff, along with a lot of Channel/Band configuration to deal with problems. We had the same issues of needing to reboot and it didn’t matter if it was 60+ people or only 10. I tried to see if it was a time of day and that didn’t seem to matter. I thought it was a POE issue for a bit but after playing with different things, it didn’t seem to be the case.

We actually just switched everything to Meraki (https://meraki.cisco.com/). I manage our infrastructure but also chat quite a bit with the building owner that offers WIFI to the rest of the building (4 floors). They had Unifi as well and were noticing the same things. The verdict is still out - on day 2 right now but I like the additional reporting within Meraki.

I also like how Meraki handles wireless band selection (2.4GHz vs 5GHz) much better as well. Unifi is supposed to do this but doesn’t do it well. We noticed a lot of users (mostly Mac) could connect to 5GHz but got stuck at 2.4GHz often. I ended up broadcasting only 5GHz and created another SSID for 2.4GHz for the few users still needing that. Wasn’t ideal but everyone had a much better experience. Meraki does “Band Steering” much better by detecting clients capable of 5GHz operation and steers them to that frequency, while leaving 2.4GHz available for legacy clients.

I’d be curious if you figure it out but we decided to switch to Meraki ourselves.

···

Aaron Schaap
The Factory - www.workthefactory.com
@schaapy and @coFactory

Interesting - we did a trial with Meraki and for us, the broadcast range was terrible in our building.

I found some tools that work with the Unifi API to detect issues and can even trigger an access point reboot, I’m considering an experiment to cycle access points regularly to keep them “fresh” and see if that helps.

-Alex

···

On Mon, Apr 27, 2015 at 9:18 AM, Aaron Schaap [email protected] wrote:

We’ve been using Unifi for awhile now and started having the same issues after a few months of usage. I did a lot of the load balancing stuff, along with a lot of Channel/Band configuration to deal with problems. We had the same issues of needing to reboot and it didn’t matter if it was 60+ people or only 10. I tried to see if it was a time of day and that didn’t seem to matter. I thought it was a POE issue for a bit but after playing with different things, it didn’t seem to be the case.

We actually just switched everything to Meraki (https://meraki.cisco.com/). I manage our infrastructure but also chat quite a bit with the building owner that offers WIFI to the rest of the building (4 floors). They had Unifi as well and were noticing the same things. The verdict is still out - on day 2 right now but I like the additional reporting within Meraki.

I also like how Meraki handles wireless band selection (2.4GHz vs 5GHz) much better as well. Unifi is supposed to do this but doesn’t do it well. We noticed a lot of users (mostly Mac) could connect to 5GHz but got stuck at 2.4GHz often. I ended up broadcasting only 5GHz and created another SSID for 2.4GHz for the few users still needing that. Wasn’t ideal but everyone had a much better experience. Meraki does “Band Steering” much better by detecting clients capable of 5GHz operation and steers them to that frequency, while leaving 2.4GHz available for legacy clients.

I’d be curious if you figure it out but we decided to switch to Meraki ourselves.


Aaron Schaap
The Factory - www.workthefactory.com
@schaapy and @coFactory

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

Those tools look great. Thanks for sharing Alex!

Our APs get rebooted about once per month. It’s difficult to tell if they actually needed it, it’s the first thing members will do when they experience any connectivity problems.

We have between 60 and 100 devices per day across 5 access points, two of which can only get an uplink at 100Mbit due to old wiring. We’ve left the configuration to defaults, they adjust their own power levels and channels as the environment changes.

I’m of the opinion that the easiest way to improve WiFi is simply to buy more access points (provided they are smart enough to keep their power levels low and can roam users to their nearest AP). I’ve already spent too much of my life trying and failing to optimise WiFi configurations. :slight_smile:

···

On 27 April 2015 at 14:51, Alex Hillman [email protected] wrote:

Interesting - we did a trial with Meraki and for us, the broadcast range was terrible in our building.

-Alex

I found some tools that work with the Unifi API to detect issues and can even trigger an access point reboot, I’m considering an experiment to cycle access points regularly to keep them “fresh” and see if that helps.

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

On Mon, Apr 27, 2015 at 9:18 AM, Aaron Schaap [email protected] wrote:

We’ve been using Unifi for awhile now and started having the same issues after a few months of usage. I did a lot of the load balancing stuff, along with a lot of Channel/Band configuration to deal with problems. We had the same issues of needing to reboot and it didn’t matter if it was 60+ people or only 10. I tried to see if it was a time of day and that didn’t seem to matter. I thought it was a POE issue for a bit but after playing with different things, it didn’t seem to be the case.

We actually just switched everything to Meraki (https://meraki.cisco.com/). I manage our infrastructure but also chat quite a bit with the building owner that offers WIFI to the rest of the building (4 floors). They had Unifi as well and were noticing the same things. The verdict is still out - on day 2 right now but I like the additional reporting within Meraki.

I also like how Meraki handles wireless band selection (2.4GHz vs 5GHz) much better as well. Unifi is supposed to do this but doesn’t do it well. We noticed a lot of users (mostly Mac) could connect to 5GHz but got stuck at 2.4GHz often. I ended up broadcasting only 5GHz and created another SSID for 2.4GHz for the few users still needing that. Wasn’t ideal but everyone had a much better experience. Meraki does “Band Steering” much better by detecting clients capable of 5GHz operation and steers them to that frequency, while leaving 2.4GHz available for legacy clients.

I’d be curious if you figure it out but we decided to switch to Meraki ourselves.


Aaron Schaap
The Factory - www.workthefactory.com
@schaapy and @coFactory

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.

Jonathan Markwell

Lessons learned building better workplaces: http://jonathanmarkwell.com

Work better in Brighton: http://theskiff.org

Coworking community with workspace in North Laine.

Find your coworking community: http://worksnug.com

Worldwide workspace directory that puts communities first.

Ship your digital product: http://coderfounders.com

Coaching for businesses that want to make money while they sleep.

+44 (0)7766 021 485
skype: jlmarkwell | twitter: http://twitter.com/jot

We’ve only just started so I’m keeping my eyes open for this problem. Those tools look promising. Is there a stand-alone utility to reboot an AP? Or do you need to code something up in Python?

-jacques

If you’re running the management software (which you really should - even though it’s not “require” it handles SO much automatically), you can browse to an access point and restart it with a single click.

See this screenshot: http://dangerouslyawesome.com/snaps/indyhalljukebox.at.indyhall.org_-_UniFi_2015-04-29_14-59-42.jpg

···

On Wed, Apr 29, 2015 at 2:57 PM, Jacques Paquin [email protected] wrote:

-jacques

We’ve only just started so I’m keeping my eyes open for this problem. Those tools look promising. Is there a stand-alone utility to reboot an AP? Or do you need to code something up in Python?

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

I am running the management software and I have played with all those options. But if this was a concern in the future, or just for cruft cleanup, I might put them on a once a month reboot schedule. And much like everything else at this point in my life, if I don’t set up a recurring task to just DO IT, I tend to forget :slight_smile:

···

On Wed, Apr 29, 2015 at 3:00 PM, Alex Hillman [email protected] wrote:

If you’re running the management software (which you really should - even though it’s not “require” it handles SO much automatically), you can browse to an access point and restart it with a single click.

See this screenshot: http://dangerouslyawesome.com/snaps/indyhalljukebox.at.indyhall.org_-_UniFi_2015-04-29_14-59-42.jpg

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to a topic in the Google Groups “Coworking” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/coworking/e8lywtX02h8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

On Wed, Apr 29, 2015 at 2:57 PM, Jacques Paquin [email protected] wrote:

-jacques

We’ve only just started so I’m keeping my eyes open for this problem. Those tools look promising. Is there a stand-alone utility to reboot an AP? Or do you need to code something up in Python?

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.

A few years ago, when I built an outdoor public network, we had to put an appliance timer in to power cycle a Ubiquiti AP for a minute at 3AM every day. :slight_smile: It was on a roof at the far end of a point to point link. In the rest of the network, we used IP enabled power switches that we could do on-demand reboots with.

This kind of thing has been a problem with Ubiquiti equipment for years. It is a great value, but requires care and feeding.

When and why did you switch from Ruckus?

Craig

···

On Thursday, April 23, 2015 at 2:56:05 PM UTC-4, Alex Hillman wrote:

Hey gang!

I’m especially curious if other Unifi users find themselves needing to reboot access points from time to time. It seems like a few of ours tend to get used more, and over time…they seem to slow down.

A quick restart from the Unifi console gets them back to their snappy usual selves, but I’m wondering if we can address the problem somewhere else in the admin console? I’ve been experimenting with load balancing within wlan groups but I can’t tell if it’s helping or not :slight_smile:

Configuration tips welcome!

-Alex


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

“When and why did you switch from Ruckus?”

It’s been about 6 months. We had the same problems and worse with Ruckus. Unifi has been 100x better for us, and I’m feeling more confident in this thread that if we auto-reboot our APs overnight on a schedule the remaining problems will be gone.

I’ll report back when we do!

-Alex

···

On Friday, May 1, 2015, Craig Plunkett [email protected] wrote:

A few years ago, when I built an outdoor public network, we had to put an appliance timer in to power cycle a Ubiquiti AP for a minute at 3AM every day. :slight_smile: It was on a roof at the far end of a point to point link. In the rest of the network, we used IP enabled power switches that we could do on-demand reboots with.

This kind of thing has been a problem with Ubiquiti equipment for years. It is a great value, but requires care and feeding.

When and why did you switch from Ruckus?

Craig

On Thursday, April 23, 2015 at 2:56:05 PM UTC-4, Alex Hillman wrote:

Hey gang!

I’m especially curious if other Unifi users find themselves needing to reboot access points from time to time. It seems like a few of ours tend to get used more, and over time…they seem to slow down.

A quick restart from the Unifi console gets them back to their snappy usual selves, but I’m wondering if we can address the problem somewhere else in the admin console? I’ve been experimenting with load balancing within wlan groups but I can’t tell if it’s helping or not :slight_smile:

Configuration tips welcome!

-Alex


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast

Visit this forum on the web at http://discuss.coworking.com


You received this message because you are subscribed to the Google Groups “Coworking” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

For more options, visit https://groups.google.com/d/optout.


The #1 mistake in community building is doing it by yourself.

Join the list: http://coworkingweekly.com

Listen to the podcast: http://dangerouslyawesome.com/podcast