Does NPM 11.5.2 support snmpV3 traps from networking devices?

In solarWinds can cou change de poller fot snmp v3 in edit node. there you can change collection method.

That is ONLY for polling the switch. Not for receiving traps.  Are you implying that it should be the same for both and that the Polling and Trap config have to be identical?

No, I not thought about it. Inside the device is enabled to send traps to the Orion server: If you are and it does not trap see the firewall rules if the port 162 are enabled, among them

maybe this can help you

Cisco IOS Network Management Command Reference - snmp-server enable traps through snmp-server enable traps ospf cisco-sp…

.

I don't think that is the problem. Because when I change the trap from the switch to v2 I can receive it fine on the port it's set at and both the switch and server are on the same subnet....

But when exchange for v2 fia ok, so it's something in the configuration for v3 and is not in Orion.

better see documentation NPM work snmp v3,

are ok*

It is not from the server polling the node, because I can change it to snmpv3, input the correct configuration settings and I can poll the switch device successfully.

My problem is I am trying to have the switch send the snmpv3 traps to the server.

I have switches that are not configured or detected for polling in SolarWInds at all, but the traps are still received in the Trap Viewer once I set the configuration on the switches for snmpv2 traps to be sent to the server's IP address.  This is because for snmpv2, in the switch all I need to configure is the trap server's IP address  and a community string.  SNMPv3 has additional authentication and I am not seeing v3 traps at all and I am wondering if there is somewhere else I have to configure additional authentication settings either in SolarWInds or somewhere on Windows Server 2012 in order to receive it.  Anyone else have this issue?

The node must be added to NPM as an SNMP v3 node for NPM to receive SNMP v3 traps.  In addition the polling IP and the IP sending the traps must match (along with the credentials).  This is only required for SNMP v3 traps, v1 & v2c work without the node being added to NPM.

So the v3 trap credentials config. on the switch must match the v3 polling credentials config on the polling server...?  I will give this a try and report back when I'm back in the the office Tuesday...thanks...

So I think I have this working now...my next question is in the trap viewer, my community column is blank whenever I receive a trap...is it because v3 is using a "username" and not a "community"?