Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

aggregate (Routing)

 

Syntax

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Statement introduced in Junos OS Release 11.3 for the QFX Series.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description

Configure aggregate routes.

Options

aggregate-options—Additional information about aggregate routes that is included with the route when it is installed in the routing table. Specify zero or more of the following options in aggregate-options. Each option is explained separately.

  • active(— Removes inactive routes from the forwarding table.

  • passive— Retains inactive routes in the forwarding table.

  • as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> <aggregator as-number ip-address>;

  • (brief | full);

  • community [ community-ids ];

  • discard;

  • (metric | metric2 | metric3 | metric4) value <type type>;

  • (preference | preference2 | color | color2) preference <type type>;

  • tag metric type number;

defaults—Specify global aggregate route options. These options only set default attributes inherited by all newly created aggregate routes. These are treated as global defaults and apply to all the aggregate routes you configure in the aggregate statement. This part of the aggregate statement is optional.

route destination-prefix—Configure a nondefault aggregate route:

  • default—For the default route to the destination. This is equivalent to specifying an IP address of 0.0.0.0/0.

  • destination-prefix/prefix-lengthdestination-prefix is the network portion of the IP address, and prefix-length is the destination prefix length.

  • next-table next-table—Specify the name of the next routing table to the destination. Forwarding for the aggregate prefix is done using this table. When you configure next-table to next-hop, route lookup is redirected to the route table that the next hop points to.

The policy statement is explained separately.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.