Who has the Largest number of managed AirOS devices

[notor1ous]

I am with a WISP in the US and am curious if anybody has a network with as many or more managed AirOS devices I'll start by saying we have 520 devices and climbing

[UBNT-Thomas]

Folks using AirControl with managed device count > 300 raise hands, we will continue to work on performance and scalability improvements and you can help by providing info or access to your system for analysis purposes. If you don't want to reply directly on the forum please send PM.

[jknapp]

I have over 300. It gets a little clunky when trying to view large groups of devices and often crashes my browser.

Are there any recommended hardware specs available for managing large deployments?

[MaximumISP]

Same here 350 ish seems to choke out and get sluggy
I also have not had good experiances on 3.5 so the AC box has been shutdown
its not much use unless your stuff is running 3.5

[UBNT-Thomas]

AirControl work with firmware 3.4 onwards and there is no significant difference in functionality regardless whether your devices are on 3.4 or 3.5.

As for the performance, the browser slowness for larger device groups in the table is a known issue that will be addressed. But you should also consider organizing your devices into manageable groups anyways (create your own groups to categorize). There is not much value looking at multiple hundreds of devices in the table at once.

[MaximumISP]

Thomas I will not upgrade any more units from 3.3.2 until
I am sure all the strange issues I have seen on 3.5 are eliminated
3.4 is no better I did start to catagorize things but it being so sluggish
makes doing alot of them a chore any way to group them in a text file config
be way faster

[unwiredhokie]

We've got close to 400 (still waiting for all of them to show up).

I'm running on an old Dell 6300, 4x400MHz PII an 1gb ram and a decent RAID disk array. It's a bit slow but I think the main problem I'm seeing is a very large number (200-400) of TIME_WAIT when running netstat.

I have a couple of radios that *must* remain at 3.2.2 due to a DHCP pass through problem. Is there a way to monitor/manage a radio but freeze the release number from automatic updates?

I've been creating names under the Watch folder and then entering subnets for the names to scan. The real AP ESSID then shows up with some, but not all the devices. Does the entry have to stay in the Watch folder in order to have that subnet continually monitored for IP changes, new systems showing up? Is it continually monitored or do you have to re-run the scan?

Edwin
All in all, I thikn this is going to be a very useful tool.

[jknapp]

As for the performance, the browser slowness for larger device groups in the table is a known issue that will be addressed. But you should also consider organizing your devices into manageable groups anyways (create your own groups to categorize). There is not much value looking at multiple hundreds of devices in the table at once.

Breaking them up is fine and make sense for things like point to point links. But to me, the main benefit of air control is not managing my point to point links, but rather doing mass firmware upgrades on my CPE units that are out there. So the easiest way to do that is just to click the firmware version which is by nature a very large group and select all the units in need of an upgrade... In spite of the slow browser performance I have to give you guys kudos on the ability to even do this.

I did a network wide firmware upgrade on roughly 300 NS2 and PS2 units a few weeks ago to bring everyone up to 3.5. I did it in a few small chunks at first to make sure it was going to work, but as I started seeing positive results I increased the size of the chunks I was pushing new firmware too. I think my largest group was about 180 units at once. There were a few failures here and there, but I would say 95% of the units took the upgrade on the first shot.

Now, what would be outstanding is if you added features like the ability to push configuration changes such as changing a WPA2 Key on multiple units at once, or changing the SSID on multiple units at once, etc. Even being able to reboot multiple units at once would be outstanding.

Overall, I'm very excited to see what the software grows into. So far it is a clean intuitive interface and a useful tool even in beta.

[UBNT-Thomas]

I have a couple of radios that *must* remain at 3.2.2 due to a DHCP pass through problem. Is there a way to monitor/manage a radio but freeze the release number from automatic updates?
The minimum firmware version required to manage devices from AirControl is 3.4. Older versions will display, but you cannot connect the units because the firmware does not support it.

I've been creating names under the Watch folder and then entering subnets for the names to scan. The real AP ESSID then shows up with some, but not all the devices. Does the entry have to stay in the Watch folder in order to have that subnet continually monitored for IP changes, new systems showing up? Is it continually monitored or do you have to re-run the scan?

Only the local subnet is scanned automatically (and you can control that under setting). Scheduled IP range scans are currently not supported, though this is a requested feature that we will implement, likely within the next 6 months.

[ddecoria]

I have around 300 UBNT units.

It would also be incredibly helpful to sort in groups and do mass changes to the traffic shaper. It is a pain in the butt to have to change 300 units!

Thanks,
Dustin

[deadjimmy]

Currently my environment is running about 1800 ubnt devices - a mix of Bullet2/HP, Nano2/Loco, Pico2/HP, Powerstations. Aircontrol and javascript make my PC go somethin somethin.....

Given the size and configuration of this environment I do have a couple suggestions that I'll post over on the wish list thread soon.

[lwq]

We have 200+ UBNT devices in our network now and the count is growing. Mostly NS5 and new M5. Java and JavaScript makes AirControl a little bit useless and "jelliesh" - server is AMD Barton 2,4GHz, 1GB RAM, 250GB SATA and client are the most of time may MacBook Pro 5,5.

Rebuilt AirControl on eg. Apache2, PHP5/MySQL (pSQL) and some bash scripts - please :icon_smile: The "new" AirControl will be hard to run on Win - I know, however AC is ment to be server-side app, or not ? Pls :icon_cool: