Query: HPE SimpliVity 5.3.1 Deployment manager cannot communicate with virtual controller

[Deepak14]

I am deploying HPE SimpliVity 5.3.1 on a two-node DL380 Gen10 setup, and during the pre-validation phase, the Deployment Manager cannot reach the OVC IP (Node 2) on required TCP ports (22, 443, 80, 9190, and 9299). The host IP for Node 2 is reachable from the Deployment Manager on ports 22 and 443, and Node 1 passed validation successfully. I have verified the USB deployment media, network connectivity, and iLO access for Node 2, but the OVC IP remains unreachable. Has anyone experienced this issue or can suggest steps to ensure the OVC IP is correctly bound during deployment?

[Joshua610]

Good day, 

Any further information in regards to what on network that could be blocking that communicaiton? What was found within the logs? MTU's etcs..?

"Get-Content “C:\Users\<yourUser>\AppData\Local\DeploymentManager\orchestrator-<date>.log” –wait"   [This command can be ran to monitor logs during deployment] 

Those are some important ports during the deployment (for quick references): 

9292/9299 TCP Deployment Manager : Deploy Installer IP (ESXi Mgmt. IP) and Virtual Controller Management IP. Deployment Manager access to the system over SSL. This port must be open to deploy the system.

9190 TCP vSphere Client & vCenter Server : Virtual Controller Management Disaster Recovery : HPE SimpliVity Management GUI
80 TCP Deployment Manager : ESXi Management IP : Monitoring deployment

443 TCP Deployment Manager : vCenter Server : The default port that the vCenter Server system uses to listen for connections from the Deployment Manager.

22 TCP Deployment Manager : Deploy Installer IP (ESXi Mgmt. IP), Management Production and Virtual Controller Management IP : For underlying communication for SSH and deployment. Also for communication to already deployed Virtual Controller.

I will follow up in a day or so - Do you have access to the the deloyment guide? 

[Joshua610]

Please let me know if you need any further help - thank you. 

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

[samuele84]

Hello, we have the same problem on deploying two 380 Gen10 SVT Nodes. We have error on all TCP (22, 80, 443, etc...) ports for HOST IP and OVC IP during the prevalidation test.

We have the error on both nodes and we are locked out to continue with the setup

Any idea on how to solve this issue?

[Sanika]

Hello @samuele84 

When deploying HPE SimpliVity, issues with OVC IP can arise due to incorrect network configuration, firewall rules, or errors during the deployment process.

Below are some steps that may help you:
First, make sure the OVC VM is actually deployed and powered on.
Then confirm that its network settings like VLAN and port group are correct, and match what Deployment Manager expects.
Ensure no firewall is blocking required ports (22, 443, 80, 9190, 9299).
If the OVC IP was assigned via DHCP, check that it received the correct address. If it’s static, verify that it’s configured properly.
You can test connectivity by pinging the OVC IP or using telnet to check if ports like 443 and 9190 are open.
Once you’ve confirmed the OVC is up and reachable, reboot Node 2 and rerun the validation in Deployment Manager.

For more information on this, you may refer the below doc:
HPE SimpliVity 5.3.1 for vSphere Documentation - Deployment Manager

If it still doesn’t work after trying everything, I recommend reaching out to HPE SimpliVity support. Provide them with detailed logs and configuration information.

Regards,
Sanika.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.

[samuele84]

Hello Saika abd thanks for your answer.
The two nodes are formatted and resetted with SVT preOS (deployment OS) ready to be discovered.
So there’s no OS installed into nodes.
We can’t reach the host or ovc ip simply because they don’t exist yet.