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 6.x with vSAN NIC enabled becomes unresponsive when vsanmgmt service is not running (55959)

Last Updated: 7/20/2023Categories: AlertsTotal Views: 3323Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

When vSAN is disabled at the cluster level but vSAN is enabled on one of the host's network adapters, the host may go into an unresponsive state if the vsanmgmt service is stopped.

The vsanmgmt service is typically disabled when a host is rebooted after disabling vSAN or if there is a network update on the host.

In vmkernel.log or hostd-probe.log, you may see a similar message:

ALERT: hostd detected to be non-responsive

The issue occurs when hostd tries to query vSAN network adapter info through the vsanmgmt service when the service is offline. Because hostd is expecting a response from vsanmgmt and not getting one, it will continue to retry the request. However, if there are multiple concurrent queries happening at the same time they may block the hostd worker threads and causing hostd to lock-up.

Solution

This issue is resolved in ESXi 6.7 GA, available at VMware Downloads.

To work around this issue when you do not want to upgrade:

Determine if you have a residual vSAN network adapter:

# localcli vsan network list

Example output shows vmk4 is our vSAN vmkernel adapter for this host:

Interface
VmkNic Name: vmk4
IP Protocol: IP
Interface UUID: 1dd11858-d4e1-f88d-ca19-90b11c441064
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Multicast TTL: 5
Traffic Type: vsan

Remove the vSAN network interface

Note: Perform only if you are sure that vSAN is not used in the cluster and if there are no plans in using it.

# localcli vsan network remove -i vmk4

Note: After removing the unnecessary vmkernel adapter with vSAN-tag set, the vsanmgmt service should stop on its own after a few minutes.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
デバイスにアクセスできるにもかかわらず iSCSI でバッキングされた VMFS データストアを検出できない (2150992)

KB
•
VMware Workstation Pro 12.x へのゲスト OS としての Windows 10 のインストール (2128790)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

Take Our Survey

Support Assistant