SNMP monitoring
Monitor switches, routers and firewalls two ways — event-driven traps and scheduled polling — in one unified device view.
SNMP monitoring
Switches, routers, firewalls, UPSes and servers rarely run an application agent, but almost all of them speak SNMP. VerOps monitors these devices two complementary ways, and both feed one unified device view:
| Method | Direction | Best for |
|---|---|---|
| Traps | Event-driven — the device pushes to VerOps the moment something happens | Faults as they occur: a link going down, a power event, an authentication failure, a fan or PSU alarm. |
| Polling | Scheduled — VerOps asks the device for its state on an interval | Continuous health and trends: is the device reachable, uptime, and per-interface status, traffic and errors over time. |
Use both. Traps tell you the instant a link drops; polling tells you the interface has been quietly dropping packets all week. A single network agent can run the trap listener and the poller at the same time.
One device, one view
However a device shows up — because it sent a trap, because you added it as a poll target, or both — it appears once in the SNMP device list with its name, vendor, last-seen time, recent trap severity, reachability and interface health merged together. Click a device to drill into its traps and its interfaces side by side.
SNMP versions
All three SNMP versions are fully supported for both traps and polling: v1, v2c (community string) and v3 — including authenticated and encrypted (authPriv) v3, with authentication via MD5 or SHA and privacy via DES or AES-128.
Where to find it
Open Network → SNMP. You will see sub-views for Traps, Polled devices, Poll targets and SNMPv3 users (for trap-side v3 credentials). The pages that follow cover each in detail.
Traps need almost no setup on the VerOps side — you point devices at an agent. Polling is managed centrally: you add each device once in the UI and VerOps takes it from there.