vmwNsxTEdgeHealthEdgeNICOutOfTransmitBuffer

Edge NIC vmwNsxTDataCenterEdgeNICName transmit ring buffer has overflowed by
vmwNsxTDataCenterTxRingBufferOverflowPercentage% on Edge node vmwNsxTDataCenterEntityId.
The missed packet count is vmwNsxTDataCenterTxMisses and processed packet count
is vmwNsxTDataCenterTxProcessed.
          
Action required:
1. If a lot of VMs are accommodated along with edge by the hypervisor
   then edge VM might not get time to run, hence the packets might
   not be retrieved by hypervisor. Then probably migrating the edge VM
   to a host with fewer VMs.
2. Increase the ring size by 1024 using the command `set dataplane
   ring-size tx <ring-size>`. If even after increasing the ring size,
   the issue persists then contact VMware Support as the ESX side
   transmit ring buffer might be of lower value. If there is no
   issue on ESX side, it indicates the edge needs to be scaled to
   a larger form factor deployment to accommodate the traffic.
3. If the alarm keeps on flapping, i.e., triggers and resolves very soon,
   then it is due to bursty traffic. In this case check if tx pps using
   the command `get dataplane cpu stats`. If it is not high during the
   alarm active period then contact VMware Support.
   If pps is high it confirms bursty traffic. Consider suppressing the
   alarm.
   NOTE - There is no specific benchmark to decide what is regarded as a
   high pps value. It depends on infrastructure and type of traffic.
   The comparison can be made by noting down when alarm is inactive and
   when it is active.

MIB

VMWARE-NSX-MIB

OID

.1.3.6.1.4.1.6876.120.1.0.2.0.33

Type

notification

Status

current

Parent

vmwNsxTEdgeHealthFeature

Siblings

43