[j-nsp] Announcing aggregate route via BGP to peers

[Peter Van Oene]

Hi John,

I'm not exactly sure what the issue is, but if you just want to leak a
single aggregate route, just use a static route.  I very rarely use
the "aggregate" route facility unless I really want dynamic
aggregates.  Most times, a static one (pointed to discard) works well.

Pete


On Tue, Mar 3, 2009 at 8:44 AM, John Center <john.center at villanova.edu> wrote:
> Hi,
>
> I'm having a problem announcing a local aggregate route to BGP peers.  I
> only want to announce the aggregate route defined in the routing-options:
>
> routing-options {
>   ...
>    aggregate {
>        route 153.104.0.0/16 discard;
>    }
>   ...
> }
>
> policy-statement BGP-ANNOUNCE {
>    term AGGREGATE {
>        from protocol aggregate;
>        then accept;
>    }
>    term ELSE-REJECT {
>        then reject;
>    }
> }
>
> What's happening is by specifying the aggregate route this way, it is
> appears to be announcing the aggregate of all the ebgp routes it sees:
>
> admin at KC-JNM120-1a> show route protocol aggregate
>
> inet.0: 277655 destinations, 559869 routes (277481 active, 0 holddown, 337
> hidden)
> @ = Routing Use Only, # = Forwarding Use Only
> + = Active Route, - = Last Active, * = Both
>
> 153.104.0.0/16     *[Aggregate/130] 18w6d 00:22:28
>                      Discard
>
> inet.1: 116 destinations, 116 routes (116 active, 0 holddown, 0 hidden)
>
> inet.2: 5194 destinations, 5195 routes (5192 active, 0 holddown, 2 hidden)
>
> inet.4: 3516 destinations, 4180 routes (3512 active, 0 holddown, 4 hidden)
>
> __juniper_private1__.inet.0: 12 destinations, 14 routes (7 active, 0
> holddown, 5 hidden)
>
> __juniper_private2__.inet.0: 1 destinations, 1 routes (0 active, 0 holddown,
> 1 hidden)
>
> inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
>
> __juniper_private1__.inet6.0: 5 destinations, 7 routes (5 active, 0
> holddown, 0 hidden)
>
>
> I tried to modify the BGP-ANNOUNCE policy by specifying the null AS:
>
> policy-statement BGP-ANNOUNCE {
>    term AGGREGATE {
>        from {
>            protocol aggregate;
>            as-path LOCAL-AS;
>        }
>        then accept;
>    }
>    term ELSE-REJECT {
>        then reject;
>    }
> }
> as-path LOCAL-AS "()";
>
> But, the ebgp routes were still being announced, with a next hop of SELF.
>  I'm at a loss on the best way to approach this problem.  I only want to
> announce the locally-defined aggregate, not all of the others.
>
> Any help would be greatly appreciated.
>
>    -John
>
>
> --
> John Center
> Villanova University
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>