evpn

You have a VXLAN EVPN fabric that already works, and now it needs to be managed by Cisco NDFC. This post walks through bringing ten Nexus 9300v switches under Nexus Dashboard as a brownfield migration, without rebuilding anything.

A DCI link goes down at 18:00. Nexus Dashboard's syslog export lands seven seconds later, the triage turns it into one incident, the investigation names the link, and the fix goes through NDFC with an approval bound to the exact lines a human read. Part 2 of FabricSRE.

Three ways to make two Nexus 9000 leaves one LACP partner: vPC, vPC Fabric Peering, EVPN ESI multihoming. All forward on both cables. Which one holds up when a leaf loses the fabric, the host leg dies, or the peer-link goes? Four pairs, one fabric, thirteen drills, three passes.

Nexus Dashboard 4.3.1 exposes enough over its GA API to build a real SRE agent. Part 1: the rules, the fabric twin, a ten-hypothesis investigation with evidence on every line, and the fault harness that proves it names the right failure.

Build two VXLAN EVPN sites with an NDFC-managed ISN and a stretched subnet in Nexus Dashboard 4.1 using an eBGP Multi-AS underlay. Follow every screen, deployment gotcha, validation step, and the Python automation that rebuilds it end to end.

Create the fabric, discover the switches, pair the leaves, add a VRF and networks, attach the host ports, and prove it with a ping matrix. One NDFC screen at a time.

Deploy Nexus Dashboard 4.3 as an EVE-NG node, bootstrap it from the console, bring up the cluster, and boot a six-switch N9Kv fabric under containerlab. Every step, with the screen it produces.

EVPN multihoming vs MLAG: what actually breaks Both make two leaf switches look like one LACP partner to a dual-homed server. Both forward on both links. So which one holds up when something fails? Two labs on Cumulus Linux, identical wiring, four failure scenarios, every probe accounted for.

Your pod is Running, your Service exists, the curl still hangs. Most Kubernetes traffic diagrams stop at a Load Balancer cloud. On bare metal that cloud is a Cisco Nexus EVPN fabric. Here is one HTTPS request traced all the way to the pod, with the command that proves every hop.