The Road to EVPN: Automated Service Migrations#

Luke Gollan, Megaport

• Why: Migrating a live global network to EVPN with automated service cutover is squarely in the PM's EVPN/BGP and interconnect territory, and this covers the whole arc: architecture, config rollout, then customer service migration with minimal disruption.
• What: Megaport's end-to-end story of automated EVPN deployment across a global telco network, from design through rollout to migrating production services, plus customer/support-facing migration tooling.
• How: Object-driven database generating device configs; NETCONF operations to configure, log, and track changes; diversity zones to contain blast radius; APIs and message queuing to trigger migrations; explicit phased migration steps with rehearsed rollback; tooling to track network changes and keep business stakeholders informed. (From abstract only — no usable source text.)
• Where applicable: Megaport-specific (global NaaS/telco topology, dense service inventory), but the checklist — rehearsed rollback, diversity zones, event-driven migration triggers, stakeholder-visible risk — is a transferable migration methodology for any EVPN or fabric migration.