Software Defined WAN Deployment
June 18, 2019
Software Defined WAN Deployment
Score 6 out of 10
Vetted Review
Verified User
Overall Satisfaction with Cisco SD-WAN
In our SD-WAN deployment, we use application routing based on the DPI to utilize 2 MPLS and 1 Internet circuit to reduce cost and added redundancy and diversity of circuits. It is currently used throughout the whole organization for branch office locations. This solution addressed our single carrier issue with various outages which impacted our users in the past. Today, we are able to still function with a single circuit outage at our branch office locations. However, we are still running into issues with DPI application identification, performance issue with the current vEdge 2k platform, DHCP, and a critical bug which causes primary vEdge to halt packet forwarding due to a race condition that is unexplainable. Cisco TAC has escalated the issue to the highest level, however, we still have not received the fix for this problem.
Pros
- Creating an application routing policy to be applied throughout the environment is a breeze.
- Failover is very seamless and even during our DR scenario we were able to confidently failover voice traffic without end users noticing the issue.
- Single pane of glass via vManage is very useful for reporting.
Cons
- Visibility to the vManage cloud to govern what Cisco has access to would be nice to have.
- We are still running into issues with DPI application identification, performance issue with the current vEdge 2k platform, DHCP, and a critical bug which causes primary vEdge to halt packet forwarding due to a race condition that is unexplainable. Cisco TAC has escalated the issue to the highest level, however, we still have not received the fix for this problem.
- Enable WAAS functionality to be able to reduce the WAN utilization.
- Integration of FMC or CDO for firewall management functionality would be great.
- Global Manager to rule policies end-to-end would be great to have. SD-WAN and SD-Access single manager would be very helpful.
- Consolidate to a single application identifier (DPI/NBAR/AVC) to avoid any confusion and mapping issues.
- Reducing the MTTR post circuit outages have been a positive impact.
- Avoiding unnecessary impact to circuit outages also frees up our network engineers to innovate and work on projects that matters.
- Multiple unvetted platform issues have negatively impacted our company by extending the deployment time.
Comments
Please log in to join the conversation