- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Cannot deploy new host to the selected cluster bec...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-15-2019 09:07 AM
08-15-2019 09:07 AM
Hello Team,
After we deployed first simplivity node in the cluster successfully we are trying to deploy the second one but unfortunatly the deployment manager gives us the folowing error:
"cannot deploy new host to the selected cluster because it contains unresponsive hpe omnistack host"
we are using Simplivity 3.7.8 Vcenter appliance 6.5
Please Advice any suggestion ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-16-2019 12:31 AM - edited 08-17-2019 01:17 AM
08-16-2019 12:31 AM - edited 08-17-2019 01:17 AM
Re: Cannot deploy new host to the selected cluster because it contains unresponsive HPE Omnistack ho
Hi @RalphYammine,
It's difficult to say what issue you are hitting here exactly, is this a Hyper-V deployment? I have seen issues where Deployment Manager is unable to reach the node over ports 80 and 443, a quick check would be to reboot the SCVMM server (if applicable) and retrying the deployment.
Otherwise your best approach would be to open a support case with us and we will work on it from there. You will need to provide the following logs, which are generated on the client you run Deployment Manager from (C:\Users\<yourUser>\AppData\Local\DeploymentManager\);
- FindDeployable.log
- orchestrator.log
- SvtDeploymentManager.txt
I hope this helps,
I work for HPE

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-16-2019 08:55 AM
08-16-2019 08:55 AM
Re: Cannot deploy new host to the selected cluster because it contains unresponsive HPE Omnistack ho
We tried to reboot the Vcenter with no luck ,
The Deployment Manager is unable to reach the node on port 443.
now we opened a case with HPE.. thank you for your reply.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-20-2019 07:13 AM
08-20-2019 07:13 AM
SolutionHello KG ,
it was a network problem between the deployment manager and the omnistak management IP Address
it is Solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-21-2019 12:25 AM
08-21-2019 12:25 AM
Re: Cannot deploy new host to the selected cluster because it contains unresponsive HPE Omnistack ho
Thanks for following up @RalphYammine and I'm glad to hear you were able to resolve this.
All the best!
I work for HPE

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP