--- title: Multivendor EVPN Just Works « ipSpace.net blog | daily.dev description: The netlab 1.9.0 release included 36 hours of integration tests covering 15 VXLAN/EVPN scenarios across multiple vendors. Tests covered bridging,... canonical: https://daily.dev/posts/multivendor-evpn-just-works-ipspace-net-blog-ncdcnd4rl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Multivendor EVPN Just Works « ipSpace.net blog | daily.dev og:description: The netlab 1.9.0 release included 36 hours of integration tests covering 15 VXLAN/EVPN scenarios across multiple vendors. Tests covered bridging,... og:url: https://daily.dev/posts/multivendor-evpn-just-works-ipspace-net-blog-ncdcnd4rl og:image: https://api.daily.dev/og/posts/NCdcND4rL.png og:image:alt: Multivendor EVPN Just Works « ipSpace.net blog og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Multivendor EVPN Just Works « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 3 min read · 0 upvotes · 0 comments ## Summary The netlab 1.9.0 release included 36 hours of integration tests covering 15 VXLAN/EVPN scenarios across multiple vendors. Tests covered bridging, asymmetric/symmetric IRB, Layer-3 VPNs, and all major BGP design patterns (IBGP+OSPF, EBGP-only, IBGP-over-EBGP, EBGP-over-EBGP). Using FRRouting containers as the baseline alongside publicly available vendor images, nearly everything worked out of the box. Only three notable caveats were found: an ArubaCX quirk with Linux VXLAN driver interop, an FRRouting OSPF MTU bug over VXLAN, and centralized VXLAN-to-VXLAN routing issues on SR Linux. All tests and configurations are open-source and reproducible. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What caveats were found during multivendor EVPN/VXLAN interoperability testing with FRRouting? Three caveats emerged: an ArubaCX quirk (likely from software-based packet forwarding) prevented interoperability with the Linux VXLAN driver as a VXLAN-to-VXLAN router; a FRRouting OSPF daemon bug causes incorrect MTU in OSPF hello packets sent over VXLAN segments; and centralized VXLAN-to-VXLAN routing failed on SR Linux, possibly due to a configuration issue. _Network engineers validating EVPN designs across vendors track findings like these on daily.dev._ ### What EVPN BGP design patterns were covered in the netlab 1.9.0 integration tests? The netlab 1.9.0 integration tests covered IBGP+OSPF, EBGP-only (including reusing BGP AS numbers on leaves), EBGP over unnumbered interface BGP sessions, IBGP-over-EBGP, and EBGP-over-EBGP. Tests also included asymmetric IRB, symmetric IRB, central routing, Layer-3-only VPN with OSPF and BGP between PE and CE routers, and bridging multiple VLANs. _Teams choosing between EVPN BGP design patterns for their fabric find real-world test data like this on daily.dev._ ## Similar posts on daily.dev - [EVPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/evpn-with-sr-mpls-core-ipspace-net-blog-taobtibzc) · ipSpace.net Blog · 0 upvotes · 0 comments - [Multivendor SR-MPLS « ipSpace.net blog](https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/multivendor-evpn-just-works-ipspace-net-blog-ncdcnd4rl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Multivendor EVPN Just Works « ipSpace.net blog","url":"https://daily.dev/posts/multivendor-evpn-just-works-ipspace-net-blog-ncdcnd4rl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/multivendor-evpn-just-works-ipspace-net-blog-ncdcnd4rl"},"datePublished":"2026-08-11T08:51:50.498Z","dateModified":"2026-08-11T08:53:50.724Z","description":"The netlab 1.9.0 release included 36 hours of integration tests covering 15 VXLAN/EVPN scenarios across multiple vendors. Tests covered bridging,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/db631b6f72b5e6fdead6b7358dd2456e?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/db631b6f72b5e6fdead6b7358dd2456e?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/multivendor-evpn-just-works-ipspace-net-blog-ncdcnd4rl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"Multivendor EVPN Just Works « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/multivendor-evpn-just-works-ipspace-net-blog-ncdcnd4rl#faq","mainEntity":[{"@type":"Question","name":"What caveats were found during multivendor EVPN/VXLAN interoperability testing with FRRouting?","acceptedAnswer":{"@type":"Answer","text":"Three caveats emerged: an ArubaCX quirk (likely from software-based packet forwarding) prevented interoperability with the Linux VXLAN driver as a VXLAN-to-VXLAN router; a FRRouting OSPF daemon bug causes incorrect MTU in OSPF hello packets sent over VXLAN segments; and centralized VXLAN-to-VXLAN routing failed on SR Linux, possibly due to a configuration issue. Network engineers validating EVPN designs across vendors track findings like these on daily.dev."}},{"@type":"Question","name":"What EVPN BGP design patterns were covered in the netlab 1.9.0 integration tests?","acceptedAnswer":{"@type":"Answer","text":"The netlab 1.9.0 integration tests covered IBGP+OSPF, EBGP-only (including reusing BGP AS numbers on leaves), EBGP over unnumbered interface BGP sessions, IBGP-over-EBGP, and EBGP-over-EBGP. Tests also included asymmetric IRB, symmetric IRB, central routing, Layer-3-only VPN with OSPF and BGP between PE and CE routers, and bridging multiple VLANs. Teams choosing between EVPN BGP design patterns for their fabric find real-world test data like this on daily.dev."}}]} ```