Appearance
Network devices
The switches, printers and UPS units your agents can't reach.
SNMP monitoring built into OpsMerge. Point an agent at a subnet, it finds the kit; poll it through the agent on the LAN or directly from the server. v1, v2c and v3 — credentials encrypted at rest, not stashed in a spreadsheet.
- v1, v2c and real v3
Community strings for v1/v2c, full v3 USM for the rest — noAuthNoPriv through authPriv, SHA/AES. Not a checkbox that silently fails.
- Agent proxy or direct
An agent on the LAN polls devices behind the firewall; the server polls anything genuinely public. You pick per device.
- Find it, don’t type it
Point an agent at a CIDR and it discovers everything that answers SNMP — pre-classified, with the working credential stored for next time.
Discovery
Stop hand-entering IP addresses.
- Point an on-site agent at a subnet in CIDR notation; it probes every host and adds whatever answers SNMP.
- Devices are auto-classified from their SNMP identity — printer, switch, router, access point, UPS, firewall, camera, phone, storage.
- The credential that worked is stored against each device, so the next poll just runs.
- Optional scheduled re-discovery of an agent’s local subnets, without clobbering credentials you set by hand.
Polling
Two ways to reach a device.
- Proxy — an OpsMerge agent on the same LAN polls the device and reports back. The right call for anything behind a firewall.
- Direct — the server polls a device that is genuinely reachable from the internet.
- Reads the MIB-2 system group: name, description, object ID, uptime, contact and location, with online/offline and last-seen.
- Per-device poll interval, plus an on-demand “Poll now” after a config change.
Credentials, handled properly
Secrets that stay secret.
- Community strings and v3 passphrases are encrypted at rest (AES-256-GCM) and never shown back — the console says “Configured”, not the secret.
- Full SNMPv3 USM: username, security level, auth protocol (MD5/SHA family) and privacy protocol (DES/AES family).
- Layer SNMP-OID checks and your existing alert rules on top for thresholds — same alerting you already use for agents.
Pairs well with
Other things in the platform
Common questions
Which SNMP versions are supported?
v1 and v2c with a community string, and v3 with the full USM security model — security levels noAuthNoPriv, authNoPriv and authPriv, with the MD5/SHA auth protocols and DES/AES privacy protocols.How do you reach devices behind a firewall?
Proxy mode: an OpsMerge agent on the same LAN polls the device and reports back. Direct mode polls from the server and is for devices genuinely reachable from the internet. You choose per device.How does discovery work?
Point an on-site agent at a subnet in CIDR notation and it probes every host, adding whatever answers SNMP — auto-classified by type, with the working credential stored against each device.Where are the SNMP credentials stored?
Community strings and v3 passphrases are encrypted at rest with AES-256-GCM and are never returned by the API or shown back in the console.What does it read from a device?
The MIB-2 system group — name, description, object ID, uptime, contact and location — plus online/offline reachability and a last-seen timestamp. Layer SNMP-OID checks and alert rules on top for thresholds.