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

NSX Host Preparation fails with an EAM error: "Host is no longer in vCenter inventory" (52550)

Last Updated: 7/30/2020Categories: TroubleshootingTotal Views: 9293Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

NSX Host preparation failure.

VXLAN / FDW

Guest Introspection

Third Party Integration

EAM is not preparing newly added host to NSX Cluster.

EAM MOB may be loading a blank page.

EAM logs contains entries similar to:

| ERROR | vc-callback | AgencyImpl.java | 1295 | Failed to add agent to agency (AgencyImpl(ID:'Agency:XXXXX')): java.lang.RuntimeException: Host is no longer in vCenter inventory.

Cause

This scenario occurs by the method used to migrate ESXi host(s) between clusters. For example, migrating an ESXi host from standalone (No cluster affiliation) into an NSX prepared cluster.

The host parent relationship is present in two properties:

(Cluster) ComputeResource's host (a list of hosts' IDs)

HostSystem's parent (id of a (Cluster)ComputeResource)

These two properties are not updated simultaneously.

Seldom (due to several conditions - network latency, concurrent locks, etc.) when an ESXi host is moved from standalone (or directly added to the cluster), the property change for cluster.hosts is received but host.parent still points to the previous object (that no longer exists).

When this condition occurs and EAM tries to create an internal representation of the host by traversing its parent, the error "Host is no longer in vCenter inventory" occurs and no agent (no preparation) is created for this host.

There are two different versions of this issue depending on the vCenter version:

Cause 1 - "Host is no longer in vCenter inventory" - vCenter 6.0 prior to U3c

ESXi Host is moved from Standalone to NSX prepared cluster.

ESXi Host is removed from vCenter without first removing EAM / NSX Configuration.

Later, ESXi Host is added back to vCenter and to a NSX prepared cluster.

EAM tries to prepare it by creating an Agent which eventually fails since the HostSystemMo in VPXD is pointing to the old or wrong parent ID that is no longer existing in the VPXD inventory.

Note: This is happening for a short time window when moving standalone host into a cluster because standalone host's parents are stopped after the host joins a cluster.

EAM fails with 'RuntimeException: Host is no longer in vCenter inventory' and host moId is still persisted in EAM's runtime.

Cause 2 - "Host is no longer in vCenter inventory" - vCenter 6.0 U3c and U3d

Similar to cause 1; ESXi Host is moved from Standalone to NSX prepared cluster.

vCenter 6.0 U3c and 6.0 U3d introduce a different problem with a mechanism which cleans up every record for the created Agent regarding adding host except the mapping record for that Agent in the Agency.

The software defect is that EAM will unload all of the existing agents from the agency in EAM Runtime.

EAM logs contains entries similar to:

| ERROR | vc-callback | AgencyImpl.java | 1295 | Failed to add agent to agency (AgencyImpl(ID:'Agency:XXXXX')): java.lang.RuntimeException: Host is no longer in vCenter inventory
| WARN | eam-0 | AgencyImpl.java | 1954 | Disposing agency: AgencyImpl(ID:'Agency:XXXXXXX') due to failed load up.
| ERROR | eam-0 | AgencyImpl.java | 1895 | Failed to load agent: ManagedObjectReference: type = Agent, value = f18cd000-dcd5-4d30-8d6b-5f12b04e46fa, serverGuid = b0827a9b-fccd-41dd-8b27-caf8418da719. Error: null java.lang.NullPointerException

EAM MOB Fails to Load “Host not covered by scope anymore”

Potential side effect consequence of either Cause 1 or Cause 2.

Caused by restarting EAM service while it is in bad state due to issues described above.

EAM logs contains entries similar to:

| ERROR | eam-0 | VcListener.java | 116 | An unexpected error in the changes polling loop
| ERROR | eam-0 | AgencyImpl.java | 1895 | Failed to load agent: ManagedObjectReference: type = Agent, value = d6429441-6953-4795-81ff-efc455232e9a, serverGuid = b0827a9b-fccd-41dd-8b27-caf8418da719. Error: Host not covered by scope anymore

Resolution

This issue is resolved in VMware vCenter Server 6.5, available at VMware Downloads.

Note: Otherwise, a database maintenance is required , please file a support request with VMware Support and quote this Knowledge Base article ID (52550) in the problem description. For more information, see How to Submit a Support Request.

Workaround

To work around this issue:

Depending on the severity of the situation, restart of EAM might resolve agents missing from EAM runtime.

A preventative workaround would be to add host to non-NSX prepared cluster prior to moving to NSX Cluster. (Avoid moving standalone host to NSX Prepared cluster)

There is a VPXD parent ID assigned to host while it is standalone, this is not the case while host is part of a cluster. The software defect is related to the VPXD parent ID and mechanism of removal while transitioning to NSX prepared cluster.

Related Information

NSX ホストの準備が次の EAM エラーで失敗する：「ホストが vCenter Server のインベントリに存在しなくなりました(Host is no longer in vCenter inventory)」 (53494)
简体中文：NSX 主机准备失败并出现 EAM 错误：“主机不再位于 vCenter 清单中 (Host is no longer in vCenter inventory)”

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
•
打开虚拟机电源失败：Could not create '/vmfs/volumes///.nvram': (2108718)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

Take Our Survey

Support Assistant