Hyberbus vmk50 interface is missing from ESXi Transport node
search cancel

Hyberbus vmk50 interface is missing from ESXi Transport node

book

Article ID: 324230

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:
The following symptoms are observed
  •  ESXi host is added to both an Overlay NVDS and a different VLAN NVDS
  •  vmk10 TEP interface is created however vmk50 hyperbus interface is missing
  •  /var/log/nsx-opsagent.log shows the creation and deletion of the hyperbus vmkernel
2019-04-15T17:54:40Z nsx-opsagent[2101313]: [nsx@6876 comp="nsx-esx" subcomp="nsx-opsagent" tid="2101536" level="INFO" s2comp="nsxa"] [CreateHyperBusInterface] Invoke command to create HyperBus interface on hostswitch reply: [ok]

2019-04-15T17:54:43Z nsx-opsagent[2101313]: [nsx@6876 comp="nsx-esx" subcomp="nsx-opsagent" tid="2101536" level="INFO" s2comp="nsxa"] [ApplyVTEP] Invoke command to delete HyperBus interface on hostswitch(75 66 a9 90 53 6b 4d 7c-84 10 69 c8 df df 31 2d) reply: [ok]
  • On the ESXi host there is no reference to vmk50 in net-dvs indicating it has been cleanly deleted
net-dvs | grep vmk50


Environment

VMware NSX-T Data Center 2.x
VMware NSX-T Data Center

Cause

nsx-opsagent running on the ESXi host creates the vmk50 hyperbus interface when the host is added to the Overlay NVDS.
Due to the problem documented here, when the same ESXi host is also added to a separate VLAN NVDS this vmk50 interface is deleted in error.

Resolution

This issue is resolved in NSX-T Data Center 2.4.0

Workaround:
To workaround this issue the same NVDS should be used for both Overlay and VLAN on the host.