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

vSAN KMS Health Check intermittently fails with SSL Handshake Timeout error: "QLC_ERR_TIMEOUT_EXPIRED" on vSphere 6.5 (67115)

Last Updated: 7/20/2023Categories: TroubleshootingTotal Views: 5805Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The vSAN Health Check shows a Warning state for the test "vCenter and all hosts are connected to Key Management Servers" in which ESXi Hosts report Warning/Failures for KMS Connectivity. However, the vCenter Server does not report issues.

Errors in vsanmgmt.log similar to below - using command:

# grep "QueryEncryptionHealth.CheckKmsStatus" /var/run/log/vsanmgmt.log

vsanmgmt.log:2018-11-13T18:15:43Z VSANMGMTSVC: INFO vsanperfsvc[2232d7da-e770-11e8] [VsanHealthEncUtil::GenerateEncryptionHealthSummary] QueryEncryptionHealth.CheckKmsStatus start

vsanmgmt.log:2018-11-13T18:15:44Z VSANMGMTSVC: INFO vsanperfsvc[2232d7da-e770-11e8] [VsanHealthEncUtil::GenerateEncryptionHealthSummary] QueryEncryptionHealth.CheckKmsStatus finish
vsanmgmt.log:2018-11-13T18:15:44Z VSANMGMTSVC: WARNING vsanperfsvc[2232d7da-e770-11e8] [VsanHealthUtil::log] QueryEncryptionHealth.CheckKmsStatus: 1.21s

Errors in vsansystem.log similar to below "grep QLC_ERR_TIMEOUT_EXPIRED vsansystem.log -B 12"

2019-02-05T09:43:13.450Z info vsansystem[9ADA6F0700] [Originator@6876 sub=Libs] VsanUtil: Get kms client key and cert, old:0
2019-02-05T09:43:13.450Z info vsansystem[9ADA6F0700] [Originator@6876 sub=Libs] VsanUtil: Create client context for server kmip
{69804} configure_backend_platform() - Configuring dynamic Linux backends
{69804} open_shared_lib() - Loaded crypto from /lib64/libcrypto.so.1.0.2
{69804} open_shared_lib() - Loaded ssl from /lib64/libssl.so.1.0.2
{69804} open_shared_lib() - Loaded qlopenssl from /usr/lib/vmware/vsan/lib64/libqlopenssl.so
{69804} try_openssl_backend() - Configured OpenSSL backend
{69804} peer_verify_cb() - Pending 3248
{69804} peer_verify_cb() - Verified certificate
{69804} connect_loop() - Connect timeout (1000000) expired
{69804} setup_ssl() - Failed to connect SSL
2019-02-05T09:43:14.596Z error vsansystem[9ADA6F0700] [Originator@6876 sub=Libs] VsanUtil: Failed to connect to key server, Err:QLC_ERR_TIMEOUT_EXPIRED

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

In vSAN 6.5 environments, this error can occur if round-trip latency between the vSAN Hosts and KMS Server exceeds 1 full second. This KMS Timeout value of 1 second is more stringent than the timeout that vCenter Server utilizes which helps explain why the Health Check failure is only reported in the Host KMS Status tab of the vSAN Health Check.

This issue can also be caused by large SSL certificates (larger than 2048 bytes) on the KMS Server which can result in delayed synchronization between ESXi Hosts and KMS.

Impact / Risks

Provided vCenter Server reports no loss of connectivity to the KMS Server and Network Health between the ESXi Hosts and KMS has been validated, this issue can be considered cosmetic in vSphere 6.5 environments and can safely be attributed to the strict network timeout of 1 second.

Resolution

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

Note: In vSphere 6.7, this KMS Timeout is increased from 1 second to 5 seconds to allow the vSAN Health Check to be flexible and closely resemble the KMS check that vCenter Server uses.

Workaround

To work around this issue, in cases where the SSL Certificate size is a contributing factor to network latency between the ESXi Hosts and KMS Server, VMware recommends reducing the size of the certificate to 2048 bits.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vSphere Auto Deploy のトラブルシューティング (2000988)

KB
•
サービス パートナーの FAQ：VMware vSAN での NetApp ONTAP Select のサポート (67037)

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

Results 1-3 of 3

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

VMware vSAN 6.6.x

Take Our Survey

Support Assistant