SNMP traps for ESX Transport Nodes are not being sent
search cancel

SNMP traps for ESX Transport Nodes are not being sent

book

Article ID: 434935

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Alarms such as "Enhanced Dp Flow Table Usage Very High" or other Transport Node Health events are generated within the NSX Manager UI, but corresponding SNMP traps are not received by external monitoring tools.

  • Other NSX Edge and Manager based traps (e.g., IDPS signature bundle failures) are received successfully, while host-specific alerts are missing.

Environment

VMware NSX

Cause

In VMware NSX, alarms related to Transport Node (ESXi) health are sent directly from the management IP of the ESXi host, rather than from the NSX Manager appliance. If the SNMP service is not configured and enabled on the underlying ESXi host, these traps will not be forwarded to the monitoring destination.

Resolution

This is expected behaviour and requires the SNMP agent to be configured on every ESXi host acting as an NSX Transport Node.

Follow the documentation for configuring ESXi for SNMP: Configure ESXi for SNMPv1 and SNMPv2c

Additional Information

Configure ESXi for SNMPv1 and SNMPv2c

How to validate if SNMP traps are being sent to the remote SNMP server from the NSX Manager or NSX Edge