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
Packet loss and latency are numbers with a time and a path. A single ping from a laptop is a hint. A test you repeat from two places you operate is a comparison. A flood is neither.
Write the destination, the packet count, the loss, and the delay. Jitter matters for voice. It does not matter until you have a calm baseline.
Multi-location results are useful when you operate those locations or the test is clearly a public measurement of your own service. Do not aim repeated tests at a host to degrade it.
If loss is real, the next page is the device on your side of the path, not a larger test.
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 destination and the reason.
- Run one modest test.
- Write loss, delay, and time.
- Compare with a second place you operate only if the ticket asked.
- Do not raise the rate.
- Hand a fault to the device you administer.
Mistakes that outlive the command
Diagnosing Packet Loss and Latency goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A high-rate test.
- A destination chosen to disrupt.
- One sample called an outage.
- No time written.
- A range instead of a host.
Decisions to write down
One decision for Diagnosing Packet Loss and Latency: The destination is allowed. The count is modest. Numbers and time are written. The rate stayed low. And your device is the next stop if the path is yours.
Checks before you call it done
Confirm this before you call the change done: The figures are in the ticket. The time is written. No flood was sent. A second test was justified or skipped. And the next action is on your gear or a stop. If one of those fails, stop.
One modest test.
Do not raise the rate.Before you leave the device
Diagnosing Packet Loss and Latency 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.