Skip to main content
NETWORKING · NETWORK MANAGEMENT

What Is SNMP?

SNMP (Simple Network Management Protocol) is the standard way to monitor and manage networked devices. A manager polls agents on switches, routers, UPSs and computers for values held in a MIB, such as port status, traffic and temperature, and agents send traps when something changes. It runs over UDP: port 161 for polling, 162 for traps.

01

How SNMP works

SNMP, the Simple Network Management Protocol, is the IETF standard for reading status from network devices and, where allowed, changing their settings. Almost every managed switch, router, firewall, UPS and printer supports it, and so do Windows and Linux computers through an agent service.

There are three parts. The agent is software on the managed device. The manager, often called a network management system or NMS, is the monitoring software that collects the data. The MIB, or management information base, is the catalog of values the agent can report, each named by a numeric object identifier (OID) such as 1.3.6.1.2.1.1.3.0 for the time since the device last restarted.

The manager polls: it sends Get, GetNext or GetBulk requests to UDP port 161 on the agent and receives the values back, typically every one to five minutes. When something important happens between polls, such as a port going down, the agent sends an unsolicited notification called a trap to the manager on UDP port 162. A Set request writes a value, for example to disable a port, if the agent allows write access.

02

SNMPv1 vs SNMPv2c vs SNMPv3

Three versions are in use, and the difference that matters most is security.

Version Defined in Authentication Encryption Main additions Use today
SNMPv1 RFC 1157 (1990) Community string, sent in clear text None Get, GetNext, Set, Trap Legacy devices only
SNMPv2c RFC 1901–1908 (1996) Community string, sent in clear text None GetBulk, 64-bit counters, Inform Widespread, read-only on trusted networks
SNMPv3 RFC 3411–3418 (2002) Per-user, HMAC with SHA AES or DES User-based security and access control Recommended for all new systems

A community string works like a shared password, and the factory defaults “public” for read and “private” for write are widely known. Because v1 and v2c send it in clear text, anyone who can capture traffic can read it. SNMPv3 adds named users with three security levels: noAuthNoPriv, authNoPriv and authPriv. Use authPriv, which both authenticates and encrypts, wherever the devices support it.

03

What SNMP can tell you

Standard MIBs give every vendor’s equipment a common baseline, and private MIBs from each manufacturer add device-specific values. Typical data from a managed switch includes:

  • //
    Port status and traffic. Link up or down, speed, bytes and packets in and out, and error and discard counters, from the IF-MIB (RFC 2863).
  • //
    System information. Device name, location, firmware, uptime and contact, from MIB-II (RFC 1213).
  • //
    Statistics history. RMON (RFC 2819) keeps traffic statistics and alarm thresholds on the switch itself.
  • //
    Power and environment. On many industrial switches, power input status, internal temperature and PoE power drawn per port, through the manufacturer’s private MIB.
  • //
    Redundancy events. Traps when a ring changes state or a redundant link takes over, so the fault is seen even though the network kept running.
04

SNMP on industrial networks

In a plant, SNMP is how the network reports on itself. A redundant ring or backup link keeps production running when a cable is cut, which also means nobody notices the fault unless a trap reaches someone. Pointing every managed switch at a network monitoring server, or at a SCADA package with an SNMP driver, turns a silent failure into an alarm. Our managed industrial switches support SNMP, with SNMPv3 on most models, and many also report status over Modbus TCP so a PLC or SCADA system can read it directly.

Keep SNMP traffic on a management VLAN, allow only the monitoring server to query the agents, turn write access off unless you need it, and change or remove the default community strings. Our guide to choosing between managed and unmanaged industrial switches covers when that monitoring is worth having.

FAQ · 01
How does SNMP relate to out-of-band management?
SNMP usually runs in-band, over the same network it monitors. Out-of-band management gives a separate path, such as a dedicated management port or a cellular link, so a device can still be reached and recovered when the main network is down.
Read the full FAQ —
05

Setting up SNMP monitoring on a new site

A small amount of planning at commissioning saves a lot of guesswork later. The steps below suit most plant networks, whichever monitoring software you use.

  • //
    Decide what you need to know. Usually link state, error counters, power inputs and ring status. Polling every value on every port adds load for little benefit.
  • //
    Create SNMPv3 users. One read-only user for the monitoring server, with authentication and encryption, and no write user unless a tool genuinely needs one.
  • //
    Set trap destinations. Send traps to the monitoring server and, where possible, a second receiver, so an alarm is not lost if one server is down.
  • //
    Load the MIBs. Import the manufacturer’s private MIB files into the manager so values appear by name rather than as bare OIDs.
  • //
    Test the alarms. Pull a cable, remove a power input and confirm each event reaches the right person before the site goes live.
06

SNMP alongside other monitoring protocols

SNMP is rarely the only source of data. Syslog, usually on UDP 514, carries text log messages that explain why something happened, while SNMP reports the counters and states that show what happened. Larger IT networks are adding NETCONF and streaming telemetry for configuration and high-rate data, but on industrial equipment SNMP remains the protocol most devices support, which is why it is still the common baseline across switches, UPSs and computers from different manufacturers.

07

Quick answers on SNMP

SNMP: common questions

What does SNMP stand for?

Simple Network Management Protocol. It is maintained by the IETF, and SNMPv3 is Internet Standard 62.

What port does SNMP use?

UDP 161 for requests and UDP 162 for traps. SNMP over TLS or DTLS, defined in RFC 6353, uses 10161 and 10162.

What is an SNMP trap?

An alert the device sends without being asked. A trap reports an event such as a link going down or a power input failing, so the manager does not have to wait for the next poll.

What is the difference between a trap and an inform?

An inform is acknowledged. A trap is sent once over UDP and may be lost. An inform, added in SNMPv2c, is resent until the manager confirms it.

Is SNMP TCP or UDP?

Normally UDP. Polling is short request-and-response traffic, so the overhead of TCP connections is not needed. TCP transport exists but is rarely used.

We supply managed industrial switches and edge computers with SNMPv3 users, trap destinations and management VLANs set to your monitoring plan as standard, so faults reach your team from the first day of operation.