OMP has a VPC prefix for VPN 10. This edge has VPN 0 and VPN 20 only. Users who should be in VPN 10 have no route to the VPC. What is missing on the edge?
Select an answer to reveal the explanation.
Short Explanation
The OMP prefix is for a VPN your edge does not have, so there is nowhere to install it. Add VPN 10 and place the users in it. The edge already has the route in OMP, so a new cloud gateway is not the missing piece.
Full Explanation
An OMP route for VPN 10 installs only on an edge that has VPN 10. This edge has VPN 0 and VPN 20, so the prefix has nowhere to install and users who should be in VPN 10 do not see the route. Add VPN 10 locally and place those users in it. A new cloud gateway does not create the missing local VPN, and OMP already holds the prefix, so the gateway is not needed to make OMP accept it. A controller certificate renewal does not create VPN 10 or other service VPNs. A strict SLA affects path selection based on loss; it does not install a VPN. Exam caveat: if a control policy also excludes this site from VPN 10, adding the VPN locally is not enough; the policy must allow the membership. The stem establishes that the prefix is present in OMP and VPN 10 is absent from the edge, making the missing local VPN the first fix. Practical check: confirm the edge lists VPN 10, then run show sdwan omp routes vpn 10 and verify that the VPC prefix is installed.