Skip to main content

OpenStack Live Migration Guidance Details SONiC EVPN-VXLAN EVPN Type-2 Flow

New guidance details how to run OpenStack live VM migration over EVPN-VXLAN using SONiC switches, focusing on MAC/IP mobility, anycast gateway consistency, and the EVPN control-plane updates needed to keep traffic forwarding correct across hosts. For enterprise IT and security teams, the deployment choices affect tenant reachability during planned compute moves.

Research Overview

The document frames live migration as a combined compute, virtual networking, and physical fabric requirement in EVPN-VXLAN networks, where Layer-2 behavior must remain consistent while a VM’s IP and gateway reachability are preserved. It emphasizes that SONiC switching and fabric behavior must maintain correct MAC/IP forwarding during host transitions to avoid packet loss.

It also outlines specific preconditions for migration in EVPN-VXLAN environments using SONiC leaf switches, then describes an operational flow for how migration traffic is expected to move through the network. Finally, it discusses an automated validation approach using a test framework for production readiness checks.

Key Findings

To keep migration transparent to applications, the guidance calls for consistent EVPN and VXLAN identifiers across source and destination compute nodes, including matching EVI and VNI participation and consistent VLAN-to-VNI mappings. It also requires anycast gateway consistency by advertising the same gateway IP and MAC address across leaf switches for the tenant subnet.

The document further specifies host-independent Layer-2 reachability through EVPN Type-2 (MAC/IP) route learning and mobility, with MAC/IP bindings moving from the source leaf to the destination leaf during migration. It adds that VTEP capabilities and underlay MTU sizing must support VXLAN overhead to prevent fragmentation or packet loss.

Technical Breakdown

The expected migration flow begins with Nova triggering live migration and pre-copying memory pages to the destination compute node, while Neutron prepares the destination port and OVS/OVN flows. On the destination host, a virtual interface is created and connected to the appropriate tenant VNI, and the destination leaf detects the VM MAC on the new server-facing port.

Next, the destination leaf executes an EVPN Type-2 MAC mobility event, advertising a BGP EVPN Type-2 update that maps MAC to the new leaf and new VTEP IP, while withdrawing the old MAC entry. The document states that convergence is typically sub-100 ms with modern BGP optimizations, followed by Neutron or OVS emitting Gratuitous ARP for IPv4 or unsolicited Neighbor Advertisement for IPv6 to refresh ARP/ND tables across other VMs, firewalls, load balancers, and network appliances.

After the refresh, VXLAN traffic is forwarded to the destination leaf’s VTEP, with the guidance stating that the VM’s network perspective does not involve a topology change. The flow concludes with source compute cleanup, EVPN withdrawing the old Type-2 route, and Nova completing the migration workflow.

Operational Impact and Validation Approach

The document includes a mapping between VMware vMotion constructs and OpenStack equivalents, pairing vMotion with Nova live migration, Storage vMotion with block migration, and vCenter with the OpenStack controller, with ESXi mapped to KVM. This mapping is positioned to help teams relate operational behavior in VMware-style environments to OpenStack migration workflows.

For validation, it describes using Aviz Networks Fabric Test Automation Suite (FTAS), described as containerized and vendor-agnostic, to test SONiC network fabric readiness before deployment. FTAS test cases listed in the document cover basic live migration with shared storage, behavior under CPU and memory load, network continuity with ARP/ND refresh and no TCP session resets, concurrent live migrations, migration failure handling with clean abort and continued VM operation on the source, and fabric-level EVPN/VXLAN validation that checks MAC/IP movement to a new VTEP and prompt route withdrawal without traffic blackholing.

Overall, the guidance treats successful OpenStack live migration over EVPN-VXLAN as a coordinated requirement across Nova, Neutron with OVS/OVN, and a SONiC-based EVPN fabric, with attention to EVPN Type-2 route mobility, anycast gateway consistency, and control-plane convergence. Blog Signals brief is a fact-based summary of the vendor blog.