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 TCP connection is a handshake, a transfer, and a close. The states have names. The explorer shows a state you select. It does not connect anywhere.
SYN, established, and a close wait are enough for a first ticket. A pile of half-open connections is a symptom you count, not a thing you answer by disabling the service.
Write the state you saw and the count. Do not paste a capture of someone else's session. A lab client you started is the example.
The port and the application belong in the sentence so the state is not a bare word.
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 service.
- Start a lab connection you own, or read a counter you already have.
- Name the state.
- Write the count.
- Do not disable the service as the first move.
- Stop.
Mistakes that outlive the command
TCP Three-Way Handshake and Connection States goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A state with no service named.
- A capture of a session you do not own.
- The service disabled to clear a counter.
- Half-open connections described as an attack plan.
Decisions to write down
One decision for TCP Three-Way Handshake and Connection States: The service is named. The state is a real name. The count is a number. The example is yours. And nothing was disabled.
Checks before you call it done
Confirm this before you call the change done: State and count are in the ticket. The service is a word. No foreign session was captured. No service was disabled. And the next step is capacity or a bug, named as such. If one of those fails, stop.
Name the state and the service.
Use a connection you started.Before you leave the device
TCP Three-Way Handshake and Connection States 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.