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 geostationary hop has a large, steady delay. A low-earth constellation has a smaller delay and a path that changes. The calculator drafts a latency figure. It does not buy a service and it does not aim at a satellite.
The question is the application at one site you operate: voice and a desktop VPN will notice GEO. A batch transfer may not. Write the application. Weather and obstruction are still site facts. A rooftop you do not control is not your install.
One site. The failover to a wire, if you have one, is part of the choice. Do not send the company's traffic onto a new path in the reading hour.
This comparison is not a coverage map of someone else's address.
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 site and the application.
- Write the latency each option implies.
- Write whether a wire remains.
- Confirm you may install at the site.
- Do not move production traffic.
- Stop.
Mistakes that outlive the command
Satellite Internet for Business (LEO vs GEO) goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- GEO chosen for interactive voice with no note.
- A rooftop you do not control.
- Production moved during the reading.
- The calculator used as a survey of a neighbor.
Decisions to write down
One decision for Satellite Internet for Business (LEO vs GEO): The site is yours. The application sets the latency need. Install rights are real. Traffic stays on the current path. And no neighbor was surveyed.
Checks before you call it done
Confirm this before you call the change done: The site is named. The latency need is written. LEO or GEO is a recommendation with a reason. The wire failover is named or absent on purpose. And no traffic was moved. If one of those fails, stop.
| Orbit | What you feel | Ask first |
|---|---|---|
| GEO | A long, steady delay | Can the application wait |
| LEO | A shorter delay and a moving path | Does the site have a clear view and a failover |
Before you leave the device
Satellite Internet for Business (LEO vs GEO) 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.