EVPN/VXLAN lab notes — practice only, no underlay
Done: The note names underlay, overlay, control, and gateways, the sketch stays labeled practice, and no fabric picture was invented.
Requirements
This page is notes. It does not install a switch OS and it does not stand up a fabric. No scrubbed diagram, no switch screenshot, and no underlay addressing were filed with this article.
- Hardware — none for this page. A later lab note needs two VTEPs and a host behind each leaf.
- OS — none for this page
- Hostname rule — public placeholders only:
leaf-01,leaf-02,vlan-N,vni-N. Change them in your private note. Do not paste real VTEP names here. - DNS / addresses — underlay addresses stay in the lab note, not on this site
- Packages — none. This procedure files a note, not a package.
| Plane | What the note must name | What stays off this site |
|---|---|---|
| Underlay | How the VTEPs reach each other | Real VTEP addresses |
| Overlay | VNI, and which VLAN maps to it | Live VLAN / VNI inventory |
| Control | EVPN, or a static flood list — the one you configured | Route-distinguisher values from a running box |
| Gateways | Anycast or not. Say so. | Gateway anycast addresses |
Procedure
Step 1 — Separate the claims
The projects card and the older seed are two claims. Mixing them makes the note look like a production fabric write-up.
-
Open a private lab note. Do not edit this public page as the note.
-
Create a working file. Change the path if you keep notes elsewhere.
mkdir -p "$HOME/lab-notes" cat > "$HOME/lab-notes/evpn-vxlan.txt" <<'EOF' lab note — practice only, not a production EVPN claim claim A: virtualized VxLAN fabric for switching tests on owned gear. Diagrams and practice notes only. claim B: EVPN/VXLAN lab designs and change checklists. Older content seed. Not the same claim as A. EOF -
Read the file back. The two claims must be separate lines.
cat "$HOME/lab-notes/evpn-vxlan.txt"Expected: the header
practice only, then claim A, then claim B.
Step 2 — File the four planes
A note that names the four planes can be checked later. This page does not draw a fabric to stand in for that note.
-
Append four headings to the private note. Use the placeholders
leaf-01,leaf-02,vlan-N, andvni-Nin any text that might be copied public.cat >> "$HOME/lab-notes/evpn-vxlan.txt" <<'EOF' Underlay: How leaf-01 and leaf-02 reach each other. Addresses stay in this lab note, not on the public page. Overlay: VNI vni-N. VLAN vlan-N maps to it. Control: EVPN, or a static flood list. Write the one you configured. Leave blank until you have configured it. Gateways: Anycast, or not. Say so. Leave blank until you have built one. EOF -
Confirm the four headings exist.
grep -E '^(Underlay|Overlay|Control|Gateways):' "$HOME/lab-notes/evpn-vxlan.txt"Expected:
Underlay: Overlay: Control: Gateways: -
Stop. Do not fill this public page with a running fabric’s numbers. Do not draw a switch UI or a topology diagram. No scrubbed fabric picture was filed.
Step 3 — Keep the sketch labeled
A sketch without a practice label reads as a capture of a running fabric. Keep the header.
-
Copy the sketch below into the private note, header included.
cat >> "$HOME/lab-notes/evpn-vxlan.txt" <<'EOF' practice sketch only — not a capture of the lab fabric [leaf-01] ---- underlay ---- [leaf-02] | | +-------- VXLAN VNI -------+ | host in vlan-N EOF -
Confirm the header is still there.
grep -F 'practice sketch only' "$HOME/lab-notes/evpn-vxlan.txt"Expected:
practice sketch only — not a capture of the lab fabric -
Do not retitle the sketch as a capture. If a measured diagram exists later, replace this sketch then. Until then, leave it labeled.
practice sketch only — not a capture of the lab fabric
[leaf-01] ---- underlay ---- [leaf-02]
| |
+-------- VXLAN VNI -------+
|
host in vlan-N
Step 4 — Record what you measured
The note is done when three facts are true. It is not done when the sketch looks finished. This article did not log into a switch to collect those facts.
-
Append the three checks to the private note. Leave the answers blank until you have measured them. Do not invent switch output here.
cat >> "$HOME/lab-notes/evpn-vxlan.txt" <<'EOF' Measured (fill only after you have two VTEPs and a host behind each leaf): [ ] two VTEPs have underlay reachability [ ] a host behind leaf-01 reaches a host behind leaf-02 in the same VNI [ ] that path was EVPN, or a static flood list, because I configured it EOF -
Confirm the three lines exist. They stay unchecked on this article’s disk.
grep -E 'VTEPs|same VNI|EVPN' "$HOME/lab-notes/evpn-vxlan.txt"Expected: the three measured lines, still unchecked.
-
Do not paste switch CLI onto this page as if it had been run. Addresses stay in the private note.
Verification
Read the note you filed. Expected:
planes named: underlay, overlay, control, gateways
placeholders only: leaf-01, leaf-02, vlan-N, vni-N
sketch header: practice sketch only — not a capture of the lab fabric
diagram: none filed (shot missing; no fake UI)
switch CLI: not run for this article
There is no installer log. Nothing was installed.
Next
When a scrubbed diagram exists, replace the practice sketch and caption it with what was measured. Until then, leave the sketch labeled and keep underlay addressing in the lab note.