Hello Con, 1&2. Prepeding appends the AS before your own AS. In this case, some routes come from AS 125, so if you prepend 1 to that the AS path would 678 1 125 instead of 678 125 1.
3. Hmmm....looks like an oversight! Should be adding community 1:1. Let me know if you have any other questions. On Sat, Jul 25, 2009 at 10:56 AM, Con Spathas <[email protected]>wrote: > Gday All, > > So the requirement is that we need to configure eBGP between R6 (vrf > VPNA) and BB_CE1 and ultimately get some comms between VPNA and VPNB. > No dramas there. > The bit that's confusing me is the config the Proctor Guide performs > on R1 to set the origin to EGP AS1 as it redistributes VPNB OSPF > routes into BGP. > > A couple of questions I'm hoping someone can shed some light on please: > > 1. Why is it needed? Performing prepend (AS 1) at R6 for all > advertisements outbound to BB_CE1 seems to do the trick. > 2. If it is needed - then can someone please explain why and also why > the config is only needed on R1 and not R8 as well? > 3. The requirement was that BB_CE1 also expects the routes to carry > community 1:1 - whilst I set this on my route-map on R6 towards BB_CE1 > - there's nothing in the Proctor Guide. I take it this is just an > oversight? > > Cheers, > Con. > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > -- Bryan Bartik CCIE #23707 (R&S), CCNP Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
