--- title: Use BGP Route Reflectors « BGP Labs | daily.dev description: A hands-on lab exercise covering BGP Route Reflectors (RFC 4456) as a scalable alternative to full-mesh IBGP. Using a six-router leaf-and-spine topology,... canonical: https://daily.dev/posts/use-bgp-route-reflectors-bgp-labs-5nfvuehsd twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Use BGP Route Reflectors « BGP Labs | daily.dev og:description: A hands-on lab exercise covering BGP Route Reflectors (RFC 4456) as a scalable alternative to full-mesh IBGP. Using a six-router leaf-and-spine topology,... og:url: https://daily.dev/posts/use-bgp-route-reflectors-bgp-labs-5nfvuehsd og:image: https://api.daily.dev/og/posts/5NfvuEHsd.png og:image:alt: Use BGP Route Reflectors « BGP Labs 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. # Use BGP Route Reflectors « BGP Labs **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 9 min read · 0 upvotes · 0 comments ## Summary A hands-on lab exercise covering BGP Route Reflectors (RFC 4456) as a scalable alternative to full-mesh IBGP. Using a six-router leaf-and-spine topology, learners remove leaf-to-leaf IBGP sessions, configure spine routers as route reflector clients using the `neighbor route-reflector-client` command, and verify that reflected routes carry ORIGINATOR_ID and CLUSTER_LIST attributes. Multiple topology options (6-router, 4-router) are available, and automated validation is supported with FRRouting and Arista EOS. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why do BGP route reflectors add ORIGINATOR_ID and CLUSTER_LIST attributes to reflected routes? BGP route reflectors add ORIGINATOR_ID and CLUSTER_LIST attributes to enable intra-AS routing loop detection. The original BGP protocol (RFC 4271) had no mechanism to detect loops within an autonomous system because AS_PATH only works between ASes. RFC 4456 introduced these attributes so that a router receiving a reflected route can detect if it originated the route or if it has already passed through a given cluster. _Engineers building scalable IBGP topologies track BGP attribute behavior and RFC details on daily.dev._ ### What happens to IBGP route visibility when I remove leaf-to-leaf IBGP sessions without configuring route reflectors? Removing leaf-to-leaf IBGP sessions without configuring route reflectors causes each leaf router to lose visibility of all other leaf prefixes. A leaf router retains only its own locally originated prefix in its BGP table. Connectivity between leaf routers is restored only after spine routers are configured as route reflectors using the `neighbor route-reflector-client` command. _Network engineers restructuring IBGP topologies find practical lab walkthroughs like this on daily.dev._ ## Similar posts on daily.dev - [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 --- Tags: [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/use-bgp-route-reflectors-bgp-labs-5nfvuehsd) ```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":"Use BGP Route Reflectors « BGP Labs","url":"https://daily.dev/posts/use-bgp-route-reflectors-bgp-labs-5nfvuehsd","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/use-bgp-route-reflectors-bgp-labs-5nfvuehsd"},"datePublished":"2026-08-11T08:55:17.137Z","dateModified":"2026-08-11T09:23:58.408Z","description":"A hands-on lab exercise covering BGP Route Reflectors (RFC 4456) as a scalable alternative to full-mesh IBGP. Using a six-router leaf-and-spine topology,...","image":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","thumbnailUrl":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","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/use-bgp-route-reflectors-bgp-labs-5nfvuehsd","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT9M"} {"@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":"Use BGP Route Reflectors « BGP Labs"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/use-bgp-route-reflectors-bgp-labs-5nfvuehsd#faq","mainEntity":[{"@type":"Question","name":"Why do BGP route reflectors add ORIGINATOR_ID and CLUSTER_LIST attributes to reflected routes?","acceptedAnswer":{"@type":"Answer","text":"BGP route reflectors add ORIGINATOR_ID and CLUSTER_LIST attributes to enable intra-AS routing loop detection. The original BGP protocol (RFC 4271) had no mechanism to detect loops within an autonomous system because AS_PATH only works between ASes. RFC 4456 introduced these attributes so that a router receiving a reflected route can detect if it originated the route or if it has already passed through a given cluster. Engineers building scalable IBGP topologies track BGP attribute behavior and RFC details on daily.dev."}},{"@type":"Question","name":"What happens to IBGP route visibility when I remove leaf-to-leaf IBGP sessions without configuring route reflectors?","acceptedAnswer":{"@type":"Answer","text":"Removing leaf-to-leaf IBGP sessions without configuring route reflectors causes each leaf router to lose visibility of all other leaf prefixes. A leaf router retains only its own locally originated prefix in its BGP table. Connectivity between leaf routers is restored only after spine routers are configured as route reflectors using the `neighbor route-reflector-client` command. Network engineers restructuring IBGP topologies find practical lab walkthroughs like this on daily.dev."}}]} ```