WANworX by Ecessa vs. HPE Aruba Networking EdgeConnect SD-WAN

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).

Incentivized

• Fairly easy to manage once its setup and running
• Updates are easy and handled with little downtime
• Price is just right for the product functionality

Incentivized

• Ran into some weird bugs along the way that required support to address
• Not having physical devices that you can reboot yourself takes a bit of control away
• Administrators have a bit of a learning curve in figuring out the new system

Incentivized

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

Incentivized

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.

Incentivized

• It has created a bit of overhead as another control panel that needs to be managed
• Recovery of invested costs will take some time
• Time is saved on the separate management of sites

Incentivized