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
802.1X asks a switch port to authenticate a device before the data VLAN is useful. The planner drafts the pieces: the port, the authentication server, and the failure behavior. It does not enable the feature.
The test port is an access port you can stand next to. The uplink, the port channel, and the port you are using to manage the switch are not the test. A failure VLAN or a closed failure has to be something you can see.
RADIUS is the usual server. The server address is one you operate. A shared secret in the draft is prompt-for-this. Certificates and the supplicant are a later proof, one device.
Do not enable this on a building of ports in the planning hour.
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 access port.
- Name the server you operate.
- Write the failure behavior.
- Keep the uplink out.
- Replace any secret in the draft with prompt-for-this.
- Do not enable the feature yet.
Mistakes that outlive the command
802.1X Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The uplink included in the test.
- A default secret saved in the note.
- Every access port enabled at once.
- No failure behavior written.
- Management locked out.
Decisions to write down
One decision for 802.1X Explained: One access port is named. The server is yours. Failure is visible. The uplink is excluded. And the secret is not in the note.
Checks before you call it done
Confirm this before you call the change done: The port is written. The server is written. Failure behavior is one sentence. The uplink is absent. And nothing was enabled. If one of those fails, stop.
Before you leave the device
802.1X 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.