A branch Catalyst SD-WAN edge shows a control connection to the management controller and no connection to the controller that distributes OMP routes. The OMP table is empty and cloud prefixes are missing. What is the failure?
Select an answer to reveal the explanation.
Short Explanation
You can see the front office and still not be on the route-distribution call. You have a management connection and no session to the controller that actually sends OMP, so the cloud prefixes never arrive. SaaS OnRamp does not empty OMP because the manager is reachable.
Full Explanation
On Catalyst SD-WAN the management connection and the OMP distribution connection are different sessions. This edge has the management session and lacks the session to the controller that advertises OMP routes. The OMP table stays empty and cloud prefixes never show up. Restore underlay reachability, certificates, and policy that allow that controller session. Cloud OnRamp for SaaS does not clear OMP because the management connection is healthy. It needs the overlay, it does not delete it. An Azure VPN gateway ASN is a native IPsec BGP setting. It does not populate or empty the OMP table on an SD-WAN edge. A zone-based firewall between service VPNs filters user traffic after routes exist. It does not tear down the management connection or replace OMP. Exam caveat: a connection to the manager can look like the overlay is fine in one screen while the OMP screen is empty. Check both. Operational check: show sdwan control connections should list the OMP controller, then show sdwan omp routes should fill with the cloud prefixes.