A campus edge connects to an OSPF area 0 LAN in VPN 10 with two equal paths and must advertise only the 10.10.0.0/16 summary into the SD-WAN overlay for remote sites. OSPF adjacency is up but remote branches see every /24 instead of the summary. Which OSPF and OMP redistribution control fixes this service-side route advertisement?
Select an answer to reveal the explanation.
Short Explanation
You've got adjacency, you just need cleaner advertising across the fabric. An OMP aggregate with aggregate-only hides those /24s behind your /16 as OSPF routes enter OMP.
Full Explanation
The WAN Edge is the boundary where OSPF routes in service VPN 10 are advertised into OMP. Because this edge sits in area 0 and is not an area border router, OSPF area-range summarization does not apply there; the summary is created at the OMP boundary with an OMP aggregate-address for 10.10.0.0/16 using the aggregate-only option, with OSPF advertised into OMP. Aggregate-only suppresses the more specific /24 prefixes, so remote branches receive just the /16. Redistributing OMP into OSPF fails by direction: it injects overlay routes into the campus LAN and does nothing to what the site advertises to the overlay. Configuring summarization on the remote branches fails by location because the /24s still leave the campus edge and enter OMP from the source. An aggregate-address configured without aggregate-only fails because the Edge advertises the /16 in addition to the /24s, so branches still see every specific prefix, which is exactly the symptom. In practice, check show omp routes on a branch to confirm only 10.10.0.0/16 from this site is present, and show ip route vrf 10 on the campus edge to confirm the OSPF /24s are still local. The OMP aggregate is created under the OMP configuration of the Edge, or in the OMP feature template in SD-WAN Manager.