[j-nsp] aggregates - active/passive option

[Bostjan Fele]

Hi,

aggregate routes have only two next-hop options: reject (default) or
discard. First one enables ICMP messages if there is no more specific route,
second one silently discards packet. This has nothing to do with having a
contributing route. I have not checked if passive option installes aggregate
route in first place if there is no contributing route or not. I would try
this with configuring one static route to contribute and then remove it.

REgards,
Bostjan Fele

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Stefan Fouant
Sent: Wednesday, February 02, 2005 4:05 PM
To: Jeroen Valcke
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] aggregates - active/passive option


I believe the passive option when used with aggregate / generated routes
  will cause the route to be continually installed in the routing and
forwarding tables, even in light of no contributing routes.  However, if
there are no contributing routes, the next-hop will be set to reject.

Stefan Fouant
Senior Network Engineer
UUNET / MCI

Jeroen Valcke wrote:
> Hello,
>
> Then when I change the active/passive parameter to passive for all these
> aggregate routes, they do get installed in the routing table. I find
> this to be weird since the doc says;
>
> 	passive - Have a route remain continually installed in the
> 	routing and forwarding tables even when it becomes inactive.
>
> Reading this, one would expect that the route should at least have been
> active before. Then how come it installs the aggregate route although
> the route itself has never been active?
>
> Best regards,
> -Jeroen-
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp