How does OMP contribute to VPN reachability, and what should you check on the edge to verify OMP adjacency?

• A. OMP distributes VPN reachability and routing information from vSmart to edges; verify OMP neighbor relationships, adjacency status, and route distribution on the edge.
• B. OMP handles TLS certificate issuance for edge devices and requires CA trust validation.
• C. OMP selects best path for SaaS traffic and rewrites NAT rules at the edge.
• D. OMP manages edge device firmware updates from the vManage server.

Answer: (A)

OMP is the overlay control-plane protocol that carries VPN reachability and routing information from the vSmart controllers to each edge. It ensures every edge learns the remote prefixes for every VPN and installs the correct forwarding entries so traffic can reach the intended destinations.

To verify OMP adjacency on the edge, check that there is an OMP session with the vSmart and that the session is established. You should also confirm that the edge is receiving and installing VPN routes via OMP, meaning routes for each VPN appear in the OMP route table and are reflected in the edge’s forwarding table. In practice, this means looking for an up neighbor relationship with vSmart and a populated route set for the VPNs. If the OMP session isn’t established or routes aren’t being learned, VPN reachability won’t be available. Troubleshooting typically involves confirming the neighbor status, examining the OMP route summary or routes, and ensuring the control-plane connection (including certificates/trust and basic network reachability to vSmart) is healthy.