Academy/VCAP — VCF Networking (3V0-25.25)/Lab NN1: BGP Convergence & Graceful Restart on NSX Edges
This lab targets VCF 9.0

Lab NN1: BGP Convergence & Graceful Restart on NSX Edges

VCF 9.0Intermediatevcap-advanced⏱ 75 min

Objectives

  • Design and validate sub-second BGP convergence between NSX Edges and ToR switches.

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 NN1: BGP Convergence & Graceful Restart on NSX Edges

Design and validate sub-second BGP convergence between NSX Edges and ToR switches.

Step 1

Enable BFD with 300ms interval between Edge and ToR.

Step 2

Enable BGP Graceful Restart on both sides.

Step 3

Kill one Edge via forced reboot and measure steady-state traffic drop.

Step 4

Test control plane separation: BGP peer dies but data plane keeps forwarding.

Step 5

Document tuning knobs with their trade-offs (CPU vs convergence speed).

Validation Gate

Check: Verify lab completion

Expected: Lab exercise completed successfully

Common Errors

BGP graceful restart timer mismatch between NSX Edge and physical router
Fix: Graceful restart requires matching restart and stale-route timers on both peers. If NSX Edge restarts and the physical router's stale timer is shorter than the Edge's restart time, routes are withdrawn during Edge reboot. Set stale-route timer on physical router > Edge restart time (typically 120-180s).
BFD false positives during Edge VM vMotion
Fix: BFD with aggressive timers (e.g., 300ms) can detect Edge VM vMotion latency as a failure, causing route withdrawal. Either: disable BFD during planned Edge maintenance, or tune BFD timers to tolerate vMotion switchover latency (set detect-multiplier × interval > vMotion switchover time).
Not verifying BGP convergence time meets SLA requirements
Fix: BGP convergence after Edge failover includes: BFD detection (ms) + BGP session timeout (if no BFD) + route propagation (ms-seconds) + FIB update (ms). Measure actual convergence time with traffic during planned Edge failover test. Compare against SLA requirement.

Final Validation

Lab completed successfully

✓ All steps completed → No errors observed

Cleanup / Restore

• Revert to snapshot if needed

Design Reflection (VCDX)

BGP convergence tuning shows deep networking expertise. VCDX panelists test whether you measured actual convergence times and tuned timers for your SLA.

⚠ Known Pitfalls (from Community KB)

Using aggressive BFD timers without accounting for vMotion latency — causes false failovers.
Assuming default BGP timers meet SLA — always measure actual convergence during Edge failover test.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.