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

Hosts with custom certs appear non-responsive when vmware-vsan-health is enabled on vCenter (77107)

Last Updated: 1/30/2021Categories: TroubleshootingTotal Views: 3846Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

- You are using VMCA as an intermediate/subordinate certification
- You have verified all certificates across the environment are correct and consistent

When starting the vmware-vsan-health service on the vCenter, we see the following error messages in the vpxa.log on the hosts:

2020-01-28T00:27:38.423Z info vpxa[16742038] [Originator@6876 sub=Default opID=vsan-PC-59d27b8701b25-sq111:j1-W910-sq123:j2-c6-98] [VpxLRO] -- ERROR lro-52 -- vsanSystem -- vim.host.VsanSystem.fetchVsanSharedSecret: vim.fault.NotAuthenticated:
--> Result:
--> (vim.fault.NotAuthenticated) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    object = 'vim.host.VsanSystem:vsanSystem',
-->    privilegeId = "none"
-->    msg = "Received SOAP response fault from [<cs p:000000a694a672d0, TCP:localhost:8307>]: fetchVsanSharedSecret
--> The session is not authenticated."
--> }
--> Args:
-->

This eventually leads to the host disconnecting from vCenter with the following messages in the vpxa.log:

2020-01-27T23:58:24.985Z error vpxa[16721871] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500
2020-01-27T23:58:34.991Z error vpxa[16721873] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500
2020-01-27T23:58:44.993Z error vpxa[16721898] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500
2020-01-27T23:58:54.995Z error vpxa[16721875] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500
2020-01-27T23:59:04.990Z error vpxa[16721874] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500
2020-01-27T23:59:14.998Z error vpxa[16721871] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500
2020-01-27T23:59:25.002Z error vpxa[16721899] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500
2020-01-27T23:59:35.006Z error vpxa[16721870] [Originator@6876 sub=HTTP session map] Out of HTTP sessions: Limited to 500

Cause

This is due to VsanMgmtAdapters.py [located in /usr/lib/vmware-vpx/vsan-health/pyMoVsan/] calculating the thumbprint of the hosts incorrectly.

Impact / Risks

Hosts go non-responsive in vCenter losing management capabilities. This affects both vSAN and non-vSAN clusters managed by the same vCenter.

Resolution

Upgrade vCenter to 6.7U3b build 15132721 or higher and ESXi to 6.7U3 P01 build 15160138 or higher.

Workaround

We need to make changes to VsanMgmtAdapters.py to adjust the way it calculates the host certificate thumbprint.
Download the attached script "fix_vsanMgmtAdapters.sh" to /tmp directory in vCenter

Give it executable permissions.
# chmod +x /tmp/fix_vsanMgmtAdapters.sh

Run the script
# /tmp/fix_vsanMgmtAdapters.sh

After this is done, restart the management agents on the host with the following commands.

/etc/init.d/hostd restart
/etc/init.d/vpxa restart

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

fix_vsanMgmtAdapters_sh

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

VMware vCenter Server

Related Versions:

VMware vSAN 6.7.x

VMware vSAN 6.5.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

Take Our Survey

Support Assistant