- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Deployement failed step 32 of 34 : Cannot connect ...
-
- 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, 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
07-25-2019 05:50 AM
07-25-2019 05:50 AM
Deployement failed step 32 of 34 : Cannot connect to Virtual Controller after rebooting it.
This is regarding 3.7.9 deployment ( 2 nodes ). The first node got deployed successfully, the second node fails at step 32 with the aforementioned error message. Tried deploying the node 3 times, but the nodes fails at step 32 whatsoever. The following action plans were performed, which failed to resolve the issue :
.) Re - seating the TIA card ( through CLI commands ).
.) Tweaking DNS configuration.
.) Manually updating the identity store.
.) Checking the ports.
We went through the Orchestrator log, but coulnd't find anything relevant or helpful to the concerned issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-26-2019 12:36 AM
07-26-2019 12:36 AM
Re: Deployement failed step 32 of 34 : Cannot connect to Virtual Controller after rebooting it.
Hi @Karthik7 ,
Usually once the deployment has reached this stage most of the installation steps have been completed locally on the OVA, are you able to log in to it through an SSH or Console session? The last step would entail the Federation join step which can be completed manually using the dsv-federation-join command (refer to the 3.7.9 command reference guide).
Otherwise it would be best to open a support case to look in to this further should you still be hitting this road block.
I work for HPE

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