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
SNMP reads counters from a device you operate. Version 1 and 2c use a community string that is a password. Version 3 uses a user. The command builder and the user generator draft text. They do not poll a device until you run something, and you run it only against your device.
The community or the password is prompt-for-this in the note. A string of public or private is a string you replace. The allowed source is the monitor, not the world.
Write the version and the source prefix. Do not enable SNMP on an internet-facing interface to see if the graphs appear.
A walk of every object is rarely the ticket. One counter is the proof.
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 device and the monitor.
- Choose version 3 unless the ticket says the device cannot.
- Draft a user or replace the community.
- Set the source to the monitor.
- Keep the secret out of the ticket.
- Do not poll a device you do not run.
Mistakes that outlive the command
SNMP Explained (v1, v2c, v3) goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Community public on any interface.
- SNMP opened on the WAN.
- A secret in the note.
- A walk of a device you do not administer.
- Versions enabled that you do not need.
Decisions to write down
One decision for SNMP Explained (v1, v2c, v3): The version is written. The source is the monitor. The secret is not in the note. The device is yours. And one counter is enough proof later.
Checks before you call it done
Confirm this before you call the change done: Version and source are in the ticket. No default community remains. No WAN exposure. No foreign device was polled. And the secret is in the store. If one of those fails, stop.
Version 3 when you can.
The monitor is the source. Not the world.Before you leave the device
SNMP Explained (v1, v2c, v3) 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.