A retailer runs Catalyst SD-WAN with an MPLS color that has no internet breakout and a public internet color. The Azure cloud gateway uses a public address. Which transport should carry BFD to that gateway?
Select an answer to reveal the explanation.
Short Explanation
You cannot reach a public front door on a private road that never meets the street. The Azure gateway has a public address, and this MPLS color has no internet breakout, so BFD belongs on the public internet color. OMP does not rewrite that for you.
Full Explanation
The cloud gateway's public address is reached over the internet underlay. The retailer's public internet color has that route. The MPLS color stays inside the private WAN and has no internet breakout, so it cannot forward BFD to the Azure public address. Private colors are not preferred for a public cloud gateway in this topology. They simply have no path. OMP distributes overlay routes and TLOCs. It does not NAT a private transport into a public destination or move BFD from one color to another. VPN 512 is the out-of-band management VPN on Catalyst SD-WAN. User-data BFD to a cloud gateway rides the transport VPN, VPN 0, on the internet color. It is not carried in VPN 512. Exam caveat: if the MPLS provider later adds an internet breakout, that color can be reconsidered. Until then it cannot be the cloud-gateway transport. Operational check: show sdwan bfd sessions toward the cloud gateway should list the internet color, and a trace from the MPLS interface to the gateway public address should fail.