SNMP polling

SNMP polling (scheduled)

Polling turns the picture around: instead of waiting for a device to speak up, VerOps asks each device for its state on a schedule. That gives you continuous reachability and per-interface health — the data you need to see a slow degradation, not just a hard failure.

Add a device to poll

Polling is platform-managed: you add each device once and VerOps handles the rest. Go to Network → SNMP → Poll targets → Add device and provide:

• IP address of the device.
• Agent — the network agent (on the device's network) that should poll it.
• SNMP version — v2c or v3 (both fully supported).
• Credentials — for v2c, the community string; for v3, the username plus authentication (MD5 or SHA) and, for encrypted polling, privacy (DES or AES-128) passphrases.
• Interval — how often to poll (default 60s).
• Profile — MIB-II standard by default.

Enable or disable a device with a single toggle, and edit or remove it any time.

No restart, no agent edits

Because polling is managed centrally, adding, editing, disabling or removing a device takes effect on the polling agent automatically, usually within about a minute — no agent restart and no editing files on the agent. Rotate a community string in the UI and the next poll uses it.

What MIB-II collects

The MIB-II standard profile gathers the health that matters for almost any device:

• Reachability — is the device responding to SNMP right now.
• Identity — system name and vendor.
• Uptime — how long since the device last restarted.
• Per-interface — operational status (up/down), inbound and outbound traffic, and inbound and outbound errors, for each interface.

The Polled devices view shows reachability up/down, name, vendor and uptime; click a device to see its interface table with live status, traffic and error counts.

Credentials are safe

Community strings and v3 keys are stored encrypted and are never shown back in the UI or the API — you will see only a "configured" indicator. To change one, type a new value; leave it blank to keep the existing one.

Metrics and alerting

Every poll produces metrics you can chart and alert on exactly like application metrics. Traffic and error counters let dashboards derive rates (for example, bandwidth from octets):

Metric	Meaning
snmp_poll_up	1 if the device answered this poll, 0 if not.
snmp_sysuptime_seconds	Device uptime.
snmp_poll_duration_ms	How long the poll took.
snmp_poll_failures_total	Failed polls.
snmp_if_oper_status	Per-interface up/down.
snmp_if_in_octets / snmp_if_out_octets	Per-interface traffic.
snmp_if_in_errors / snmp_if_out_errors	Per-interface errors.

An unreachable device raises an alert through the normal alerting system — the same place your trap and application alerts live — so "the core switch stopped answering" reaches you the same way everything else does.

Traps and polling share one device view: a device you poll will also show any traps it sends, and vice-versa. Enable both for the fullest picture — instant fault notification plus continuous interface health.