HPE SimpliVity
cancel
Showing results for 
Search instead for 
Did you mean: 

Deployement failed step 32 of 34 : Cannot connect to Virtual Controller after rebooting it.

 
Karthik7
Occasional Contributor

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.

1 REPLY 1
KGman
HPE Pro

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.