An edge receives a VPC prefix by OMP and does not install it. The TLOC that prefix needs was filtered by control policy. Other prefixes that use a different TLOC install normally. What was filtered?
Select an answer to reveal the explanation.
Short Explanation
You can see that the prefix arrived, but the TLOC it needs was filtered, leaving it without a usable next hop. Since prefixes using a different TLOC install normally, the prefix itself was not filtered; allow the needed TLOC in policy.
Full Explanation
An OMP route installs only when its TLOC is usable. Here, control policy filtered the TLOC the VPC prefix needs, so the edge receives the prefix but cannot install it with a usable next hop. Prefixes using a different TLOC still install, which supports a TLOC-specific issue rather than rejection of the VPC prefix itself or a broader loss of controller connectivity. Allow the needed TLOC in policy. Filtering the VPC prefix itself would mean that prefix was rejected, not received and left waiting for its next hop; it would not explain the stated TLOC dependency. A controller certificate does not selectively filter one TLOC while leaving control up. A voice SLA does not remove a TLOC from OMP because loss is zero. Exam caveat: even after the TLOC is allowed, a preference or restrict on that TLOC can still direct the prefix toward a color this site does not have. Check which TLOC the route actually resolves to. Operationally, confirm that the filtered TLOC appears in the TLOC table and that the VPC prefix installs with that next hop.