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 prefix length tells you how many addresses the block contains. The network address and the broadcast address are not hosts. The calculator shows the usable count. It does not assign the addresses.
A /24 has 256 addresses and 254 usable hosts in the ordinary IPv4 habit. A /31 or a /32 is a different habit, used on a link you have already decided is a link, not a LAN of PCs. Write which habit this ticket uses.
Do not round a group of 50 hosts up to a /16 because the field allowed it. The parent prefix is still the one you were assigned.
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 stay in the note.
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.
- Write the prefix.
- Read the address count.
- Subtract the reserved ends if this is a LAN.
- Write the usable count.
- Name the gateway habit.
- Do not configure a device.
Mistakes that outlive the command
How to Calculate Usable Hosts in a Subnet goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Handing the network address to a host.
- Handing the broadcast to a host.
- Using a /31 for a LAN of PCs.
- Ignoring the assigned parent.
- Configuring the router from the calculator.
Decisions to write down
One decision for How to Calculate Usable Hosts in a Subnet: The length is the one in the ticket. Usable hosts exclude the reserved ends for a LAN. A /31 is labeled if you use one. The parent is unchanged. And no device was configured.
Checks before you call it done
Confirm this before you call the change done: The prefix is written. The usable count is written. The gateway is named. No host received the broadcast. And the device was left alone. If one of those fails, stop.
Before you leave the device
How to Calculate Usable Hosts in a Subnet 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.