Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

ESX hosts lose network connectivity rendering the host inaccessible from network (60293)

Last Updated: 12/20/2018Categories: TroubleshootingTotal Views: 9812Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

ESX hosts lose network connectivity and users are no longer able to ping or ssh into the host

In vmkernel.all, you see entries similar to:

2018-12-16T04:31:38.663Z cpu2:66409)KCPNATParseAndTranslate:577:[nsx@6876 comp="nsx-esx" subcomp="kcp" errorCode="ESX1"]Pkt copy failed with error Failure on port 33554511 : Failure
2018-12-16T04:31:44.777Z cpu8:66409)KCPNATParseAndTranslate:577:[nsx@6876 comp="nsx-esx" subcomp="kcp" errorCode="ESX1"]Pkt copy failed with error Failure on port 33554524 : Failure
2018-12-16T04:31:47.484Z cpu6:66409)KCPNATParseAndTranslate:577:[nsx@6876 comp="nsx-esx" subcomp="kcp" errorCode="ESX1"]Pkt copy failed with error Failure on port 33554474 : Failure

You will see the following errors in vmkwarning.log:

2018-11-23T12:31:23.948Z cpu7:1149450)WARNING: Heap: 3818: Could not allocate 2048 bytes for dynamic heap NetPktHeapLow. Request returned Out of memory
2018-11-23T12:31:23.948Z cpu7:1149450)WARNING: Heap: 3818: Could not allocate 2048 bytes for dynamic heap NetPktHeapLow. Request returned Out of memory
2018-11-23T12:31:23.948Z cpu7:1149450)WARNING: Heap: 3818: Could not allocate 2048 bytes for dynamic heap NetPktHeapLow. Request returned Out of memory
2018-11-23T12:31:23.948Z cpu7:1149450)WARNING: Heap: 3818: Could not allocate 2048 bytes for dynamic heap NetPktHeapLow. Request returned Out of memory

User can further confirm by executing the following steps on the impacted ESXi host

vsish

cat /system/heaps/NetPktHeapAny-0x43042d286000/stats

The output of the above commands looks like below:

cat /system/heaps/NetPktHeapLow-0x43039d283000/stats

The output of the above commands looks like below:

Cause

The problem is seen due to a memory leak in NetPktHeap memory due to stale hyperbus ports

To determine if there are stale hyperbus ports existing on the impacted host, use the following procedure

ssh into the impacted ESXi host and execute the following command

net-dvs -l |grep -E "port hb-|volatile.status" |grep -A 1 hb-

Output of the above command looks as below. The one in RED is the orphaned/stale hyperbus ports while the one in GREEN is active hyperbus ports

 port hb-25cca551-795f-4693-9f3d-06a9c0681b59:

com.vmware.common.port.volatile.status = free

port hb-d89902f7-2e1e-4099-8a0f-71c73312243c:

com.vmware.common.port.volatile.status = free

port hb-ed8c128a-531e-4117-b3e9-3f35b541bcbe:

com.vmware.common.port.volatile.status = free

--

port hb-ebb7eead-9c4a-4bfe-8887-d2391ca7ec62:

com.vmware.common.port.volatile.status = inUse linkUp portID=50331692  propType = RUNTIME

port hb-01753ec5-c306-4dae-b60d-3b5c0739b8df:

com.vmware.common.port.volatile.status = inUse linkUp portID=50331693  propType = RUNTIME

port hb-c9ba1928-8230-4468-89b8-a88803a2ad9e:

com.vmware.common.port.volatile.status = inUse linkUp portID=50331731  propType = RUNTIME

port hb-dc27e5ff-3230-4c9c-a351-ad7113006195:

com.vmware.common.port.volatile.status = inUse linkUp portID=50331732  propType = RUNTIME

Resolution

File a support request with VMware Support and quote this Knowledge Base article ID (60293)  in the problem description. For more information, see How to Submit a Support Request.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Transformers

Related Versions:

VMware NSX Transformers 2.x

Take Our Survey

Support Assistant