Troubleshooting Trap Issues in the SolarWinds Platform

This article give guidance for working with trap issues. If you are having trouble receiving traps from devices configured to send traps to your SolarWinds Platform server, verify that both SNMP Trap Service and SolarWinds Trap Service are running, the traps receiving port is set correctly, and that the traffic is not blocked by any firewall.

By default, SNMP traps are received by the SolarWinds Trap service that listens on UDP port 162. If traps are sent to a different port, change the traps receiving port.

A. Verify trap services and ports

1. Log in to your SolarWinds Platform server using an account with administrative privileges.
2. Click Start > Control Panel > Administrative Tools > Services.
3. Confirm that the SolarWinds Trap Service is the only trap service currently running.
4. Confirm that the SolarWinds Trap Service is the only service on port 162:
   1. Click Start > Run, and enter cmd.
   2. Enter netstat -aob.
   3. Confirm that there are no other connections on port 162 (PID = 162).
5. Confirm that the SNMP Trap Service that passes received traps to the SNMP Trap Viewer is installed:
   1. Click Start > Control Panel > Add or Remove Programs.
   2. Click Add/Remove Windows Components.
   3. Select Management and Monitoring Tools, confirm that it is selected, and click Details.
   4. Select Simple Network Management Protocol, confirm that it is checked, and then click OK.
   5. On the Windows Components window of the Windows Components Wizard, click Next.
   6. Click Finish when the Windows Components Wizard completes.
6. Confirm that all installed firewalls, including Windows Firewall and any third-party installed firewalls, allow traffic to and from your Orion server on port 162.

Change the Traps Receiving Port

To change the port for receiving Traps, open the file SWTrapService.exe.config with a text editor and provide the new port number in the value field of the following line:
<add key="TrapPort" value"162" />

The default location for SWTrapService.exe.config is C:\Program Files\SolarWinds\Orion\

B. Check if the device is configured properly to send SNMP Traps to the SolarWinds Platform
C. Check if there's a Firewall blocking the SNMP Trap port (162)
D. In OLV/LA version Syslog and Traps, the device must be 'Enabled' or 'Default' for Log and Event Monitoring then monitored by the Polling Engine receiving the traps:

E. If you're not receiving trap messages from a specific device, check if it's a duplicate IP. From the trap log you will see something like 

2022-10-11 09:46:24,572 [31] ERROR SolarWinds.Orion.LogMgmt.LogServices.Common.NodeMapper.OrionNodeMapper - Detected duplicate nodes with primary IP address 

Learn more

• Trap service is stopped: Trap service is stopped because another application is using UDP port 162
• Monitor SNMP traps