Receiving SNMP Traps
Map device events to readings and automation triggers.
A receiver can listen on a managed Go network agent or a compatibility collector. Hosted panel execution requires service access. Enable Receive SNMP Traps under Agents → Configure and add every source address to its permitted targets before creating the listener. Equipment must be configured to send notifications to that host's reachable IP and UDP port. A collector can receive traps locally and forward normalized events over its outbound panel connection; traps do not need a public Internet listener.
The receiver requires explicit source IPs and either community credentials for SNMPv1/v2c or authenticated SNMPv3 users. No wildcard sources, DNS names or anonymous SNMPv3 users are accepted. SNMPv3 supports SHA-1, SHA-256 or SHA-512 authentication, with optional AES privacy. Community matching is access control, not encryption; prefer authenticated/private SNMPv3 where the device supports it.
The default listener is UDP/IPv4 on port 1162. The bind address and port are configurable. Devices commonly default to UDP 162, so either configure their destination port or configure the receiver for that port with the necessary host privileges. Match the IPv4/IPv6 transport to the bind address. If NAT exists between sender and receiver, allow the source address observed by the receiver.
Mapping Notifications
Each mapping matches one exact trap OID, optionally limited to one source IP, and can:
- Set a configured equipment service/check to Up or Down.
- Emit a named custom event for automation.
- Publish selected numeric varbind values as equipment metrics, with an optional scaling factor.
A vendor-specific clear/recovery trap should have its own mapping back to Up. Receiving an alarm does not imply that a later lack of traps means recovery. Numeric metric values require a freshness policy in the consuming panel; a silent receiver cannot prove current device health.
SNMPv1 generic notifications normalize to standard notification OIDs, e.g. linkDown is 1.3.6.1.6.3.1.1.5.3. Enterprise-specific v1 traps normalize to <enterprise>.0.<specific>. SNMPv2c and SNMPv3 use the snmpTrapOID.0 value. Matching does not guess MIB names or auto-discover vendor meanings.
Accepted unmapped traps produce only a timestamp, source IP and trap OID. Raw text varbinds, community strings, authentication keys and privacy keys are never emitted to Activity. Rejected packets affect receiver counters rather than creating individual user-facing alerts.
Limits And Validation
The receiver allows 256 source IPs, 16 communities, 16 SNMPv3 users and 200 mappings. Each trap accepts at most 128 varbinds; each mapping has at most 30 numeric metrics. Packet processing is limited to 100 packets per second and delivery queues to 128 events; excess traffic increments Dropped. Large or malformed packets are rejected before normalization. Exact source filtering runs before ASN.1 decoding using the pinned net-snmp receiver implementation.
Tests use real local UDP notifications for SNMPv1, SNMPv2c and SNMPv3 SHA-256/AES authPriv, and verify mapping, credential rejection, downgrade rejection, source filtering, lifecycle and port collision errors. Vendor hardware has not been tested here. UDP traps can be lost or duplicated; use polling for reconciliation and automation cooldowns for duplicate-trigger protection.
Native Agent Support
Native agents accept authenticated SNMPv3 traps with SHA, SHA256 or SHA512 authentication and AES privacy, as well as v1/v2c community traps. v2c informs are acknowledged. SNMPv3 engine-discovery/inform negotiation is not implemented; configure v3 senders for traps. Duplicate packets are suppressed and v3 engine timing rejects stale packets during the listener session. Use Install The Native Agent for the full setup and prerequisites.