- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Re: Deployement failed step 32 of 34 : Cannot conn...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- 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
- 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