Can't install VCSA 6.7

[AvivKR]

Hi everyone,

my name is Aviv and i'm new in vSphere "world".

I need help, I made a home lab on my PC (I5 8250, 32GB, 500SSD)

I installed 2 Machines running SVR16 (dc,DNS role) with 4gb 2 CPU and SVR12R2 (vCenter) with 4gb and 2 CPU

Then have my 2 ESXI Hosts 6.5: 4CPU 11GB.

But when trying install VCSA 6.7 i got this ERROR:

This happened on 0% after I made whole 9 first stages.

And here what I got in the Installer Log:

2018-12-24T11:16:41.379Z - info: output:ERROR

+ <Errors>

2018-12-24T11:16:41.379Z - info: output:+ <Error>

+ <Type>

+ vim.fault.FileFault

+ </Type>

+ <LocalizedMsg>

+ Error caused by file /vmfs/volumes/5c20bdee-3d02f254-264c-000c2949f5aa/vCenter Server

+ </LocalizedMsg>

+ <Arg type="string" fieldName="file">

+ /vmfs/volumes/5c20bdee-3d02f254-264c-000c2949f5aa/vCenter Server

+ </Arg>

+ </Error>

+ </Errors>

RESULT

+ ERROR

2018-12-24T11:16:41.379Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>vim.fault.FileFault</Type><LocalizedMsg>Error caused by file /vmfs/volumes/5c20bdee-3d02f254-264c-000c2949f5aa/vCenter Server</LocalizedMsg><Arg type="string" fieldName="file">/vmfs/volumes/5c20bdee-3d02f254-264c-000c2949f5aa/vCenter Server</Arg></Error></Errors></data>

2018-12-24T11:16:41.379Z - error: Ovf Service:vmrefFlag: false

2018-12-24T11:16:41.379Z - info: Cancelling timeout due to error from progress callback

2018-12-24T11:16:41.394Z - error: Progress Controller: [VCSA ERROR] - Progress callback error

2018-12-24T11:16:41.394Z - error: Progress Controller: [VCSA ERROR] - Details Error caused by file /vmfs/volumes/5c20bdee-3d02f254-264c-000c2949f5aa/vCenter Server

2018-12-24T11:16:41.409Z - info: Cancelling the ping timer for session mgmt

2018-12-24T11:16:41.410Z - info: Cancelling the ping timer for session mgmt

2018-12-24T11:16:41.446Z - info: ovfProcess child process exited with code 1

2018-12-24T11:17:42.215Z - info: User clicked on the cancel button to Close Dialog

2018-12-24T11:17:53.657Z - info: Log file was saved at: C:\Users\administrator.KRIEF\Desktop\installer-20181224-031133553.log

Sorry on my bad English.

Plz Help me!!!!

Thank you!

[ChrisFD2]

Are you migrating from a Windows 6.5 install to 6.7 on an appliance?

[AvivKR]

Hi, no.

Installed the 6.7 version, I need to install 6.5 version first?

[ChrisFD2]

You mention:

I installed 2 Machines running SVR16 (dc,DNS role) with 4gb 2 CPU and SVR12R2 (vCenter) with 4gb and 2 CPU

Why do you have a Windows server for vCenter? I assumed by the above that you are upgrading.

If it's a new install, deploy a new vCenter appliance. Ensure forward and reverse lookup entries for all hosts and the new vCenter box are in DNS.

[AvivKR]

The server only called vCenter.

Now, I want to install on him vCenter.

Where do I install vCenter if not on windows SVR?

[ChrisFD2]

You open the ISO file on a computer that has network access to your hosts. You then run the UI installer and point it at a host.

It then deploys a Photon OS template to the host and configures it depending on your inputs. This Photon machine is the embedded vCenter appliance.

I believe VMware are discontinuing vCenter on Windows after 6.7 so there's little point in using Windows for it.

https://www.tech-coffee.net/step-by-step-deploy-vcenter-server-appliance-vcsa-6-5/

Plenty of other guides on the usual blog sites.

[AvivKR]

that's exactly what I've done..

when I get into the last stage and click "install" it began and 1 minute after I get the ERROR above

I"ll said now all the process I've done:

first machine: SVR 16 (DC, DNS, ISCSi roles)

2nd machine: SVR12R2 called: vCenter. Installed on it: FireFox, vmware vSphere Client

3rd machine: ESXi Hypervisor 6.5

4th machine: ESXi Hypervisor 6.5

All the machines are in my Virtual domain called "Krief.net", and have connection between all the machines.

For the 2 ESXI have ISCSi 310 GB disk. Now i want to install vCenter Server Appliance to make a cluster between those "hosts"

Please help me my friend!

[ChrisFD2]

That makes more sense. Are the machines on VMware Workstation?

Can you create a VM on either of the hosts via the host UI directly, on the datastore which you attempted to install the appliance on?

[AvivKR]

Yes, the machines are on VMware Workstation.

Sorry I don't know what you mentioned for UI.

but if realize right.. Yes I can create VM's on my ESXI hosts...

[ChrisFD2]

On the same datastore you're installing the appliance on?

What licenses are assigned to both hosts? Are they on the eval license, or free license?

[daphnissov]

Please show screenshots of the installation process you're using for the vCSA. Please also ensure those screenshots capture the actual ​values​ you're supplying so we can see where the problem is.

[AvivKR]

free license 60 days.

and after i've tried some changes.. The installation began and now have other problem

In 80%, RPM installation- I got this error:

here is the screen shots:

[AvivKR]

>

[a_p_]

You seem to have duplicate IP addresses in your network!?

Please explain your virtual network setup in VMware Workstation, the ESXi hosts, and the VMs (configuration, IP addresses used, ...).

Also note that VMware Workstation usually uses the ".1" IP address for the host virtual network adapter, and the ".2" IP address in case of NAT.

André

[IRIX201110141]

AvivKR​

there is

vCenter for Windows (version 6.7 is the last one)

vCenter as Appliance called VCSA (this is the future)

If you name a new Windows VM "vCenter" and try to install VCSA this confuse the ppl which like to help. Because this usecase is only valid when you wanna migrate from Windows vCenter to the VCSA.

The VCSA Installer push the VCSA through a  OVA/OVF deployment like style to the ESXi. It tries to place the new VM on a ESXi Datastore you have specifed in the Installer... /vmfs/volumes/*aa5/ and this went fail.

Please: Can you try to create a VM within your virtual ESXi on that Datastore?  Also you should take care of any kind of security software(anti virus) on the maschine your performing the installation from.

Hint: The one and only "Client" today is your Browser. So you can remove your vSphere Client on your Windows vCenter VM.

ESXi:

Host Client = WebGUI on the ESXi = http://esxip/ui

vCenter:

VAMI = Adminpage of the VCSA = https://vcsaip:5480

WebClient = Flash based GUI = https://vcsaip/

HTML5 Client = Non Flash = https://vcsaip/ui

Regards,

Joerg

[AvivKR]

Whole my VM's is in the same NAT adapter in subnet 172.16.1.0/24

DC: 172.16.1.1 (the dns of all machines)

vCenter: 172.16.1.2    

ESXI 1 : 172.16.1.44

ESXI 2 : 172.16.1.55

Default Gateway: 172.16.1.254

Virtual Editor Snap:

[a_p_]

According to the error message "172.16.1.2" is already in use!?

What I would do is to simply use another IP address. Make sure that you reconfigure the DNS records (Forward, and Reverse) for the vCSA in that case.

André

PS: You cannot use the same IP address for the "vCenter" Windows VM, and the vCSA! Theses are two different systems, and each of them requires its own unique IP address.

[AvivKR]

Hoooo... Sorry.

I am a Beginner in this vMware "world" ..

I dont have any anti-virus in my VM's and even the firewall is off..

why the RPM installation is faild ?

there is only 5 addresses in my Virtual Network.. there is no way for duplicate.!

and Yes I can create VM on datastore.

[daphnissov]

If you insist your networking is correct (.2 is usually in use by the host), then two things:

1. Double check you have forward AND reverse DNS records set up in your local DNS server for this vCSA appliance.
2. Change the prefix into a subnet mask (octal). Past attempts at using a prefix length (24) has resulted in failure whereas subnet mask did not. Something to try.

[IRIX201110141]

Setting up a vSphere Environment as a Virtual one is not a beginner task

After the initial placing of the OVA and turning on the VM the installer try to reach the Linux OS for Post installation processes over the network. In your setup this went fail.

Reasons:

- VM on wrong/not reachable Virtual Network(Portgroup)

- Mistyped IP Settings

- Wrong (Reverse) DNS