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 site survey records signal and interference where clients will stand. The CSV analyzer reads a file you export from a survey you were asked to do. It does not scan a neighborhood and it does not map people.
Walk only the floors you have permission to walk. A reading through a wall into a tenant you do not serve is not your cell. Write the access point names that match your controller.
One floor or one building in the ticket. The output is a list of weak spots, not a configuration push. Placement changes are a later visit.
Do not raise power during the survey to paint a greener map.
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.
- Confirm the site is yours to survey.
- Export one floor.
- Read the weak spots.
- Match the names to your access points.
- Do not survey a neighbor.
- Do not move radios yet.
Mistakes that outlive the command
How to Do a Wi-Fi Site Survey goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A survey of a building you do not administer.
- Power raised to color the map.
- Names that do not match the controller.
- A file that includes client identities you were not asked to hold.
Decisions to write down
One decision for How to Do a Wi-Fi Site Survey: The site is permitted. One floor is the scope. Weak spots are written. Names match. And no neighbor was surveyed.
Checks before you call it done
Confirm this before you call the change done: The floor is named. The file was read. Weak spots are listed. Power was not raised. And no configuration was pushed. If one of those fails, stop.
Before you leave the device
How to Do a Wi-Fi Site Survey 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.