Tag Archives: PowerCloud

An Outsider Looks At AirTight’s Recent Hires

I don’t get to the Silicon Valley very often, but I am a professional free-lance media type and have been monitoring and covering goings on in the WLAN space for a lot of years. Last night I got an email regarding Steven Glapa leaving Ruckus, and heading for AirTight networks as the company’s new Chief Marketing Officer. I don’t usually give coverage to staff changes in the Valley, as there are just too many of them that happen frequently, and I’m not big on puffing up egos by reporting on individuals’ career decisions. But something about the AirTight email got me thinking beyond their new CMO.

The sender of the email used the words “snagged” and “talent poaching” to describe the luring of Glapa away from Ruckus, and perhaps that’s what set the Hook of Deeper Thinking into my handsomely chiseled jaw. I have no knowledge of what made AirTight appealing to Glapa, or what it is about Ruckus that made him want to move on, and frankly I don’t really give a rip. But being a habitual Big Picture thinker, here’s what Glapa’s move got me thinking about.

  • The notion of Validation has gotten used often lately. Cisco buying Meraki validated cloud-managed wireless, which also made Aerohive and PowerCloud happy.  More recently, Aruba Networks released their opening cloud volley, followed by an interesting offering from Enterasys– again, validating the model. AirTight is part of the growing cloud-managed WLAN space, and though it’s roots are in the love-it-or-hate-it security overlay realm, has picked a hot direction to evolve given all of the validation of cloudy wireless going on these days.
  • AirTight also recently “poached” a couple of high profile staff assets from Aerohive Networks, in the forms of one Devin Akin and one Andrew von Nagy. Again, staff moves aren’t my kind of news as a rule, but there is a significance here- cloud-managed wireless has matured to the point where cloud vendors can steal each others’ expertise, as there is now an experienced cadre of cloud-savvy networkers to court. This wasn’t the case not so long ago.
  • Perhaps a “shaking out” of this market sector is imminent? AirTight gained a CMO from Ruckus, two “Evangelists” (I’m starting to of tire that term, Jimmy Swaggart) from Aerohive, and all three companies are arguably “small”. Though wireless itself is a big and growing market, could these sorts of moves reflect some hidden gloom at the “donor” companies? This is pure speculation, obviously, but also a natural mental path to wander down. How many smaller and/or cloud-managed companies can the market sustain at this point?
  • AirTight better make a splash soon, as none of these guys are probably working for cheap. Akin certainly has name recognition as a WLAN deity, with von Nagy no slouch in this regard. I don’t know much about Glapa, but given that Ruckus has been on fire at times, he must have a good business touch. So three strong HR adds have been made to a company that has a product line that needs to do some catching up before (in my opinion, at least) it legitimately competes with Meraki and Aerohive for robustness of feature set. Hopefully the new guys hasten that development for AirTight’s sake, given that payroll seems to be swelling for a company “new” to the WLAN access market.
  • Despite all of the growth and media coverage of cloudy WLAN of late, the controller-based folks still own the market. But… the division between controller-based and cloud-managed is being blurred as more vendors are doing unholy things to the control and data planes and diluting the bajeezus out of the controller model at times. The point? There is still an awful lot of industry evolution to be done. Each and every vendor in the mix has the daunting task of evolving while not losing customers or overwhelming them with constantly changing license models, lexicon, and topologies. Whether controllers completely age out and the cloud wins, or whether we end up with options in a few years remains to be seen. Meanwhile, the religious wars surrounding each kind of WLAN will rage on.

And that pretty much ends my lunch hour of deep thought- back to work I go.

How WLAN Vendors Can Solve The College Dorm Problem

Ladies and gentlemen of the WLAN industry, here are the problems with wireless networking in college dorms, and a head start on how you can develop a solution.


  1. College dorms are usually covered by the same enterprise 802.1x network used on the rest of campus, but are really more residential feeling at the operational level.
  2. Wireless printing doesn’t work where you have hundreds of anything-goes printers with no coordination on the same WLAN- and consumer-grade $40 printers don’t support enterprise security.
  3. Game consoles and Bonjoury toys also are fraught with problems and usually need yucky work-arounds on the business network usually found in dorms, or get relegated to the wired network.
  4. Rogues get installed to get around what campus WLAN can’t easily provide
  5. Ditching the enterprise WLAN and letting students bring their own wireless routers is a recipe for chaos and angst from the RF and support perspectives.


It’s not cut and dry, and my enormous cranium hasn’t yet formed the whole solution. But it starts like this:

  1. Keep all the benefits of a centrally-managed solution. RF coordination, central monitoring and configs, etc- whether cloud-based or local not so important here.
  2. Study PowerCloud’s Skydog network paradigm. Everything about it doesn’t fit the dorm challenge, but a lot of it does. If you can treat each dorm room as an apartment, with a dedicated SSID or some other compensating control (not all dorm rooms would need their own AP) we’d be off to a good start
  3. Maybe use elements of Ruckus‘ Secure Hotspot in a way that lets a single student or roommates have all of her/their gadgets in a little “private WLAN” all somehow using the same private PSK.
  4. Make sure any one student’s most common gadgets can all interact in their own little WLAN space (even Bonjour toys and printers), that it’s all easy to self-setup, and can be administered by WLAN admins if trouble hits. 
  5. With all device types accomodated, the reasons for rogues are eliminated.
  6. Make sure students can’t get to each other’s stuff, but allow for on-demand temporary access when sharing is desired.
  7. Make sure that however it all gets put together, the RF environment is still well-coordinated.

There- that was easy. Now someone just needs to build the code and interfaces…