OneWAN Traffic Engineering: Unifying Inter-Datacenter and Internet Backbones
summary
Microsoft consolidates AS8075 and AS8074 into OneWAN, a SDN-controlled backbone that connects 60+ Azure regions and 190 PoPs and handles 10× the devices and routes Swan did. It uses site labels + node segment IDs for traffic steering, controller-created tunnels with weighted hashing and per-router agents for fast local repair, and small-TCAM backbone routers to avoid full Internet RIBs. Migration uses BlastShield slices and ITE moves traffic for congestion mitigation (70% egress, 95% peering), yielding measurable CapEx and OpEx savings.
AI-written summary · about
chapters (8)
- 0:00OneWAN Traffic Engineering intro
- 1:56From two WANs to OneWAN
- 4:51OneWAN architecture design
- 7:02Traffic steering in OneWAN
- 8:54Local repair and control
- 10:20Live migration challenges
- 10:40Internet traffic engineering
- 13:16OneWAN summary and benefits
related talks
16mOneWAN is better than two: Unifying a split WAN architecture
19mDecentralized cloud wide-area network traffic engineering with BLASTSHIELD
13mContracting Wide-area Network Topologies to Solve Flow Problems Quickly
13mEfficient Multi-WAN Transport for 5G with OTTER
17mMeta’s Network Journey to Enable AI
15mOffloading Cloud Network Services at Production Scale
32mIntelligent cloud networking: Create simplicity, remove complexity (PRT214)
17mAWS On Air ft. Cloud WAN & Direct Connect SiteLink