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 troubleshooting checklist is an order: the hostname, the port, the VLAN, the gateway, the path, then the far end. Ping and traceroute are tools for a destination you may test. They are not the first click.
Ask what changed. If nothing is written down, look for the last change anyway. One change is the usual cause. Do not undo three things at once.
The first failed check is the result. Fixing it is a later window unless the fix is obviously the rollback you already saved.
Do not scan the site to see what else is open. Do not open a rule to the world to see if that was it.
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 complaint in one sentence.
- Confirm the port and the VLAN.
- Confirm the gateway address.
- Test one destination you may test.
- Stop at the first failure.
- Write that failure. Do not stack changes.
Mistakes that outlive the command
Network Troubleshooting Checklist goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Three changes at once.
- A scan of the building.
- A world-open rule as a test.
- The complaint left unwritten.
- A reboot of the core as step one.
Decisions to write down
One decision for Network Troubleshooting Checklist: The complaint is one sentence. Checks run in order. You stopped at the first failure. No scan was run. And no emergency any-any rule was added.
Checks before you call it done
Confirm this before you call the change done: The failed check is named. The device name is written. No stacked changes. The rollback, if used, was the saved one. And the next window is one fix. If one of those fails, stop.
Stop at the first failed check.
Do not open the network to test.Before you leave the device
Network Troubleshooting Checklist 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.