Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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 -- Error when enabling vSAN Encryption: "Limit exceeded" (52723)

Last Updated: 8/6/2023Categories: TroubleshootingTotal Views: 3453Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Enabling vSAN Encryption fails due KMS Cluster name being too long (= Provided by User).
Error Message: "A general system error occurred: Failed to add key to KeyCache: Limit exceeded."
( seen in Host log: /var/run/log/vsansystem.log )

Cause

The keyId is generated by external KMS and cannot be shortened.
vSAN needs to add keyId to its Key cache along with the kmsClusterName (= KMS Cluster name provided by User).
The field which is being used for that is $kmsClusterName/$keyId .
The max size of this field is 100 bytes.

You will see the error message if $kmsClusterName/$keyId exceeds its maximum size of 100 bytes.
(size is being defined by KEYCACHE_KEYNAME_MAX_LEN )

Example:
The keyId created by the external KMS is 64 bytes long: 5C3AA873097E8AF8AC200B6ED3690B148D9685EC725D3E96730ADC58231FA775
As a result the max size of kmsClusterName can only be 35 bytes (= 100-64-1).
Example: KMIP_Live_Resource_CL_PRE_LN06_0099

Note:
This explanation applies for ASCII characters.
If the Name has non-ASCII codes, please ensure it consumes no more than the aforementioned space limit.

Resolution

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

Workaround

To workaround this issue, define a shorter KMS Cluster (= kmsClusterName ) .

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
•
仮想マシンのハード ディスク使用率のアラームを設定する (2144546)

KB
•
Download and Install VMware Fusion (2014097)

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.5.x

Take Our Survey

Support Assistant