CCDE Enterprise Case Study Part 11 – Choosing the Right SD-WAN Operating Model
In this part of the CCDE enterprise architecture case study, we analyze one of the most important strategic decisions enterprises face during WAN transformation:
🎯 Should Jacobs choose a fully managed SD-WAN solution or a self-managed SD-WAN solution?
This question is not simply about technology.
It is fundamentally about:
- Operational agility
- Change velocity
- Application awareness
- Business responsiveness
- Control versus outsourcing
- Automation maturity
The Question
Which SD-WAN operating model would be most suitable for Jacobs?
Correct Answer
✅ Jacobs self-managed SD-WAN solution
Table of Contents
- 1. Understanding the Requirements
- 2. Fully Managed SD-WAN Analysis
- 3. Self-Managed SD-WAN Analysis
- 4. Application-Aware Routing Explained
- 5. Automation and Real-Time Policy Control
- 6. Hybrid WAN Architecture
- 7. Machine Learning and SD-WAN Analytics
- 8. SD-WAN Policy Examples
- 9. Managed vs Self-Managed Comparison
- 10. Architectural Takeaways
- 11. Related Articles
1. Understanding the Requirements
The question provides critical enterprise constraints:
We would have the option to steer our traffic over specific links on an application basis. This would be fundamental to us. We’d need the ability to do this effectively in real time without raising changes. Network changes are taking too long.
These statements immediately reveal:
- Operational bottlenecks
- Slow provider change processes
- Lack of agility
- Need for application-centric networking
💡 Key CCDE Insight
The business problem is not connectivity.
The real problem is:
$$ Operational\\ Inflexibility $$2. Fully Managed SD-WAN Analysis
A fully managed SD-WAN solution typically means:
- Provider controls orchestration
- Provider manages policy
- Provider provisions changes
- Provider handles monitoring
Advantages
| Benefit | Explanation |
|---|---|
| Lower operational burden | Provider handles daily operations |
| Centralized support | Single operational ownership |
| Faster deployment | Provider may accelerate rollout |
| Reduced staffing pressure | Less in-house expertise required |
The Major Problem
Jacobs specifically requires:
$$ Real\\text{-}Time\\ Policy\\ Changes $$A managed provider introduces:
- Ticketing delays
- Change approval delays
- Operational dependency
- Reduced flexibility
If approval delays increase:
$$ Agility \downarrow $$3. Self-Managed SD-WAN Analysis
A self-managed SD-WAN model gives Jacobs:
- Direct orchestration control
- Real-time application policy creation
- Dynamic traffic engineering
- Independent operational control
Why This Fits Jacobs
The business explicitly states:
Changes are taking too long.
This means:
$$ Operational\\ Speed $$is now a strategic requirement.
🎯 Enterprise Architecture Principle
When the network becomes application-driven, the enterprise requires:
$$ Policy\\ Agility $$Operational Benefits
- Rapid onboarding of new SaaS applications
- Real-time path steering
- Business-driven policy control
- Reduced provider dependency
4. Application-Aware Routing Explained
Traditional MPLS WANs are:
$$ Transport\\ Centric $$Modern SD-WAN architectures are:
$$ Application\\ Centric $$Traditional Routing Decision
Destination IP
Modern SD-WAN Decision
Application + SLA + Latency + Loss + Jitter
Application Path Selection Formula
$$ Best\\ Path = f(Latency, Jitter, Loss, SLA) $$For example:
- Office 365 may prefer Internet DIA
- VoIP may prefer MPLS
- Backup traffic may use broadband
Why Jacobs Needs This
Jacobs already suffers from:
- Latency-sensitive applications
- Cloud SaaS performance issues
- Operational delays
This makes application-aware routing:
$$ Mission\\ Critical $$5. Automation and Real-Time Policy Control
Modern enterprises increasingly depend on:
- Automation
- Intent-based networking
- Dynamic orchestration
- Programmability
Why This Matters
If every new application requires:
- Provider ticket
- Manual approval
- Maintenance window
then cloud agility collapses.
This is why self-managed SD-WAN aligns better with:
- SaaS growth
- Cloud migration
- Business agility
- DevOps operating models
6. Hybrid WAN Architecture
Jacobs also mentions:
We should definitely be moving toward some kind of hybrid WAN solution.
What Is Hybrid WAN?
Hybrid WAN combines:
- MPLS
- Broadband Internet
- LTE/5G
- Cloud connectivity
Benefits
| Benefit | Explanation |
|---|---|
| Cost optimization | Internet circuits reduce MPLS dependency |
| Cloud optimization | DIA improves SaaS performance |
| Resilience | Multiple transports available |
| Dynamic pathing | Traffic can shift automatically |
Related MPLS and SD-WAN concepts:
- Complete MPLS L3VPN Configuration Lab
- Complete MPLS QoS Configuration Lab
- Reliable BGP Peering Physical Connectivity
- Optimizing OSPF Timers for Faster Convergence
7. Machine Learning and SD-WAN Analytics
Modern SD-WAN platforms increasingly use:
- Machine learning
- Traffic analytics
- Anomaly detection
- Predictive path optimization
Relevant machine learning concepts:
- Time Series Forecasting Beginners Guide
- Stationary vs Nonstationary Data
- How to Evaluate and Ensure Your Data
- RandomizedSearchCV Beginners Guide
8. SD-WAN Policy Examples
Code Example – Application-Aware Routing
policy app-route OFFICE365
policy
app-route-policy OFFICE365
sequence 10
match application office365
action accept
set local-tloc-color biz-internet
Code Example – SLA-Based Path Steering
sla-class VOICE
sla-class VOICE latency 100 jitter 20 loss 1
Code Example – Dynamic Path Selection
vpn 10
vpn 10 omp advertise connected omp advertise static
Why Real-Time Policy Changes Matter
Modern enterprises onboard applications constantly.
If policy deployment requires provider approval:
- Cloud adoption slows
- Business projects delay
- Operational friction increases
Self-managed SD-WAN eliminates these bottlenecks.
9. Managed vs Self-Managed Comparison
| Feature | Managed SD-WAN | Self-Managed SD-WAN |
|---|---|---|
| Operational agility | Lower | Higher |
| Policy control | Provider controlled | Enterprise controlled |
| Application onboarding | Slower | Faster |
| Provider dependency | High | Low |
| Skill requirement | Lower | Higher |
| Business responsiveness | Lower | Higher |
10. Architectural Takeaways
✅ Correct Answer
Jacobs self-managed SD-WAN solution
Why This Is Correct
- Jacobs requires operational agility
- Application-aware routing is critical
- Real-time policy creation is required
- Provider delays are already a business issue
- Cloud and SaaS adoption require flexibility
Why Managed SD-WAN Is Suboptimal
- Additional change delays
- Provider dependency
- Reduced operational flexibility
- Slower onboarding of applications
11. Related Articles
CCDE Enterprise Case Study Series
- CCDE Enterprise Case Study Part 1 – Enterprise Architecture
- CCDE Enterprise Case Study Part 2 – Main Issues Facing Jacobs
- CCDE Enterprise Case Study Part 3 – Scalability and Management Overhead
- CCDE Enterprise Case Study Part 4 – MPLS Architecture
- CCDE Enterprise Case Study Part 5 – MPLS Operational Analysis
- CCDE Enterprise Case Study Part 6 – DMVPN Analysis
- CCDE Enterprise Case Study Part 7 – Enterprise Architecture Decisions
- CCDE Enterprise Case Study Part 8 – SD-WAN Transformation
- CCDE Enterprise Case Study Part 9 – SD-WAN Security
- CCDE Enterprise Case Study Part 10 – WAN Transformation
- Part 12 - CCDE SD-WAN Architecture Explained – Orchestration, Management, Control and Data Planes
Final Conclusion
This question highlights a major shift occurring in enterprise networking:
Modern WANs are no longer transport-centric.
They are:
$$ Application\\ Centric $$Jacobs requires:
- Real-time application steering
- Rapid policy deployment
- Reduced operational delay
- Cloud agility
A self-managed SD-WAN architecture provides:
- Operational flexibility
- Application-aware control
- Dynamic policy orchestration
- Faster business responsiveness
Therefore:
No comments:
Post a Comment