Review: Meraki Controls WLANs From The Cloud

Wireless vendor replaces costly on-premises WLAN controllers with a hosted alternative.

Meraki's Enterprise Cloud Controller challenges the thin wireless model espoused by Aruba, Cisco, Meru, and others by moving controller functions into the cloud. Its goal: Slash the cost of business-class wireless.

Where typical controllers take the form of pricey and specialized chassis switch blades or self-contained appliances, Meraki's Cloud Controller requires no data center space or power. Setup and maintenance are via a straightforward GUI, there's no need to tinker with controller patches, and security configurations are managed just as if the unit were on-site. Control resides in Meraki's multiple redundant data centers. Access points from Meraki's extensive product line simply plug into your local network, find their way to the Internet for system control, and join the Cloud Controller over an AES-encrypted secure tunnel. Local traffic stays on your network--only control packets travel off-site.


More Mobility Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

That's Not All
There's more to learn about Cloud Controller.
Meraki provided three access points for testing. We connected them at two sites 17 miles apart and within minutes had a secure 802.1x-based wireless LAN; an open, portal-based visitor WLAN; and a WEP-based WLAN. All delivered expected throughput levels given WLAN setups and Internet connectivity.

There are trade-offs to Meraki's system, including limited VLAN scalability, no rogue detection, and the need to contact Meraki for many advanced features. However, we were pleased overall with the Enterprise Cloud Controller.

Lee Badman is a network engineer at Syracuse University.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links