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
A lab for learning uses a topology you can reload: a small switch, a virtual router, or a container lab. The topology generator drafts a picture. It does not connect the lab to a network you do not administer, and it does not advertise a prefix.
Keep the lab on its own VLAN or its own host. The family's router, or the office VPN, is not the lab uplink unless you have written the risk and you administer that router. A default password on lab gear still gets changed before the lab shares any real LAN.
One protocol is the week's goal. Notes you can repeat are the evidence. This page does not certify you and does not replace a vendor's exam rules. Do not collect exam questions from a dump.
Secrets in the lab are prompt-for-this if the files might be shared.
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 the one protocol.
- Draw a reloadable topology.
- Keep it off networks you do not administer.
- Change any default password before it shares a LAN.
- Write a note you can redo.
- Do not advertise a lab prefix.
Mistakes that outlive the command
Home Lab Guide for Network Engineers goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The lab bridged to a network you do not run.
- A default password left in place.
- A lab prefix advertised.
- An exam dump used as the lesson.
- A claim that the lab certified you.
Decisions to write down
One decision for Home Lab Guide for Network Engineers: The topology is reloadable. The boundary is written. Default passwords are gone. No prefix was advertised. And no certification is claimed.
Checks before you call it done
Confirm this before you call the change done: The protocol is named. The boundary is in the note. A default password was changed. Nothing was advertised. And the note can be repeated. If one of those fails, stop.
Before you leave the device
Home Lab Guide for Network Engineers 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.