During NSX VIB installation on a host, a script runs that executes two commands back to back. The first creates the network stack with default values, and the second updates the name. If the second command fails for any reason, the network stacks remain configured with default values.
There is no functional impact to the names of the netstacks being different than expected.
This is a cosmetic issue only and has no negative impact on environmental behavior, network functionality, or datapath performance. The underlying netstack instance keys remain correct, ensuring full operational stability.
If you wish to change the display names for consistency, follow these steps on the affected ESX host(s):
esxcli network ip netstack get -N vxlan# > esxcli network ip netstack get -N vxlan
vxlan
Key: vxlan
Name: vxlan <--This is the field that may or may not show the correct name. Leave all other settings unchanged.
Enabled: true
Max Connections: 11000
Current Max Connections: 11000
Congestion Control Algorithm: newreno
IPv6 Enabled: true
Current IPv6 Enabled: false
ECN Status: enabled
State: 4660esxcli network ip netstack set -N vxlan -n nsx-overlayesxcli network ip netstack set -N hyperbus-n nsx-hyperbus# > esxcli network ip netstack set -N vxlan -n nsx-overlay
# > esxcli network ip netstack get -N vxlan
vxlan
Key: vxlan
Name: nsx-overlay <--This is the field that now shows the correct name. Leave all other settings unchanged.
Enabled: true
Max Connections: 11000
Current Max Connections: 11000
Congestion Control Algorithm: newreno
IPv6 Enabled: true
Current IPv6 Enabled: false
ECN Status: enabled
State: 4660
# > esxcli network ip netstack set -N hyperbus -n nsx-hyperbus
# > esxcli network ip netstack get -N hyperbus
hyperbus
Key: hyperbus
Name: nsx-hyperbus
Enabled: true
Max Connections: 11000
Current Max Connections: 11000
Congestion Control Algorithm: newreno
IPv6 Enabled: true
Current IPv6 Enabled: false
ECN Status: enabled
State: 4660