TCP/IP Stack display name show as "vxlan" or "hyperbus" instead of "nsx-overlay" or "nsx-hyperbus" after NSX installation on ESX host
search cancel

TCP/IP Stack display name show as "vxlan" or "hyperbus" instead of "nsx-overlay" or "nsx-hyperbus" after NSX installation on ESX host

book

Article ID: 444351

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • After installing NSX on one or more hosts, the TCP/IP netstack names for the vxlan and hyperbus network stacks may appear different depending on which host is examined:
  • After NSX 4.1.x, the expected values for the TCP/IP Stack names are
  • You may see older names in the vCenter UI or a mixture of old and new:

Environment

  • VMware NSX

Cause

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.

Resolution

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):

  1. Verify the current status of the "name" field:
    esxcli network ip netstack get -N vxlan
  2. The output will show the complete list of settings for the netstack:
    # > 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: 4660
  3. Update the display name for the vxlan (nsx-overlay) netstack:
    esxcli network ip netstack set -N vxlan -n nsx-overlay
  4. Update the display name for the hyperbus (nsx-hyperbus) netstack:
    esxcli network ip netstack set -N hyperbus-n nsx-hyperbus
  5. Verify the change has gone into effect:
    # > 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