Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Netcpa process may crash in Environment with L2 Bridges configured on DLRs (71038)

Last Updated: 9/23/2021Categories: TroubleshootingTotal Views: 22351Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

On environments where there are DLR layer 2 bridges the netcpa process of ESXi hosts may experience issues.

On the Fabric status of the dashboard, Host Communication Channel Status may show as down.
Control plane agent to controller may show as down on Host Preparation Tab.

You may see the following log entries on the vmkernel.log of the affected ESXi host:

2018-11-29T08:52:01.624Z cpu6:11936471)WARNING: vdrb: VdrCpVdrBridgeNetworkFdbUpdate:3792: CP:[I:0x2714] Bridge Network FDB Update: Failed to post message status: Limit exceeded

You may see the following on the syslog of the affected ESXi host:

2019-06-01T23:24:39.055Z esxi_host_fqdn.com netcpa: error netcpa[26D2221700] [Originator@6876 sub=Default] Connection error with controller 192.168.10.1:0 on source port 0, triggering reconnect
2019-06-01T23:24:43.726Z esxi_host_fqdn.com netcpa: error netcpa[26D2221700] [Originator@6876 sub=Default] Connection error with controller 192.168.10.1:0 on source port 0, triggering reconnect
2019-06-01T23:24:44.902Z esxi_host_fqdn.com netcpa: error netcpa[26D2221700] [Originator@6876 sub=Default] Connection error with controller 192.168.10.1:0 on source port 0, triggering reconnect

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

Cause

The issue is caused by the size of the messages being sent to the NSX Controllers from the ESXi host for bridging updates. This may cause the netcpa connection to flap which in turn will cause some log spew, this log spew will cause the netcpa crash.

Impact / Risks

Netcpa process on the ESXi host may crash.

Resolution

This is resolved in NSX for vSphere version 6.4.5.

Workaround

At present there is no workaround.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VMware vSphere Metro Storage Cluster (vMSC) を使用した INFINIDAT InfiniBox アクティブ/アクティブ複製 (71047)

KB
•
从适用于 Windows 的 vCenter Server 到 vCenter Server Appliance 6.5 的迁移路径 (70793)

KB
•
对于在 HPE Custom Image 6.0 U3、6.5 和 6.7 上运行、使用基于 SFP28 和 535T 的网卡且 bnxtnet 驱动程序版本为 212.0.xxx.x 或更低版本的主机，出现大量随机 I/O 流量时可能会发生 PSOD (76441)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant