[j-nsp] Aggregate and directly connected routes (route preference)

[Gary Tate]

On Jan 26, 2004, at 7:24 PM, Pedro Roque Marques wrote:

> robin at gyron.net (Robin Balen) writes:
>
>>
>>> You could advertise the aggregate if you really want to by using
>>> advertise-inactive option on the bgp group or neighbor that you wish
>>> the aggregate to be advertised on.  This is needed because as
>>> you have mentioned the aggregate will always be inactive in this
>>> configuration.
>>
>
> advertise-inactive only advertises inactive BGP routes. So it won't
> advertise an aggregate if it is inactive.
>
Indeed, sorry Robin for any confusion.  However,  you can still achieve 
what you want as stated bellow:

> But you can advertise the interface route when active and the
> aggregate when the interface goes down... all you need to do is accept
> that prefix indepedently of the originating protocol.
>
policy-options policy statement aggeregate {
    term send-agg-5 {
		from route-filter 5.5.5.0/24 exact
		then accept;
        }
    term send-agg-6 {
		from route-filter 6.6.6.0/24 exact
		then accept;
        }
	term reject-rest {
        then reject
	}
}

this is what we discussed earlier.

> A static discard will less preference will also do the job.
>
> Again, as Gary mentioned, the potential drawback is that you may be
> attracting traffic that is going to be droped while there may be an
> alternate route in the network, when advertising a discard route.
>
>   Pedro.
>