This expert panel explores how SD-WAN has evolved from earlier WAN and MPLS models into a more flexible option for modern network environments. The discussion covers cost savings, performance, security, vendor complexity, and the planning required to build an SD-WAN strategy that fits real business needs.
Panelists from PTP and Avant share practical lessons from real deployments, including how organizations can reduce complexity, improve connectivity, and avoid common implementation mistakes.
Key takeaways
- SD-WAN emerged as a more flexible response to cloud-driven changes in networking.
- Organizations often adopt SD-WAN for cost savings, performance improvements, and simpler connectivity.
- Security decisions depend on existing infrastructure, vendor capabilities, and the organization’s risk profile.
- Some businesses still need MPLS or hybrid designs based on application and compliance needs.
- Successful SD-WAN deployments depend on planning, collaboration, and avoiding unnecessary complexity.
The Evolution of WAN and the Emergence of SD-WAN
The panelists began by discussing how wide area networking has changed over time. Mike McElaney from PTP reflected on the shift from older T1-based environments to MPLS and, more recently, to SD-WAN. Over that period, the cost of connectivity dropped significantly, while network design became more flexible and better suited to modern business demands.
John Hudson explained that MPLS once made more meshed network architectures possible, especially for voice and video traffic. But as more applications moved into the cloud, traditional closed-network models became less effective. That shift helped drive the rise of SD-WAN as organizations looked for more agile ways to connect users, locations, and cloud services.
Niko O’Hara from Avant added that the SD-WAN market has also become more crowded and more difficult to evaluate, with many vendors offering different approaches, capabilities, and security models.
The Value Proposition of SD-WAN
One of the strongest themes in the discussion was the value SD-WAN can deliver when it is aligned to real business requirements. The panel highlighted flexibility, cost savings, and improved network performance as the most common reasons organizations begin evaluating SD-WAN.
Mike shared a case study involving a business services organization with 280 locations. By replacing a secondary MPLS network with dedicated internet access, the company reduced monthly connectivity costs by nearly $250,000 while still maintaining reliable performance.
John emphasized that the right design depends on the business. Some organizations may need a more robust MPLS-based or hybrid model because of application, security, or compliance requirements, while others may be better served by the flexibility and lower cost profile of SD-WAN.
Security Considerations with SD-WAN
Security was a major part of the conversation. John noted that many SD-WAN solutions use IPsec encryption with PKI certificates to secure traffic, but that additional controls are often needed to address malware, inspection, and broader threat protection requirements.
Niko pointed out that SD-WAN vendors vary significantly in their security capabilities. Some include stronger built-in controls, while others are designed to work alongside third-party security platforms such as Palo Alto Networks or Zscaler.
The panel agreed that organizations need to understand their own security posture before selecting a design. Some businesses will want to extend an existing security architecture into the SD-WAN environment, while others may prefer a more integrated platform approach.
Lessons Learned and Avoiding Common Pitfalls
The panelists stressed that many SD-WAN challenges are not caused by the technology itself, but by poor planning. One of the most important lessons was the need to understand the business’s applications, priorities, and technical requirements before implementation begins.
Niko shared that organizations should identify the right reasons for moving to SD-WAN and avoid over-engineering the solution. In one example, a customer with high-bandwidth primary circuits and lower-bandwidth backup circuits did not need an active-active SD-WAN design. A simpler failover model was the better fit.
The panel also emphasized collaboration. Mike noted that SD-WAN projects require input from networking, IT, and security stakeholders, and that working with experienced partners can help organizations avoid common landmines during rollout.
Conclusion
The panel concluded that SD-WAN can deliver meaningful cost savings, stronger performance, and more flexibility when it is designed around real business needs. At the same time, security requirements, application behavior, and operational ownership all need to be considered carefully before making the transition.
Overall, the discussion provided practical insight into how organizations can evaluate SD-WAN more effectively, avoid common mistakes, and build a network strategy that supports modern business operations without unnecessary complexity.
Get more bandwidth and better uptime with NetOps expertise
Explore Cisco SD-WAN resources, then take a short survey to evaluate your current WAN environment and forecast future needs.
If you would rather have a direct conversation, reach out to Mike McElaney through PTP to discuss your network goals, current challenges, and whether SD-WAN is the right fit for your environment.