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

ixgbe driver reload during NSX installation (52980)

Last Updated: 7/4/2018Categories: TroubleshootingTotal Views: 6520Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

5-10 second network outage at the end of NSX host prep on servers which only has ixgbe driver based physical NICs.

Cause

The ixgbe driver will be reloaded with Receive Side Scaling (RSS) option to improve the vxlan throughput. This typically takes about 5-10 seconds. Very rarely (if the system memory is very badly fragmented), the driver reload may fail.

Note: The ixgben (native) driver does not experience this issue.

Resolution

This is a known issue affecting VMware NSX for vSphere 6.4.x.

Currently, there is no resolution.

Workaround

To work around this issue, apply either one of these workarounds:

Workaround #1

In the vSphere Web Client, click Policies and Profiles.

Click Host Profiles.

Click Edit Host Profile and expand the General System Settings folder.

Expand Kernel Module Configuration, then select Kernel Module.

If ixgbe is loaded, select it.

Select Kernel Module Parameter > max_vfs . If the parameter Value is non-empty, click Cancel.

Select Kernel Module Parameter > CNA . If the parameter Value is non-empty, click Cancel.

Select Kernel Module Parameter > RSS . If the parameter Value is non-empty, click Cancel.

Set RSS value to 4,4,4,4,4,4,4,4.

Click Finish.

Notes:

If you reached step 10 above, reboot the host after moving all the virtual machines out. If not, no need to reboot.

Then prepare the host for NSX where the VIBs are pushed to the hosts.

Workaround #2

Manual Install using the "Resolve" button from Host Preparation Tab.

Here are the steps required to get a cluster prepared, these steps assume the issue was found during host prep, and you have a partially prepared cluster.

Make a note of what ESXi your NSX Manager is on.

Make sure NSX Manager is on an already prepared ESXi, NSX Manager can also be on an ESXi in a different cluster that is not being prepared for NSX.

From Network and Security > Installation and Upgrade -> Host Preparation tab, on the cluster you started prepping, select a host that has not been prepped yet. There are two options on doing this:

Option #1 - Resolve

Do an individual "Resolve" on the ESXi host. This has the host reach out to the NSX Manager to get the appropriate VIB for the host version, download and install it.

Monitor the ESXi host. The network disconnects from 5-10 seconds but should return to normal. If it does, the ESXi host requires a reboot.

Repeat this process for the other ESXi hosts in the cluster until the entire cluster is prepared for NSX.

Option #2 - Manual Install

Do a manual VIB install on an ESXi host. For more information, see the Host Preparation section of the NSX Troubleshooting Guide.

Navigate to https://NSXMGR_IP/bin/vdn/vibs-6.4.0/6.0-7564187/vxlan.zip.

You need the VIB for your ESXi host version. The VIB to look for is the "esx-nsxv" and load it to the shared storage where all affected ESXi host have access to.

From Hosts and Clusters > Select your Cluster > Select your Host > Enter the Host into maintenance mode.

SSH to the ESXi host as the root user.

Validate that the VIBs are installed by running this command:

esxcli software vib list | grep nsx

Note: This should not return anything.

Install the VIB manually by running this command:

esxcli software vib install -d /filepath/vxlan.zip

Since the ESXi host was placed in Maintenance Mode, there should not be any network disruption.

Exit the ESXi host out of Maintenance Mode and validate if the VIBs are installed correctly by running this command:

esxcli software vib list | grep nsx

Note: This should return a value with the esx-nsxv VIB.

Repeat all steps from Option #2 for the other ESXi in the cluster.

Workaround #3

Move to the ixgben driver on the ESXi host which does not have strict physical requirements.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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

Take Our Survey

Support Assistant