Concept Guide
• Assign the IP address and mask of the prex to be aggregated.
CONFIG-ROUTER-BGP mode
aggregate-address ip-address mask [advertise-map map-name] [as-set] [attribute-map map-name]
[summary-only] [suppress-map map-name]
Example of Viewing Aggregated Routes
In the show ip bgp command, aggregates contain an ‘a’ in the rst column (shown in bold) and routes suppressed by the aggregate
contain an ‘s’ in the rst column.
Dell#show ip bgp
BGP table version is 0, local router ID is 10.101.15.13
Status codes: s suppressed, d damped, h history, * valid, > best
Path source: I - internal, a - aggregate, c - confed-external, r - redistributed, n - network
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 7.0.0.0/29 10.114.8.33 0 0 18508 ?
*> 7.0.0.0/30 10.114.8.33 0 0 18508 ?
*
>a 9.0.0.0/8 192.0.0.0 32768 18508 701 {7018 2686 3786} ?
Conguring BGP Confederations
Another way to organize routers within an AS and reduce the mesh for IBGP peers is to congure BGP confederations.
As with route reectors, BGP confederations are recommended only for IBGP peering involving many IBGP peering sessions per router.
Basically, when you congure BGP confederations, you break the AS into smaller sub-AS, and to those outside your network, the
confederations appear as one AS. Within the confederation sub-AS, the IBGP neighbors are fully meshed and the MED, NEXT_HOP, and
LOCAL_PREF attributes are maintained between confederations.
To congure BGP confederations, use the following commands.
• Species the confederation ID.
CONFIG-ROUTER-BGP mode
bgp confederation identifier as-number
– as-number: from 0 to 65535 (2 Byte) or from 1 to 4294967295 (4 Byte).
• Species which confederation sub-AS are peers.
CONFIG-ROUTER-BGP mode
bgp confederation peers as-number [... as-number]
– as-number: from 0 to 65535 (2 Byte) or from 1 to 4294967295 (4 Byte).
All Confederation routers must be either 4 Byte or 2 Byte. You cannot have a mix of router ASN support.
To view the conguration, use the show config command in CONFIGURATION ROUTER BGP mode.
Enabling Route Flap Dampening
When EBGP routes become unavailable, they “ap” and the router issues both WITHDRAWN and UPDATE notices.
A ap is when a route:
• is withdrawn
• is readvertised after being withdrawn
• has an attribute change
The constant router reaction to the WITHDRAWN and UPDATE notices causes instability in the BGP process. To minimize this instability,
you may congure penalties (a numeric value) for routes that ap. When that penalty value reaches a congured limit, the route is not
Border Gateway Protocol IPv4 (BGPv4)
213