Cisco Catalyst SD-WAN Reviews

We use this solution for banks in the private sector. They use it to connect their headquarters to multiple branches with the SQL connection. They previously used different technologies, like MPLS, so we offered Cisco SD-WAN and did the project using this technology.

We are a system integrator and Cisco partner and usually sell products to customers. So we have different use cases, not only in Cisco SD-WAN but for other products. So the use case often differs from customer to customer.

The availability of services and combining different connections is most valuable.

Cisco should pay attention to the software as we recently found some bugs. There should also be better integration with other third-party software for the SD-WAN.

There are some features I'd like to see in the next release, and we have them for the Cisco account manager. First, we would like a single sign-on to be supported on the SD-WAN. Integration with third-party applications, like Active Directory, is not available and is also very important. They should also enhance traffic monitoring.

We have been using Cisco SD-WAN for about a year but are not using the latest version. It is deployed on-premises.

It is a stable solution, and I rate the stability a nine out of ten.

I rate the scalability a nine out of ten, and we have approximately 150 users from different departments. We may increase our usage depending on customer and business needs.

The technical support is very responsive and helpful, and I rate them a ten out of ten.

We've used different technologies from different vendors. Some customers preferred the SD-WAN from Cisco, and some preferred other vendors.

I rate the initial setup an eight out of ten, and it is straightforward. The deployment time depends on the use case and the number of branches and connections. It could take two or even three weeks because you may have the migration from a new to an old system. First, we had to prepare for the deployment, vulnerability design and migration plan. We then had to migrate branches one by one and check the services. The deployment was also completed in-house, and one person can complete it.

Regarding price, it should be better than S3 to be more competitive than other vendors. I rate the price a seven out of ten, with ten as very high and one as low. The licensing is annual.

I rate the solution a nine out of ten and recommend it to others.

I work for a global telecom operator. I'm a system integrator. It's deployed on cloud and on-premises.

The most useful features will depend on the clients' requirements.

Cisco SD-WAN doesn't have automation capabilities, artificial intelligence, machine learning, and isn't IOT-based. There are a lot of technologies coming onto the market that Cisco SD-WAN doesn't have. I would like to see AI-driven capabilities.

It should be more cloud-based and compatible with all the clouds.

I have used Cisco SD-WAN for seven years.

Sometimes there are issues on the routing layers. Most of the time, the protocols don't meet the compliance standards. If one site is Cisco and another site is Juniper, then there is a mismatch in the protocols, so there is latency. If all the sites are Cisco, then it's stable.

I would rate the stability as six out of ten.

The scalability is good. I would rate it as seven out of ten.

I would rate technical support as eight out of ten. They're responsive, but many of the people I speak to don't have a lot of technical knowledge.

For new telecom companies that have a 5G or 4G setup, there are other service providers that they can contact.

Initial setup is easy. I would rate setup as seven out of ten. 

It depends on the sites, the connectivity, and how many tunnels there are between various planes, like the control plane and management plane.

The cost is reasonable. I would rate the price as seven out of ten.

Huawei has their own cloud, and they don't have any dependencies. The best part is that there isn't a lot of tactic latency. Cisco doesn't have that kind of feature. Huawei is more advanced compared to Cisco.

I would rate this solution as seven out of ten.

The most valuable feature of Cisco SD-WAN is its compatibility and integration with the rest of the infrastructure.

Cisco SD-WAN could improve on the ease of integration, the configuration should be easier. At the moment the process is more command line based and it would be better if it was able to be done through an interface.

In a feature release, Cisco SD-WAN could add more features for wireless SaaS-based solutions.

I have been using Cisco SD-WAN for approximately two years.

Cisco SD-WAN is stable.

The scalability of Cisco SD-WAN is good.

The support sometimes is delayed. They could improve their response times. They are knowledgeable about the solution but you have to reach the correct person.

I rate the support from Cisco SD-WAN a three out of five.

Neutral

The initial setup of Cisco SD-WAN is not overly complex, but there should be a good understanding of the configuration and setup. There are many technical commands for the process that one should be aware of.

I rate the initial setup of Cisco SD-WAN a three out of four.

We used a third-party vendor help to implement the solution.

Overall, we are receiving a better financial cost advantage using Cisco SD-WAN than what we were using before.

I rate the ROI of Cisco SD-WAN a four out of five.

The price of Cisco SD-WAN could improve, it is expensive. The cost of the solution is approximately 30 percent higher than competitors.

I rate the price of Cisco SD-WAN a two out of five.

There are other competitors in the market that work well, such as Fortinet. The best solution is determined by its ability to handle a use case. There is not one overall best solution, there are suitable use cases for the different vendors.

If a customer is looking for a solution for a large enterprise, then I would recommend Cisco SD-WAN. However, if they have a small setup for a small business setup, Fortinet is better. It is integrated well with all the security features.

I rate Cisco SD-WAN an eight out of ten.

The integration to the LAN could be improved. It should be an end-to-end solution, not only on the WAN side but also on the LAN and wifi, so a full end-to-end solution.

The integration of Layer 3 and application routing is great.

The technical support is a bit slow. Regarding additional features, it would be good to have a fully integrated solution with the Meraki solution, leading to a seamless Cisco solution.

We have been using this solution for about six years. It is deployed on-premises, and we are using our own management.

The stability is good.

I think the scalability fits the customer requirements. The number of staff required for maintenance depends on the complexity of the network and the number of sites. A single part does not cover it, so we have about 20 staff running our network services.

I rate the technical support a seven out of ten. They are good but not very innovative, and the feature requests take too long to implement.

We use different solutions like Viptela, VeloCloud and Versa.

The initial setup was complex, and it was completed in-house.

I am unsure about licensing costs.

I rate this solution an eight out of ten.

Cisco SD-WAN is primarily used in the banking industry in Pakistan for bandwidth development and application control.

Cisco SD-WAN's best features are the development of network links, application control, and bandwidth monitoring.

Cisco SD-WAN's clustering mechanism needs to be improved. If there are more than five milliseconds of latency time between installations of the VM manager, the cluster automatically breaks down.

I've been using Cisco SD-WAN for a year.

Cisco SD-WAN is stable.

Cisco SD-WAN is very easy to scale.

Cisco's technical support is very good, and they're one of the few companies that provide local support. If we face any problem, they respond to and resolve it within three to four hours at most.

Positive

I previously used Forcepoint, but they have no local support, which means we had to wait much longer to get resolutions to our issues. Cisco's knowledge base was also better.

The initial setup wasn't easy, and I would rate the setup experience as two out of five.

In the first phase, our partner implemented the solution, but afterward, we managed it by ourselves.

For 600 links, the license for Cisco SD-WAN costs us US$250k a year. In Pakistan, we have the option to get this solution at a more discounted price.

I would give Cisco SD-WAN a rating of seven out of ten.

The load sharing in the fabric and the cloud connectivity are both pretty flexible. The solution offers us the correct field mechanisms.

The solution is stable and reliable.

It can scale according to our needs. 

While the environment itself is not a bottleneck, the dependencies and the provisioning and the different parties involved altogether form, complexity and introduce limitations.

The initial setup is really complex.

We've been using the solution for two years. 

The stability is really great. It's definitely reduced downtime. There are no bugs or glitches. It doesn't crash or freeze. 

For us, the solution scales well. We are far away from its limits. That said, we are not, let's say, a very big company.

Technical support has been good. They are helpful and responsive. 

We did not previously use a different solution. We had a fairly traditional wide area network without any sophisticated connection options.

The initial setup is not straightforward or simple. It's very complex. 

I'm not sure how many staff members are needed for deployment and maintenance. 

We did outsource the initial setup.

I'm on the technical side. I have no idea what the price is and don't deal directly with licensing. I do know that this is an all-in deal, meaning there aren't extra fees associated with the cost. 

We're basically an end-user interacting with Cisco on this, however, the final responsibility is with our ISP.

SD is an enterprise tool and you should not use an ISP for implementation. Better to use an NSP or do it yourself. 

I'd rate the solution nine out of ten.

We primarily use the solution for connectivity.

The connectivity is great.

The dashboard is excellent.

It's a scalable solution.

The product is stable. 

Technical support is very good. 

The solution is a bit complicated. They could work on simplifying the product. For example, doing configurations could be easier. 

The initial setup is tedious.

It was a bit expensive. They can improve their licensing model.

We'd like to see more monitoring features. 

They can improve in terms of their GUI. 

They can improve in terms of hardware.

I've been using the solution for five years. 

The solution is stable. There are no bugs or glitches. it doesn't crash or freeze. It's reliable.

The product is scalable. 

We have been satisfied with the technical support. They are great. There is always room for improvement, however, they're always resolving the issues

Positive

We also have experience with Meraki. The differences are licensing and pricing, however, the features are pretty much comparable.

The solution is difficult to set up. It's tedious. We'd like it to be easier. You really need to know a lot of stuff before initially trying to configure everything.

I'd rate the process a three out of five in terms of ease of use. 

It took us about two weeks to set up.

It's one of the more expensive solutions out there. I would rate it two out of five in terms of affordability. All you need to pay is the licensing fee. There are no extra costs. 

I'd rate the solution a six out of ten.

Some clients resist switching to new technology and they're also afraid of problems with compatibility and the layout of the NOC. The NOC must change because nowadays new things are happening, but I believe that the beauty of SD-WAN is the vEdge. So for the customers that are afraid of new technologies, we can install the vEdge without spending a lot of money. It's just a virtual machine over there. You can do it on Cisco CSR or even ISR.

So we deploy a new branch or similar branch with this technology and show them. Then they're not afraid of it. It's very easy. Now, vManage is coming. So we have the analytics team, we have all the GUI interfaces so you can create a policy and now deploy it anywhere or you can define it. I believe everything is very easy for the people who want to work with it. 

Technologies are not new. Just the name changes. VPN is the same as VRF, which is the same as Tenant, but the way they're playing with this technology is very different. The method of management is different. I believe that if I show clients what is happening with vManage— the interface, the analytics how you can integrate with them—they will be in love with that. Mostly what I have done is to define and elaborate for them the differences between two solutions, and point out the advantages like visibility and easy management. In the end, but they agree to move to SD-WAN

But I believe that most of the customers are still afraid of SD-WAN because they rely on old solutions. And the old solution was great and working for many years, so they are afraid of the new solution. With vEdge, we have a great way to attract them to make them feel comfortable upgrading everything into the Cisco SD-WAN.

The best feature is SD-WAN's automation capabilities. I believe many customers don't care whether we use VPN, or that use color or mGRE. When you're talking about management of, for example, a DMVPN solution or MDI solution, what is the option? So we have to go to a bug-by-bug report, like for example, NSRP to show these things. With vManage, we can see everything. We have a graph that we can click on and it helps us to remember better. 

Another good feature in the HCI is the integration of a health monitoring system. Other solutions like SDx are all the same. They have an integrated health monitoring system. So if you are deploying a data center, the options aren't really that great. But this integrated health system in HCI in vManage or even SD-WAN in the vManage is helping a lot. And also 

Customizing SD-WAN is very easy because you can define two colors. You can define two different operators. You can deploy a partial mesh, a full mesh, or hub-and-spoke totally differently. If you want to do this on a DMVPN solution, that's really hard. Also, things like Quality of Service in mGRE environment, in my opinion, are very hard because when you are dealing with mGRE, you have one tunnel at the hub and a different tunnel at the spoke. So what if I want to limit the traffic in my hub at the spoke? Because I have one tunnel, all the branches will be affected if I implement a limitation or restriction. So that's why we have advanced technology, like adaptive quality of service. With SD-WAN, the QoS is much easier because it is separate from the VPN.

The very beauty of SD-WAN is the separation of the plane. Right now, there are different planes. Compared to other solutions, the whole thing is totally changed. Rebound and vManage came into play as well as the new protocols like PnP. I started to convert most of the solutions from regular DMVPN into SD-WAN because we have the capability to define our VPN or define our color and customize by making a full or partial image. 

In the next release, Cisco should focus on simplifying the configuration of SD-WAN.  SD-WAN has a lot of room to grow. If you compare vEdge and something like Cisco CSR, you'll see the difference. Because vEdge is natively from Viptela, it is a little more complicated to set up an SD-WAN compared with an ISE device like CSR or ISR, or ISR 4000. You have now two different configuration spaces like iOS, and then some commands and styles are Viptela. So this is the thing that Cisco should work on. 

I've spent a lot of time on it. I started with version 17 when SD-WAN first came out. I continued using the product after Cisco acquired Viptela because I really love Cisco. I followed everything Cisco-related since I was 18 or 19. I got my CCNP in 2003 and my first CCA in 2011. So I spend all my time on Cisco systems. Right now, I have more than 32 certificates. I recently passed the CISSP. I also have more than 20 certificates that have expired, like Cisco Sales Expert, Cisco ASA, VPN, and several old things.

SD-WAN is 100 percent stable. If you use the suggested operating system, all the Cisco solutions are stable. According to the Gartner Magic Quadrant rating, I believe Cisco was No. 1 three years ago. Now it is No. 2 or 3, so I believe that they could improve more.
And many customers have used DMVPN or VPN solutions for many years, so those solutions are also extremely stable.

it is very easy to deploy the whole solution. I have a customer with VoIP and data. For most of the data, the hub and spoke are enough, but for IP telephony or collaboration like chatting or video conference, they need to have a connection between spokes —between branches together — but not for data. With SD-WAN it's very easy. 

I think vEdge is much easier to work with when you compare it to Cisco CSR. Most of the people I know prefer to use ZTP or Zero Touch Provisioning, but it depends on the type of customer. With some customers, ZTP maybe is not the best solution. They should know what's going on. And if you try to configure SD-WAN on a solution like ISR 4000 or CSR, and you compare the same thing on vEdge, you will see that the vEdge is very straightforward. I believe in CSR and ISR 4000. There are some glitches. It's possible that you will get a little bit confused, but you have followed the instruction. You have to do it very carefully. Then you make the connection vManage and everything is done.

I would rate Cisco SD-WAN seven out of 10.