An Azure cloud gateway is healthy, and other sites reach it. One store's internet color is forced down by a local interface tracker even though the circuit is up. BFD from that store to the gateway is down. What should be corrected?
Select an answer to reveal the explanation.
Short Explanation
The gateway is fine, and this store has taped its own on-ramp shut. You fix the local tracker that is holding the internet color down. Other sites can already reach the gateway, so you do not rebuild the cloud side for one store's interface.
Full Explanation
BFD to a public cloud gateway rides the internet color. A local tracker that forces that color down removes the transport even when the circuit itself is up and other sites have BFD to the same gateway. Correct the tracker or the probe it uses so the color can come up. Rebuilding the cloud gateway would not explain why every other site is fine. Cloud OnRamp for SaaS application lists do not establish BFD to an Azure IaaS gateway. The OSPF area on the store LAN distributes local routes. It does not authenticate a WAN TLOC. Exam caveat: a tracker is often there to withdraw a bad circuit. Clear it only if the probe is wrong. If the probe is correctly failing, the circuit is the fault and the tracker is doing its job. Operational check: the store's internet color should show up, and show sdwan bfd sessions to the Azure gateway should then match the other sites.