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

Jumpstart failed to start: nsxv-vib reason: Execution of command: /etc/init.d/nsxv-vib start failed with status: 1 (54476)

Last Updated: 11/16/2018Categories: TroubleshootingTotal Views: 10243Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

You have prepared ESXi 6.5 hosts in the "Host preparation" tab.

From syslog.log file after host reboot, you see entries similar to:

​2018-04-16T10:00:16Z jumpstart[66444]: executing start plugin: nsxv-vib
2018-04-16T10:00:17Z init.d/nsxv-vib: INFO: Refreshing hostd netstack cache^@
2018-04-16T10:00:18Z init.d/nsxv-vib: ERROR: Failed to execute "esxcli network ip netstack set -N defaultTcpipStack": Connection failed Traceback (most recent call last):   File "/etc/init.d/nsxv-vib", line 836, in <module>     refreshHostdNetstackCache()   File "/etc/init.d/nsxv-vib", line 155, in refreshHostdNetstackCache     esxcli(['network', 'ip', 'netstack', 'set', '-N', 'defaultTcpipStack'])   File "/etc/init.d/nsxv-vib", line 141, in esxcli     raise Exception('Failed to execute "%s": %s' % (' '.join(cmd), out)) Exception: Failed to execute "esxcli network ip netstack set -N defaultTcpipStack": Connection failed
2018-04-16T10:00:18Z jumpstart[66444]: Jumpstart failed to start: nsxv-vib reason: Execution of command: /etc/init.d/nsxv-vib start failed with status: 1

Purpose

This article is to explain the impact of a failure that might be logged after host reboot.

Cause

This issue occurs because of race condition between startup of hostd and init.d script of NSX.

Impact / Risks

If you don't use ixgbe as a NIC driver, there is no impact.

To check if you use ixgbe, run this command and see the Driver:

esxcli network nic list

If you use ixgbe as a NIC driver, check the current RSS configuration.

To check the RSS configuration, run this command and see the value of RSS:
esxcli system module parameters list -m ixgbe
If the value is "4,4,4,4,4,4,4,4", RSS parameters are configured and there is no impact.

If you use ixgbe as a NIC driver and its RSS parameter is not configured as "4,4,4,4,4,4,4,4", you might experience degraded network performance.

Resolution

This issue is resolved in:

VMware NSX for vSphere 6.4.1, available at VMware Downloads.
VMware NSX for vSphere 6.3.7, available at VMware Downloads.

Workaround

To work around this issue, first check if performance is impacted. See Impact / Risks for details.

If performance is degraded, run this command and the RSS parameter is configured correctly:

/etc/init.d/nsxv-vib start

Note: /etc/init.d/nsxv-vib start causes temporal link down for ixgbe NICs. Migrate the VMs to other hosts or move the host into maintenance mode if required.

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 vSphere ESXi

VMware NSX for vSphere

Related Versions:

VMware vSphere ESXi 6.5

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant