Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

PKS Container creation fails due to HyperBus interface vmk50 not being present on ESXI. PKS 1.2 NSX-T 2.1 (67432)

Last Updated: 3/13/2019Categories: TroubleshootingTotal Views: 8075Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Container creation fails.

Log snippet for reference.

2018-12-05T20:28:46.137Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11471 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] oslo.
privsep.daemon privsep process running with capabilities (eff/prm/inh): CAP_DAC_OVERRIDE|CAP_DAC_READ_SEARCH|CAP_NET_ADMIN|CAP_SYS_ADMIN|CAP_SYS_PTRACE/CAP_
DAC_OVERRIDE|CAP_DAC_READ_SEARCH|CAP_NET_ADMIN|CAP_SYS_ADMIN|CAP_SYS_PTRACE/none
1 2018-12-05T20:28:46.137Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11471 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] oslo.privsep.daemon privsep daemon running as pid 11471
1 2018-12-05T20:28:46.256Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] nsx_ujo.agent.agent Created veth pair nsx_agent_outer, nsx_agent_inner
1 2018-12-05T20:28:46.465Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] nsx_ujo.agent.agent Configured interface nsx_agent_inner with IP 169.254.1.0/31, MAC 00:50:56:a5:87:76
1 2018-12-05T20:28:46.480Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] nsx_ujo.agent.agent Added OVS port nsx_agent_outer with vlan 4094
1 2018-12-05T20:28:46.520Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] nsx_ujo.agent.nsxrpc_client Listening NSX RPC connection...
1 2018-12-05T20:28:46.521Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] cli.server.container_cli_server Starting node_agent CLI server
1 2018-12-05T20:28:46.532Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] nsx_ujo.agent.cni_watcher CNI socket is listening...
1 2018-12-05T20:39:05.068Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="ERROR" errorCode="NCP01004"] nsx_ujo.agent.cni_watcher Unable to retrieve network info for container nsx.kube-system.kube-dns-6b697fcdbd-fb4tg, network interface for it will not be configured
1 2018-12-05T20:39:06.073Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] nsx_ujo.agent.cni_watcher Failed to find OVS port for container 3497dd0a78a264bf97e4de52a88ce6e57158db92b92107f0abcdfce975c1e407: __init__() takes exactly 1 argument (2 given)
1 2018-12-05T20:44:05.328Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="ERROR" errorCode="NCP01004"] nsx_ujo.agent.cni_watcher Unable to retrieve network info for container nsx.kube-system.kube-dns-6b697fcdbd-fb4tg, network interface for it will not be configured
1 2018-12-05T20:44:06.331Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="INFO"] nsx_ujo.agent.cni_watcher Failed to find OVS port for container f2226c12e3786a35e180f669159e1c48dbf44981c7c558b78b8f25da2e8dd74f: __init__() takes exactly 1 argument (2 given)
1 2018-12-05T20:49:05.606Z 37f52426-7afa-4226-b109-60293ad8ce19 NSX 11443 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_node_agent" level="ERROR" errorCode="NCP01004"] nsx_ujo.agent.cni_watcher Unable to retrieve network info for container nsx.kube-system.kube-dns-6b697fcdbd-fb4tg, network interface for it will not be conf

Purpose

Purpose is to overcome container creation failure due to HyperBus interface vmk50 not being present on ESXI.

Cause

Container is not created because the HyperBus interface vmk50 might be missing on vSphere ESXi.

Impact / Risks

None

Resolution

Upgrade to NSX-T 2.3 and post that removed and added back the Fabric nodes or use the below workaround.

Issue 1998217: HyperBus interface vmk50 might be missing on vSphere ESXi causing container creation failure

Container is not created because the HyperBus interface vmk50 might be missing on vSphere ESXi.

Workaround: Complete the following steps.

Retrieve the vmk50 port ID using CLI on vSphere ESXi
net-dvs | grep vmk50 -C 10

Create the vmk50 interface on vSphere ESXi.
esxcli network ip interface add -P <port-id from step-1> -s DvsPortset-0 -i vmk50 -N hyperbus

Assign an IP address to the vmk50 interface.
esxcfg-vmknic -i 169.254.1.1 -n 255.255.0.0 -s DvsPortset-0 -v <port-id from step-1> -N hyperbus

Workaround

Issue 1998217: HyperBus interface vmk50 might be missing on vSphere ESXi causing container creation failure

Container is not created because the HyperBus interface vmk50 might be missing on vSphere ESXi.

Workaround: Complete the following steps.

Retrieve the vmk50 port ID using CLI on vSphere ESXi
net-dvs | grep vmk50 -C 10

Create the vmk50 interface on vSphere ESXi.
esxcli network ip interface add -P <port-id from step-1> -s DvsPortset-0 -i vmk50 -N hyperbus

Assign an IP address to the vmk50 interface.
esxcfg-vmknic -i 169.254.1.1 -n 255.255.0.0 -s DvsPortset-0 -v <port-id from step-1> -N hyperbus

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant