Buffer overflow alarms for unused fp-eth interfaces on an NSX edge deployed from OVA
search cancel

Buffer overflow alarms for unused fp-eth interfaces on an NSX edge deployed from OVA

book

Article ID: 377643

calendar_today

Updated On:

Products

VMware NSX-T Data Center

Issue/Introduction

Rx buffer overflow alarm is raised for unused fp-eth# interfaces. When disconnected, edge NIC Link down alarm is raised.

Logs similar to following may be observed -

/var/log/syslog
##-mgmt-## NSX 69833 MONITORING [nsx@6876 alarmId="c91fa9b3-####-4351-####-####4af81af" alarmState="OPEN" comp="nsx-manager" entId="33160dfa-####-11ee-####-####56a751ae" errorCode="MP701099" eventFeatureName="edge_health" eventSev="CRITICAL" eventState="On" eventType="edge_nic_link_status_down" level="FATAL" nodeId="33160dfa-####-11ee-####-####56a751ae" subcomp="monitoring"] Edge node NIC fp-eth3 link is down.



##-mgmt-## NSX 9041 - [nsx@6876 comp="nsx-edge" s2comp="nsx-monitoring" entId="0000####-####-0000-####-00000000####" tid="9172" level="WARNING" eventState="On" eventFeatureName="edge_health" eventSev="warning" eventType="edge_nic_out_of_receive_buffer"] Edge NIC fp-eth2 receive ring buffer has overflowed by 3.760952% on Edge node 0000####-####-0000-####-00000000####. The missed packet count is 3030972 and processed packet count is 77559580.

Environment

VMware NSX-T Data Center

Cause

When NSX edge is deployed manually from OVA it is required to connect all network adapters during OVA deployment so all fp-eth# interfaces remain in connected state. Since the fp-eth# interface is in connected state traffic flooding in thar port-group can lead to buffer overflow alarms.

Resolution

  • The alarm can be ignored as interface is not in use.
  • One of the following can be done as a workaround -
    1. Control flooding in port-group
    2. Remove unused interface from data path. Please refer to following KB for steps -
    Edge NIC link status down alarm


Additional Information

This issue is not seen when the edge is deployed from NSX manager because NSX manager connects unused uplinks to a special 'none' port-group.