Academy/VCAP — VCF Networking (3V0-25.25)/Lab NN2: VRF-Lite & Route Leaking for Multi-Tenant Isolation
This lab targets VCF 9.0

Lab NN2: VRF-Lite & Route Leaking for Multi-Tenant Isolation

VCF 9.0Intermediatevcap-advanced⏱ 75 min

Objectives

  • Implement VRF-based isolation across tenants with controlled route leaking for shared services.

Prerequisites

VCF lab environment deployed and operational

Lab Environment

Standard VCF lab environment for Advanced VCF 9.0 Networking (NSX & Advanced Routing)

Tasks

Task 1 Lab NN2: VRF-Lite & Route Leaking for Multi-Tenant Isolation

Implement VRF-based isolation across tenants with controlled route leaking for shared services.

Step 1

Create 3 VRFs on T0 for tenants A, B, C plus a Shared-Services VRF.

Step 2

Configure route leaking so tenants reach shared services but not each other.

Step 3

Apply per-VRF BGP policies to upstream ToR.

Step 4

Validate with traceroute and packet captures.

Step 5

Stress test with scale: 100 prefixes per VRF, observe Edge CPU.

Validation Gate

Check: Verify lab completion

Expected: Lab exercise completed successfully

Common Errors

VRF route leaking allowing unintended cross-tenant traffic
Fix: Route leaking between VRFs must be explicit and controlled. Leak only the specific routes needed (e.g., shared services subnet), not the entire VRF routing table. Use route maps on the leak configuration to filter permitted routes. Audit leaked routes regularly.
Overlapping IP address spaces between tenants without VRF
Fix: Without VRF, overlapping tenant IP ranges cause routing conflicts. VRF-Lite on NSX T0 creates isolated routing tables per tenant. Each tenant can use 10.0.0.0/8 without conflict. Verify VRF isolation with traceroute from each tenant — traffic should never cross VRF boundaries unless explicitly leaked.
Leaking routes between VRFs through the same external AS without planning for AS-path loop prevention
Fix: A Tier-0 VRF inherits the parent Tier-0 ASN when the Local AS field is left blank, or can set its own ASN — the docs present a separate ASN as important for service-provider and multi-tenant designs where tenants bring their own ASN, not as a requirement (VCF 9.0.1 docs p.1862). With VRF-lite, each VRF peers over its own sub-interface into a matching VRF on the ToR, so a shared ASN alone does not cause problems. The caveat is route leaking between VRFs through the same external AS: the receiving router drops routes carrying its own ASN in the AS path. Plan for this with per-VRF ASNs (Local AS per Tier-0 VRF) or allowas-in on the peers.

Final Validation

Lab completed successfully

✓ All steps completed → No errors observed

Cleanup / Restore

• Revert to snapshot if needed

Design Reflection (VCDX)

Multi-tenant networking with VRF shows enterprise design capability. VCDX panelists test isolation guarantees and how you handle shared services across tenants.

⚠ Known Pitfalls

Leaking full routing tables between VRFs — defeats the purpose of tenant isolation.
Leaking routes between VRFs through the same external AS without planning for BGP AS-path loop prevention — the router drops routes carrying its own ASN; use per-VRF ASNs (NSX supports a Local AS per Tier-0 VRF) or allowas-in.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.