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 cheat sheet is a lookup, not a design. The useful rows are the lengths you actually see: /24 for an ordinary LAN, /30 or /31 for a point-to-point, longer masks for small device groups.
The generator can print a row. You copy the prefix and the mask into the ticket only after they match. The dotted mask and the bit length are one fact.
Do not pick a /16 because the sheet made it look simple. The subnetting guide is where a site is carved. This page only reminds you what a length means.
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 device, the host, or the zone in the ticket.
- Confirm you administer it.
- Use the browser tool to draft, then read the draft.
- Remove secrets and any target you do not run.
- Record one result line with the time.
- Stop. A second test is a new ticket.
Mistakes that outlive the command
Subnet Mask Cheat Sheet goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A mask from the wrong length.
- A /16 chosen from habit.
- The sheet used as a production plan.
- A documentation address left in a router config.
Decisions to write down
One decision for Subnet Mask Cheat Sheet: The length and the mask match. The size fits the group you named. This is a lookup, not a carve. And documentation ranges stay in the note.
Checks before you call it done
Confirm this before you call the change done: The length is written. The mask matches. The usable count is plausible for the site. And no device was configured from the sheet alone. If one of those fails, stop.
| Length | Mask | Usual use |
|---|---|---|
| /24 | 255.255.255.0 | One ordinary LAN |
| /30 | 255.255.255.252 | A point-to-point with two hosts |
| /31 | 255.255.255.254 | A point-to-point that uses both addresses |
/24 mask 255.255.255.0 is one fact.
Check both forms.Before you leave the device
Subnet Mask Cheat Sheet 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.