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

ESXi transport node may face PSOD during LACP port creation with ENS enabled on its N-VDS (78659)

Last Updated: 9/1/2020Categories: InformationalTotal Views: 3163Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You can see the backtrace related to ENS on vmkernel core with PF Exception type 14. The backtrace may be different each time it occurs because it depends on page fault timing. LACP port creation is operated during edit lag configuration or NSX-T upgrade with LACP configuration.

Cause

With ENS enabled, ESXi Host cannot handle large LACP port index properly which is managed in inside operation. If LACP port is created with over 127 port index during LACP configuration, it leads to pointer address corruption. ESXi Host will face PSOD when it access to the pointer address because it is not loaded on physical memory.
If LACP port creation is operated with all of the following conditions (a)-(c) met, you will face this PSOD.

(a) ESXi version is prior to 7.0

(b) ENS is enabled on the N-VDS

(c) Current largest port index is larger than 122 on the N-VDS

Resolution

This issue is fixed in ESXi 7.0.

Workaround

If current port index is larger than 122, reboot ESXi Host to reset port index for workaround.
You can check current largest port index as follows.

(1) Power on a VM whose vnic is connected to the N-VDS just before LACP port creation. The largest port index will be assigned to its VM's vnic.

(2) Check port indices. In this example, largest port index is 125. ESXi Host reboot is needed to avoid this PSOD before LACP port creation.

# ps=DvsPortset-0
# for num in `vsish -e ls /net/portsets/${ps}/ports`; do vsish -e cat /net/portsets/${ps}/ports/${num}status | egrep "port index|clientName"; done

port index:1
clientName:Management
port index:2
clientName:LACP_MgmtPort
port index:3
clientName:lag
port index:4
clientName:vmnic1
port index:5
clientName:Shadow of vmnic1
port index:6
clientName:vmnic2
port index:7
clientName:Shadow of vmnic2
port index:9
clientName:L2CtrlPort
port index:10
clientName:vdr-vdrPort
port index:125
clientName:vm-test.eth0

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
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center

Take Our Survey

Support Assistant