Your monitoring system suddenly shows a router as "SNMP unavailable", a newly deployed switch never appears in the NMS, or you have just moved an agent to SNMPv3 and are not sure the credentials match. SNMP problems are awkward to debug because a device that does not like your request usually says nothing at all.
The SNMP Diagnostic tests whether a device you manage answers SNMPv1, SNMPv2c or SNMPv3 from the internet, reads its standard system information (name, description, object ID, uptime, location, contact, services), measures response times and lets you read single OIDs. Everything it sends is a read-only GET request.
What is SNMP?
In simple terms
SNMP, the Simple Network Management Protocol, is how monitoring systems ask routers, switches, firewalls, servers, printers and UPS systems for status information: "what is your name?", "how long have you been running?", "how many bytes went through this interface?". The device runs an SNMP agent that answers on UDP port 161. Each piece of information has a numeric address called an OID (object identifier), for example 1.3.6.1.2.1.1.5.0 for the device name.
Technical background
SNMP messages are encoded in ASN.1 BER and carry a PDU (protocol data unit) such as GetRequest, Response or Report. The objects are described in MIBs; the tool reads the system group of SNMPv2-MIB (RFC 3418):
| Object | OID | Content |
|---|---|---|
| sysDescr | 1.3.6.1.2.1.1.1.0 | Free-text description, usually hardware and software version |
| sysObjectID | 1.3.6.1.2.1.1.2.0 | Vendor's identification OID, under 1.3.6.1.4.1 followed by the IANA enterprise number |
| sysUpTime | 1.3.6.1.2.1.1.3.0 | TimeTicks (1/100 s) since the agent (re)started |
| sysContact | 1.3.6.1.2.1.1.4.0 | Contact person, as configured |
| sysName | 1.3.6.1.2.1.1.5.0 | Administratively assigned name |
| sysLocation | 1.3.6.1.2.1.1.6.0 | Physical location, as configured |
| sysServices | 1.3.6.1.2.1.1.7.0 | Bit mask of the OSI layers the device offers services on |
The three versions differ mainly in security:
- SNMPv1 and SNMPv2c authenticate with a community string sent in plain text. SNMPv2c adds better error reporting (
noSuchObject,noSuchInstance) and 64-bit counters; in SNMPv1 one unknown object fails the whole request withnoSuchName. - SNMPv3 uses the User-based Security Model (USM, RFC 3414): a username, a security level (noAuthNoPriv, authNoPriv, authPriv), HMAC message authentication (MD5 and SHA-1 in RFC 3414, SHA-2 in RFC 7860) and optional AES encryption (RFC 3826). Before an authenticated request, the manager discovers the agent's engine ID, boot counter and engine time; keys are derived from the passwords and localised to that engine ID, and messages outside the agent's time window are rejected.
Why use the SNMP Diagnostic?
- Separate "agent down" from "credentials wrong". For SNMPv3 the tool shows whether engine discovery succeeded, which proves an agent is listening even when the authenticated request fails, and it names USM errors such as an unknown user or a wrong authentication key.
- Test from outside your network. It shows what a cloud-hosted monitoring system or an external NMS sees, not what works from the management VLAN.
- Verify an SNMPv3 migration. Check username, security level and protocols against the device before rolling the change out to the monitoring platform.
- Identify a device. sysDescr, sysObjectID with the vendor's enterprise number and sysServices tell you what answered.
- Spot unwanted exposure. If a device answers SNMP from the internet with a community string, that is a finding in itself.
Who should use it?
Network engineers and system administrators who run SNMP-monitored equipment, monitoring and NOC teams integrating devices into an NMS, and MSPs checking customer devices they are contracted to administer. It is not a scanner: use it only for devices you own or are authorized to administer.
How the SNMP Diagnostic works
The browser sends the form to the NetTools.tech API; the SNMP requests themselves are sent from the NetTools server in Latvia by its own SNMP implementation (a small BER encoder/decoder and USM code, no external SNMP library).
- Validation. The target must be an IP address or hostname. The port must be 161 or 1024–65535; other well-known ports belong to other services and are refused, so the tool cannot be pointed at arbitrary UDP services. Community strings must be 1–64 printable ASCII characters, SNMPv3 usernames 1–32, SNMPv3 passwords 8–64 characters.
- Resolution and guard. The hostname is resolved once and checked by the same public-address guard as the other network tools: private, loopback, link-local and reserved addresses are refused, and the resolved IP is pinned for the whole test so DNS rebinding cannot redirect it. IPv6 targets are refused because the probe server has no IPv6 connectivity yet.
- SNMPv3 discovery (v3 only): an unauthenticated GetRequest with an empty user, which the agent answers with a Report carrying its engine ID, engine boots and engine time. Keys are then derived per request from your passwords and that engine ID.
- Probes: 1–3 GETs of
sysUpTime.0, one after another, to measure response time. If the first probe gets no answer, the test stops there instead of sending more. - System read: one GET of the seven system-group objects. With SNMPv1, an object the agent does not know is removed and the request repeated.
- OID query (on request): one GET of the OID you enter, with the same credentials.
Responses are accepted only from the target address and only with the matching request or message ID; other datagrams are ignored. SNMPv3 responses at authNoPriv or authPriv must carry a valid HMAC before their content is used, and encrypted responses are decrypted with the localised privacy key. If the agent reports "not in time window", the tool re-synchronises from that report and retries once.
Limits (SNMP_LIMITS on the server):
| Limit | Value |
|---|---|
| Timeout per request | 1, 2, 3 (default) or 5 seconds |
| Probes | 1–3 (default 3) |
| Maximum test duration | 35 seconds, then the test is stopped |
| Tests per device (all users) | 15 per 10 minutes |
| Different devices per visitor | 6 per hour |
| Different credential sets per device and visitor | 4 per hour |
| Concurrent tests on the server | 6 |
The credential limit exists so that the tool cannot be used to guess community strings or passwords; it compares a keyed hash of the credentials, not the credentials themselves.
The SNMPv3 key derivation was checked against the test vectors in RFC 3414 appendix A.3, and interoperability was verified against the public PySNMP test agent (demo.pysnmp.com) with SNMPv1, SNMPv2c and SNMPv3 using MD5 and SHA, with and without AES.
How to use the NetTools.tech SNMP Diagnostic
Open the SNMP Diagnostic and fill in the form:
- Device (IP address or hostname): the public address or name of the device, for example
router.example.com. - UDP port:
161unless the agent was moved to a port from 1024 to 65535. - SNMP version: SNMPv1, SNMPv2c (default) or SNMPv3.
- Credentials:
- For v1/v2c, the Community string as configured on the device.
- For v3, the Security level (authPriv, authNoPriv or noAuthNoPriv), Username, and depending on the level the Authentication protocol (SHA-256, SHA-512, SHA-384, SHA-224, SHA (SHA-1) or MD5) with Authentication password, and the Privacy protocol (AES-128; DES is listed as not available on this server) with Privacy password.
- Show reveals a secret field while you type.
- Advanced (optional): Timeout per request (1, 2, 3 or 5 s) and Probes (1, 2 or 3).
- Tick I own this device or am authorized to administer it. The test does not start without it.
- Click Test SNMP. Cancel stops a running test; Clear credentials empties the secret fields.
- If the device answered, the Read-only OID query panel appears below the results. Enter a numeric OID (2–64 arcs, first arc 0–2, a leading dot is accepted) or click an example (
1.3.6.1.2.1.1.1.0,1.3.6.1.2.1.1.3.0,1.3.6.1.2.1.1.5.0) and click Read OID. - Export with CSV, JSON, Copy all or Print.
The page URL is updated to hold only the target, the port (if not 161) and the version, such as /snmp?target=router.example.com&version=v3, so you can bookmark the test without exposing credentials.
Tip
If your device only accepts SNMP from your monitoring hosts, add the NetTools server temporarily to the access list for the test and remove it afterwards.
Understanding the results
Status and summary
| Result | Meaning | What to look for |
|---|---|---|
| Banner SNMP Reachable | A valid SNMP response arrived; shows the average response time | Green banner plus device cards |
| Banner No SNMP Response | No SNMP response received within the configured timeout | Not proof that the port is closed (see Troubleshooting) |
| Other banners | Network unreachable, UDP port unreachable, Authentication failed, Unknown SNMPv3 user, Access denied, Security level not supported, Outside the time window, Decryption failed, Protocol not supported here, Malformed response | The explanation text names what to check |
| KPIs | SNMP version (and v3 level), target with resolved IP and UDP port, response time with min/max, requests answered / sent, test time (UTC) | A few unanswered requests among answered ones point at loss or a slow agent |
| Protocol status: Network | The device answered, ICMP reported the host, unreachable, or unknown | "No answer — unknown" is honest: silence proves nothing |
| Protocol status: SNMP | Valid responses, engine discovered (v3), no agent on this port, or not confirmed | "Engine discovered" means an SNMPv3 agent is running |
| Protocol status: Authentication | Community accepted, the v3 protocols verified, not used (noAuthNoPriv), the USM error, or not confirmed | — |
| Protocol status: System MIB | How many of the 7 system objects were read | Fewer usually means a restricted view |
| Protocol status: OID query | Last OID read, its error type, or not run | — |
Device, availability and uptime
| Result | Meaning | What to look for |
|---|---|---|
| Device card | sysName, sysDescr, sysObjectID with the enterprise number (labelled for a small built-in list of vendors such as Cisco, Juniper Networks, MikroTik, Net-SNMP), location, contact, sysServices decoded into layers | "not set" for name, location or contact means the field is empty on the device |
| Services | sysServices value and the layers it sets: physical, datalink/subnetwork, internet, end-to-end, applications | A switch typically sets layer 2, a router layer 3 |
| Availability card | Reachability, average response time and number of successful probes, version and level, time of the last successful response | — |
| Uptime card | sysUpTime as days, hours and minutes, raw ticks, an estimated "agent running since" time, and a bar showing how far the counter is into its 497-day range | The counter wraps after about 497 days, and it measures the agent, not necessarily the hardware |
| System information table | OID, name, type and value of each system object | "Not available on this device / not in the view" for noSuchObject or noSuchInstance |
Timing and technical details
| Result | Meaning | What to look for |
|---|---|---|
| Response time bars | One bar per probe with its time in ms, ✕ for a probe without an answer | Large variation between probes |
| Last, min / avg / max | Probe statistics | — |
| Tests in this session (not stored) | Up to 10 earlier tests on this page: time, target, version, result, average response | Kept in memory only; gone when you reload |
| SNMP response details (technical) | Version, transport, timeout, start and finish time; for v3 the security level, protocols, authoritative engine ID and engine boots / time; then every exchange with request PDU and OIDs, response PDU and OIDs, error status / index and time | Engine boots that increase often indicate agent restarts |
Below the results, buttons open Ping, Traceroute, MTR, Port Check, IP Lookup and, for a hostname, Nslookup with the same target.
Example: SNMPv2c test of a router
The following values are illustrative, made up for this guide on a documentation address; your device's output will differ.
Target router.example.com, resolving to 203.0.113.10, UDP port 161, SNMPv2c with the community configured on the router, default timeout of 3 s and 3 probes:
SNMP Reachable — SNMPv2c answered in 23.4 ms on average.
Response time 23.4 ms (min 21.8 · max 25.9 ms)
Requests 4 / 4 answered · 0 without answer
sysDescr OCTET STRING Linux router 6.1.0 x86_64
sysObjectID OBJECT IDENTIFIER 1.3.6.1.4.1.8072.3.2.10 (enterprise 8072, Net-SNMP)
sysUpTime TimeTicks 42 days 8 hours 12 minutes (365834500 ticks)
sysContact OCTET STRING [email protected]
sysName OCTET STRING router.example.com
sysLocation OCTET STRING Rack B2
sysServices INTEGER 6 (datalink/subnetwork, internet)Four requests: three sysUpTime probes and one system-group GET. The sysServices value 6 sets the bits for layers 2 and 3. A follow-up Read OID of 1.3.6.1.2.1.1.5.0 would return the same sysName as a single-row table.
The same test with a mistyped community would end after the first probe with No SNMP Response, 1 request sent and 0 answered, and the note that a wrong community string cannot be distinguished from a firewall or a disabled agent.
Common use cases
- Onboarding a device into monitoring: confirm it answers with the intended version and credentials before adding it to the NMS.
- SNMPv3 rollout: test each combination of user, level and protocols and read the USM error if one fails.
- Checking external exposure: verify that a firewall really blocks SNMP from the internet (expect No SNMP Response) or that only SNMPv3 works.
- Reboot investigation: read sysUpTime and engine boots to see whether the agent restarted recently.
- Reading one value: fetch a single scalar OID such as sysName or a vendor object without installing
snmpget.
Troubleshooting
"No SNMP Response"
No SNMP response received within the configured timeout. Possible causes: a wrong community string (v1/v2c agents stay silent), a source-address ACL on the agent that does not include the NetTools server, a firewall dropping UDP 161, the agent disabled or bound to another interface, or the wrong port. Check the community and the ACL first, try a longer timeout for slow devices, and use Port Check or Ping only to confirm the host itself is reachable (they test TCP and ICMP, not SNMP). Do not conclude that the port is closed.
SNMPv3: discovery answered, authenticated request not
The note says the agent answered SNMPv3 engine discovery, so SNMP is running, but the authenticated request was not answered. Recheck the username, security level and both protocols; some agents silently drop requests they cannot authenticate instead of sending a report.
"Authentication failed", "Unknown SNMPv3 user", "Decryption failed"
These are USM reports from the agent (or a response whose HMAC did not verify). Authentication failed points at the authentication protocol or password, Decryption failed at the privacy protocol or password, Unknown SNMPv3 user at the username. Passwords are case-sensitive and must be at least 8 characters.
"Security level not supported"
The user exists but is not configured for the chosen level, for example authPriv for a user without a privacy key. Choose the level configured on the device.
"Protocol not supported here"
DES privacy was selected. The NetTools server cannot use DES; configure AES-128 for the user on the device.
"Access denied"
The agent accepted the credentials but returned authorizationError or noAccess: the view or access configuration does not allow these objects.
"UDP port unreachable" or "Network unreachable"
Port unreachable means the host answered with an ICMP port-unreachable message, so nothing listens on that UDP port; check the port and whether the agent runs. Network unreachable means no route to the target; continue with Traceroute.
Validation and rate-limit messages
"Use port 161 or a port from 1024 to 65535", private-address refusals, the IPv6 message and "Rate limited" (too many tests of one device, more than 6 devices per hour, or more than 4 different credential sets per device per hour) are safeguards. Wait before retrying.
Common mistakes
- Reading silence as "closed". UDP and SNMP give no answer for many different reasons.
- Testing a private address.
10.x,192.168.xor an internal hostname cannot be reached from the NetTools server; test the device's public address, or test from inside your network with your own tools. - Mixing up auth and privacy protocols. Both must match the device exactly, including SHA-1 vs SHA-256.
- Trying many communities. The tool limits different credential sets per device; it is not meant for guessing and will lock you out for an hour.
- Treating sysUpTime as hardware uptime. It is the agent's uptime and wraps after about 497 days.
- Leaving SNMP open after testing. Remove any temporary ACL entry for the NetTools server.
Limitations
- Read-only GET only: no SET, no walks, no GETNEXT/GETBULK, no table reads, no traps. The OID query reads exactly one object.
- Public IPv4 targets only: no private networks, no IPv6 at the moment.
- One vantage point: the NetTools server in Latvia; ACLs or routing may treat your monitoring hosts differently.
- Silence is ambiguous: without a response the tool cannot tell a wrong community from a firewall or a disabled agent.
- Privacy protocols: AES-128 only; DES is unavailable on this server, AES-192/256 are not offered.
- System data is self-reported: sysDescr, sysName, location and contact are whatever the device is configured to say. The vendor label covers only a short list of enterprise numbers.
- Response times are measured at the application level on the server and include the agent's processing time.
Security & privacy
This tool needs credentials, so it handles them narrowly: the community string or SNMPv3 passwords are sent in the body of the request to the NetTools.tech API, used to build the SNMP messages (SNMPv3 keys are derived on the server for this test only) and then discarded. They are never stored, logged, exported or put in the URL; the request log records the target only, and the result returned to the browser contains no secrets. Exports also omit the SNMPv3 username. The browser clears the secret fields when you leave the page, including when it is restored from the back/forward cache, and the session history keeps only target, version, result and timing in memory.
Even so, prefer a dedicated read-only SNMPv3 user or community for tests, change it afterwards if you used a production credential over the internet, and never enter credentials for devices you do not administer. SNMPv1/v2c communities cross the internet in plain text between the NetTools server and your device; SNMPv3 with authPriv avoids that. See the privacy policy.
Related tools
- Ping – check that the host answers ICMP; guide.
- Port Check – test a TCP service on the same host; guide.
- Traceroute – find where the path to an unreachable device ends; guide.
- MTR – loss and latency per hop for slow or flaky SNMP responses; guide.
- IP Lookup – network and owner of the device's address; guide.
- Network diagnostics overview.
Summary
The SNMP Diagnostic sends read-only SNMP GET requests from the NetTools server to a public device you manage: SNMPv3 engine discovery if needed, up to three sysUpTime probes and one read of the system group, plus single OID reads on request. It reports response times, the system information and specific USM or protocol errors, and treats an unanswered request as exactly that. Credentials are used for the test only, and private, reserved and IPv6 targets are refused.
Frequently asked questions
Why does a wrong community string show "No SNMP response"?
SNMPv1 and v2c agents silently drop requests with a community string they do not know, so from the outside this looks exactly like a firewall, an access list or a disabled agent. The tool therefore reports that no SNMP response was received within the configured timeout and never claims the port is closed.
Which SNMPv3 protocols does the tool support?
Authentication with HMAC-MD5, HMAC-SHA (SHA-1), SHA-224, SHA-256, SHA-384 and SHA-512, and privacy with AES-128. DES privacy is refused before anything is sent because the server's crypto library no longer provides it, and AES-192/256 are not offered because devices implement two incompatible key-extension variants.
Can I test a device on my private network or LAN?
No. The test runs from the NetTools.tech server on the internet and only contacts public addresses. Private, loopback, link-local and reserved ranges, and hostnames that resolve to them, are refused to protect internal networks.
Does the SNMP test support IPv6?
Not at the moment. The NetTools probe server has no IPv6 connectivity yet, so an IPv6 target is refused with an explanation instead of timing out; test the device's IPv4 address instead.
Does the tool change anything on the device?
No. The client only builds GetRequest PDUs: there is no code for SET, GETNEXT, GETBULK or walks. It reads a fixed set of system objects and, if you ask for it, one OID that you enter.
Is my community string or SNMPv3 password stored?
No. Credentials travel in the body of the request to the NetTools server, are used only for that test and are never stored, logged, exported or put in the URL. The result the server returns contains no credentials, exports also leave out the SNMPv3 username, and the browser clears the fields when you leave the page.
Why does sysUpTime show less time than the device has been running?
sysUpTime counts hundredths of a second since the SNMP agent was (re)started, which is often but not always the device boot. It is a 32-bit TimeTicks value, so it also wraps back to zero after about 497 days.
Should SNMP be reachable from the internet?
Generally no. Expose SNMP only to your monitoring systems, restrict it with access lists and prefer SNMPv3 with authentication and encryption. If you want to test from outside, allow the NetTools server temporarily and remove the rule afterwards.