From: Narbik Kocharians (narbikk@gmail.com)
Date: Mon Jun 02 2008 - 22:46:32 ART
Besides the *confederation*, here are some choices:
Let's say you have R1 in AS 100 and R2 in AS 200. R1 needs to advertise
network 1.0.0.0/8 to R2, but it does NOT want the routers in AS 200
advertise that route to any of their EBGP peers, R1 can accomplish this task
in two ways:
1. R1 can identify the network, in this case 1.0.0.0/8, then configure a
route-map and set the community to *no-export* and then send community and
the route-map to R2.
2. R1 can identify the network, in this case 1.0.0.0/8, then configure a
route-map and then set the community to *local-as* and then send the
community and the route-map to R2.
Now if R2 is advertising network 2.0.0.0/8 and it want that network to stay
local (meaning in its own AS) and NOT be advertised to any EBGP peer/s, R2
can be configured using one of the following:
1. R2 can be configured to advertise network (2.0.0.0/8) using a network
statement with a route-map, and the route-map just sets the community to *
local-as*.
2. R2 can be configured to advertise network (2.0.0.0/8) using a network
statement with a route-map, and the route-map just sets the community to *
no-export*.
On Mon, Jun 2, 2008 at 5:57 PM, John Jones <acer0001@gmail.com> wrote:
> After searching the DocCD, I have been unable to find out the difference
> between these, other than they are opposite logic. no-export means don't
> sent a BGP update out of the AS. local-AS means keep the update within the
> AS that the router is in.
>
> Is the difference when using confederations? I can see there the
> significance, but is this the only one?
>
> Thanks, guys.
>
> John Jones
> Networking, Linux & Storage Interconnect Trainer
> Dell Inc.
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
-- Narbik Kocharians CCSI#30832, CCIE# 12410 (R&S, SP, Security) www.Net-Workbooks.com Sr. Technical Instructor
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:20 ART