In Cisco SD-WAN, OMP routes are present on vSmart but absent from WAN Edge routing tables. Which issue is the most likely cause?

• A. CAPWAP join failure
• B. EtherChannel suspension
• C. STP root inconsistency
• D. Control policy filtering the routes

Answer: (D)

In Cisco SD-WAN, OMP distributes routing information from vSmart to WAN Edges, but what actually gets installed on an edge depends on the edge’s control policies. If OMP routes exist on vSmart but don’t appear in the WAN Edge routing table, it’s because a control policy on the edge is filtering those routes and preventing their import. The policy might deny certain prefixes, rely on tags, or have conditions that don’t match the routes, so they’re dropped before being installed in the edge’s routing table.

CAPWAP join failures would stop the edge from joining the fabric and OMP exchange altogether, not result in selective route absence. EtherChannel suspension affects link aggregation, not the selective import of routes. STP root inconsistencies pertain to Layer 2 topology and aren’t about OMP route distribution. To fix this, inspect the WAN Edge control policies and their import rules for those routes, adjust the policy to permit the prefixes, and verify route tagging/matching.