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
OSI numbers layers from the cable up to the application. TCP/IP folds some of those names. The reference shows the map. Neither model configures a device.
When something fails, say the layer you have evidence for. No link is layer 1. A VLAN mistake is layer 2. A missing route is layer 3. A refused port is layer 4. A certificate error is higher. Guessing the top layer first wastes the window.
Write one sentence at the lowest layer you actually checked. Do not reconfigure three layers because the poster has seven.
One fault.
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 fault.
- Name the lowest layer you checked.
- Write what you observed.
- Do not change a higher layer yet.
- Hand the fix to the guide for that layer.
- Stop.
Mistakes that outlive the command
OSI vs TCP/IP Model goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Three layers changed at once.
- A layer named with no observation.
- The model treated as a procedure to reconfigure.
- A higher layer blamed before link and address were looked at.
Decisions to write down
One decision for OSI vs TCP/IP Model: The fault is one sentence. The layer has an observation. Higher layers were not changed. The next guide matches the layer. And one fault.
Checks before you call it done
Confirm this before you call the change done: The layer is in the ticket. The observation is a fact. No multi-layer change. The next page is named. And a second person agrees the layer. If one of those fails, stop.
Name the lowest layer you checked.
The model is a label, not a change.Before you leave the device
OSI vs TCP/IP Model 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.