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.

Positive

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.

When you want to access cloud applications, or you want to have secure connectivity at a branch or hub location, it is quite useful. If you want to have a local breakout that is also possible. If you want to do a load balancing or even you can optimize the ISP to cost as well, you can do that. These are the benefits. We can even integrate security as well. This is an all-in-one box solution.

The product is very good. The information is accessible, and the integration is also easy.

It is stable.

The solution scales well.

It has a very good GUI.

The interface is straightforward. 

We find it very simple to deploy.

If a user needs documentation, it's readily available. 

I cannot speak to what areas need improvement. 

It's an expensive solution.

I've used the solution for one year. 

I find the solution to be stable and reliable. There are no bugs or glitches. It doesn't crash or freeze.

The solution is scalable. You can expand it as necessary.

It's a great option for enterprise-level organizations. 

We have multiple companies using the solution. They range from 500 to 1000 or so.

The response is pretty good. The solution they offer depends on a case-to-case basis, however, their turnaround time is pretty good.

The implementation process is pretty straightforward. 

The administration of the solution might need two or three people and they can work 24/7 to maintain it. Everything is remote. It's very easy to maintain. 

The pricing is quite high. There are other vendors that provide relatively low prices as compared to Cisco.

The cost depends on the number of devices and the application the customer is using. It is not a fixed price. It depends on the bundle. It varies on what application you wanted to use. 

There are other options available. Each OEM has its pros and cons. What is acceptable depends on the application use case. Cisco is positioned pretty well in the market as compared to its competitors.

I'm a consultant. We are Cisco resellers and partners.

For new users, a POC would be required so that they can understand whether it is fitting into their requirements or not. Implementation is not a big deal here. The deal is whether will serve its purpose or not.

I'd rate the solution eight out of ten.

We replaced all our legacy routers with Cisco SD-WAN. The number one use case is more to do with network management, better policy integration, and keeping the policies consistent across all our locations. That was one of the major areas where we thought SD-WAN has reduced a lot of burdens so that the engineer can focus on actual issues. 

We were doing a lot of policy-based routing earlier for our hub and spoke topology. With SD-WAN, the hub and spoke, of course, stays. However, manageability, scalability, and ROI are the three major factors with which it has helped a lot. 

We could eliminate most of our expensive MPLS links, move them, do the local internet breakouts, and integrate with the NGFW firewalls. These were an added benefit to us. It was a tectonic shift. Right now, we are not spending as much on resources or engineers to keep the lights on.

The integration, scalability, and ROI that Cisco SD-WAN provided are the main features that helped the organization advance further.

The solution has helped us to lower expenses.

The initial setup is quite straightforward. 

It is very stable. 

We can scale the solution. 

SD-WAN itself is vendor locked in. At one point, Cisco should make it open so that if we have multiple mergers and acquisitions happening, it's easier to consolidate. Right now, if we are running Cisco, and the other organization in an acquisition scenario is deploying some other competitive vendor, the communication, the manageability of running two separate ESD instances, becomes a burden that falls back on us, especially the network administrators. It's better to consolidate and come up with better products, especially targeting AWS as their underlying transport.

Traditionally, what Cisco has done, is they have always considered internet gateways or links and the MPLS links as their transport technology. In some devices, they have also used ELTs. Now, since we have 5G in place, they could look at private 5G ELTs, and they could expand that line, again, particularly in the ESD space since AWS has recently released their own SD instance where they are allowing their customers to backhaul.

With SD-WAN being a very custom solution and a vendor-specific solution,  we would end up having multiple software-defined instances where one is running in Cisco, and one you are running with AWS, and then again tomorrow, another SaaS-based player or a similar player will come up with something else. 

For example, when two organizations merge with each other, there is likely a scenario where organization X is running (for example) Juniper, and the other organization is running Cisco. The administrators would end up having to separate ESD controllers. You do not have a single ESD controller that is open in nature, where you can manage Cisco and Juniper devices. That is a concern. So if the controllers were made open, with compatibility between the vendors, that would be a very good thing for the industry overall.

As a market leader, they are better positioned to go ahead and make that kind of change. If you look at the history of Cisco, before MPLS came into the game, it was Cisco, Juniper, and a few other vendors who came together and created a very good protocol. 

We need them to start focusing on the SD-WAN compatibility with other environments and not being so vendor locked with Cisco environments.

They should get better controllers that can especially talk with AWS and Azure. Right now, I have taken a subscription with AWS Project Gateway. I will have to place a Cisco CSR image if I want to make it a true SD-WAN solution. Instead of using a separate image, if they could make the Cisco's controller open or a transit gateway solution, that would be ideal. 

I've used the solution since 2018. We've used it for around four years. 

We found the solution to be quite stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

We haven't seen major issues. 

The product is pretty scalable. 

In terms of Cisco SD-WAN, we have close to 200, and that's a pretty big number. We have about 12 engineers around the clock using the solution. 

For the SD-WAN portion, we are getting good support. We have no major concerns about the level of attention we get.

Positive

I did do a POC with VMware, and it was not great. We struggled with configurations. I've also done a POC with Aryaka and have used Fortinet and Palo Alto, as well as Viptela. 

The difference between Cisco and other options is that you get a good number of engineers. Second, the amount of time required to troubleshoot the protocol level is lower. I'm using the word protocol on the operating system that gets loaded and comes with the software. They don't even have a proper support line, and the support will not be aware of the production issues. The other competitors are three years away compared to where Cisco is today.

The solution is very straightforward and simple.

We did engage with Cisco during the initial POC and rollout. Later, with adequate materials and training materials, engineers, and resource availability, we never ran into challenges. 

When I speak with my other colleagues in other organizations where they did use Fortinet, they did use other products, they ended up spending a lot of labor hours and only figuring out that near the end after they struggle with configuration.

I'd rate the setup a four out of five in terms of ease of implementation.

From a maintenance perspective, it's not that frequent. Every quarter, the manufacturer releases its own patches and updates, which we are following through its life cycle. That's very normal. 

We handled the implementation ourselves. We did not need to worry about getting help from outside vendors. 

We have seen a positive ROI and a reduction in costs.

The price varies. They have different products, including routers, some of which are now being removed or deprecated. The new platforms with the CSR 8,000 series have competitive pricing, and the kind of features they're providing justifies the cost - especially when you look at the number of features and support that comes with it.

I'd rate the pricing at a four out of five in terms of its competitiveness.

We are a customer of Cisco.

I'd rate the solution seven out of ten. 

Cisco SD-WAN is predominantly used for the zero-touch deployment, centralized dashboards, and live monitoring of tunnels and the links. It's also used for software image management. 

This solution is deployed on the cloud. 

One of the most valuable features is that they have multiple SD-WAN options: you have Meraki for simple management solutions, you have Viptela, and you have the option of having any type of WAN interfaces. Presently, you can also have a single combined solution for both WAN as well as for voice, so you can have a voice bundle as well. These are major unique points of this solution. 

This solution could be improved with a simpler implementation process and licensing model. 

As for additional features, maybe from a security perspective, it could have more features built into the SD-WAN itself. Rather than going and integrating Cisco with some other solutions, it could have one single SD-WAN solution with more advanced user security features. 

I have been working with this solution for 15-20 years. 

The stability and performance of Cisco SD-WAN are really good. It's a reliable solution. 

This solution is easy to scale. 

Cisco has multiple options: it has Meraki SD-WAN, which is a simplified version. It can be suitable for any retail or small- to medium-sized customers. For large customers, we have Viptela, which is for customers who need more control on their traffic. This solution is suitable for any type of customer. 

I have contacted technical support, but it wasn't specifically about SD-WAN. Cisco's tech support is wonderful—they have a good support team and they have a Customer Experience team as well, where they completely focus on the customer environment. There are dedicated resources available for large customers, and the Customer Experience team supports customers from the same cycle, as well as implementation, so in that way, it's really good. 

The implementation process is complex because there are multiple touchpoints and initial configurations that we need to do in order to get the setup up and running. For example, opening a lot of firewall ports. Overall, it has multiple components to manage—there are multiple controller components where we need to do the configurations to get it up and part of the architecture. 

Compared to a few other OEM solutions, it's a bit complicated because there are multiple controller elements. For example, vBond: I have to do some specific configuration to it and need to have a public IP for it to be part of the architecture. Then we have vManage and vSmart—three, four components are there which have to be managed, which is why we have to do specific configurations for those. All the control elements can talk to each other, which is why it's a bit time consuming. Even in the cloud, you have to make some changes to your existing setup so that it can be part of the SD-WAN architecture. 

We implement this solution for customers. We are a Global Gold partner of Cisco, so we consult, design, implement, and provide support to customers. 

We're an SSP as well, so we also offer maintenance services. We can provide standard maintenance services of supporting only the hardware, or if a customer asks for full managed services, we can deploy our engineers either on the customer side or remotely. We have a NOC facility, from which we can provide remote support. 

The pricing is fair, and it's on par with the market vendors. But based on the competition, Cisco could work on the pricing, go deep on discounts and provide more commercially viable solutions to customers. 

Some similar SD-WAN products from different vendors are Silver Peak, Steelhead Riverbed, Fortinet, VMware, and VeloCloud. Frankly, I've only been working with Cisco, but Silver Peak seems to be good too—I heard that they're doing well in the market. Otherwise, I know about these products and have seen how they work in webinars and trainings, but I haven't really worked on any products apart from Cisco. 

I rate Cisco SD-WAN a ten out of ten. 

To those considering implementation, my advice would be to understand your current infrastructure better. What exactly is being implemented, currently, and what use cases are you looking at? Having a thorough understanding of the existing infrastructure would really help to decide which option to go with: either the Meraki SD-WAN or Viptela. Have a thorough understanding of how your infrastructure currently is, connectivity, how the architecture is, which applications you use, and which use cases you're looking at. These things are helpful to know before choosing and implementing a Cisco solution. 

We use the solution to interconnect the branch network.

Cisco's performance is very good. The branches that we installed went on smoothly. We operate with no complaints. When it comes to management, it's simple. One PIN will allow us visibility into everything. Another thing is troubleshooting; we can see the issues quickly, dig down, and know exactly what the issue is.

Since the new one comes with the included IPSec tool, we don't have any security issues. It's already covered because all the data is fully encrypted between the branch and the office.

Cisco provides visibility. We can see the performance of the branch. Troubleshooting is swift, allowing for fast turnaround times whenever we encounter an issue.

The user interface needs improvement. Users should be able to find various features faster without much tweaking.

I have been using Cisco SD-WAN since 2019.

The product is stable. We don't have any downside so far.

Cisco is very stable, whether a branch network or the branches. We don't have any issues with them.

Seven members of the team interact with the solution.

We haven't encountered any issues with scalability when adding more branches or refining the solution.

We interact with them whenever we need access to the services.

Positive

I have used SilverPeek. It is made for the end user, not for technical engineers. It is easy to deploy and has better visibility of how the network is performing than Cisco.

I have used both solutions. I have evaluated some other solutions. Technically, all the SD-WAN solutions work the same, so it depends on the organization. Cost is a factor. Cisco is on the higher side but is stable. There have been a few upgrades.

The initial setup is straightforward. Initially, it may seem a bit complex, but overall it is straightforward.

Deployment typically takes from four to six months to complete. Additional time may be needed, especially if issues with procuring hub routers were not included in the original plan. Developing the actual network implementation plan may take around six months. However, the actual migration process after that is quick. It usually takes less than three months to migrate the network fully.

We work with three guys from the internal team and four from vendors.

From a technical perspective, we used to experience failures, especially when using two service providers where data wouldn't come up if one link went down. We no longer encounter that issue. We're able to utilize both links simultaneously. Thus, we haven't faced the necessity of quick upgrades as we did when relying on a single link. Having one link operational at any given time was less elastic.

Cisco is expensive.

We need to renew the licensing after three years whenever updates are required. These licenses are valid for three years. There's no longer a need for routine physical maintenance of the devices, which is typical for network devices.

We initially faced some challenges with sizing and acquiring the necessary devices. We encountered some issues with missing hub routers. However, once we overcame those obstacles, we involved Cisco professional services. They assisted us in creating the low-level design and supported the initial site deployments. After that, we were able to proceed independently. Our corporate professional services team guided us through the process and helped us develop the design.

Overall, I rate the solution an eight out of ten.

I'm in Indonesia, where I use Cisco SD-WAN for DC and DRC to communicate with bank branches. One customer uses traditional simple routing via VGP or SPF to communicate to the head office data center or disaster recovery center. Still, I proposed using SDN technology, Cisco SD-WAN, to improve the application experience, have visibility to the provider link, and communicate directly from the branches to the application, such as Microsoft 365.

The customer also wants to access an application in the cloud from the branches, which requires a proxy, so the traffic goes to the data center and then to the cloud. You can directly connect all components to the cloud with Cisco SD-WAN, so I've implemented the product for the customer.

The primary use case for Cisco SD-WAN is direct internet access, including onboard security. Customers don't want just a simple routing. Customers also want a firewall and IPS feature from Cisco SD-WAN.

One of the benefits of Cisco SD-WAN is cost reduction for customers. In Indonesia, it's costly to use NPLS and Metro for connection, so I always propose using an internet link to communicate between branches to the data center or disaster recovery center. Cisco SD-WAN can provide that service; the product also keeps traffic secure. Some customers may be afraid to use the internet link or connection to communicate between the branches and the data center because of some critical applications, so it may not be the best practice for some customers.

However, as my company is a partner of Cisco, I give the customer the PLC first before providing the solution, and I have customers happy about what I propose, in this case, Cisco SD-WAN.

If a customer wants access to cloud-based collaboration apps, such as WebEx, Google Meet, Zoom, and Teams, Cisco SD-WAN can integrate with Cisco Umbrella for cloud security.

With Cisco SD-WAN, customers can enjoy cost reduction. Customers also don't need to use a third-party DNS or process security solution because Cisco SD-WAN integrates with Cisco Umbrella. This is how beneficial Cisco SD-WAN is to an organization or business.

The most valuable features of Cisco SD-WAN include the DIA and its integration with Cisco Umbrella for DNS security.

One area for improvement in Cisco SD-WAN is reporting. The report needs to give more visibility to the customer. For example, the report should provide API information. I have a customer who wants to integrate the application via API and wants a summary of the utilization, branch links, and all internet connections on Cisco SD-WAN. The product has a monitoring menu, but it's very simple and needs to be more detailed, so that could be improved.

The security feature in Cisco SD-WAN also needs improvement, particularly if Cisco wants to challenge other brands, such as Fortinet. Fortinet has a firewall layer with an IPS feature, plus it can also run SD-WAN within the same box or device, while Cisco SD-WAN has a limited firewall and IPS feature, which could be improved.

In the next release, I also want to see more flexibility in the product when integrating with other infrastructure or monitoring solutions.

My experience with Cisco SD-WAN is around two to three years. Just last week, I implemented Cisco SD-WAN for one of my customers.

I found the stability of Cisco SD-WAN good enough.

Cisco SD-WAN has good scalability, so I'm giving its scalability an eight out of ten.

I'd rate the Cisco SD-WAN technical support team as seven out of ten because my company had difficulty getting the best engineer for a partner and a customer.

Neutral

Some customers need more detail about Cisco SD-WAN, so it takes a long discussion before the product is implemented, but for a customer that knows Cisco SD-WAN, at least how it works, signing up for it and implementing it takes three to six months. Sometimes, completing the deployment of Cisco SD-WAN takes one year if the customer requirement is complicated and challenging.

For simple routing, Cisco SD-WAN is easy to set up. It's an eight out of ten. If you're setting up the product with some security features, then the setup would be more complex, and that's a three out of ten for me.

The last time I deployed Cisco SD-WAN, mainly for three hundred to four hundred cases, the deployment took six months to one year.

I deployed the product for a bank, so the deployment and maintenance should not disrupt the production, which means it takes more time to migrate the current connection or the current infrastructure to Cisco SD-WAN because my team also needs to build the data center and the RC, and then migrate the traditional link with Cisco SD-WAN, and refresh the router at the branches. For three hundred to four hundred cases, that required many field engineers, about fifteen engineers. The bank also had project and implementation teams, but I have no idea how many people made up the teams.

I implemented Cisco SD-WAN with fifteen engineers, plus implementation and project teams from the bank.

The ROI from Cisco SD-WAN is good for me, so it's an eight out of ten.

The pricing for Cisco SD-WAN is more expensive than other brands or solutions, such as Fortinet and Palo Alto Networks, so it's one out of ten.

Cisco SD-WAN also doesn't have flexibility using bandwidth tiering licenses, while Palo Alto Networks and Fortinet have more flexibility with the licensing.

One customer is on a three-year subscription, while another chose a different type of subscription and tiering license. Customers only pay for the standard licensing fees.

I'm a pre-sales engineer, but only for Cisco products, such as Cisco DNA Center, Cisco SDI, Cisco SD-WAN, and other Cisco technologies.

I implemented the latest version of Cisco SD-WAN for a customer.

I deployed Cisco SD-WAN on the public cloud for customers, but I'm unsure if it runs on AWS, Google, or Azure cloud.

Cisco SD-WAN requires two types of maintenance, on-call and onsite. Three engineers handle onsite maintenance during office hours—two from 8:00 AM to 5:00 PM and one from 5:00 AM to 11:00 PM. There's a second or backup engineer on standby that handles troubleshooting for the customer.

In each bank, Cisco SD-WAN has many users. Based on how many panels or bandwidth each bank uses, I'd say one bank already has two thousand to two thousand five hundred.

My rating for Cisco SD-WAN is eight out of ten. Despite needing some improvements, the product is already good for both customers and partners and is competitive enough.

My company is a gold partner of Cisco.

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. 

My client wants to use SD-WAN to reduce their line costs. By using SD-WAN, they aim to lower transport costs and better use internet traffic and bandwidth.

Clients use SD-WAN, which encapsulates the packet into a VPN tunnel. This allows them to be ready. In SD-WAN, the internet line is generally much cheaper than other lines. For example, they can use DIA to access internet traffic. With strong encryption, such as TLS or IPsec, they can securely send business traffic over the internet at a lower cost.

It depends on the customer’s requirements. In our area, Taiwan, we help users build SD-WAN. They are only using SD-WAN for transport. They want multitasking and QR code functions enabled.

Customers collaborate with ISPs and currently work with three ISPs, using options like LSM VPN and MPLS VPN to reduce line costs. They are considering moving from their current setup to an MPLS VPN and might also consider using a DIA line for internet access. However, due to government regulations and audits of internet access, they are cautious about using an internet line. They are still deciding which bank should be the first to implement this change.

If I want to improve the SD-WAN in the future, they might consider integrating it with technologies like SignalR and SRv6 into the SD-WAN control plane. This would enhance functionality, such as SRv6 video capabilities. They can simply use an SD-WAN solution based on SRv6.

I have been using Cisco SD-WAN for one year.

I rate the solution's stability as eight out of ten.

It is scalable. 8200 users are using this solution.

I rate the solution's scalability an eight out of ten.

Our banking customers trust Cisco. I work for a company that serves these banking clients, and we provide Cisco's CX service to help them build their SD-WAN solution. They purchase the product and the associated service, and the Cisco team assists with the deployment, making the process straightforward. It takes a couple of hours to deploy completely.

The product is expensive.

I recommend the solution.

Overall, I rate the solution as five out of ten.