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
Five steps are enough: name the parent, list the groups, pick a length for each group, check that they fit without overlap, and write the gateway rule. The calculator drafts the cuts. You reject a cut that overlaps or that uses a documentation range in production.
Start from the prefix the network already assigned. Do not start from 10.0.0.0/8 because it is large. A group of thirty hosts does not need a /16.
The gateway address is a habit you pick once per site, often the first usable address. Write it. The network address and the broadcast are not hosts.
Stop when the table fits on one page. A second site is a second ticket.
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 parent prefix.
- List the groups and their sizes.
- Assign one length per group.
- Check for overlap.
- Write the gateway habit.
- Leave the devices alone until the table is agreed.
Mistakes that outlive the command
How to Subnet a Network in 5 Steps goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Overlapping blocks.
- A documentation range used as the parent in production.
- A /16 for a closet.
- The broadcast assigned to a host.
- Configuring routers before the table exists.
Decisions to write down
One decision for How to Subnet a Network in 5 Steps: The parent is the assigned prefix. Each group has one length. Nothing overlaps. The gateway habit is written. And devices are not configured yet.
Checks before you call it done
Confirm this before you call the change done: The parent is written. The groups fit. Overlap was checked. The gateway rule is one sentence. And a second person can read the table. If one of those fails, stop.
Carve on paper. Then stop.
192.0.2.0/24 is not your parent prefix.Before you leave the device
How to Subnet a Network in 5 Steps 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.