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

Trusted Infrastructure Host Decommission Alarm is triggered when host is moved out of a cluster (77146)

Last Updated: 10/14/2021Categories: InformationalTotal Views: 4189Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

Trusted Infrastructure Host Decommission Alarm is triggered after moving an ESXi host out of a Trust Authority or Trusted cluster. A com.vmware.vc.TrustAuthority.DecommissionHost error category event is posted.

Cause

When you remove an ESXi host from a Trusted Cluster or Trust Authority cluster, the host continues to retain its vSphere Trust Authority configuration. The alarm notifies that the moved out host must be decommissioned by following a specific procedure. This is a necessary step the user must perform in order to remove the existing vSphere Trust Authority configuration if they desire to continue using the host. Failing to perform the decommission procedure results in a security risk and undefined behavior if the user decides to use the host in other Trusted Infrastructure clusters. Decommissioning a host removes its vSphere Trust Authority Configuration.

Resolution

Prerequisites

You must be a Trust Authority Administrator

Do not perform any other operations on the ESXi host when running the script

Steps:

Remove the ESXi host from the Trust Authority or Trusted cluster.

Remove the ESXi from the vCenter inventory.

Use SSH or another remote console connection to start a session on the ESXi host.

Log in as the root user.

Extract the script from the attached file 77146_trusted-infra-decommission-esx.zip

Copy the script trusted-infra-decommission-esx.sh to the ESXi host  and change the permissions to make it executable                                                                                                                                                                             chmod +x /tmp/trusted-infra-decommission-esx.sh

Run the trusted-infra-decommission-esx.sh bash script

Once the decommission process has finished, a reboot is required. The script will ask at the end whether you want to perform it now. Type "Y" for yes or "N" for no and press Enter.

When the reboot is complete. Re-add the ESXi host to the vCenter inventory.

Reset the alarm state to Green.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

77146_trusted-infra-decommission-esx

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 vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant