API Guide

advertisement-interval
Sets the minimum time interval for advertisement between the BGP neighbors or within a BGP peer group.
Syntax
advertisement-interval seconds
Parameters seconds—Enter the time interval value in seconds between BGP advertisements, from 1 to 600.
Default EBGP 30 seconds, IBGP 5 seconds
Command Mode ROUTER-NEIGHBOR
Usage
Information
The time interval applies to all peer group members of the template in ROUTER-TEMPLATE mode. The
no version of this command resets the advertisement-interval value to the default.
Example
OS10(conf-router-neighbor)# advertisement-interval 50
Supported
Releases
10.3.0E or later
advertisement-start
Delays initiating the OPEN message for the specified time.
Syntax
advertisement-start seconds
Parameters seconds—Enter the time interval value, in seconds, before starting to send the BGP OPEN message,
from 0 to 240.
Default Not configured
Command Mode ROUTER-NEIGHBOR
Usage
Information
The time interval applies to all the peer group members of the template in ROUTER-TEMPLATE mode.
The no version of this command disables the advertisement-start time interval.
Example
OS10(conf-router-neighbor)# advertisement-start 30
Supported
Releases
10.3.0E or later
aggregate-address
Summarizes a range of prefixes to minimize the number of entries in the routing table.
Syntax
aggregate-address address/mask [as-set] [summary-only] [advertise-map map-
name] {attribute-map route-map-name] [suppress-map route-map-name]
Parameters
● address/mask — Enter the IP address and mask.
● as-set — (Optional) Generates AS set-path information.
● summary-only — (Optional) Filters more specific routes from updates.
● advertise-map map-name — (Optional) Enter the map name to advertise.
● attribute-map route-map-name — (Optional) Enter the route-map name to set aggregate
attributes.
● suppress-map route-map-name — (Optional) Enter the route-map name to conditionally filter
specific routes from updates.
Default None
Command Mode ROUTER-BGPv4-AF
Usage
Information
At least one of the routes that is included in the aggregate address must be in the BGP routing table for
the configured aggregate to become active. If routes within the aggregate are constantly changing, do
618 Layer 3