LEARN. PRACTICE. GROW.The ABR role
The topology contains R1 in the backbone, R2 between areas 0 and 10, and R3 in area 10. R2 maintains information for each area and advertises reachability between them. Do not expect R1’s LSDB to be a complete copy of area 10 router LSAs. In OSPFv2, inter-area information is represented by type-3 LSAs. The term summary LSA does not mean that multiple prefixes were aggregated: it can also represent one prefix advertised between areas. Initially, R1 learns 10.50.1.1/32 and 10.50.2.1/32 individually.
Case: reduce the table without losing visibility
A team wants the ABR to advertise less detail. In the exercise, configure the 10.50.0.0/16 range for area 10 on R2. Confirm that R1 learns the aggregate and stops learning the two /32s through OSPF. Separately confirm that R2 still knows the components and both endpoints answer probes sourced from R1’s loopback. R1’s table change is the expected control-plane outcome, not sufficient proof for every destination. Also record prefix scope: the /16 includes many addresses never provisioned in this lab.
The aggregate can survive a partial failure
Remove only 10.50.1.1 from R3 and retain 10.50.2.1. After convergence, R2 no longer knows the first /32 but still has a reachable component within the range. The aggregate remains on R1. The first endpoint probe fails while the second continues to respond. An alarm based only on the presence of 10.50.0.0/16 misses this partial loss. For a reconciliation service, monitor critical endpoints and transactions as well as aggregate prefixes. Do not claim summarization caused address removal: it reduced the information exposed about that removal.
Summarizing is not filtering traffic
An advertisement policy controls distributed routing information. It is not equivalent to an ACL permitting or denying application traffic. Likewise, an inter-area filter should not be interpreted as arbitrary editing of an area’s shared LSDB. Define the requirement first: reduce advertisements, prevent propagation of a prefix, or restrict service access. Choose and observe the appropriate mechanism. This unit executes ABR summarization; advertisement filters and traffic rules are discussed to establish boundaries, but the runner does not exercise them.
Recovery with two checks
Restore the removed address and verify that the ABR learns the /32 again and the endpoint responds. Then remove summarization and verify that R1 learns both specific prefixes again and stops learning the aggregate. These are separate changes: restore service and restore the original policy. Removing summarization alone leaves the missing address absent. Retain before-and-after LSDB, routing-table and probe observations. This lab uses two normal areas; it does not validate stub areas, NSSA, virtual links or every OSPF design option.
# FRRouting lab, r2 is the ABR for area 10
configure terminal
router ospf
area 10 range 10.50.0.0/16
end
show ip ospf database
show ip route
# Recover initial advertisement policy:
# router ospf -> no area 10 range 10.50.0.0/16
The /16 exists on R1, but only one of two endpoints responds.
Common pitfalls
Aggregate as service inventory; summary LSA as proof of aggregation; route filter as firewall.
Related topics: OSPF: adjacency and controlled failures · OSPF lab and operational acceptance
Validate components and critical destinations even when the aggregate remains stable.
Reference: FRRouting OSPFv2 · 350-401 ENCOR v1.2, effective 2026-03-19; core component of CCNP Enterprise