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

Trusted Infrastructure Host Not Configured Alarm when moving host into a cluster (77234)

Last Updated: 3/8/2022Categories: TroubleshootingTotal Views: 7928Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Trusted Infrastructure Host Not Configured Alarm is triggered after moving an ESXi host into a Trust Authority or Trusted cluster.

com.vmware.vc.TrustAuthority.HostNotConfigured error category event is raised.

Cause

When you add an ESXi host to a Trusted Cluster or Trust Authority cluster, the new host must be consistent with the vSphere Trust Authority configuration already applied to the cluster. The alarm notifies that the added host must be configured in order to use it as part of vSphere Trust Authority. If you move an ESXi host to a Trust Authority or Trusted cluster and do not configure it, the cluster will be in an inconsistent state and you won't benefit from the new host.

Resolution

This issue can be resolved by using a PowerCLI module called VMware.TrustedInfrastructure.Helper that can be found here PowerCLI-Example-Scripts.
The functions in the module will automatically add the host to the desired cluster and configure it.

Prerequisites:

You must be a Trust Authority Administrator, a part of the TrustedAdmins group and also have the Host.Inventory.Add Host To Cluster privilege on vCenter system.

Do not perform any other operations on the ESXi host and existing ESXi hosts in the target cluster when running the script.

The ESXi host must be wiped from existing Trusted Infrastructure configuration. If the ESXi host has been previously configured as part of vSphere Trust Authority (part of a vCenter configured for vSphere Trust Authority, a Trust Authority Cluster or Trusted Cluster), you must use the decommission script first - Trusted Infrastructure Host Decommission Alarm is triggered when host is moved out of a cluster.

Clusters should be in a healthy state (check all vSphere Trust Authority APIs which return Health field).

The ESXi host must be removed from vCenter.

You must know the ESXi host root credentials (username and password).

You must have purchased sufficient license for vSphere Trust Authority.

You must have PowerCLI 12.0.0 and above.

Following PowerCLI modules are required to be imported: VMware.VimAutomation.Security, VMware.TrustedInfrastructure.Helper

Run the command Get-Command -Module VMware.TrustedInfrastructure.Helper. This should inform the following functions are available:

Add-TrustAuthorityVMHost

Add-TrustedVMHost

If you do not see these functions listed, the PowerCLI module is not loaded correctly.

To add an ESXi host to an already configured Trust Authority Cluster:

You will need access to the following information used at the time of configuration of the Trust Authority Cluster:

Host base images binary imgdb.tgz files.

Private part of client certificate (if not using self signed certificates).

In PowerShell, run the command Add-TrustAuthorityVMHost. You can get details about the command by running Get-Help Add-TrustAuthorityVMHost -full:

After cmdlet has finished successfully you can reset alarm state to Green.

To add an ESXi host to an already configured Trusted Cluster:

In PowerShell, run the command Add-TrustedVMHost. You can get details about the command by running Get-Help Add-TrustedVMHost -full.

After the cmdlet has finished successfully you can reset alarm state to Green.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 7.0.0

Take Our Survey

Support Assistant