A library ESXi host's overlay TEP flaps, and Distributed Firewall realization on that host flaps with it. vmkping to other TEPs drops whenever one member of the physical NIC team errors. What should the administrator inspect first?
Select an answer to reveal the explanation.
Short Explanation
If one copper cable is dying, the TEP looks possessed and DFW realization rides the same roller coaster. Check the pNIC, cable, and switch light before rewriting firewall sections. Physical NIC failure loves to wear an NSX mask.
Full Explanation
NSX-T TEPs ride the host's physical NICs. A bad cable, pNIC, or switch port in a NIC team causes TEP flaps that interrupt host communication with Managers and can make Distributed Firewall realization appear unstable. Application-section edits, Carbon Black Cloud policy, and Workspace ONE Access connector health do not repair underlay NIC failure. Inspect physical-layer counters, swap the cable or pNIC, and confirm TEP stability before changing security policy.