Hyperbus interface (vmk50) missing from ESXi
search cancel

Hyperbus interface (vmk50) missing from ESXi

book

Article ID: 381973

calendar_today

Updated On:

Products

VMware NSX-T Data Center

Issue/Introduction

  • VMK50 failed to get created post V2T migration. 
  • VMK50 was removed by users.
  • net-dvs might have the vmk50
    Login to the ESXi host as user root and run the command below
    net-dvs -l | grep vmk50 -C 10
                        pktsInException = 0
                        pktsOutException = 0
                        propType = RUNTIME
                com.vmware.nsx.vxlan.vmknic = 0x 0. 1.a8. 1
                        propType = POLICY
                com.vmware.common.port.volatile.status = inUse linkUp portID=100####29  propType = RUNTIME
                com.vmware.common.port.volatile.vlan = VLAN ####
                        propType = RUNTIME
                com.vmware.common.port.volatile.ptstatus = noPassthruReason=1,  propType = RUNTIME
        port 44####43-####-46e0-####-e582####4bdf:
                com.vmware.common.port.alias = vmk50 ,  propType = CONFIG
                com.vmware.common.port.connectid = 175####585 ,         propType = CONFIG
                com.vmware.common.port.backingType = nsx ,      propType = CONFIG
                com.vmware.common.port.portgroupid =  ,         propType = CONFIG
                com.vmware.port.extraConfig.vnic.external.id = hyperBusVmknic175####141 ,       propType = CONFIG
                com.vmware.vswitch.port.security = 0x 5. 0 <repeats 3 times>
                        propType = POLICY
                com.vmware.common.port.volatile.status = free
                com.vmware.common.port.volatile.vlan = VLAN 0
                        propType = RUNTIME VOLATILE

 

  • On ESXi host the log /var/log/nsxaVim.log may report "Address not available"

    less nsxaVim.log | grep -i 'hyperbus'

    2025-06-27T12:49:42Z nsxaVim: [2103219]: INFO HyperBus interface config add received
    2025-06-27T12:49:45Z nsxaVim: [2103219]: INFO Creating hyperbus port on [33 ## ## 50 ## ## 8a ##-## b4 ## ## 82 ## ## d1]
    2025-06-27T12:49:45Z nsxaVim: [2103219]: INFO Successfully created hyperbus port [44####43-####-46e0-####-e582####4bdf] on dvs [33 ## ## 50 ## ## 8a ##-## b4 ## ## 82 ## ## d1]
    2025-06-27T12:49:45Z nsxaVim: [2103219]: INFO Adding hyperbus interface on dvs [33 ## ## 50 ## ## 8a ##-## b4 ## ## 82 ## ## d1]
    2025-06-27T12:49:46Z nsxaVim: [2103219]: INFO Failed to add hyperbus interface on dvs [33 ## ## 50 ## ## 8a ##-## b4 ## ## 82 ## ## d1]: {'fault': 'PlatformConfigFault', 'msg': 'An error occurred during host configuration.', 'faultMessage': ['Operation failed, diagnostics report: Unable to Set: Address not available']}
    2025-06-27T12:49:47Z nsxaVim: [2103219]: INFO Adding hyperbus interface on dvs [33 ## ## 50 ## ## 8a ##-## b4 ## ## 82 ## ## d1]
    2025-06-30T09:58:56Z nsxaVim: [2103219]: INFO HyperBus vmknic [vmk50] exists for dvs [33 ## ## 50 ## ## 8a ##-## b4 ## ## 82 ## ## d1], no need to create again

 

Environment

VMware NSX-T Data Center

 

Cause

  • When any other vmkernel adapter vmkX is using the 169.254.1.1, NSXA fails to complete the vmk50 creation.
    Therefore, it prevents the completion of vmk50 creation.

 

 

Resolution

To resolve the VMK50 missing issue, follow the steps below until vmk50 is created.

  1. Remove the respective vmkX which is being used with the IP 169.254.1.1 or change the IP if vmkX is manually configured.
  2. Restart the opsagent service.
    /etc/init.d/nsx-opsagent restart
  3. Put the ESXi host into maintenance mode and Reboot.
  4. Put the host into maintenance mode, bring the host out of the cluster and add it back into the cluster.

Additional Information

Note:- Agent opsagent/nsxa is responsible for creating and deleting VMK50.