From: CCIE To Be (ccie.tobe81@gmail.com)
Date: Mon Jan 12 2009 - 18:27:58 ARST
Got it....
Other question is related to local-as community. Let suppose we don't want
to advertise a specific prefix outside 'AS 10' then we will have again same
option of no-export. What about using local-as community in this scenario
which will not allow a particular prefix to go out of local AS 10 ??
On Tue, Jan 13, 2009 at 12:01 AM, Huan Pham <pnhuan@yahoo.com> wrote:
> No-export of course!
>
> Using no-advertise will prevent prefixes received from AS10 to be
> advertized to R3 iBGP peers as well which are undesirable here.
>
> Sent from my iPhone
>
> On 13/01/2009, at 6:28 AM, CCIE To Be <ccie.tobe81@gmail.com> wrote:
>
> Dear Group,
>
> I have a confusion regarding usage of no-advertise and no-export
> communities. I know that no-advertise means NOT TO ADVERTISE to any bgp
> peer
> ( iBGP & eBGP ) whereas no-export says NOT TO ADVERTISE to any eBGP peer
> means don't advertise outside this AS. Consider the following topology,
>
> R1(AS 10) --------R2(AS 10)------------R3(AS 30)
>
> Let say AS 10 is advertising a prefix to AS 30 and requirement is that AS
> 30
> should not forward this prefix further to any other AS. Now we have option
> to use either no-advertise or no-export on R2 towards R3. Both will give
> the
> desired result , what should be the recommended approach here ??
>
>
> HTH
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:43:37 ARST