>John, > >So isn't that Local-AS means can only send routes within the local AS, while >no-export means only advertised to IBGP peers (which means advertised to >only local AS).. so aren't they the same thing - I'm still very confused. > >Best Regards, >Hunt Lee >WebCentral
local-AS is used in conjunction with confederations. It keeps announcements inside one of the confederation AS. If you used no-export, all the confederation AS would see the update, but nothing outside the registered AS. There's a subtle distinction between true eBGP and confederation AS to confederation AS eBGP. > > >""John Neiberger"" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... >> From reading an FAQ on CCO: >> >> Community Description >> >> Local-AS: Use in confederation scenarios to prevent sending >> packets outside the local autonomous system (AS). >> >> no-export: Do not advertise to external BGP (eBGP) peers. Keep >> this route within an AS. >> >> no-advertise: Do not advertise this route to any peer, internal >> or external. >> >> none: Apply no community attribute when you want to clear the >> communities associated with a route. >> >> internet: Advertise this route to the internet community, and >> any router that belongs to it. >> >> HTH, >> John >> >> >> ________________________________________________ >> Get your own "800" number >> Voicemail, fax, email, and a lot more >> http://www.ureach.com/reg/tag >> >> >> ---- On Sun, 10 Feb 2002, Cebuano ([EMAIL PROTECTED]) wrote: >> >> > Aren't these two acvhieving the same purpose? Please tell me >> what i'm >> > missing. >> > Thanks. >> > >> > Elmer >> > >> > In the following example, routes that pass the autonomous >> system path >> > access >> > list 1 have the community set to 109. >> > Routes that pass the autonomous system path access list 2 >> have the >> > community >> > set to no-export (these routes >> > will not be advertised to any external BGP [eBGP] peers). >> > >> > route-map set_community 10 permit >> > match as-path 1 >> > set community 109 >> > >> > route-map set_community 20 permit >> > match as-path 2 >> > set community no-export >> > >> > >> > In the following similar example, routes that pass the >> autonomous system >> > path >> > access list 1 have the community >> > set to 109. Routes that pass the autonomous system path >> access list 2 >> > have >> > the >> > community set to local-as >> > (the router will not advertise this route to an eBGP peer >> outside the >> > local >> > autonomous system. >> > >> > route-map set_community 10 permit >> > match as-path 1 >> > set community 109 >> > >> > route-map set_community 20 permit >> > match as-path 2 >> > set community local-as >> [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=35372&t=35372 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
