Add support for removing HCX ESXi hosts from System Overview Report host count

[serbiansky]

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

When HCX IX is used it create virtual ESXi hosts which is added to Datacenter directly (not part of any cluster). If customer have multiple clusters they can have multiple HCX IX ESXi hosts added to Datacenter.

In such case when System Overview Report is generated number of hosts in Hardware Overview will be correct but in vCenter Server Overview Total Hosts will be incorrect as HCX IX hosts will be added.

Use Case(s)

All customers with HCX IX configured as that configuration will deploy ESXi virtual appliance added to Datacenter and number of hosts in System overview Report will not be accurate.

Potential Configuration

Goal is to identify and remove HCX IX virtual ESXi hosts from Total host count in vCenter Server Overview. One way of identifying HCX IX ESXi virtual hosts is by Server Model which is VMware Mobility Platform.

Or other way can be by resources available on that Host which is 768 CPUs and 24 TB of RAM.

HCX IX Host:

Regular ESXi host (virtual example):

References

Best explanation of HCX IX I found here, for older version, but still relevant https://www.softwaredefinedblog.com/hcx-mobility-agent-aka-dummy-host/

[tenthirtyam]

Hi @serbiansky - could you provide an -anonymized of report that shows the HCX IX virtual ESXi hosts being returned in the overview report? Since the report only collects this information directly from SDDC Manager, I think that these would not appear by default.

[serbiansky]

I will request next week from some of my customers with HCX.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.