This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
VXLAN carries a layer-2 segment across a layer-3 fabric. The VNI is the identifier. EVPN is the control plane that advertises the MAC and the IP information. The planners draft a VNI and a route distinguisher or target. They do not configure a switch.
One segment. The VNI, the VLAN it maps to, and the route target have to be the same story at every leaf that should carry it. A target that imports every VNI is a flood you did not design.
This is your fabric. Do not extend a VNI to a network you do not administer. A lab VNI must not be advertised beyond the lab. Documentation addresses are not the underlay.
The underlay routing is a different ticket. Do both and you will not know which one failed.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name one segment.
- Assign one VNI.
- Write the route target.
- Refuse an import of every VNI.
- Keep the lab inside the lab.
- Do not configure the underlay in this hour.
Mistakes that outlive the command
VXLAN and EVPN Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- One VNI mapped to two VLANs.
- A route target that imports everything.
- A VNI extended to a network you do not run.
- The underlay changed in the same window.
- A documentation prefix as the underlay.
Decisions to write down
One decision for VXLAN and EVPN Explained: One segment has one VNI. The target is specific. The fabric is yours. The underlay waits. And the lab is not advertised.
Checks before you call it done
Confirm this before you call the change done: The VNI is written. The VLAN map is written. The route target is written. No any-import remains. And no switch was configured. If one of those fails, stop.
Before you leave the device
VXLAN and EVPN Explained ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.