Meraki goes iWAN, but retires a marketed feature.

Cisco iWAN

If you have not read up on Cisco’s iWAN architecture it is pretty cool stuff.     I will not explain the entire concept, but provide you a link to read on.

The concept is pretty simple, instead of having a WAN circuit like an MPLS, and then an Internet with a VPN backup that is inactive,  Intelligent WAN will let you use both the WAN and the VPN at the same time based on all sorts of things, link performance, latency and application routing.  It is all based on PFR and various topics which I will admit – I am not that good at, I have however looked at it, and it is VERY complicated.   After speaking with a colleague who set it up, his message was “It works well, but it was hard to setup and get working properly”

Meraki Goes iWAN!

Today Meraki announced more details about how they are adding iWAN technology to their portfolio.

Link here –

They explain it pretty simple – Dual Active Path and intelligent path control.     If Meraki can bring the Meraki simplicity to something as complicated as iWAN  — All I can say is, bravo.   This is not a simple technology to setup, and Meraki has a history of making the complicated simple.    As soon as I can get my hands on this I will be testing it out, I have a few clients that will be extremely happy to hear about this.

Imagine if your Intranet, Sharepoint site, and other services could be sent over Internet VPN, and file sharing over expensive WAN links.     The savings could be significant, and now iWAN can be used by the SMB marketplace.     I know that @networkingnerd is always asking the question — is Meraki Ready for Enterprise  — if they keep doing things like this — and if the implementation is good this will be a huge step forward.

Now for the down note.

Meraki removes WAN Optimization

This is not the first time Meraki has retired a feature, some of the MR series used to support PPPoE  as an example.

To quote a recent email blasted from Meraki

After careful review, Cisco Meraki has determined that the current WAN Optimization feature in the MX Security Appliance product line does not meet the quality standard that our customers and partners deserve. As a result, the decision has been made to retire the WAN Optimization feature. This will allow the Meraki team to focus efforts on providing the best security platform in the industry for distributed networks.

   Wait a second — Didn’t Meraki market this feature – as an example in this blog post.   What if a customer purchased this feature only to find out that

  1. They are removing it by end of 2015
  2. You are forced to implement a new feature which means possibly bringing in a partner or support person to help
  3. Between now and the end of 2015 there will be no more bug fixes

How would you feel if you were marketed this feature, and then it is removed, with no idea on how the new feature will function and if it will provide the same features or not.

    The argument could be made that if you purchased a NON Cloud product, and that feature was working just fine – you could keep it because it works for you – however in this case Meraki because of the cloud controller concept is removing a feature regardless of how the end user customers feel about it.     While I am sure if I pour through the fine print at Meraki Policies there is something that says “Yeah we can just remove features you paid for”

     This is the kind of stuff that makes people nervous about “Cloud” controlled products.    We will see how this ends up.

One thought on “Meraki goes iWAN, but retires a marketed feature.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s