VMs lost network connectivity in heavy workloads ESXi host
search cancel

VMs lost network connectivity in heavy workloads ESXi host

book

Article ID: 389310

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Symptoms:

  • VMs lose network connectivity after vMotion to an ESXi host running heavy workloads.
  • VMs encounter network interrupts suddenly.
  • Able to see the <PortNum> of problematic VM in "net-stats -l"
  • Unable to see the <PortNum> connected in "nsxdp-cli ens port list -s 0 | grep <PortNum>"
  • Error message is observed in /var/run/log/vmkernel.log  "<YY-MM-DD-HH-MM-SS> cpu2:315897912)ENS: Ens_DoDetachPort:5073: Detach port 0x4000cdf from ENS, handle: 0x450140049c40"
  • Error message 0xbad0014 is observed in vmware.log  "<YY-MM-DD-HH-MM-SS> In(05) vcpu-0 - VMXNET3 user: failed to activate 'Ethernet0', status: 0xbad0014 " ,which indicates "Not enough memory"

 

Environment

VMware NSX-T Datacenter

VMware NSX

Cause

ESXi may fail to allocate memory to activate the network driver when under heavy workloads.

Resolution

Reduce memory utilization by reducing workloads or scaling out the number of ESXi hosts managing those workloads. A reboot of ESXi is recommended once this is resolved.

Powered by Wolken Software