The first part that we like is that we can reuse certain hardware, which is a valuable asset. You can use hardware SKUs that already exist in the network.
The second part that we like is the integration with the cloud and the measurement of the cloud's quality. These are the two values that this solution gives as compared to other implementations that we have seen.
Its license model needs to be improved. They always make the license model too complex. There are too many license models and too many options. They should have a flexible license model.
They can improve a lot of things in terms of scalability, templates, and automation, mainly automation for onboarding a number of sites.
If you want some new features, it can take quite a long time. If you want a feature and it is not yet developed, you need to have the support of the business units to have the feature developed. If the feature is not on their roadmap, it can take quite some time before you get the feature.
I have been using this solution for about a year.
Its stability is fine if you stay within certain releases. From the stability point of view of the releases, it is fine.
We don't have deployments that have more than 500 sites. That's our biggest deployment from one customer. I cannot say anything for huge deployments because we do not have a lot of metrics.
Their technical support is good. They know what they are talking about, and you can see that they are experienced in their product.
It is easy to set up for small deployments. If you go for larger deployments, you hit some limitations in the GUI, and it could be more complex. This is because not all features that we assumed to be available are available in the GUI. For example, you know there are some features in the traditional MPLS router, but these features are not available when you run the same hardware on Cisco SD-WAN.
In small deployments, you don't see such an issue. In larger deployments, such as data center setups, you see some limitations popping up. Some features that we had in traditional routing are not available in Cisco SD-WAN. Bootstrapping is okay, but you are limited to the serial number. A limitation is that you need to link the serial number and the bootstrap process, which depends on the model. If you are used to working with a serial number, it is fine, but if you are not, it can be more difficult.
The license model is too complex with too many flavors and options. You might not be able to see it from an end user's point of view, but from a telco point of view, their license model is too complex. They should have a flexible license model. If you want to have good pricing, you need to buy it for a two-year, four-year, or five-year license immediately. Some other vendors have much more flexible license models.
I would rate Cisco SD-WAN a seven out of ten.