Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Doubt on SNMP Trap

Hi Fellow Members,

I have doubt in receiving SNMP trap, it may be a dump question.

Do we need to add the node through SNMP V2/V3 to receive the SNMP traps from the device or it's not required, we can receive traps if everything configured properly on the device end?

Kindly clarify this.

Thanks,

Find more posts tagged with

Accepted answers

vinay.by

Do we need to add the node through SNMP V2/V3 to receive the SNMP traps from the device or it's not required, we can receive traps if everything configured properly on the device end?

- No, this is not linked (this has nothing to do with your node addition). You can as well add a node as ICMP and you should still be able to receive traps from that node if the end device (node) is configured properly to send traps into SolarWinds Orion.

All comments

vinay.by

Do we need to add the node through SNMP V2/V3 to receive the SNMP traps from the device or it's not required, we can receive traps if everything configured properly on the device end?

Martin_Crothers

Hi @DN,

To validate that the trap is being received by the Orion server you would want to use Wireshark to perform a packet capture. (NOTE: If you don't already have Wireshark installed on your server, be aware that when you do install (and later update) it, you will get a prompt to install "Npcap", which is also used by Orion. Uncheck this installer inside of the Wireshark installer to keep the integrity of Orion)

You can perform a capture using a capture-filter like this: udp port 162 and host 192.168.1.100
The "udp port 162" section indicates that you want to capture packets that are SNMP-Traps. The "and host 192.168.1.100" section indicates that you want to capture packets that are sourced from IP address 192.168.1.100. You can swap the "host 192.168.1.100" for "src net 192.168.1.0/24" to capture packets sourced from that whole subnet.

If you want to decrypt the packets inside of Wireshark, follow these instructions: https://support.radware.com/app/answers/answer_view/a_id/1008985/~/how-to-decrypt-snmpv3-packets-using-wireshark

If your Orion server is not receiving the SNMP-Traps, you'll need to have the admin of the device you're expecting the trap from to check that the configuration of the device is enabled to:

Send traps
Send traps to your Orion server IP address (or a load balancer if you're able to)
Traps use the same SNMP version and credentials

If you're still not receiving the packets, check the firewall on the Orion server (or use Wireshark to validate if you're receiving any other traps), or check with your Network/Firewall admins to see if there is a possibility that a switch/router ACL or firewall rule could be blocking snmp-traps.

Thanks for the detailed information.

Thanks for the clarification. This what I want to know.

-DN

planglois

... As long you are expecting v2 traps. SNMPv3 Traps requires you to monitor the source device using SNMPv3 so it uses the same config (auth, priv, etc...) for processing those traps...