Cisco Meraki SD-WAN is a cloud-managed solution that simplifies and secures wide area networking across branch, campus, and remote locations. Built on Meraki’s dashboard, it delivers centralized visibility, automation, and traffic optimization without the complexity of traditional WAN deployments. The solution improves application performance by dynamically routing traffic based on real-time conditions, integrating advanced security, and providing seamless multicloud connectivity. With support…
N/A
HPE Aruba Networking EdgeConnect SD-WAN
Score 8.0 out of 10
N/A
The HPE Aruba Networking EdgeConnect SD-WAN platform addresses the challenges associated with backhauling cloud-destined traffic to the data center, thereby reducing the cost of bandwidth connectivity from the data center to cloud providers.
At our level, we had to optimize our 3 internet links (MPLS and LTE) with applications like O365, SAP, Microsoft CRM Dynamics and our collaborative work tools like Teams. We also had to ensure that both client workstations and servers could communicate with minimal latency with our Microsoft Intune infrastructure.
Have remote sites and need them to feel local? Want to get all your locations virtually on the same network? This is the way. And if you're like us and need an easy way to manage all your remote locations in one place this is the tool you want to use.
AutoVPN sites to site firewall rules needs to be improved
there is no logging or any insights which would be able to tell you what are the hit counts or actual usage for site to site firewall rules
SD-WAN plus license includes Smart breakout which has only few applications and those do not work properly, so it is quite useless
VPN exclusions (local internet breakout) for TCP/UDP type of traffic can not be specified with port ranges
VPN exclusions (local internet breakout) can be defined only for destinations, but not the sources. It is policy based routing which should support also Source definition
Often there are alarms that are false positives due to bugs in the code - these are usually rectified in the next patch but that seems to be a common occurrence with updates
Can only have 7 "BIOs" - which are effectively policies that you use to choose how traffic is handled in terms of routing and QoS
Devices throughput is capped by Aruba licensing meaning that's an additional concern you'll have to monitor and take into consideration when choosing ISPs.
Alerts sometimes don't tell you things you'd like to know (like when a site is nearing its bandwidth cap)
We implemented Meraki in most of our organization sites, so we are always looking for ways of improving its usage, add more features and discover characteristics that we do not know we already have. As it is an easy to use tool and we are growing, hiring new employees, it is really simple to onboard the new joiners.
The product and its management as a whole are worth investigating for any kind of people interested in looking at new SD-WAN appliances. The devices possess a lot of capability for granularity which makes them much more advanced than other products I've worked with in the past. Ironically, for all the granularity though, this product is held back that you can ultimately only have 7 different policies for routing decisions. We've ran into instances where we wanted two sites to only share certain routes between each other (through the use of tags which are basically an arbitrary way to say this traffic is special) but then we had to collapse some of our routing decisions in order to make a specific route table for these two to be able which felt like a step back in the advanced routing decisions we had previously made
Fast and efficient. The only issue currently is that the support is only overseas support and not in South Africa, which causes delays in resolution for some cases. Escalating issues is quite simple and the opening of new cases from the dashboard is easy. I have never had a support issue that could not be resolved.
We did a very stringent valuation a few years ago. And we evaluated probably about a dozen suppliers on paper that we evaluate just by capabilities. And, we of some other business criteria, and we whittled that down to a list of five. And out of those five, we brought four of those into our lab environment where we ran approximately 350 different test cases on, we really beat on it pretty heavily. And some of those other suppliers would've been companies like Fortinet Versa Networks Silver Peak, which is now owned by Hewlett Packard.
Prisma SD-WAN is a very simple solution to configure and maintain (so much to the point that in that environment, I questioned if my skills as a Network Engineer were needed). However it worked almost primarily on its own with very little input, by default and at the time of review had no way to do fully mesh (which was desired), and constantly suffered from memory leak. Its integrations were through the use of obscure tags and suffered from a "when it works - it works but when it doesn't - it doesn't and you don't know why" mentality. In contrast, HPE Aruba Networking EdgeConnect SD-WAN gives you a lot of insight into what is going on with the site, the integrations are done easily within Orchestrator (the control plane), and ultimately the product is typically a very stable product with many ways to configure and tweak the solution to fit your business needs.
Being a cloud-first solution, Meraki Dashboard will scale as needed without any effort for the client. The Meraki cloud will provision (upscale and downscale) the resources as you grow or shrink in size. You only have to physically install the MX on your site, all the management is one through the Internet via Meraki Dashboard. Worth noting that you can fully-configure the MX prior to the physical installation on site.
It was mostly around logs. I mean I understand because the aim is to provide the simplified solution to the people as an end user, be it an IT manager or the oil team. So I understand where you don't have lots of tools assigned where you can actually take help from the track. But in terms of having that logging information, I think that's where it's been a bit of a kind of journey where struggling, we have been struggling there.
