A store's public address changed after a circuit move. BFD to the AWS cloud gateway now flaps, and the TLOC still advertises the old public address. Other stores are stable. What is stale?
Select an answer to reveal the explanation.
Short Explanation
You moved and left the old street number on the sign. The circuit's public address changed, and the TLOC is still advertising the old one, so BFD to the cloud gateway flaps. Other stores are stable, which means the gateway itself is not the thing that moved.
Full Explanation
A public TLOC has to advertise the address the rest of the overlay can reach. After the circuit move, the store's public address changed and the TLOC still names the old one. Return traffic for BFD goes to an address that is no longer on this store, so the session flaps. Update the advertised address. Rebuilding the cloud gateway would not explain why every other store is stable. A SaaS application list does not set a TLOC public address for an AWS cloud gateway. The OSPF router ID on the LAN is not the TLOC address AWS or the overlay uses. Exam caveat: if a NAT device is supposed to discover the public address automatically, confirm it is learning the new address rather than pinning the old one. A static public address in the configuration will not follow a circuit move. Operational check: the TLOC should show the new public address, and show sdwan bfd sessions to the AWS gateway should stay up.