tools

Net-SNMP: The Complete CLI Suite Overview

A tour of Net-SNMP — the snmpget, snmpwalk, snmpbulkwalk, snmptable, snmptranslate and snmptrap commands, the snmpd agent, plus install and config pointers.

By the SNMP Monitoring team · Reviewed July 2026

Almost every SNMP command you'll see in a tutorial — including all the ones on this site — comes from Net-SNMP, the open-source suite that's been the de-facto SNMP toolkit on Unix and Linux for decades. It's more than snmpwalk: a dozen query and helper commands, the snmpd agent, and the snmptrapd receiver, all sharing one set of flags and one config format. This overview is the hub — what each tool does and when to reach for it — with links out to the dedicated how-tos rather than repeating them here.

Parent: tools. Deep dives: snmpwalk, snmpget, MIB browser, snmpsim.

What's in the suite

The suite splits cleanly into query tools, helpers, and the agent side:

CommandPurpose
snmpgetRead one specific object
snmpgetnextRead the next object after a given OID
snmpwalkWalk a subtree via GetNext
snmpbulkwalkWalk a subtree via GetBulk (fewer round-trips)
snmptableRender a conceptual table in columns
snmptranslateResolve OID ↔ symbolic name
snmpstatusQuick device health summary
snmptrapSend a trap/notification
snmpd / snmptrapdThe agent and the trap receiver

Learn the query tools first; the helpers and agent tools come in as your needs grow.

What's worth appreciating is how consistent the suite is. Every command shares the same argument grammar — the version flag, the credential flags, the output formatting — so once you can drive snmpget, you can drive snmptable and snmptrap with almost no new learning. That uniformity is a large part of why Net-SNMP became the standard: it's not a dozen unrelated programs but one coherent toolkit with a dozen entry points. The client tools and the snmpd agent even read overlapping configuration, so knowledge transfers from the querying side to the agent side as well.

Querying tools

The four you'll use constantly are the read commands. snmpget fetches one object when you know the OID; snmpgetnext returns whatever comes next, which is the primitive snmpwalk is built on. snmpwalk chains GetNext calls to dump a subtree, and snmpbulkwalk does the same with GetBulk for far fewer round-trips on large tables. As a rule: get for a known single value, walk for discovery or a whole subtree, bulkwalk when that subtree is big and the agent speaks v2c+. The single-object reads are covered in depth on snmpget.

Helper tools

Beyond raw queries, three helpers save real time. snmptable renders a conceptual table — like the interface or storage table — in aligned columns instead of a flat list of indexed rows:

snmptable -v2c -c S3cr3tR0str1ng 10.0.0.20 hrStorageTable

snmptranslate converts between numeric OIDs and names without touching a device:

snmptranslate -On SNMPv2-MIB::sysUpTime.0
.1.3.6.1.2.1.1.3.0

And snmpstatus prints a one-shot health summary — uptime, packets, a couple of key counters — handy as a first look at an unfamiliar host.

Of the three, snmptranslate is the one people underuse. Because it never touches the network, it's the fastest way to answer "what is this OID?" or "what's the numeric form of this name?" without waiting on a device or worrying about credentials. When a dashboard shows you a bare numeric OID you don't recognise, a single snmptranslate call names it instantly. And snmptable turns the genuinely painful task of reading a raw indexed table — where every row is scattered across dozens of ifDescr.1, ifDescr.2, ifSpeed.1, ifSpeed.2 lines — into a clean grid you can actually scan. Both are small tools that disproportionately reduce friction once you know they exist.

The agent (snmpd) & trap tools

The suite isn't only a client. snmpd is the agent — the daemon that listens on UDP 161 and answers queries about the host it runs on; its entire behaviour is driven by snmpd.conf. On the notification side, snmptrap sends a trap to a manager, and snmptrapd is the receiver that listens on UDP 162 and hands incoming traps to a handler. Together they cover both halves of SNMP: the polling you initiate and the asynchronous alerts a device pushes to you.

Common flags

The flags are consistent across every command in the suite, which is what makes it quick to learn:

  • -v 1|2c|3 — SNMP version.
  • -c <community> — community string, for v1/v2c.
  • -u / -l / -a / -A / -x / -X — v3 user, security level, auth protocol/passphrase, privacy protocol/passphrase.
  • -O <opts> — output formatting (-On numeric, -Os short, -Oqv values only).
  • -m / -M — which MIB modules to load, and where to look for them.

Learn these once and they apply everywhere — a v3 walk and a v3 get take the same credential flags.

Installing Net-SNMP

Net-SNMP ships in every mainstream distro's repositories. To get up and running:

  1. On Debian/Ubuntu, install the client tools (snmp) and, if you need the agent, snmpd.
  2. On the RHEL family, install net-snmp (agent) and net-snmp-utils (the client commands) via dnf/yum.
  3. Optionally add the downloadable MIB set so names resolve out of the box.
  4. Confirm with snmpget --version or a quick local snmpwalk.

The step-by-step, including which package holds which binaries and the client-side snmp.conf, is on Ubuntu/Debian setup and CentOS/RHEL setup. Client behaviour can be tuned in ~/.snmp/snmp.conf or /etc/snmp/snmp.conf — for example, default version, default MIBs, and output format, so you're not retyping the same flags.

Frequently asked questions

What is Net-SNMP?

Net-SNMP is the standard open-source SNMP implementation for Unix and Linux. It bundles the command-line client tools (snmpget, snmpwalk, snmpbulkwalk, snmptable, snmptranslate, snmptrap and more), the snmpd agent, and the snmptrapd trap receiver. It's what most SNMP documentation and tooling is built around.

What commands come with Net-SNMP?

The core query tools are snmpget, snmpgetnext, snmpwalk, snmpbulkwalk, and snmpbulkget; helpers include snmptable, snmptranslate, and snmpstatus; and the notification tools are snmptrap and snmptrapd. The snmpd daemon is the agent. All share a common flag set for version, credentials, and output formatting.

What is snmpbulkwalk?

snmpbulkwalk walks a subtree using the GetBulk operation (available in SNMPv2c and later) instead of repeated GetNext calls. GetBulk returns many objects per request, so a large table that would take hundreds of round-trips with snmpwalk completes in a handful. Use it whenever you're walking big tables on a v2c+ agent.

How do I load MIBs in Net-SNMP?

Use -m <MIB> to load a specific module (or -m ALL for everything available) and -M <dir> to add a directory to the MIB search path. Persistent settings go in snmp.conf via mibs and mibdirs. Loading the right MIBs is what lets the tools resolve numeric OIDs to readable names, and it's the usual reason a name won't resolve — the object is fine, the MIB just isn't loaded.

Key takeaways

  • Net-SNMP is the standard Unix/Linux SNMP suite — client tools, snmpd agent, and snmptrapd.
  • Query tools: snmpget (one object), snmpwalk (subtree), snmpbulkwalk (big tables).
  • Helpers: snmptable, snmptranslate, snmpstatus.
  • Agent side: snmpd (driven by snmpd.conf) and snmptrap/snmptrapd for notifications.
  • Flags are consistent: -v, -c, the v3 -u/-l/-a/-A/-x/-X, -O output, -m/-M MIBs.
  • Install via apt or dnf; tune the client in snmp.conf.

Monitor it from outside the network

SNMP only tells you a box is healthy while something is still asking. ostr.io polls your endpoints externally and fires email + SMS alerts the moment a reading crosses your line — or the agent goes silent.