Search the VMware Knowledge Base (KB)
View by Article ID

Netcpa stops running on an ESXi host that runs a Bridging DLR VM (2147181)

  • 0 Ratings
Language Editions


  • Netcpa process is in a stopped status
  • In the /var/log/vmkernel.log file of the ESXi host, you see entries similar to:

    2017-08-02T18:47:49.522Z cpu2:74108937)User: 3816: wantCoreDump:netcpa-worker signal:6 exitCode:0 coredump:disabled

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


This issue occurs when a Distributed Logical Router (DLR) Control VM configured for bridging is deployed on an ESXi host that is prepared with a NIC Teaming policy of LACP.

The Bridge learns the MAC address of virtual machines on the associated VLAN and VXLAN networks. If the Bridge sees a MAC address on a different uplink to the one it has learned it on, it reports a MAC Learning Table change. However, in an environment configured with a LAG/LACP, it is expected that the same MAC addresses are seen on multiple interfaces. This results in a very high volume of MAC Learning Table updates. These updates are sent from the DLR module to the NSX Controllers through the netcpa process. A high volume of updates in a very short time frame can cause netcpa to run out of memory and crash.


This issue is resolved in VMware NSX for vSphere 6.3.0, available at VMware Downloads.

To work around this issue if you do not want to upgrade, the LACP hashing policy on the physical switch should not use a flow based hashing algorithm, such as source IP-destination IP. Instead, it must be configured to pin MAC addresses to the same uplinks, such as change the policy to source-MAC.

If you encounter the issue where the netcpa process is stopped on an ESXi host:
  1. Log in as root to the ESXi host through SSH.
  2. Confirm that the netcpa service is stopped by running this command:

    /etc/init.d/netcpad status

  3. Once confirmed, run this command to restart the netcpa process:

    /etc/init.d/netcpad restart

  4. Confirm that the netcpa service is now running by running this command:

    /etc/init.d/netcpad status

See Also

Language Editions


Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 0 Ratings