Most stores learn a new cloud prefix by OMP. One store's centralized control policy rejects that prefix. The store has BFD to the cloud gateway and does not install the prefix. Why is this store different?
Select an answer to reveal the explanation.
Short Explanation
Everyone else got the prefix, and this store's policy threw it away. You reject it in the control policy for this site, so BFD being up does not put it in the table. A loss of zero would not make an SLA delete an OMP route.
Full Explanation
Centralized control policy can reject a prefix for one site list and allow it for everyone else. This store's policy rejects the new cloud prefix, so the prefix never installs even though BFD to the gateway is up. The other stores are the proof that the gateway is advertising it. BFD is not down, so it is not the reason the route is missing. A strict SLA does not remove an OMP route because loss is zero. Zero loss is healthy, and strict acts on forwarding, not on whether the prefix is learned. A SIG credential does not clear one store's OMP table for a cloud prefix. Exam caveat: rejecting the prefix may be intentional for a store that must not reach that VPC. If this store should reach it, the reject is the mistake. Operational check: the policy preview for this store should show the reject, and removing it should make show sdwan omp routes list the prefix.