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 static route is a prefix and a next hop you type. A dynamic protocol learns routes from neighbors. The generator drafts a static route. It does not install it. Dynamic routing is the pillar's design, not a command you paste because the comparison felt unfinished.
A static default is still a default. 0.0.0.0/0 stays out unless the ticket already names that path and you delete every wider sample. Prefer a prefix you can say. Documentation prefixes are the example.
One path. The next hop has to be a router you administer or the provider hop you were given. Do not point a static route at a device you do not know.
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 prefix and the next hop.
- Say why it is static or dynamic.
- Delete 0.0.0.0/0 if the ticket did not name it.
- Do not install the route.
- Do not start a protocol.
- Stop.
Mistakes that outlive the command
Static vs Dynamic Routing goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A default kept from a sample.
- A next hop you do not administer.
- Starting OSPF or BGP to finish the comparison.
- A documentation prefix installed on production.
- Two paths in one window.
Decisions to write down
One decision for Static vs Dynamic Routing: The prefix is yours. The next hop is known. Dynamic, if chosen, waits for its own page. Nothing was installed. And no protocol was started.
Checks before you call it done
Confirm this before you call the change done: The prefix is written. The next hop is written. Static or dynamic is one sentence. No route was installed. And no neighbor was added. If one of those fails, stop.
| Choice | What you write |
|---|---|
| Static | One prefix, one next hop, no neighbor. |
| Dynamic | A protocol and a neighbor you administer. Not this hour's paste. |
| Default | Only if the ticket named it. A sample 0.0.0.0/0 is deleted. |
Before you leave the device
Static vs Dynamic Routing 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.