Solution · SNMP

SNMP monitoring where the counters already have names


The switch's counters show up as 1.3.6.1.4.1.9.9.…, and nobody sets a threshold on a dotted number without looking it up first. SysPeep ships the lookup.


Key points

  • SNMP v2c and v3 polling with instance walks and interface scans; v1 and v2c traps and v2 informs received.
  • A compiled MIB set beside the service names walked OIDs, types and enumerations for the standard IETF and IEEE modules and for Cisco, Juniper, Arista, Fortinet, Palo Alto, HPE, Dell, APC, MikroTik and Synology, among others: about 2.2 million objects in 14,400 modules.
  • Upload a device's own MIB files for what the set does not know; uploads take precedence and are compiled again at every start.
  • Sensors are unlimited per device, so the fortieth counter on a switch costs the same as the first.
  • Up to 5 devices free at full depth, for as long as you like.

On this page: Polling MIBs and names Interfaces Traps and informs How the poller behaves Learn SNMP


SNMP is how most monitoring asks a network device about its health, and it is also the part of monitoring most likely to be half-configured: the right community string on the wrong version, a vendor MIB nobody could find, a threshold set on a counter that turned out to be the wrong instance. SysPeep's SNMP support was built by people who had done all of that, and it is designed so that the common cases need no lookup at all.


Polling: v2c and v3, walks and scans


What SysPeep doesWhat it means on call
SNMP v2c and v3 polling, with instance walks and interface scansInterface utilization and error rates, routing, device health, printers, firewalls and VPN concentrators, in one view with per-interface trend history
Per-instance sensors: one sensor for a set of interfaces, volumes or services, whose status is the worst instance's and whose value is the worst, the total, or "2 of 9 failing" as the type demandsOne failing interface among nine is reported as the problem, not averaged away, and each instance is its own chart line
Test before Add: every catalog sensor is tested against the device before it is added, and a card names which credential the test will useNo more guessing whether a failed test used the device's community or the global default
Discovery runs continuously after the first sweep; every sensor is offered on every device, and the ones discovery did not detect are marked, with whyA protocol the sweep missed is still one click away, with what was recorded and when

MIBs: named out of the box, plus your own


A compiled MIB set installed beside the service names walked OIDs, types and enumerations for the standard IETF and IEEE modules and for the common network vendors, about 2.2 million objects in 14,400 modules. A vendor's counters are picked by name instead of by a dotted number, usually without finding and uploading a MIB first.


For a device the set does not know, upload its own MIB files. The names appear, missing dependencies and duplicates are reported, uploads take precedence over the bundled set, and they are kept and compiled again at every start, so an upgrade does not lose them. The same names are used for traps, so a trap from a known vendor reads as words.

Named out of the box

  • IETF and IEEE standard modules
  • Cisco, Juniper, Arista
  • Fortinet, Palo Alto
  • HPE, Dell, APC
  • MikroTik, Synology, and others
  • Your uploads, with precedence
Monitoring a device thoroughly costs exactly what monitoring it badly costs: licensing counts devices, and sensors are unlimited.

Interfaces, with the names the device uses


Interface scans find every port on a switch and keep per-interface trend history. Two predefined sensors turn interface use in and out into a threshold in percent of the link speed the device reports, seeded with a warning at 80%, so a saturating uplink alerts like anything else without a bandwidth figure typed in per interface. When a monitored device starts exporting NetFlow, sFlow or IPFIX, its interfaces are scanned automatically so that the Flows page shows "ifIndex 14" as the uplink's real name. Adding the thirtieth interface on a switch you already monitor adds nothing to the license.


Traps and informs


The same service receives SNMP v1 and v2c traps and v2 informs, beside syslog lines and Windows event log subscriptions. Rules turn them into alerts by kind, application and severity, and a built-in tester shows which rule wins for a given event. The syslog and trap receiver page covers the event side in full. The traps versus polling guide in the library explains what belongs in each channel.


How the poller behaves when a device does not


A clock grid, not a queue

Polling runs on a fixed 30-second cycle; intervals are whole cycles from 30 seconds to a day. Sixteen collection workers by default (adjustable from 1 to 64) keep one session per device and method, so one slow switch never delays the readings of the rest of the estate.

Honest when it overruns

The cycle waits at most 25 seconds; a slow device keeps collecting in the background and a hung one delays only its own sensors. When a poll takes longer than its interval, the chart and the device row say so in plain words, with the advice to lengthen it. A missed poll is a red gap on the graph, never a flat line pretending to be data.


Security note. SNMP v3 with authentication and privacy is supported for polling, and the library's securing SNMP guide explains why the default community string on a v2c device is the first thing an attacker tries. Device credentials in SysPeep are encrypted with AES-256-GCM under a key kept in the installation's own data folder, never in the configuration file.


Learn SNMP before you deploy it


The library's SNMP monitoring guides cover the protocol from the ground up: v1 versus v2c versus v3, OIDs and MIBs, an snmpwalk tutorial, traps versus polling, securing SNMP, enabling it across the device zoo and troubleshooting when the numbers are missing or wrong. They are vendor-neutral and long enough to teach the subject.


Questions administrators ask about SNMP


What is the management information base (MIB) in SNMP, and do I have to download MIBs?

The MIB is the catalogue of everything a device can be asked about, as a tree of named objects, each with a numeric OID. Usually you do not have to download anything: a compiled MIB set beside the service already names the standard IETF and IEEE modules and the common vendors' counters, about 2.2 million objects. You download a vendor's MIB files only for a device the set does not know, and upload them in the console.


Where do I download SNMP MIBs for an unknown device, and what MIB file format does it accept?

From the device vendor's support site, usually as a bundle of interdependent files in SMI text format, which is the MIB file format every tool accepts. Upload the bundle; SysPeep compiles it at every start, reports missing dependencies and duplicates, and lets your uploads take precedence over the bundled set.


What port does SNMP use, and which ports do I open for polling and traps?

Polling goes to UDP port 161 on the device; traps come back to UDP port 162 on the SysPeep server or the probe. Allow 161 outbound from the monitor to the devices and 162 inbound from the devices to the monitor. SNMP v3 uses the same ports. Quick Start offers the trap listener's firewall rule on the Windows server.


Does it receive SNMP traps on Windows, and do I need the Windows SNMP trap service?

SysPeep's own service listens for v1 and v2c traps and v2 informs on port 162; the Windows SNMP Trap service is not needed and should be stopped so it does not compete for the port. Traps are named through the same compiled MIB set as polled counters and turned into alerts by rules.


Does it monitor Windows 11, Windows Server 2012 and newer over SNMP, or over WMI?

Over WMI by default, because Windows exposes far more that way with nothing to install, and over SNMP as well if the Windows SNMP service is enabled on the host. The Windows SNMP service itself can be monitored as a service sensor like any other.


What are SNMP community names, and where do I enter them?

A community name (community string) is the shared password of SNMP v1 and v2c, sent in clear text, so it should be read-only, changed from the default, and restricted on the device to the monitor's address. In SysPeep it lives in a credential, encrypted under a per-install key, assigned per device or as a default, and every test names which credential it used.


What is the SNMP engine ID, and when does it matter?

In SNMP v3, every agent has an engine ID that the manager discovers on first contact and uses in authentication. It only matters when two devices share one, usually because a configuration was cloned, and the symptom is v3 polling that works on one of the twins and fails on the other.


Is there an SNMP OID lookup and a MIB browser in the console?

Yes. The catalog shows a device's counters by name with their OID, type and units from the compiled set, and walked OIDs that the set knows are translated as they arrive, so an OID lookup is a search rather than a trip to a website. An SNMP OID list for a device is what the catalog is.


Does it use SNMP GET, GETNEXT and GETBULK (bulk walk)?

GET for single objects, instance walks for tables, and GETBULK on v2c and v3 so an interface table is read in a few packets rather than hundreds. Polling runs on a 30-second clock grid with parallel workers, and a slow device delays only its own sensors.


Does it support IF-MIB, HOST-RESOURCES-MIB, ENTITY-MIB and the other standard SNMPv2 MIBs?

The standard IETF modules are in the compiled set, so interface counters, host resources (storage, processes, CPU on hosts that run an SNMP agent), physical entities and the rest are named out of the box, beside the vendor modules for Cisco, Juniper, Arista, Fortinet, Palo Alto, HPE, Dell, APC, MikroTik and Synology.


Can it monitor HPE iLO, Dell iDRAC and APC PowerNet devices over SNMP?

Server management controllers answer SNMP and, better, IPMI and Redfish, which SysPeep uses for hardware health while the operating system is down. APC UPSes and PDUs with a network management card speak SNMP through the PowerNet MIB, which is in the compiled set.


Is there an SNMP manager download for Windows, and how do I check that SNMP is enabled on a device?

SysPeep is the SNMP manager; the installer is the download. Test before Add runs the sensor against the device with a named credential and tells you whether SNMP is enabled and answering, which is faster than reading the device's status page. The setup cookbook covers enabling it per device type.


SMTP vs SNMP: which one does monitoring use?

SNMP, the Simple Network Management Protocol, reads counters from devices. SMTP, the Simple Mail Transfer Protocol, sends email, which is how SysPeep delivers notifications and how its mail-flow sensors test a mail server. The acronyms collide; the jobs do not.


Can I script SNMP checks with PowerShell, and does it keep SNMP log files?

A script or command sensor turns whatever PowerShell prints into a reading, so a bespoke SNMP check can live beside the built-in ones. Failed polls are recorded on the device as events with the reason (timeout, no such object, authentication failure), on the events timeline rather than in a log file nobody reads.


Does it poll Ubiquiti and other vendor-specific MIBs?

Vendor modules for the common network vendors are compiled in; for others, including Ubiquiti and the many small vendors, upload the device's MIB files and the counters are named. Devices with no useful MIB are still monitored by the standard interface and host counters.


How do I configure SNMP on Linux hosts, and check the SNMP status on Linux?

Install and enable the host's SNMP agent with a read-only v2c community or a v3 user restricted to the monitor's address, or skip SNMP and let SysPeep read the host over SSH. The setup cookbook has the per-platform steps and the verification commands.


Using SNMP to monitor servers, NAS devices and hardware: Synology, Dell, HPE, UPS and PDU devices

A server's SNMP agent exposes HOST-RESOURCES-MIB (storage, processes, CPU); a Synology or other NAS exposes its own MIB for disks, volumes and temperatures; server management controllers and UPS or PDU network cards expose hardware health. Each is one device with unlimited sensors, named through the compiled MIB set or an uploaded MIB file; traps from any of them are received as well.


Do I need to install Net SNMP on Windows, and how do I know the SNMP status is enabled?

No: Windows is monitored over WMI, and SysPeep itself is the SNMP manager. If you want a Windows host to answer SNMP as well, enable the built-in Windows SNMP service rather than a third-party agent. An SNMP connection test, Test before Add, tells you whether the agent on any device is enabled and answering with the credential you chose.


Where is the SNMP OID list for a device: the root OID, snmpwalk and snmpget OID lists, HOST-RESOURCES-MIB and ENTITY-MIB?

In the device's sensor catalog: every walked OID the compiled set knows is shown by name with its OID, type and units, grouped by MIB module, so the OID list is a search rather than a walk you paste into a spreadsheet. The root OID of a vendor's tree is 1.3.6.1.4.1 followed by its enterprise number.


What are SNMP location and contact, and what do snmp-server host and snmp-server community mean on a switch?

sysLocation and sysContact are two text objects every device carries, shown on the device page once polled; fill them in on the device and the inventory report gets them for free. snmp-server community sets a v2c community on many switches; snmp-server host names the trap receiver, which is where the SysPeep server's address goes.


Is it an SNMP web manager and a real time SNMP monitoring tool, and can it read a Modbus to SNMP gateway?

The console is the web manager, in any browser, with readings on a 30-second clock. A Modbus to SNMP gateway is just an SNMP device with the plant-floor values in its MIB, and SysPeep also speaks Modbus TCP directly where no gateway exists.


What is the SNMP port no. 161 and 162, and do I need a MIB downloader, snmp-mibs-downloader or an OID locator?

SNMP agents answer queries on UDP port no. 161 and send traps and informs to port 162 on the manager, so the SysPeep server needs 161 open towards the devices and 162 open from them. You do not need a MIB downloader: the compiled MIB set ships with SysPeep, about 14,400 modules and 2.2 million objects covering Cisco, Juniper, Arista, Fortinet, Palo Alto, HPE, Dell, APC, MikroTik, Synology and the rest, so every counter in the sensor catalog carries its MIB name and you never look up an OID by hand. snmp-mibs-downloader is the Debian package that fetches MIBs for Net-SNMP on Linux; it has no part in a SysPeep install.


Walk a switch and see its counters by name

Download SysPeep, run discovery against one subnet, and open the switch's sensor catalog. Up to 5 devices are free at full depth with unlimited sensors; the 30-day trial unlocks every feature except clustering.

Download Free TrialEverything it monitors