<br clear="all">+1<br><br><br><br>
<div class="gmail_quote">On Fri, Mar 4, 2011 at 10:58 AM, Andy Vance <span dir="ltr"><<a href="mailto:andy.vance@360.net">andy.vance@360.net</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div lang="EN-US" vlink="purple" link="blue" bgcolor="white">
<div>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt">I would utilize community tags to differentiate the routes and apply different behavior to them in my export policy.</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> </span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> entry 5</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> from</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> protocol bgp</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> community ebgp-community-tag</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> exit</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> action accept</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> next-hop-self</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> exit</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> exit</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> entry 10</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> from</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> protocol bgp</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> community ibgp-routes</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> exit</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> action accept</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> exit</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> exit</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> </span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt">Would that accomplish what you need?</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> </span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt">Cheers,</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt">Andy</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> </span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> </span></p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt">From:</span></b><span style="FONT-SIZE: 10pt"> <a href="mailto:alcatel-nsp-bounces@puck.nether.net" target="_blank">alcatel-nsp-bounces@puck.nether.net</a> [mailto:<a href="mailto:alcatel-nsp-bounces@puck.nether.net" target="_blank">alcatel-nsp-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Ben Robinson<br>
<b>Sent:</b> Thursday, March 03, 2011 10:35 PM<br><b>To:</b> Griego, Michael (Michael)
<div class="im"><br><b>Cc:</b> <a href="mailto:alcatel-nsp@puck.nether.net" target="_blank">alcatel-nsp@puck.nether.net</a><br></div>
<div>
<div></div>
<div class="h5"><b>Subject:</b> Re: [alcatel-nsp] 7750 Route Reflector Server Question</div></div></span>
<p></p></p></div></div>
<div>
<div></div>
<div class="h5">
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span>The goal is to collapse RR an ASBR functions into the same router. The solution I'm after would meet the best practice of keeping the route reflector out of the forwarding path while allowing the same router to pick up external peers. <br>
<br>Ben Robinson<br>Systems Engineer<br>LS Networks</span></p></div>
<p class="MsoNormal"><br><br>-----Original message-----</p>
<div>
<p style="MARGIN-BOTTOM: 12pt" class="MsoNormal"><b><span style="FONT-SIZE: 10.5pt">From: </span></b><span style="FONT-SIZE: 10.5pt">"Griego, Michael (Michael)" <<a href="mailto:michael.griego@alcatel-lucent.com" target="_blank">michael.griego@alcatel-lucent.com</a>><b><br>
To: </b>Ben Robinson <<a href="mailto:brobinson@lsnetworks.net" target="_blank">brobinson@lsnetworks.net</a>><b><br>Cc: </b>"<a href="mailto:alcatel-nsp@puck.nether.net" target="_blank">alcatel-nsp@puck.nether.net</a>" <<a href="mailto:alcatel-nsp@puck.nether.net" target="_blank">alcatel-nsp@puck.nether.net</a>><b><br>
Sent: </b>Fri, Mar 4, 2011 03:21:17 GMT+00:00<b><br>Subject: </b>Re: [alcatel-nsp] 7750 Route Reflector Server Question</span></p></div>
<div>
<div>
<div>
<p class="MsoNormal">Where is the placement of the route-reflector? If you place the route-reflector so that it is not the ebgp peering router (asbr) then all that is needed is to set next hop self on asbr and leave route reflector without next hop self. I thought best practice was to typically remove a route reflector from forwarding path. <br>
<br>Mike </p></div>
<div>
<p style="MARGIN-BOTTOM: 12pt" class="MsoNormal"><br>On Mar 3, 2011, at 5:28 PM, "Ben Robinson" <<a href="mailto:brobinson@lsnetworks.net" target="_blank">brobinson@lsnetworks.net</a>> wrote:</p></div>
<blockquote style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">Greetings,</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">I’m using route reflection on 7750-SR (8.0R7) and want to set next hop self for routes learned from external BGP peers, but not on routes learned from internal BGP peers. The goal is to reflect routes from internal peers, preserving the IGP next hop while setting next hop self on routes from external peers. Perhaps this is the default behavior.</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">I can set all routes to next hop self in the 7750 Peer/Group configuration and with a policy. Since I don’t want all routes advertised internally by the 7750 to have the next hop self set, I’m assuming that it is accomplished in a policy. </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">Firstly, does anyone know if this is the default behavior? Or, if possible, how to accomplish this with SROS policy.</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">The Juniper policy equivalent is:</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">term external {</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> from route-type external;</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> then {</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> next-hop self;</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> accept;</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> }</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">}</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">term internal {</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> from route-type internal;</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> then accept;</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">}</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">…</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">Policy nhs-ipv6:</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> Term external:</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> from route-type external</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> then nexthop self accept</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> Term internal:</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> from route-type internal</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> then accept</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">Thanks,</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">Ben Robinson</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">Systems Engineer</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">LS Networks, Inc.</span></p>
<p class="MsoNormal"> </p></div></div></blockquote>
<blockquote style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
<div>
<p class="MsoNormal">_______________________________________________<br>alcatel-nsp mailing list<br><a href="mailto:alcatel-nsp@puck.nether.net" target="_blank">alcatel-n </a></p></div></blockquote>
<p class="MsoNormal"> </p></div></div></div></div></div></div><br>_______________________________________________<br>alcatel-nsp mailing list<br><a href="mailto:alcatel-nsp@puck.nether.net">alcatel-nsp@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/alcatel-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/alcatel-nsp</a><br><br></blockquote></div><br>