[j-nsp] aggregated route shows as REJECT
Daniel Roesen
dr at cluenet.de
Thu Mar 18 08:20:30 EST 2004
On Thu, Mar 18, 2004 at 02:03:57PM +0100, Peter löfqvist wrote:
> On the juniper I advertise an aggregated route and export it in the peering
> with the cisco. When I do "show route 192.168.124.0" on the juniper I get:
>
> peter at fredriksborg# run show route 192.16.124.0
>
> inet.0: 418 destinations, 420 routes (417 active, 0 holddown, 1 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 192.168.124.0/22 *[Aggregate/130] 3d 18:57:04
> Reject
> [BGP/170] 1d 01:50:37, MED 0, localpref
> 100, from 192.168.124.2
> AS path: I
> > to 192.168.124.10 via fe-0/1/2.0
reject is the normal "next-hop" for aggregate routes. What would you
expect?
http://www.juniper.net/techpubs/software/junos/junos62/swconfig62-routing/html/routing-tables-config24.html#1017501
> and the best route is the one received from the cisco not he local one.
No. The route marked with the "*" is the best one, so the local
aggregate is the one.
> As I see it, the route originated from aggregate has a preference
> of 130 and should rank higher than 170 of bgp.
Well it does, you're misreading the "show route" output.
Best regards,
Daniel
More information about the juniper-nsp
mailing list