https://8bd9e53a.aww-3cz.pages.dev/tags/reflector/ Recent content in Reflector on Aaron's Worthless Words Hugo en Sat, 11 Jun 2011 00:00:00 +0000 https://8bd9e53a.aww-3cz.pages.dev/posts/2011/06/bgp-notes-route-reflectors/ Sat, 11 Jun 2011 00:00:00 +0000 https://8bd9e53a.aww-3cz.pages.dev/posts/2011/06/bgp-notes-route-reflectors/ <ul> <li>Route reflectors remove the requirement of having a full mesh iBGP network.</li> <li>Any iBGP route a router reflector learns is sent to all route reflector clients. <ul> <li>Non-client iBGP neighbors do not get the new route per iBGP rules.</li> </ul> </li> <li>RR clients are configured like normal iBGP routers. <ul> <li>All RR client config is done on the route reflector.</li> </ul> </li> <li>RRs and clients are part of a <em>cluster</em>. <ul> <li>RRs in each cluster must be neighbors with each other.</li> <li>Each cluster RR appends the cluster ID to the CLUSTER_ID PA; this is used similarly to AS_CONFED_SEQ.</li> </ul> </li> <li>The ORIGINATOR_ID PA is set by and preserved by the RR. <ul> <li>If a route contains the ORIGINATOR_ID of the receiving router, the update is ignored.</li> </ul> </li> <li>Only best routes are passed to RR clients and non-client neighbors.</li> </ul> <blockquote> <div class="highlight"><pre tabindex="0" class="chroma"><code data-lang="fallback"><span class="line"><span class="cl">router bgp 123 </span></span><span class="line"><span class="cl"> no synchronization </span></span><span class="line"><span class="cl"> bgp cluster-id 1 </span></span><span class="line"><span class="cl"> neighbor 6.6.6.6 remote-as 123 </span></span><span class="line"><span class="cl"> neighbor 6.6.6.6 route-reflector-client</span></span></code></pre></div></blockquote> <p>-&mdash;- Comment with corrections, please.</p>