cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2346
Views
10
Helpful
7
Replies

Errors found during hypervisor Configuration

almccanuel
Level 1
Level 1

Hi Guys,

Good Day,

I want to share error that we encounter during our installation of Cisco Hyperflex,

Can you help identify the cause of this error?

Thanks

7 Replies 7

Manish Gogna
Cisco Employee
Cisco Employee

Hi,

I would suggest following the Hyperflex install guide below to ensure that the compatibility requirements and exact procedure is followed

http://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/GettingStartedGuide/2-0/b_HyperFlexSystems_GettingStartedGuide_2_0/b_HyperFlexSystems_GettingStartedGuide_2_0_chapter_011.html

Manish

- do rate helpful posts -

gassolini
Level 1
Level 1

Check if CIMC ips have been assigned in the UCS manager see attached image.

Cheers Sandro

Ignacio Orozco
Cisco Employee
Cisco Employee

Make sure the CIMC IP addresses have been assigned to the severs from the IP Pool hx-ext-mgmt.

Also, make sure you can ping them from the installer. This can be done by SSHing into the installer VM and log in as root with the password of Cisco123 (Unless the password was changed).  In addition, ensure that the IPs are in the same subnet as the UCSM since the connection to the CIMCs IP traverse the management ports on the Fabric Interconnects for out of band management.

jkilleda
Level 3
Level 3

Hello Al Mc. Ronald,

Errors found during hypervisor Configuration
You need to check UCS FI configuration as well as ESXI configuration.

Hello,
I am also experiencing same issue, however the only difference is that it shows success rate is 1 out of 3 nodes. I am not even able to take kvm session for the 2 hx nodes that fail.
I tried giving manual ip in esxi hypervisor for those nodes but no luck.
Any help would be much appreciated.
Regards
Asif

aliasifali
Level 1
Level 1
Hi,
Did u manage to sort out this issue????

Errors found during hypervisor Configuration

Case Solution:
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.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: