Cannot create VSA cluster

[Owenb9]

I am running 2 nested ESXi 5 hosts and  VSA 5.1. When I attempt to create the VSA cluster I get the following error:

Cannot create VSA cluster: Unable to login to VMware Cluster Service at: https://172.30.30.160:4336/services/pseudosvaservice. Please ensure the service is up, and retry.; nested exception is:
java.net.ConnectException: Connection timed out: connect

I have 4 nics on each host in the default configuration. I have tried putting the VSA back end on a different VLAN and subnet. Running netstat tells me that port 4336 is listening for connections and the VSA cluster service is up and running. Does anyone know what might be causing this? I have included the log file.

Thanks.

[JPFrancis80]

I assume that the 172.30.30.160 address is the IP address of you vCentre server and this is where you have installed the VSA cluster service.

You need to make sure that the port is open through windows firewall. Also any vlans you configure need to be tagged on all ports on the switch as VSA will automatically select the network cards.

I only added a second card to vswitch0 and plugged in the other two NICs but left all other configuration default.

I hope this helps as it solved the issue for me.

[squeaky369]

I am having the same issue, althought mine is:

Cannot create VSA cluster: Unable to login to VMware Cluster Service at: https://192.168.6.211:4336/services/pseudosvaservice. Please ensure the service is up, and retry.; nested exception is:

java.net.ConnectException: Connection timed out: connect

Different IP.

The 192.168.6.211 is the VSA Cluster Service IP Address that is entered during the installation. It was my understanding that this is the IP address that is assigned to one of the VM's that the cluster creates to maintain the storage. I don't even see those VMs being created when I get the error, and it happens only after a few seconds after starting the installer.

I went ahead and changed that IP to the vCenter server, and it appears to be going. This is different from VSA 1.0 when I set that to what I wanted the virtual machine to be...

I'll know in about 20 - 30 minutes if it works or not. I'll report back if it does or not.

[CHogan]

In a 2 node cluster, you need to explicitly point to the VSA cluster service.

If vCenter is in the same subnet, you can point to the VSA cluster service running in vCenter.

If vCenter is in a different subnet, such as might be the case in a ROBO deployment, you will need to deploy a Linux or Windows VM or physical host at the remote site (where the VSA is) and install the appropriate VSA service - more details here: https://my.vmware.com/web/vmware/details?downloadGroup=VSP51-VSA-51&productId=285&rPId=2766

Then, when the VSA installer asks for the IP address of the VSA service, you supply the ip address of the host or VM where the VSA cluster service is running.

HTH

Cormac

[jraimer]

I ran into the same error installing VSA 5.5. In my case, it turned out that the installer did not add the second IP address (the one defined during the VSA install script along with all the other IP's) to my vCenter server. I added it manually and confirmed it with ipconfig. After doing that, I pressed the back button on the VSA installer and went forward again. It moved past that issue.

Good luck!

[philip8]

Thanks Cormac.

A Windows VM with VSA service in the same subnet as the ESXi hosts did the job.

After that the "VSA Installer" on the vCenter Server performed the steps:

• Configuring VSA cluster network
• Deploying vSphere Storage Appliance
• Installing VSA cluster
• Mounting the datastores

Kind regards,

Philip