Specifying Aggregate Route Options

In the defaults and route parts of the aggregate statement, you can specify aggregate-options, which define additional information about aggregate routes that is included with the route when it is installed in the routing table. All aggregate options are optional. Aggregate options that you specify in the defaults part of the aggregate statement are treated as global defaults and apply to all the aggregate routes you configure in the aggregate statement. Aggregate options that you specify in the route part of the aggregate statement override any global aggregate options and apply to that destination only.

To configure aggregate route options, include one or more of them in the defaults or route part of the aggregate statement. For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement. Each of these options is explained in the sections that follow.

[edit]

routing-options {

    aggregate { 

        (defaults | route) {

            (active | passive); 

            as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> 

                <aggregator as-number in-address>; 

            community [ community-ids ]; 

            discard;

            (brief | full); 

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

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

            tag string; 

        }

    }

}

The following sections explain how to specify aggregate route options:

• Specifying the Route Metric
• Specifying the Route Preference
• Specifying a Next Hop for a Route
• Specifying Community Information
• Specifying the AS Path
• Specifying Which AS Numbers to Include in the Aggregate Route
• Specifying the OSPF Tag
• Specifying Whether Inactive Routes Are Removed from the Routing or Forwarding Table