CCDE Enterprise Case Study Part 18 – Best SD-WAN Branch Design for Jacobs Stores
As Jacobs continues its enterprise WAN modernization journey, one of the most important architectural decisions involves the physical and logical branch design for stores transitioning from traditional MPLS to hybrid SD-WAN.
This question focuses on selecting the best branch topology that balances:
- High availability
- Operational simplicity
- WAN resiliency
- Traffic engineering
- Migration simplicity
- Security policy compliance
- Scalability
🎯 Correct Answer
Option C is the optimal SD-WAN branch design.
It provides:
- Resilient dual-router architecture
- Separation of transport circuits
- Efficient traffic forwarding
- Proper VRRP implementation
- Simplified WAN migration
- Optimal traffic flow
Table of Contents
- 1. Enterprise SD-WAN Migration Overview
- 2. Jacobs WAN Requirements
- 3. Why Option C Is Correct
- 4. Traffic Flow Analysis
- 5. VRRP Design Deep Dive
- 6. Branch Resiliency Design
- 7. MPLS and DIA Hybrid WAN
- 8. 5G WAN Integration
- 9. SD-WAN Design Mathematics
- 10. Configuration Examples
- 11. Why Other Answers Are Wrong
- 12. AI and Analytics in SD-WAN
- 13. Related Articles
1. Enterprise SD-WAN Migration Overview
Jacobs currently operates:
- Dual MPLS circuits in Jacobs stores
- Traditional CE router architecture
- VRRP gateway redundancy
- Static routing toward MPLS providers
The enterprise now wants to evolve toward:
$$ Hybrid\\ WAN $$using:
- One MPLS circuit
- One DIA Internet circuit
- SD-WAN overlays
- 5G backup connectivity
Hybrid WAN Formula
$$ WAN = MPLS + DIA + LTE/5G $$This allows:
- Cost reduction
- Better SaaS performance
- Cloud optimization
- Dynamic path selection
- Improved resiliency
2. Jacobs WAN Requirements
Several critical design constraints exist:
| Requirement | Impact |
|---|---|
| Maintain resiliency | Requires redundant WAN architecture |
| Preserve VRRP design | Gateway continuity needed |
| Use SD-WAN overlays | Application-aware routing required |
| Minimize operational complexity | Simplified branch topology preferred |
| Use integrated security | Edge router security stack required |
| Support 5G | Wireless backup transport needed |
3. Why Option C Is Correct
Option C provides:
- Dual edge routers
- Transport separation
- Direct forwarding path
- Optimal traffic flow
- WAN resiliency
- Scalable migration model
Key Architectural Principle
Each SD-WAN edge router directly connects to:
- One transport medium
- One access switch
This creates:
- Predictable forwarding
- Reduced complexity
- Cleaner failover logic
4. Traffic Flow Analysis
Correct Traffic Flow in Option C
LAN → VRRP Gateway → SD-WAN Edge → WAN Transport
This is extremely important.
Traffic should not:
LAN → SD-WAN → LAN → MPLS Router
because this creates:
- Tromboning
- Ping-pong forwarding
- Extra latency
- Additional congestion
💡 What Is Tromboning?
Tromboning occurs when traffic unnecessarily traverses:
- extra interfaces
- extra VLANs
- extra routers
before reaching its destination.
This increases:
$$ Latency + CPU + Congestion $$Why Option B Is Suboptimal
Option B introduces:
LAN → SD-WAN → LAN → MPLS CE
This creates:
- inefficient forwarding
- unnecessary switching
- additional operational complexity
5. VRRP Design Deep Dive
Jacobs already uses:
$$ VRRP $$within stores.
This is preserved in the SD-WAN migration.
VRRP Purpose
- Gateway redundancy
- Automatic failover
- High availability
- Default gateway continuity
Availability Formula
$$ Availability = \frac{Uptime}{Total\\ Time} \times 100 $$VRRP Flow
Store Devices
↓
VRRP Virtual IP
↓
Active SD-WAN Edge
↓
WAN Transport
VRRP Failure Scenario
Example Failover Process
- Primary MPLS transport fails
- VRRP priority decreases
- Secondary edge becomes active
- Traffic reroutes toward Internet/5G
6. Branch Resiliency Design
Option C provides:
| Component | Resiliency |
|---|---|
| WAN | MPLS + DIA |
| Access Layer | Dual switches |
| Routing | VRRP redundancy |
| Wireless Backup | 5G integration |
| Traffic Steering | Application-aware SD-WAN |
Resiliency Equation
$$ Enterprise\\ Resiliency = Transport\\ Diversity + Device\\ Redundancy + Path\\ Intelligence $$7. MPLS and DIA Hybrid WAN
The design intelligently combines:
- MPLS reliability
- Internet scalability
- SD-WAN intelligence
Why Keep One MPLS Circuit?
- Predictable latency
- SLA guarantees
- QoS support
- Voice prioritization
Why Add DIA?
- Cheaper bandwidth
- SaaS optimization
- Cloud access
- Internet breakout
Cost Optimization Formula
$$ Hybrid\\ WAN = Reduced\\ MPLS\\ Cost + Internet\\ Scalability $$8. 5G WAN Integration
One major modernization feature is:
$$ Integrated\\ 5G $$inside SD-WAN edge routers.
Benefits
- Rapid branch deployment
- Backup transport
- Emergency failover
- Temporary connectivity
5G Use Cases
| Scenario | 5G Benefit |
|---|---|
| MPLS outage | Instant failover |
| Store opening | Rapid deployment |
| DIA failure | Wireless continuity |
| Construction delay | Temporary WAN access |
9. SD-WAN Design Mathematics
Path Selection Logic
$$ Best\\ Path = Latency + Loss + Jitter + Policy $$WAN Availability
$$ Availability = 1 - (Failure_1 \times Failure_2) $$Traffic Engineering
$$ Optimal\\ Routing = Application\\ SLA + Link\\ Health $$Operational Complexity
$$ Complexity \propto Devices \times Manual\\ Processes $$10. Configuration Examples
VRRP Configuration Example
interface vlan 100 vrrp 10 ip 10.10.10.1 vrrp 10 priority 110 vrrp 10 preempt
SD-WAN Tunnel Interface
interface Tunnel0 tunnel source GigabitEthernet0/0 tunnel mode ipsec ipv4
Application-Aware Routing
policy
app-route-policy VOICE
sequence 10
match application voip
action accept
set preferred-color mpls
5G Backup Configuration
interface Cellular0/1/0 ip address negotiated dialer in-band
11. Why Other Answers Are Wrong
Why Option A Is Incorrect
Option A fails because:
- No EtherChannel support
- Duplicate VLAN/interface problem
- Improper subnet assignment
💡 Important Layer 2 Rule
A physical interface cannot belong to:
- the same VLAN
- the same subnet
across multiple standalone links without:
$$ EtherChannel $$Why Option B Is Suboptimal
Traffic trombones through the LAN.
This creates:
- unnecessary forwarding
- extra switching load
- increased latency
Why Option D Is Incorrect
Option D introduces:
$$ Single\\ Point\\ of\\ Failure $$because only one SD-WAN edge router exists.
12. AI and Analytics in SD-WAN
Modern SD-WAN increasingly uses:
- Machine learning
- Anomaly detection
- Predictive analytics
- Intent-based automation
to optimize:
- traffic engineering
- application steering
- capacity planning
- failure prediction
Useful Machine Learning Articles
- Time Series Forecasting for Network Analytics
- Data Quality for AI-Based Operations
- Stationary vs Nonstationary Traffic Analysis
13. Related Articles
CCDE Enterprise Case Study Series
- Part 1 – Enterprise Architecture
- Part 8 – SD-WAN Transformation
- Part 11 – Self-Managed SD-WAN
- Part 12 – SD-WAN Planes
- Part 13 – WAN Design
- Part 14 – Internet Design
- Part 15 – 5G and DIA
- Part 16 – Toolmate Integration
- Part 17 – Building the SD-WAN Strategy
- Part 19 : CCDE SD-WAN Routing Loop Prevention Explained | OMP, OSPF Down Bit, EIGRP & BGP SoO
CCIE and Enterprise Networking Articles
Final Conclusion
Option C is the best SD-WAN branch design because it provides:
- transport separation
- clean traffic forwarding
- VRRP resiliency
- scalable migration
- reduced operational complexity
- optimal WAN utilization
The architecture aligns perfectly with modern enterprise WAN principles:
$$ Resiliency + Application\\ Awareness + Transport\\ Diversity + Operational\\ Simplicity $$which are essential for Jacobs as it modernizes hundreds of retail branches toward a hybrid SD-WAN future.
No comments:
Post a Comment