VMware Cloud Community
JamesJon
Contributor
Contributor
Jump to solution

VSphere VCenter Server Appliance install issue

Hi,

After welcome help from you guys I have managed to set up my isolated home lab with an evaluation version of VMware 6.5 ESXi.. The Server 2008 R2 PDC (10.0.0.1) acts as an AD/DNS/DHCP server and it and the windows 7 client (10.0.0.100) ping both ways with no issues. The client joined the domain also with no errors.

However I'm having problems installing the VCSA appliance in that it completes the first part (the install) but wont allow the second part (configuration) to start.

I get the following error saying it cant talk to the appliance.

"Unable to proceed with stage 2 of the deployment process. Click close to exit the installer.

You may attempt to continue with stage 2 by logging in to the appliance at https://vcenter.lab.local:5480/ "

Installer log files are located at C:\Users\LASERL~1\AppData\Local\Temp\vcsaUiInstaller"

When i use that url to login it doesn't connect

I think it may be something to do my isolated network but I cannot work out what, so I was wondering please if someone could look at my 'configure network settings' area of the install to advise?

The network is Isolated

IP version is ipv4

IP assignment is static

System name is vcenter.lab.local

IP address is 10.0.0.101 (reserved)

Subnet mask is  255.255.255.0

Gateway is 10.0.0.1 ( i don't have a gateway as the network is isolated but I have to put an entry in to continue)

DNS Server is 10.0.0.1

Any advice or suggestions would be gratefully received Smiley Happy

Also, the install seems huge (239GB) Is that normal?

Cheers

James

Reply
0 Kudos
26 Replies
thecloudxpert
Enthusiast
Enthusiast
Jump to solution

‌hi James,

so you have a dns a record entry for  vcsa01.cool.local at ip 192.168.0.9 and a PTR record?

IF you do ping -a 192.168.0.9 does it resolve the name vcsa01.cool.local? And when you do ping -a vcsa01.cool.local it returns the 192.168.0.9 up address. It may not actually respond because it doesn't exist But it should resolve.

HAve you try adding the host entry on your admin laptop?

chris

Reply
0 Kudos
JamesJon
Contributor
Contributor
Jump to solution

Hi Chris, sorry for the late reply

I am now on night shift for 4 nights so wont be able to test out my setup until Friday. I will start again from scratch deleing my local host files and wiping Esxi from my server.

A fresh attempt on Friday will hopefully bear fruit.

I will let you know how it goes, and thanks again for all your help and suggestions.

Cheers

James

Reply
0 Kudos
thecloudxpert
Enthusiast
Enthusiast
Jump to solution

Hi James,

I was tinkering with my homelab last night and have created an automatic install file for VCSA for you and uploaded it here VCSA65-JJ.json · GitHub

Download this file and save it to c:\temp.

Edit the file as needed for your environment (change at least the value for datastore, the deployment.network and any passwords you want to change).

The deployment.network should be the name of the Port Group - this may still be VM Network.

The datastore should be the name of the datastore you want to deploy the VCSA too.

Note: i have pre-filled the rest based on our conversations but if you need to change it then please do.

i have used vcsa01.cool.local with an IP of 192.168.0.11

Assuming your cd-rom drive is z: (and you have mounted the VCSA iso to it) type the following command in a CMD/Powershell prompt:

z:\vcsa-cli-installer\win32\vcsa-deploy.exe install "c:\temp\vcsa65-jj.json" --accept-eula --no-esx-ssl-verify --verify-only

This will verify the installation will work with the file.  if that works then run:

z:\vcsa-cli-installer\win32\vcsa-deploy.exe install "c:\temp\vcsa65-jj.json" --accept-eula --no-esx-ssl-verify


And that should automatically install the VCSA for you.

Chris

Reply
0 Kudos
Dee006
Hot Shot
Hot Shot
Jump to solution

James,

Can you share the installation failed logs?I doubt due to resource contention.

Reply
0 Kudos
thecloudxpert
Enthusiast
Enthusiast
Jump to solution

Hi James,

I just noticed in the picture you added that you have your gateway as 192.168.0.10, it should be 192.168.0.1

Chris

Reply
0 Kudos
JamesJon
Contributor
Contributor
Jump to solution

Hi Chris,

I followed your step by step guide from earlier on in this thread from scratch and it worked a treat Smiley Happy

Thanks so much for your help and ideas - without them I would have given up on my lab a long time ago.

James

PS I just noticed your configurable vcsa install in this thread - I would have 100% used that if needed, but happily everything now works and am setting up my SCCM vm.

Reply
0 Kudos
thecloudxpert
Enthusiast
Enthusiast
Jump to solution

Hi James,

Glad you got it working finally.


Happy to help and good luck with SCCM Smiley Happy

You thought your home lab was complicated Smiley Wink

Chris

Reply
0 Kudos