Monitor SNMP traps
This Orion Platform topic applies only to the following products:
IPAM — NAM — NCM — NPM — NTA — SAM — SRM — VNQM
If you monitor a large number of devices, where each device may have many connected objects of its own, requesting information from each device is impractical. You can set up the SNMP Trap Server, and each managed device can notify it about any issues by sending a trap message.
Starting with Orion Platform 2019.4, you can optionally manage Syslog and SNMP trap messages through the Orion Web Console using the free Orion Log Viewer (OLV).
SNMP traps are received by the SolarWinds Trap Service, which listens for incoming trap messages on UDP port
162, and then decodes, displays, and stores the messages in the SolarWinds Orion database.
By default, SNMP traps are stored in the Traps and TrapVarBinds tables in the Orion database.
The SolarWinds Trap Service can receive and process SNMP traps from any type of monitored network device, and can handle large numbers of simultaneously incoming traps.
A SolarWinds installation can process approximately 500 traps per second. Higher capacity can only be achieved with significant hardware improvements over minimum SolarWinds requirements.
Before you begin
- Configure devices to send SNMP traps to the IP address assigned to the Orion server. For more information about proper configuration, refer to the documentation supplied by the vendor of your devices.
- Make sure the
UDP port 162is open for IPv4 and IPv6.
- When you use SNMPv3 for polling a device and receiving traps from it, confirm that the same authentication type (auth, noauth, or priv) is configured for both polling and traps.