"Faulty TEP" alarm is present in the NSX manager for one or more ESXi host transport nodes

Products

• VMware NSX

Issue/Introduction

• When workloads are moved to ESXi transport tode the TEP (Tunnel Endpoint) status shows tunnels towards Host and Edges as down.
• NSX manager report 'Faulty TEP' alarm for that vmk interface.
  
  

• The host may have BFD session UP with other vmk interface i.e., both vmk10 and vmk11 may not be affected at the same time.
• Vmkping from affected vmkernel interface is failing.

Environment

VMware NSX

Cause

• Bidirectional layer2 or layer3 connectivity from affected vmkernel interface is down.
• Packet capture on uplink interface shows BFD packets are not reaching peer end.
  Reference -
  Troubleshooting NSX using Packet Captures

Resolution

This issue may occur due to an invalid TEP configuration, duplicate IP addresses, or a loss of connectivity from the affected TEP."

• Check if the IP address assigned to TEP interface is valid and not duplicate.
• Check if the TEP can ping its default gateway.
• If the packets are not reaching peer host or default gateway then check underlay network for any layer 2 or layer 3 connectivity issues.

Additional Information

TEP tunnels are down between ESXi Transport Node and Edge Transport Node. (Alarm: Event type: Faulty TEP)