--- title: Multivendor SR-MPLS « ipSpace.net blog | daily.dev description: A hands-on lab demonstrates multi-vendor SR-MPLS interoperability using Arista EOS, FRRouting, and Nokia SR Linux as PE1, P, and PE2 respectively, built with... canonical: https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Multivendor SR-MPLS « ipSpace.net blog | daily.dev og:description: A hands-on lab demonstrates multi-vendor SR-MPLS interoperability using Arista EOS, FRRouting, and Nokia SR Linux as PE1, P, and PE2 respectively, built with... og:url: https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk og:image: https://api.daily.dev/og/posts/QEKokwdUk.png og:image:alt: Multivendor SR-MPLS « 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 SR-MPLS « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 3 min read · 0 upvotes · 0 comments ## Summary A hands-on lab demonstrates multi-vendor SR-MPLS interoperability using Arista EOS, FRRouting, and Nokia SR Linux as PE1, P, and PE2 respectively, built with netlab. It walks through differences in Segment Routing Global Block (SRGB) defaults across vendors, showing how prefix segments and MPLS LFIB label swapping work when each device uses its own default SRGB range. Includes the full lab topology configuration and instructions to reproduce the setup via GitHub Codespaces. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why do different vendors show different SRGB ranges in the same SR-MPLS network? Each vendor uses its own default Segment Routing Global Block size and starting label when the topology doesn't explicitly configure SRGB values. In one multivendor lab, Arista EOS defaulted to a 65536-size SRGB starting near 900000, FRRouting used an 8000-size block starting at 24000, and Nokia SR Linux used a 10000-size block starting at 16000, resulting in different labels for the same prefix SID across devices. _Compare vendor default behaviors like these before troubleshooting label mismatches in daily.dev's developer feed._ ### How does MPLS label swapping work across vendors with different SRGB values in segment routing? A router receiving traffic labeled with its own SRGB-derived value swaps it for the neighbor's SRGB-derived label for the same prefix SID before forwarding. For example, Arista EOS expecting label 900003 for a prefix advertised with SID 3 swaps it to 24003 when forwarding to a neighboring FRRouting device, which uses a different SRGB range for the same SID. _Track multivendor networking interop details like this while designing segment routing deployments on daily.dev._ ## Similar posts on daily.dev - [MPLS/VPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/mpls-vpn-with-sr-mpls-core-ipspace-net-blog-nw3uwiphe) · ipSpace.net Blog · 0 upvotes · 0 comments - [BGP-Free Core with SR-MPLS « ipSpace.net blog](https://daily.dev/posts/bgp-free-core-with-sr-mpls-ipspace-net-blog-h7kronzy3) · ipSpace.net Blog · 0 upvotes · 0 comments - [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 --- Tags: [#networking](https://daily.dev/tags/networking) [View this post on daily.dev](https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk) ```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 SR-MPLS « ipSpace.net blog","url":"https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk"},"datePublished":"2026-08-25T05:53:13.159Z","dateModified":"2026-08-25T05:53:33.934Z","description":"A hands-on lab demonstrates multi-vendor SR-MPLS interoperability using Arista EOS, FRRouting, and Nokia SR Linux as PE1, P, and PE2 respectively, built with...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","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-sr-mpls-ipspace-net-blog-qekokwduk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"networking","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 SR-MPLS « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk#faq","mainEntity":[{"@type":"Question","name":"Why do different vendors show different SRGB ranges in the same SR-MPLS network?","acceptedAnswer":{"@type":"Answer","text":"Each vendor uses its own default Segment Routing Global Block size and starting label when the topology doesn't explicitly configure SRGB values. In one multivendor lab, Arista EOS defaulted to a 65536-size SRGB starting near 900000, FRRouting used an 8000-size block starting at 24000, and Nokia SR Linux used a 10000-size block starting at 16000, resulting in different labels for the same prefix SID across devices. Compare vendor default behaviors like these before troubleshooting label mismatches in daily.dev's developer feed."}},{"@type":"Question","name":"How does MPLS label swapping work across vendors with different SRGB values in segment routing?","acceptedAnswer":{"@type":"Answer","text":"A router receiving traffic labeled with its own SRGB-derived value swaps it for the neighbor's SRGB-derived label for the same prefix SID before forwarding. For example, Arista EOS expecting label 900003 for a prefix advertised with SID 3 swaps it to 24003 when forwarding to a neighboring FRRouting device, which uses a different SRGB range for the same SID. Track multivendor networking interop details like this while designing segment routing deployments on daily.dev."}}]} ```