WAN Edge devices show stable vBond and vSmart connections but no OMP routes are exchanged. What is the most likely cause?

• A. DNS failure
• B. STP blocking uplinks
• C. NAT exhaustion
• D. Control policy restricting OMP route advertisement

Answer: (D)

OMP routes are exchanged only if the control plane can advertise and receive them without being blocked. When WAN Edge devices establish stable vBond and vSmart connections, the control-plane is reachable, so the absence of OMP routes points to a policy issue rather than a connectivity problem. A control policy can explicitly permit or deny OMP route advertisements; if a rule blocks advertising from the edge to vSmart (or vice versa), no OMP routes will be exchanged even though the tunnels are up. In this situation, the fix is to inspect the control policies in vManage (and the edge templates) for any rules that deny or filter OMP updates, and adjust them to allow OMP route advertisements.

Other issues like DNS failure or NAT exhaustion would typically prevent establishing or maintaining the control-plane connections in the first place, and STP blocking uplinks would disrupt the underlying transport to reach the controllers. Since vBond and vSmart connections are already stable, those scenarios are less likely explanations for the lack of OMP routes.