"Local-AS" if viewed in a Confederation point of view
tells the BGP router to keep this community info within
this "local"(confed) Local-AS, and not to an IBGP peer
that does not belong to my "local" confederation peer ID.

The "no-export" pertains to EBGP peer.
This got me confused too until I realised that you can have
a "local" Local-AS in a confederation.

HTH,
Elmer
Note: if it's still fuzzy, check Confedration example by Halabi on CCO's
BGP4 Case Studies.

----- Original Message -----
From: "Hunt Lee" 
To: 
Sent: Wednesday, February 13, 2002 9:01 PM
Subject: Re: set community no-export V.S. set community local-as [7:35355]


> 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
>
>
> ""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=35365&t=35365
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to