20 BGP Summarization
Summarization reduces the number of prefixes advertised by representing several specific routes with one larger prefix. BGP offers two approaches: a manual method using a static route to Null0, and the aggregate-address command. This note also covers the Atomic Aggregate and Aggregator attributes, which appear as a result of summarization.
Method 1: static route to Null0 plus network
The BGP network command only advertises a prefix that exists exactly in the routing table. A summarized (larger) prefix usually does not exist as such, only its component subnets do. To make it exist, a static route for the summary is created pointing to Null0, and then the summary is advertised with network.
Null0 is a virtual discard interface. Traffic that falls into the summary range but has no more specific route is dropped, which prevents loops or black holes for unassigned addresses inside the block. Legitimate traffic uses the more specific component routes; only the leftover of the block goes to Null0.
Method 2: aggregate-address
The aggregate-address command generates and advertises a summary prefix automatically, provided at least one component subnet of the summary exists in the BGP table.
By default:
- The AS-PATH information of the component routes is not included.
- The Aggregator attribute is included (identifying which router and AS performed the aggregation).
- Because AS-PATH detail is lost, the route is marked Atomic Aggregate.
Options
summary-only: advertises only the summary and suppresses the more specific component routes. Without this option, BGP advertises both the summary and the specific routes, which does not reduce the neighbor’s table.as-set: preserves the AS-PATH information of the components (as a set of AS). Because AS-PATH detail is no longer lost, the route is no longer marked Atomic Aggregate.
The two options can be combined.
Atomic Aggregate and Aggregator attributes
- Atomic Aggregate (well-known discretionary): a flag indicating that summarization occurred and that AS-PATH information from the component routes was lost. It does not say which AS the original routes came from; that is exactly the information that was lost.
- Aggregator (optional transitive): identifies which router (Router ID) and which AS performed the aggregation.
Why as-set matters beyond cosmetics
as-set does more than remove the Atomic Aggregate flag. By carrying the component ASNs in the aggregate’s AS-PATH, it preserves loop-prevention information: it prevents the summary from being sent back into an AS that was in the original path. Without as-set, an aggregate loses that protection.
Auto-Summary (legacy)
BGP Auto-Summary is a legacy behavior, disabled by default on modern IOS. When enabled, it summarizes to the classful network boundary and requires the classful network in the network command, with at least one subnet of the prefix present in the routing table. It is problematic in the classless (CIDR) Internet because it can advertise a larger block than actually held, which is why it is left off. It is studied mainly for historical context and because it may appear enabled in old configurations.
Self-check
Q1 — Why is a static route to Null0 used when summarizing with the
networkcommand?A) To drop all traffic to the summary
B) To create an exact routing-table entry for the summary sonetworkcan advertise it
C) To raise the TTL
D) To authenticate the route
Respuesta
B is correct. BGP
networkneeds an exact match; a summary usually does not exist in the table, so a static route to Null0 creates that exact entry. The Null0 also safely discards leftover traffic in the block.
- A) False — only leftover traffic (no specific route) is dropped, not all traffic.
- C) False — TTL is unrelated to summarization.
- D) False — Null0 is not an authentication mechanism.
Q2 — What does the
summary-onlyoption do?A) Advertises both the summary and the specific routes
B) Advertises only the summary and suppresses the specific component routes
C) Preserves the component AS-PATH information
D) Deletes the component routes from the routing table
Respuesta
B is correct.
summary-onlyadvertises just the summary and suppresses the more specific routes, actually reducing the neighbor’s table.
- A) False — advertising both is the behavior without
summary-only.- C) False — preserving AS-PATH is
as-set.- D) False — it suppresses advertisement, it does not delete routes from the table.
Q3 — What does the Atomic Aggregate attribute indicate?
A) Which router and AS performed the aggregation
B) That summarization occurred and AS-PATH information from the components was lost
C) That the route is invalid
D) That the route uses IPv6
Respuesta
B is correct. Atomic Aggregate is a flag signaling that a summary was formed and component AS-PATH detail was lost. It does not reveal the original AS.
- A) False — identifying the router and AS is the Aggregator attribute.
- C) False — it is a valid summarized route.
- D) False — it is unrelated to address family.
Q4 — Beyond removing the Atomic Aggregate flag, what does
as-setaccomplish?A) It suppresses the specific routes
B) It preserves component ASNs in the AS-PATH, restoring loop-prevention information
C) It raises the Local Preference
D) It disables auto-summary
Respuesta
B is correct.
as-setcarries the component ASNs into the aggregate’s AS-PATH, preserving loop prevention so the summary is not sent back into an AS that was in the original path.
- A) False — suppressing specifics is
summary-only.- C) False — it does not change Local Preference.
- D) False — it is unrelated to auto-summary.