Network & Infrastructure / EVPN, VXLAN & Data Center Fabrics
Rolling fabric upgrades and EVPN feature compatibility
A rolling upgrade creates intermittent failures only when traffic crosses leaves running different software releases. Successful BGP sessions can mask differences in supported EVPN attributes or forwarding behavior.
Environment and inputs: BGP EVPN overlays on a routed underlay; supported route types and multihoming behavior depend on the network OS. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Inventory release combinations, enabled route types, multihoming features and known interoperability constraints. Compare received attributes and FIB state across old and new leaves for representative tenant flows.
Explain the result
Control-plane session compatibility is narrower than complete feature interoperability. A newly enabled capability may require every participating VTEP or border to understand its associated forwarding semantics.
Plan the fix
Follow the vendor-supported upgrade matrix and keep new features disabled until the required fabric population is ready. Prepare device-specific rollback and configuration compatibility checks.
Check the result and rollback
Test same-subnet, routed, BUM and multihomed traffic at every upgrade stage. Halt and restore the previous release if any required cross-version flow or failure scenario fails.