07-24-2018 10:59 AM
Hi,
trying to deploy HX and getting the following error:
07-24-2018 11:09 AM - edited 07-24-2018 01:05 PM
Greetings.
Please confirm you already have an appropriate HX customized version of ESXi installed on the servers before running the HX installer.
What version are you running for:
Thanks,
Kirk...
07-24-2018 04:15 PM
Hi Kirk,
running the pre-installed esxi version that came out of the box from cisco.
Regarding the other components:
Double checked the compatibility matrix all good..no alarms on FIs/Servers..all good in the installer validation..until the hypervisor configuration..
No problems with KVM access...tested SOL ssh with success..
Saw a couple of bugs but don't think its the same..
Thanks in advance.
07-24-2018 05:17 PM
What are your boot drives comprised of ?
SAS SSD, M.2, etc
You might want to fire up the KVM on one of the Rack servers while It's re-attempting to push the install, and see if it's hanging at the UEFI shell.
Thanks,
Kirk...
07-24-2018 05:50 PM
Hi Kirk,
all the disks running same package (Picture in attach)
Regarding the KVM i did made several tests without any problem, access from UCSM, https to CIMC IP, SSH to CIMC SOL..no problem...
Thanks.
07-25-2018 03:28 AM
My reference to the vKVM, was not so much that the vKVM was working, but to see what the ESXi boot process was showing on the console, errors/alerts if any, etc.
Thanks,
Kirk...
07-25-2018 05:13 PM
Hi Kirk,
the esxi boot process is visible in the KVM without any errors..it seem to be very straight forward and successful..
08-14-2018 06:19 AM
I've got similar issue
Looks like ESXi already assigned by static IP or DHCP
In my case it solve by reinstalling ESXi custom ISO and retry Hypervisor configuration from HX installer
09-03-2018 11:55 PM
Retry upgrade fails at validation on vMotion compatibility.
This is due to a sync issue between vCenter and ESXi.
Rescan the storage system on the ESX host using a vCenter client.
See VMware article, Perform Storage Rescan in the vSphere Client, at
https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.hostclient.doc/GUID-FA49E8EF-A3DC-46B8-AA5B-051C80762642.html
Manually power on the VM
Step 1
From ESX command line, power on the VM.
Step 2
Using controller VM command line, run command
# stcli cleaner start
If, during an upgrade, two nodes fail, the upgrade fails because controller VMs do not power on.
Action: Restart EAM Service
Procedure
Step 1
Restart the vCenter EAM service.
From the ESX command line:
# /etc/init.d/vmware-eam restart
Step 2
Proceed with the upgrade.
10-17-2018 07:43 AM - edited 10-17-2018 07:46 AM
Hi,
I have this problem too.
Do you have solved the problem please ?
Thanks.
10-17-2018 03:22 PM
In my case it solved by reinstall ESXi HX custom iso and redeploy HX installer
10-18-2018 05:42 AM
08-20-2020 03:40 AM
sorrym but by what step did it work
05-17-2020 08:57 AM
05-26-2020 08:13 AM
Had the same problem,
Going into the server, right-click and recover server prompt:
Reset CIMC (Server Controller), and it worked!
I got connection to the CIMC.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide