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 speed test measures the path from this browser to the test server. It does not measure a user's home line if you ran it from the office. Write where you were.
One run is a sample. Three calm runs are a better sample. A hour of runs is a load on a link you should not create by accident. Do not aim a test at a server you do not have reason to measure against if a normal test server is the point.
Wireless, VPN, and a busy LAN change the number. Note them. The capacity guide owns the design number. This page owns the sample.
Do not treat the number as a commitment from a provider. It is an observation at a time.
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 place and the path.
- Run one test, or three if the ticket asks.
- Record down, up, and the time.
- Note VPN or wireless.
- Stop.
- Compare with the capacity note later, not with a second hour of tests.
Mistakes that outlive the command
How to Run an Accurate Internet Speed Test goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A long loop of tests.
- The place left unwritten.
- A VPN path reported as the bare internet.
- The number treated as a contract.
- A test aimed to congest someone.
Decisions to write down
One decision for How to Run an Accurate Internet Speed Test: The place is written. The count is one or three. VPN or wireless is noted. The time is written. And the loop stopped.
Checks before you call it done
Confirm this before you call the change done: Numbers and time are in the ticket. The path is named. No long loop ran. The figure is called a sample. And capacity design stays on its own page. If one of those fails, stop.
Write where you ran the test.
One sample, not an hour of them.Before you leave the device
How to Run an Accurate Internet Speed Test 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.