I added a ESXi host to a cluster and everything seems smooth.
However, when I tried to migrate a VM to the new host, I am getting the attached message.
Please advise what I should look at.
Thanks in advance.
VMware
Last Comment
Albert Widjaja
8/22/2022 - Mon
Richardson Porto
Sorry, but where is the attachment ?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
You must check
1. ALL VMKernel Portgroups, you have selected for vMotion, can ALL ping each other, and more importantly VMKPING each other and communicate. ping and vmkping are commands you can use at the console of the ESXi host server, or remotely via SSH.
2. ALL VMKernel Portgroups selected for vMotion all have the same MTU or Jumbo Frame setting.
3. Whilst at the console or remotely via SSH, you can also troubleshoot whilst looking at the logs in /var/log/vmkernel.log you can also use the command tail, and watch the logs when you complete a vMotion, to also check for errors in the log.
The new host has a Intel (R) Xeon(R) CPU E5-2667 v4 @ 3.2GHz - Please see attached.
The other hosts in the cluster has Intel (R) Xeon(R) CPU E5-2600 0 @ 2.20GHz cpu.png
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
which version of the E5-2600 0 @ 2.20GHz
there are v1, v2, v3 and v4 ?
if it's the V1, you will need a EVC baseline of Sandy Bridge, V2 is Ivy Bridge, and V3 is Haswell, and for completeness a V4 is Broadwell, but you must use the "lowest common denominator" or chipset version for EVC. So baseline for the oldest CPU, so it masks all the newer features in the new HOST CPU.
Albert Widjaja
nav2567,
So in that case, you need to perform offline migration due to the processor difference.