Generated routes are very similar to aggregate routes, with one
exception: generated routes inherit a real next-hop interface, while
aggregate routes only allow discard or reject as next-hops.
For example, the following config:
routing-options {
aggregate {
route 192.168.16.0/21;
}
generate {
route 10.0.0.0/16;
}
}
Results in:
lab@groupstudy> show route protocol aggregate
inet.0: 57 destinations, 60 routes (57 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.0.0/16 *[Aggregate/130] 00:00:04
> via so-0/0/0.0 <<<<<<REAL NEXT HOP (inherited
from contributor)
192.168.16.0/21 *[Aggregate/130] 1d 08:33:02
Reject <<<<<<Reject is the default (can
be configured to discard)
Note that they both show up in the routing table as protcol type
Aggregate.
HTH,
Scott
JunoGuy wrote:
>
> Could someone please explain to me the use of a Generated route? I understand that it is use as a "route of last resort" but say I have the following configuration:
>
> routing-options {
> generate {
> defaults {
> metric 10;
> }
> route 172.16.12.0/21;
> }
> }
>
> Will this generated route statement mean that a default route will be installed in the routing table with a metric of 10 and will become active IF a more specific route to that destination is not found? Am I understanding this right?
>
> TIA,
>
> JunoGuy
> --
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:39 EDT