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

Products

• VMware NSX Networking
• VMware vSphere ESXi

Issue/Introduction

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

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

Environment

VMware NSX for vSphere 6.3.x
VMware NSX for vSphere 6.4.x
VMware vSphere ESXi 6.5

Cause

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

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.

Additional Information

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.