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

ESXi Hyperbus is stuck in MISS_VERSION_HANDSHAKE state (76131)

Last Updated: 2/26/2020Categories: InformationalTotal Views: 4971Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The following symptoms are observed

NSX-T environments running versions earlier than 2.5.0

PKS cluster creation fails

vmk50 exists on the ESXi host

#esxcfg-vmknic -l | grep hyperbus
vmk50      c35cb381-946e-440e-ba3f-70b626689736    IPv4      169.254.1.1    255.255.0.0     169.254.255.255 00:50:56:6e:70:8a 1500    65535     true    STATIC              hyperbus

Hyperbus state is MISS_VERSION_HANDSHAKE

#nsxcli -c get hyperbus connection info
VIFID                            Connection                         Status
73e4cfe8-d761-4bcc-ae4f-2f26079d4948         169.254.1.10:2345              MISS_VERSION_HANDSHAKE
841ff404-d528-49a9-8a92-b8f99477a2b4         169.254.1.11:2345              MISS_VERSION_HANDSHAKE

Hyperbus TCP state is SYN_SENT

#esxcli network ip connection list -N hyperbus
Proto  Recv Q  Send Q  Local Address      Foreign Address    State     World ID  CC Algo  World Name
-----  ------  ------  -----------------  -----------------  --------  --------  -------  ----------
tcp         0       0  169.254.1.1:29357  169.254.1.10:2345  SYN_SENT  22107284  newreno  netcpa
tcp         0       0  169.254.1.1:47155  169.254.1.11:2345  SYN_SENT  22107284  newreno  netcpa

ESXi Firewall has hyperbus disabled blocking the traffic on port 2345

# localcli network firewall ruleset list | grep hyperbus
hyperbus                       false

Cause

The hyperbus communication is from vmk50 to destination TCP port 2345. This traffic must be allowed by the ESXi firewall.
There is a known issue on NSX-T when netcpad service is restarted it will disable the hyperbus component of the ESXi firewall

#localcli network firewall ruleset list | grep hyperbus
hyperbus                       true

#/etc/init.d/netcpad restart

#localcli network firewall ruleset list | grep hyperbus
hyperbus                       false

Resolution

This issue is resolved in NSX-T Data Center 2.5.0

Workaround

Re-enable hyperbus connections on the ESXi firewall

#localcli network firewall ruleset set -e true -r hyperbus

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
仮想マシン ハードウェアの変更後または vMotion の後、DFW ルールが想定どおりに機能しない (76111)

KB
•
在同一 Edge 上的两个第 1 层之间无法建立 IKEv1 会话 (76177)

KB
•
NSX Manager 升级到 6.4.5 或更高版本后，将从所有 NSX 群集中卸载 NSX。 (76106)

KB
•
NSX-T で使用可能なトンネルがない場合でも、トンネルが「UP」と表示される (76104)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant