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
Ping asks if an address answers ICMP. Traceroute shows hops that reply. Both are tests of a path you are allowed to test: your device, your provider's handoff, or a host a ticket names.
A loss of answers is not always loss of traffic. Filters drop ICMP. Write what you sent and what came back. Do not raise the rate to force a reaction.
Visual traceroute is a drawing of the same replies. It is not a map of a person. Documentation addresses do not answer; do not point a flood at them either.
One destination, a small count, then stop. A range is not a destination.
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 why you may test it.
- Send a small ping.
- If the path matters, one traceroute.
- Write the loss and the last hop that replied.
- Do not increase the rate.
- Stop.
Mistakes that outlive the command
Ping and Traceroute Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A sweep of a range.
- A high rate.
- A destination you do not have a reason to test.
- ICMP failure treated as proof the host is down.
- A traceroute filed as a person's location.
Decisions to write down
One decision for Ping and Traceroute Guide: The destination is allowed. The count is small. The result is written. No range was tested. And the rate was not raised.
Checks before you call it done
Confirm this before you call the change done: The destination is in the ticket. The count is written. Loss is a number. No sweep ran. And the next step is one device you administer, or a stop. If one of those fails, stop.
One host. A small count.
Do not sweep a range.Before you leave the device
Ping and Traceroute Guide 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.