- [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
(aggregate | generate) (defaults | route)],
- [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
rib routing-table-name (aggregate | generate) (defaults | route)],
- [edit logical-systems logical-system-name routing-options (aggregate | generate) (defaults |
route)],
- [edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)],
- [edit routing-instances routing-instance-name routing-options (aggregate | generate) (defaults |
route)],
- [edit routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate) (defaults | route)],
- [edit routing-options (aggregate | generate) (defaults |
route)],
- [edit routing-options rib routing-table-name (aggregate | generate) (defaults | route)]
Statement introduced before JUNOS Release 7.4.
Associate a routing policy when configuring an aggregate or generated route’s destination prefix in the routes part of the aggregate or generate statement. This provides the equivalent of an import routing policy filter for the destination prefix. That is, each potential contributor to an aggregate route, along with any aggregate options, is passed through the policy filter. The policy then can accept or reject the route as a contributor to the aggregate route and, if the contributor is accepted, the policy can modify the default preferences. The contributor with the numerically smallest prefix becomes the most preferred, or primary, contributor. A rejected contributor still can contribute to a less specific aggregate route. If you do not specify a policy filter, all candidate routes contribute to an aggregate route.
policy-name—Name of a routing policy.
See Configuring Aggregate Routes and Configuring Generated Routes.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.