At 08:26 PM 4/5/2003 +0000, Salvatore De Luca wrote: >I have to agree that it is a bit silly, dangerous, and should not be done on >a production enviornment.. but so are a lot of scenarios on the CCIE Lab.. >Just to add to the sillyness:
Because it is silly and dangerous, you also can't do it without creating an entirely fresh route with the same nlri and conditionally advertising it somehow. You simply are not supposed to muck with AS-PATH elements unless you are aggregating, it which case you follow the defined guidelines. >Not sure how this would work, but you can try it.. have you tried as-path >manupulation? From what I can see you want to remove as 1 from the path as >R3 see's it. This config may work for what you are looking to do. You can >try applying this to the config aggregating the 150.50.200.0 network. I >think AS2 would have to originate the 150.50.200.0 net. > > >router bgp 3 >neighbor x.x.x.x route-map as-path in > > >route-map as-path permit 10 >match as-path 1 >route-map as-path permit 20 >match as-path 2 > > ip as-path access-list 1 permit _2_ & ! _2_ _1$ > ip as-path access-list 2 permit .* > >Sal Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=66938&t=66928 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
