Re: bgp route advertisment , particularly aggregate/summary to

If additional interfaces & static routes are not allowed, you will need to
get those subnets into the BGP table via network statements or
redistribution. Use the 'summary-only' keyword with your aggregate-address
statement, and use route-maps to limit advertisement of that route to
particular neighbor[s]. If there are certain neighbors that should receive
the component subnets, then use unsupress-map.

-Yuri

On Sat, Mar 10, 2012 at 10:58 AM, Aaron <aaron1_at_gvtc.com> wrote:

> In a recent scenario I was using for my studies I was presented with the
> following..Please tell me how to do the following or link to where it is on
> doc cd.
>
>
>
> If R1 has in its igp table.
>
>
>
> 172.16.1.0/24
>
> 172.16.2.0/24
>
> 172.16.3.0/24
>
>
>
> And you need to send an aggregate of that as 172.0.0.0/8 to a IBGP
> neighbor
> how would you accomplish that? I don't think a static route is
> permissible.
> I don't think you can create additional interfaces on r1 either.
>
>
>
> If you can just verbalize to me a few ideas of how that is accomplished
> without some elaborate config then that's fine.like what are the moving
> parts?
>
>
>
> Is it possible to generate an aggregate based solely on the contents of the
> IGP table? I think I read that a subordinate part of a larger aggregate
> needs to be present in the igp table in order for the aggregate to be sent,
> but do I use "aggregate-address" ?....suppresmap? unsurprssmap? .neighbor
> statement to that certain neighbor?
>
>
>
> Aaron
>
>
> 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
Received on Sat Mar 10 2012 - 12:57:33 ART