The SD-WAN Implementation Playbook
A field-tested methodology for migrating from MPLS to SD-WAN without breaking the network.
60% of SD-WAN projects face delays not because of technology, but because of poor planning. You are replacing the central nervous system of your company. This is not a "rack and stack" project; it is an architectural transformation.
Phase 1: Discovery & Audit (Weeks 1-4)
You cannot route what you do not know. Before you buy a single box, you need a "Source of Truth."
The Circuit Inventory
Build a master spreadsheet containing:
- Circuit ID: The carrier reference number (e.g., DHEC-12345).
- Media Type: Fiber, Coax, DSL, LTE, MPLS.
- Bandwidth: Up/Down speeds.
- Static IP info: Gateway, Subnet Mask, DNS.
- Contract End Date: Crucial for timing MPLS disconnects.
Application Mapping
Identify your "Top 10" apps. SD-WAN needs to know what to prioritize.
- Real-time: VoIP, Zoom, Teams (Needs Low Jitter).
- Transactional: SAP, Oracle, POS (Needs Low Loss).
- Bulk: Backup, OS Updates, YouTube (Needs High Bandwidth).
Phase 2: The Proof of Concept (POC) (Weeks 5-8)
Never believe the datasheet. Test the solution in your lab or a non-critical site.
Success Criteria
| Test Case | Procedure | Success Criteria |
|---|---|---|
| Brownout | Introduce 2% packet loss on Link A. | Voice call must not drop. |
| Blackout | Physically pull the cable on Link A. | Failover < 1 second. Session persists. |
| Steering | Saturate Link A with file transfer. | Critical apps move to Link B automatically. |
Phase 3: Design & Architecture (Weeks 9-12)
This is where the engineering happens. You must define the templates.
Topology Choices
- Hub-and-Spoke: All traffic goes to a Data Center/Cloud Hub. Best for centralized security.
- Full Mesh: Every site talks to every site. Best for VoIP reliability, but consumes more tunnels.
- Partial Mesh: Regional hubs.
The Overlay IP Schema
SD-WAN creates a virtual network on top of the physical one. You need a new subnet strategy (e.g., 10.200.x.x/24 for Loopbacks) to manage the overlay interfaces.
Phase 4: Pilot Deployment (Weeks 13-16)
Select 3-5 "Friendly User" sites. These should be low-risk branches where the local manager is sympathetic to IT.
Goal: Validate the "Gold Configuration" template. If you find a bug here, you fix it once. If you find it in mass rollout, you fix it 500 times.
Phase 5: Mass Rollout (ZTP)
This is the industrial assembly line. You should aim to deploy 5-10 sites per night.
Zero Touch Provisioning (ZTP) Workflow
- Ship: Box is shipped directly to site (no pre-staging).
- Plug: Site contact plugs WAN 1 into Internet.
- Call Home: Box reaches out to the Controller Cloud.
- Auth: Box presents its Serial Number; Controller validates.
- Config: Controller pushes the full config template.
- Up: Site is online in < 15 minutes.
Common Pitfalls to Avoid
Asymmetric Routing
If you keep MPLS parallel to SD-WAN, firewalls often block return traffic coming back on a different interface. Ensure you use proper tagging or flow symmetry checks.
MTU Mismatches
SD-WAN adds headers (IPsec + VXLAN/Geneve). This increases packet size. If your underlying ISP doesn't support 1500 bytes + overhead, you will get fragmentation. Adjust MSS Clamping to 1350 bytes.
Ready to Build?
Implementation is complex. Don't go it alone if you don't have to.