asked on

VSA installation error

I'm running the auto VSA installation and getting the below error towards the end. The first three tasks complete... Any ideas?

Cannot create VSA cluster. Creating cluster for datacenter: datacenter-59 timed out.

Cluster creation rollback will undo any tasks that where completed. This may take a couple of minutes to complete.

I also see the below. My gateway is not setup in my lab yet.. Once I get it setup does it need to route anything? Everything but the backend network is on the same subnet and VLAN ID. VSA but the backend in a different range/VLAN ID.. Does it simply just need to ping it?

vSphere HA agent on host asxesxi2.asx.local in
cluster VSA HA Cluster could not reach isolation
address: 192.168.251.1
error
9/3/2013 11:56:36 AM
asxesxi2.asx.local

vSphere HA agent on host asxesxi3.asx.local in
cluster VSA HA Cluster could not reach isolation
address: 192.168.251.1
error
9/3/2013 11:56:36 AM
asxesxi3.asx.local

ASKER CERTIFIED SOLUTION

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gopher_49

ASKER

I added a gateway and reinstalled. I'm able to ping the gateway. But.. We just tested the ESXi management network via the test on the console and where it was able to ping the gateway it was unable to resolved DNS. We fixed all DNS issues and starting the VSA install again. Waiting on install to finish now.. I also SSH'ed into each ESXi and they resolve. Where else does this gateway need to route to and/or what does it actually test on the gateway?

Also,

Where can I find the log files? I don't see anymore errors in the events/tasks. I just get the timeout error on the install wizard like before.

gopher_49

ASKER

We're getting the same error.. We tested the management network via each console. It passed.. I don't know what it's actually testing when it tests the gateway but all ESXi hosts can see the gateway, they can ping it, resolve external DNS, and internet DNS. What else is required?

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

check

1. you can ping all by IP Address (Reverse DNS)
2. you can ping all by hostname (DNS)
3. check all gateways

also use tracert, it's important than DNS is working correctly for All Hosts, vCenter Server, VSA

gopher_49

ASKER

We got it to work... The backend network was on VLAN ID 250. So, we setup a dedicated interface for VLAN ID on the Endian firewall. We assigned it 192.168.250.1. We then put the two IP addresses of the backend servers in this VLAN ID and/or network range... Then it worked just fine... Everything looks good now!