Simplivity Deployment Manager error test host port

[ThsisGenius]

Hi everyone,

I'm here to get some help with one of my new simplivity installation.

First of all, we've done a lot of simplivity installations so we know how it works and how ti deploy a simplivity infrastructure.

The problem I'm facing today is really strange and I can't find a way to fix that.

I have two new servers ProLiant DL325 Gen10 Plus V2 for Simplivity.

So what I've done as usual :

- Checked the interroperability guide, we will install the last version OVC 4.1.2.

- Downloaded the deploy package, the ESXi iso.

- Vcenter 7.0.3e is installed and working fine, simplivity web plugin is also installed a working fine.

- The 2 new servers are initialised, iLOs are well configured, Simplivity OS is loaded with temporary IP's waiting to be discovered.

- Arbiter is installed on a virtual machine as usual, on the same subnet as the servers and vcenter.

- Isolated available IP's to attribute for hosts, ovc, storage, etc...

the problem I have is that the deploy manager software is stuck at the test host settings when he tests everything before doing the deployment.

The first host passed all the tests, but the second is failing at the test of "Host Network Availability", when he test the communication between the deployment manager and the futur host ip for ports 22,80,443, etc...

It fails, communication timed out...

It is completly strange because, the first host passed those tests without problems, configuration are exactly the same. Beside that, there is no restriction in the intranet network, no firewall rules inside intranet. Windows firewall of the virtual machine where run the deployment manager is off, and there is no firewall rules for outgoing traffic... So for me there is no reason at all for that test to fail ! espescially if it works for the first host with the same configuration !

I tried to rung the deployment manager from another machine, same issue. Tried to set another IP for the second host, same issue...

I really don't know how to fix that...

What is struggling me is that I've done the exact same deployment with the same server models just a day before for another client with same ressources and it worked perfectly !

If anyone has an idea it would be great... HPE support wont help... even if I'm Gold partner, with several servers, installations and support licences... because I  dont have a project licence and because the problem is at the installation, they dont want to help.... very nice from them...

Hope you will be more kind

The log file is showing : 

2022-08-11 09:28:24,383Z ERROR main [c.s.d.v.NetworkPortAccessValidator] logValidationSummary(AbstractValidator.java:407) - TcpPortValidator: Check your network environment (for example, firewall) to ensure the Virtual Controller can access the port.
2022-08-11 09:28:24,384Z ERROR main [c.s.d.v.NetworkPortAccessValidator] logValidationSummary(AbstractValidator.java:407) - TcpPortValidator: Deployment Manager 192.168.71.49 cannot communicate with Virtual Controller 192.168.71.46 on TCP port 22.
2022-08-11 09:28:24,384Z DEBUG main [c.s.d.v.NetworkPortAccessValidator] executeTestPlan(ValidationExecutor.java:35) - Deployment Manager to Virtual Controller 192.168.71.46 on TCP Port 80
2022-08-11 09:28:24,385Z INFO main [c.s.d.v.NetworkPortAccessValidator] testPort(TcpPortValidator.java:63) - Testing TCP port 192.168.71.46:80
2022-08-11 09:28:25,386Z ERROR main [c.s.d.v.NetworkPortAccessValidator] testPortAccess(TcpPortValidator.java:135) - Connection failed with error type: DROP
2022-08-11 09:28:25,387Z DEBUG main [c.s.d.v.NetworkPortAccessValidator] testPortAccess(TcpPortValidator.java:136) - Caught exception: java.net.SocketTimeoutException: connect timed out

Here is how look the tests for the first host, everything is passed correctly :

And now the second host with the failed tests.

Thank you everyone.

[support_s]

System recommended content:

1. SimpliVity OmniStack Host Deployment Guide (Release 3.6.1, Rev A)

2. SimpliVity OmniStack Host Deployment Guide (Release 3.6.1 U1, Rev B)

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

Thank you for being a HPE valuable community member.

[ThsisGenius · Accepted solution]

I have found the solution...

During deployment when you choose wich nic to assign to Management or storage, I did check the 2 first 1Gbs nic for management on both nodes.

Probleme was that I think one of the 2 nics of the second node is not connected to the lan but to the dmz ^^

I will need to have a little talk with the colleague who did the install ^^

Well, its solved then.

thank you,

[Sunitha_Mod]

Hello @ThsisGenius, 

Perfect! Glad to know the problem has been resolved. 

[kangpen]

Hello,

how to resolve if we found the same issue like yours ?

thanks.

[Mahesh202]

Hi Kangpen

I suggest you watch the video HPE SimpliVity—Defining Deployment Location and Connecting the Deployment Manager with SVT Host.
This video demonstrates adding a new node to an existing Simplivity federation and how to define Deployment Location and connect the Deployment Manager with SVT Hosts.

Hope this helps.

Regards
Mahesh