Cloud OnRamp for Multicloud has a healthy AWS cloud gateway, and BFD from the stores is up. Stores in service VPN 10 still have no route to the VPC. VPN 10 was never attached to that cloud gateway. What is missing?
Select an answer to reveal the explanation.
Short Explanation
The dock is open, and your shipping department was never added to the manifest. You attach service VPN 10 to the cloud gateway so the VPC prefixes are offered to those stores. BFD is already up, and VPN 512 is management, not the VPN where the stores' users live.
Full Explanation
Cloud OnRamp for Multicloud connects selected service VPNs to the cloud gateway. BFD up only proves the transport to the gateway works. If VPN 10 was never attached, the gateway does not offer the VPC prefixes into that service VPN, and the stores have nothing to install. Attach VPN 10. Disabling BFD would tear down the data plane the stores need. It does not cause OMP to fill VPN 10. VPN 512 is the out-of-band management VPN. User traffic to a VPC belongs in a service VPN such as VPN 10, not in VPN 512. A SIG tunnel inspects internet-bound traffic. It does not, by default, carry private VPC prefixes in place of the cloud gateway. Exam caveat: attaching the VPN is not the same as advertising every VPC the account owns. The host VPC still has to be the one mapped to this gateway. Operational check: after the attachment, show sdwan omp routes for the VPC prefix in VPN 10 on a store should list the cloud-gateway TLOC.