By the SNMP Monitoring team · Reviewed July 2026
Straight answers to the questions people actually ask about SNMP — each one direct enough to stand alone, with a link to the page that covers it in full. Use this as a fast reference: skim to your question, get the short answer, and follow the link when you need the depth. Nothing here is padded, and nothing here duplicates a full how-to — the point is a quick, accurate reply and a signpost to more.
Parent: FAQ & reference. Hub: glossary, all sensors.
Basics
What is SNMP? The Simple Network Management Protocol — an IETF standard that lets a manager read (and sometimes change) values on network devices and servers over the network. It's the most widely supported monitoring protocol there is. More on what is SNMP.
What does SNMP stand for? Simple Network Management Protocol. "Simple" refers to the protocol's design, not necessarily its security model — v1/v2c are simple but insecure, while v3 adds real protection. See what is SNMP.
How does SNMP work? A manager sends a request to an agent on the target device; the agent looks up the requested OID and returns its value in a response. Devices can also push unsolicited traps. It's mostly a request/response poll. Details on how SNMP works.
Does SNMP use TCP or UDP? UDP. The agent listens on UDP 161 and traps go to UDP 162. Being connectionless is why an unreachable agent times out rather than refusing a connection. See ports.
Ports and versions
What port does SNMP use? UDP 161 for queries to the agent, UDP 162 for traps to the receiver. Both are UDP. Full detail on ports.
What's the difference between 161 and 162? 161 is where the agent listens for your get/getnext/getbulk/set requests; 162 is where a trap receiver listens for the asynchronous notifications devices push when something happens. One is pull, the other is push. See ports.
Which SNMP version should I use? SNMPv3 wherever possible — it's the only version with authentication and encryption. Use v1/v2c only on a trusted, segmented network with an allowlist. Compare them on versions.
Is SNMPv2c secure? No. v2c authenticates with a cleartext community string and provides no encryption, so anyone who can see the traffic can read the community and the data. It's acceptable only on a trusted network with tight ACLs. For security, use v3 — see security.
OIDs and MIBs
What is an OID? An Object Identifier — a dotted-number address like 1.3.6.1.2.1.1.3.0 that names one specific managed value in the global tree. Every value SNMP can read has one. More on OIDs.
What is a MIB? A Management Information Base — the schema that maps OIDs to readable names, types, and descriptions, so 1.3.6.1.2.1.1.5.0 resolves to sysName. Loading the right MIB is what makes output human-readable. See OIDs.
How do I find the OID I need? Start from a reference of common OIDs, walk the device to see what it exposes, or load the vendor MIB and browse it. The all sensors page is a ready map of the OIDs behind common metrics.
Monitoring and tools
What can SNMP monitor? Interface traffic, CPU, memory, disk, temperature, fans, power, uptime, and much more — across routers, switches, firewalls, servers, printers, UPS units, and NAS. Browse the monitoring cluster for the full range.
What's the best SNMP monitoring tool? It depends on scale and budget — open-source options like LibreNMS and Zabbix, commercial platforms, and external services each fit different needs. The tools comparison weighs them honestly.
How do I test SNMP? Run a simple walk from your manager against the system subtree:
snmpwalk -v2c -c S3cr3tR0str1ng 10.0.0.20 system
SNMPv2-MIB::sysDescr.0 = STRING: Linux web01 5.15.0 ...
SNMPv2-MIB::sysName.0 = STRING: web01
If that returns data, the agent, credentials, and network path all work. See snmpwalk.
What is external SNMP monitoring? Polling your agents from outside your own network so a local outage can't blind your monitoring — a second, independent path. An external service like ostr.io provides that off-box durability; more on external monitoring.
Security
Is SNMP secure? Only SNMPv3 is. v1 and v2c send a cleartext community with no encryption, so they're safe only on a trusted, segmented network. v3 adds authentication and privacy. Whichever version, never expose SNMP to the internet. See security.
Should SNMP be exposed to the internet? No — never. An internet-facing agent is found by scanners within minutes, and on v1/v2c it leaks its data and community in cleartext, and can be abused for amplification attacks. Keep SNMP on a management network behind a firewall. See security.
Top questions (quick reference)
The five most-asked, gathered for scanning:
- What is SNMP? A standard protocol for monitoring devices via a manager/agent model.
- What port? UDP 161 (agent), UDP 162 (traps).
- Which version? v3 for security; v1/v2c only on trusted networks.
- What can it monitor? Interfaces, CPU, memory, disk, environment, and more.
- Is it secure? Only v3; never expose any version to the internet.
And the same facts as a quick-reference card:
| Question | Short answer | Deep page |
|---|---|---|
| What is it? | Simple Network Management Protocol | What is SNMP |
| What ports? | UDP 161 agent, UDP 162 traps | Ports |
| Which version? | v3 (secure); v1/v2c trusted-only | Versions |
| Transport? | UDP (connectionless) | Ports |
| Is it secure? | Only v3; never internet-facing | Security |
Frequently asked questions
What is SNMP?
SNMP (Simple Network Management Protocol) is an IETF-standard protocol for monitoring and managing network devices and servers. A manager queries agents on each device, reading values addressed by OIDs and defined in MIBs. It's the most widely supported monitoring protocol, implemented across virtually all network and server hardware, and it underpins most infrastructure monitoring in use today.
What port does SNMP use?
SNMP agents listen on UDP port 161 for queries, and trap receivers listen on UDP port 162 for asynchronous notifications. Both use UDP rather than TCP, so a request to an unreachable or non-listening agent times out instead of being refused — a distinction that matters when you're diagnosing why SNMP isn't responding.
Which SNMP version should I use?
Use SNMPv3 wherever possible — it's the only version with authentication and encryption, making it the secure choice for any untrusted path. SNMPv1 and v2c authenticate with a cleartext community string and offer no encryption, so limit them to trusted, segmented networks protected by a source-IP allowlist. Never expose any version to the internet.
What can SNMP monitor?
SNMP monitors a huge range of metrics: interface traffic and errors, CPU, memory, disk usage, temperature, fan speed, power, uptime, and many device-specific values, across routers, switches, firewalls, servers, printers, UPS units, and NAS devices. Standard MIBs cover the common metrics uniformly, while vendor MIBs expose hardware-specific data under the enterprise branch.
Is SNMP secure?
Only SNMPv3 is genuinely secure. It provides authentication and encryption through the USM model. SNMPv1 and v2c send a cleartext community string with no encryption, so they're safe only on a trusted, segmented network with tight ACLs. Regardless of version, SNMP should never be exposed to the public internet, where it can be scanned, leaked, or abused for amplification attacks.
Key takeaways
- Each answer here is a quick, accurate reply with a link to the deep page — a fast reference, not a how-to.
- Ports: UDP 161 (agent), UDP 162 (traps); SNMP runs over UDP.
- Versions: use v3 for security; v1/v2c are cleartext, trusted networks only.
- OID addresses a value; MIB defines it — load the right MIB for readable output.
- Test with
snmpwalk … system; add external monitoring for off-box durability. - Never expose SNMP to the internet, regardless of version.