[j-nsp] Route-aggregation

[Morgan McLean]

Is the /26 in your routing table directly connected? This would override
the static and aggregate protocols, so if your route policy is exporting
from static or aggregate, I don't think they'd match.

Just an idea.

Morgan

On Wednesday, June 19, 2013, Cristian Frizziero wrote:

> Hi Shanawaz,
> Not sure to have understood: are you experimenting a limitation in the
> export of an aggregate route due to the length of the mask?
> This should not happen.
> Could you clarify, with a show route ?
> Thanks
> Cristian
>
>
>
>
> On 06/19/2013 08:35 AM, Shanawaz wrote:
>
>> Using route-aggregation like the below..
>>
>> set routing-options aggregate route 172.16.0.0/26 community 65535:10000
>> set routing-options aggregate route 172.16.0.0/26 discard
>>
>> to advertise routes to ebgp peers, this works well if the routes in the
>> table are a /27 or below. However this does not work if the route in my
>> table is a /26
>>
>> Is there a way to advertise the /26 out using the aggregate route option?
>> Kind of tell the router advertise everything /26 and more specific?
>> ______________________________**_________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.nether.net/mailman/listinfo/juniper-nsp>
>>
>
>
> --
> --------------------------
> Cristian Frizziero
>
> ______________________________**_________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.nether.net/mailman/listinfo/juniper-nsp>
>


-- 
Thanks,
Morgan