Combining VXLAN & vPC on Cisco Nexus Switches

If you’re working in a modern data center with Cisco Nexus switches (especially 9000 series), combining VXLAN (for network virtualization and Layer 2 extension over Layer 3) with vPC (Virtual Port Channel for redundancy) is a powerful way to build fast, resilient fabrics. But get it wrong — and you can create catastrophic switching loops that take down your entire network.

I share a real-world horror story from my own environment where a misconfigured VXLAN + vPC setup caused massive outages, then walk through the correct way to integrate them using vPC Fabric Peer-link. Includes live lab demos in Cisco Modeling Labs (CML), detailed CLI configs, and why the “obvious” approach fails spectacularly.

Watch the full VXLAN + vPC configuration video here:

This blog post summarizes the key lessons and config highlights so you can quickly grasp the concepts — then head to the video for the step-by-step demos, packet-level insights, and the “don’t do this” cautionary tale.

Why VXLAN + vPC Matters in Data Center Networking (2025–2026)

• VXLAN (RFC 7348) + BGP EVPN creates scalable overlays for east-west traffic in spine-leaf designs.
• vPC provides active/active redundancy and loop prevention for downstream connections without relying solely on spanning tree.
• Combining them incorrectly leads to loops because spanning tree BPDUs don’t traverse VXLAN tunnels (handled by EVPN instead). Result: duplicate frames, MAC flapping, SSH lag, excessive pings — full outage.

Video Breakdown + Hands-On Sections

Why this combo is common but dangerous — my personal data center meltdown story.

VXLAN Overview Overlay/underlay architecture, VTEPs (VXLAN Tunnel End Points), NVE interfaces, BUM traffic handling via multicast or ingress replication, BGP EVPN for control plane.

vPC Overview Cisco proprietary multi-chassis EtherChannel, peer-link for synchronization, peer-keepalive, orphan ports, and how it fools spanning tree into seeing one logical switch.

Problems with Combining VXLAN & vPC The classic mistake: extending vPC from core/spine to leaf switches directly. Spanning tree doesn’t see the VXLAN fabric, so BPDUs loop via vPC peer-link → broadcast storm. Real symptoms from my incident included network-wide instability.

Correct Configuration: VXLAN with vPC Fabric Peer-link Step-by-step lab demo (Nexus 9300v in CML):

• Enable features: feature vpc, feature vn-segment-vlan-based, feature nv overlay
• vPC domain setup: vpc domain <ID>, peer-keepalive over management VRF
• Virtual peer-link using loopback interfaces: virtual-peer-link destination <remote-loopback> source <local-loopback> loopback
• Add secondary IP to loopback for NVE source-interface
• Configure fabric interfaces: port-channel <num>, vpc peer-link, switchport mode fabric, port type fabric
• Enable bridge assurance, peer-switch, peer-gateway, ARP/ND sync
• TCAM carving notes for physical 9300 hardware
• Downstream vPC port-channels to hosts/servers Bonus: NX-OS bug workaround (enable vPC after VXLAN in some versions).

Alternative Solutions & Long-Term Recommendations

• Ideal: Make core/spine switches VTEPs (full EVPN symmetry) — but requires redesign/downtime.
• Fabric Peer-link is a “quick and dirty” production-safe workaround for existing setups.

My Honest Take After Real-World Deployment

The Fabric Peer-link method saved me from a full redesign during a critical integration, but it’s not elegant long-term. Always test in lab first (CML is perfect for this). Misconfigurations here aren’t “oops” moments — they’re outage-level events. Learn from my pain so you don’t repeat it!

Ready to Safely Combine VXLAN & vPC?

Watch the complete explanation, misconfiguration disaster story, and full Cisco Nexus config demo: 👉 Full Video Here: Combining VXLAN & vPC on Cisco Nexus Switches https://youtu.be/SIuREvpgldk

Don’t forget to:

• Subscribe to RichTechGuy for more data center, CCNP/CCIE Enterprise, VXLAN EVPN, and Nexus deep dives
• Drop a comment on the video: Have you hit a VXLAN/vPC loop before? What’s your go-to workaround?
• Related videos & resources:
  • VXLAN Part 1
  • Automate VXLAN with Python
  • Build Cisco Practice Labs
  • Cisco Official vPC Fabric Peering Guide: https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/102x/configuration/vxlan/cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-release-102x/m_configuring_vpc_fabric_peering_93x.html

Recommended Resources (Affiliate Links):

• Building Data Centers with VXLAN BGP EVPN (Cisco NX-OS Perspective): Paperback https://amzn.to/4bO5pFX | Kindle https://amzn.to/4bO5pFX
• Cisco Data Center CCNP & CCIE Core Exam Guide: Paperback https://amzn.to/4kyaxQX | Kindle https://amzn.to/4r9cVjn

SEO Keywords: VXLAN vPC configuration, Cisco Nexus VXLAN with vPC, vPC Fabric Peer-link, VXLAN BGP EVPN Nexus, avoid VXLAN vPC loop, data center redundancy 2026, Cisco Nexus 9000 vPC setup, VXLAN misconfiguration outage, Nexus virtual peer-link config, CCIE data center VXLAN tutorial.