Windows Server 2022 — VXLAN overlay endpoints cannot reach each other — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Overlay networks appear healthy, but east-west traffic between VTEPs fails intermittently or permanently.

Environment & Reproduction

Typically observed after VNI changes, UDP port filtering, or multicast/replication misconfiguration.

Root Cause Analysis

Frequent causes include inconsistent VNI mapping, blocked UDP 4789, and stale ARP/ND learning state.

Quick Triage

Validate VTEP reachability and underlay latency/jitter across participating hosts.

Step-by-Step Diagnosis

Inspect VNI-to-segment mapping and MAC learning consistency.

Solution — Primary Fix

Normalize VNI config, allow VXLAN transport, and flush stale endpoint learning caches.

Solution — Alternative Approaches

Use static endpoint mapping for critical segments while dynamic control plane is corrected.

Verification & Acceptance Criteria

All VTEPs pass synthetic probes with stable packet delivery and expected RTT.

Rollback Plan

Revert to prior VNI mappings and underlay ACL profile snapshot.

Prevention & Hardening

Implement config drift detection for overlay attributes and ACL baselines.

Related Errors & Cross-Refs

Related to NVGRE path mismatch and host vSwitch policy conflicts.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft SDN and overlay networking guidance for Windows Server.