Redefining Netflix BGP architecture#

Elise Vennegues, Netflix; Frederic Cuiller, Cisco

• Why: Real BGP architecture evolution at serious scale (20,000+ eBGP sessions, 2800+ peer ASNs, 400+ PoPs, ~175 countries) — the RR design questions and migration choreography are transferable even if the chosen platform is not.
• What: Netflix's replacement of a full iBGP mesh across edge switches, aggregation routers, and PEs with a route-reflector architecture, including the option analysis (traditional router vs VNF appliance vs integrated UCS M7 appliance), production scale figures (e.g., NA region: 38M IPv4 / 9M IPv6 paths, 300+ clients), a phased migration (staging → pilot prefixes → per-device deprefer/raise → remove the mesh), and OpenConfig YANG-based BGP telemetry with BMP activation planned.
• How: Validation via an early-field-trial process with Cisco; lessons include: cross-functional projects take longer than planned, and the lab is necessary but production churn/scale is unique.
• Where applicable: Any large edge network with full-mesh iBGP pain. Caveat: this is an openly joint Netflix–Cisco presentation and the IOS XRv9000 UCS M7 appliance gets prominent placement — treat the product comparison table as vendor-tinged and extract the architecture methodology.