NSX-T 3.0 SNMP TRAP configuration. SNMP traps are not send for alarms sourced by edge nodes.

[AdamKmet]

Hello,

I have configured SNMP on NSX-T managers and Edge Transport Nodes (VM). However , even if in alarm dashboard I can see various alarms and all of the are configured to create SNMP trap, in reality only one alarm type (License expiration) is sending traps.

I have suspicion that it is not sending alarms where the source node is not manager.

My configuration is - on manager and as well on edge VMs:

nsxmgr> set snmp v2-targets <destIP> community <community>

nsxmgr> set snmp community <community>

nsxmgr> start service snmp
nsxmgr> set service snmp start-on-boot

I have checked as well the status via API and snmp is running on all of them.

Does anybody have any experience with this or is there anything what I missed in the configuration?

Thank you

[mauricioamorim]

Have you checked connectivity from the Edge VMs to the SNMP destination? The traps you are not receiving are sourced from the Edge. It seems only the traps sent from the NSX-T Manager are reaching the SNMP destination.

[AdamKmet · Accepted solution]

The connectivity was there. The EDGE VM was not sending anything. (confirmed with TCPDUMP on the EDGE itself) As well there was lot of errors in syslog on EDGE VM regarding SNMP trap creation.

I opened ticket with VMware and they advised to upgrade to 3.0.1. After the upgrade SNMP traps are sent correctly. Seems to be known issue in 3.0.0.