Question 740
A tenant's external BGP neighbor never forms because the required routed interface and routing-policy connectivity template were not applied at the border leaf. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Track border interface, routing-zone and peer parameters together for tenant interconnect changes. An external physical link cannot provide the required tenant route exchange without explicit L3 and routing-policy configuration.
Incorrect Answers
Routing-zone connectivity and security policy authorization are distinct requirements when business traffic crosses controlled service boundaries. Here, external routing connectivity to a tenant routing zone depends on a correctly modeled Layer 3 interface and supported routing protocol or static route configuration.
Recheck virtualization inventory and network attachment mappings during cluster onboarding or maintenance. That concerns VMware inventory integration versus network deployment, while the issue here is routing zone external BGP connection. Use an authorized connectivity template for the border-leaf external connection, configure peer addressing and policy, and verify the tenant VRF adjacency.
Overlay tenant route import requires route-target membership aligned with the intended VRF and EVPN service distribution. For this issue, use an authorized connectivity template for the border-leaf external connection, configure peer addressing and policy, and verify the tenant VRF adjacency.