Skip to main content
NetApp Knowledge Base

Hyper-V Cluster Acquisition Fails with “Failed to create Hosts for the cluster”

Views:
31
Visibility:
Public
Votes:
0
Category:
data-infrastructure-insights
Specialty:
ds_dii
Last Updated:

Applies to

  • Data Infrastructure Insights (DII)
  • Microsoft Hyper-V Data Collector
  • Environments using Illumio or similar micro-segmentation firewalls

Issue

When attempting to poll Hyper-V clusters using the DII, acquisition fails for certain production clusters. The error message in the logs and UI is:

Inconsistent data retrieved: Failed to create Hosts for the cluster: '<ClusterName>'. Please check if the Host IPs are available in the cluster.

Example log output:

2025-09-22 21:39:22,070 ERROR [com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource] ClusterName[Inconsistent data retrieved] - Failed to create Hosts for the cluster: 'ClusterName'. Please check if the Host Ips are available in the cluster.com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: Failed to create Hosts for the cluster: 'ClusterName'. Please check if the Host Ips are available in the cluster....[DEBUG] Invoking command at RemoteHost - ComputerName: ClusterName.global.az.com[ClusterName.global.az.com] Connecting to remote server ClusterNmae.global.az.com failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.+ CategoryInfo: OpenError: (ClusterName.global.az.com:String) [], PSRemotingTransportException+ FullyQualifiedErrorId: CannotConnect, PSSessionStateBroken

  • Test-NetConnection to port 5985 (WinRM) from the Acquisition Unit to the affected hosts succeeds.
  • Only some nodes in the cluster are affected; others respond and are inventoried.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.