I am running the vcsa-setup.html off the DVD "VMware-VCSA-all-6.0.0-8874690.iso" and after entering all the required details, the process kicks off and creates the new vCenter server, powers it on but then stops at "Configuring the machine" which is at the point where it starts to install the various applications required for vCenter. I then check the Tasks on the newly created appliance and I can see the error:
Discover virtual appliance
NewvCenterApplianceName
VMware vSphere Update
Manager had an unknown
error. Check the events and
log files for details.
com.vmware.vcIntegrity
MyParentvCenterServerName.local
The following events keep popping up in the Events view of the newly created vCenter server:
Guest operation Initiate File Transfer From Guest performed.
info
11/13/2018 10:46:56 PM
NewvCenterApplianceName
root
This is where the upgrade sits and from what I can see it will sit here for ever:
I can putty to the new appliance but there does not seem to be much there to check. I had VMware support have a look and they said there are no logs they can check until the upgrade process errors-out. They suggested I create a new vCenter server at the new patch level which is ridiculous since all the hosts are on a distributed switch and I would have to power off the old vCenter server, power on the new one then add all the hosts to it. And during this time I would assume the virtuals on the hosts would lose network connectivity?
Putty session to the newly created vCenter appliance:
The original vCenter is Version: 5.5.0.30500 Build 4180648.
Can anyone suggest which logs I should check to see what the problem is?
Message was edited by: Julian Milano
Just a quick guess. Did you set DRS to manual prior to starting the upgrade/deployment to ensure that Initial Placement kick in, and migrate the newly created vCSA to another host?
André
I DID set DRS to manual, but I have not tried another host! I also noticed that when I signed into the vCenter admin console (port 5480) that there was an update so maybe one of these will fix the issue? I'll give it a go, thanks!
Oh, and I tried the upgrade about 4 times so far and the exact same thing happens each time. :smileyconfused:
I logged into the console of the new appliance and this is what I see:
So I logged into the new vCenter server console and opened the "/var/log/vmware/upgrade/upgrade-requirements.log and found the following:
So, it seems that the new appliance cannot contact the host? I tried to ping the host by IP and it did not resolve so I may be able to fix.....
So, I fixed the issue. Not only does the installer need access to both the host management network but so too does the newly created vCenter server, so I created a new VMKernel port group on the standard switch, and configured the VMKernel port group for management traffic and gave it an IP on the same subnet as the vCenter server. In essence, this creates a new entry point to the host and bridges the vCenter server network to the host's management network!
I completed the upgrade with this change! Thanks all for your help.