Public beta — temporary labs may change or be reset.

PRTG setup guide

Validated

Tested with 26.3.122.1665 (Community/Raw Edition)

PRTG discovers this device cleanly over SNMP v2c. These steps mirror the exact M2F validation run.

PRTG · SNMP discovery

Router (generic-router-v1)

SNMP v2c · 8 interfaces

Discovered
  • SNMP System Uptime
  • CPU Load
  • SNMP Memory
  • 8 x SNMP Traffic

Run high_cpu → CPU reads ~95% → your alert should fire.

Illustration of the expected discovery for a Router lab device, based on our 26.3.122.1665 (Community/Raw Edition) validation. Actual sensors depend on template, version and configuration.

Connection

Host
snmp-test.bonguides.com
Port
161
Version
SNMP v2c
Community
generated per device

The community is generated per device and shown only in your lab — treat it as a throwaway secret and do not reuse it. SNMP v2c is cleartext.

1. Create the device

  1. In the lab, create a Router (generic-router-v1) and copy its Host, Port, SNMP version and Community.
  2. Host is snmp-test.bonguides.com, port 161, SNMP v2c. The community is generated per device — treat it as a throwaway secret.
  3. Expect 8 interfaces (GigabitEthernet0/1–8), plus system uptime, CPU and memory over standard MIBs.

2. Configure PRTG

Add the device

Add an SNMP device with address snmp-test.bonguides.com, then set SNMP v2c and the generated community in the device credentials. Run Auto-Discovery.

Expected sensors

Auto-discovery creates SNMP System Uptime, CPU Load, SNMP Memory, and 8 SNMP Traffic sensors (one per interface). Baseline interface 1 reads ~12 Mbit/s (8 in + 4 out).

3. Run the fault scenarios

Trigger these from the device page in the lab, then watch PRTG react. Each has a recovery action that restores the baseline.

  • high_cpu — the CPU Load sensor rises to ~95%, then returns to baseline on recovery.
  • traffic_spike — interface 1 Traffic jumps to ~1,200 Mbit/s, then falls back over a few poll cycles.
  • interface_down — interface 1 Traffic drops to 0 Mbit/s.
  • snmp_down — sensors report a timeout / no response, then resume on recovery.

Caveats

  • interface_down shows as zero throughput on the Traffic sensor rather than the sensor itself turning Down — that is normal PRTG traffic-sensor behaviour.
  • PRTG's default discovery does not create a standalone sysName sensor; it reads the system group for uptime and names interfaces from ifDescr.