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.
N/A
VMware SD-WAN
Score 8.4 out of 10
N/A
VMware SD-WAN (formerly VeloCloud) aims to deliver high-performance, reliable branch access to cloud services, private data centers, and SaaS-based enterprise applications. VeloCloud was acquired by VMware in 2018.
The HPE Aruba Networking EdgeConnect SD-WAN excel in environments where you do a lot of your East - West segmentation is done by another device. While these devices can do basic firewall functions, it's their not true intent. If you can group what you want your traffic to do into a few basic groups, this product will work great (think all Guest Traffic gets low priority and sent directly to the internet, VoIP gets sent directly out but high priority, and most internal traffic gets medium throughput). There are ways to really tinker reach the desired goals but this can be a double-edged sword of those configurations being forgotten about. There is also the use of templating which if you have a larger environment, this product will make some normal configs (think SNMP) more streamlined. The units are also highly reliable, built with HA in mind - our company has only experienced a single version that had a memory leak that we just needed to remember to reboot every 90 days while we waited for the next update (which came in like 4 months).
VMware SD WAN is a great solution for tying multiple locations together that are not physically located close. The link aggregation used in the technology allows for quicker failover to redundant connections, which makes the surface traffic seem to be uninterrupted. If planning to connect multiple locations while utilizing the existing internet, Veloclouds SDWAN provides stable and accurate aggregation of connections that provide a good sense of stability for the price.
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
VMware SD-WAN has great usability. We have had a positive experience with the solution. It has helped solved a number of issues with our network such as visibility in user usage, application usage, and prioritizing critical application network traffic. VMware SD-WAN user interface is also very easy to understand and configure.
There are still some glitches that need to be worked out. As an example, I rebooted a device at one of our branch locations and it just died. That should never have happened, and I've only seen this happen when a company needs to improve hardware on some of their lower-end models.
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.
At the time we made our decision to move forward with VeloCloud, Cisco Viptela and Cisco Meraki were the two players we compared against. Cisco's offerings were very customizable when using Viptela, but there was a big learning curve to implement. Meraki at the time was a lot simpler, but we needed the ability to customize some features in order to implement SD-WAN in our environment. VeloCloud was the perfect solution during our POC as it satisfied our needs.
Ease of deployment: the amount of time saved when adding additional sites to the solution, especially when you have a profile already built and when you add a new VC you just associate that profile with that appliance. Again, in a matter of minutes, you can have a new site up and running.
Since there is not true firewall built-in, you would have to either purchase a third-party firewall or the virtual firewall that is supported by Velocloud.
