VMware ESXi 7.0 Upgrade
It is time to upgrade VMware environment, but I have an obsolete server that has a CPU compatibility problem with ESXI 7.0 version. After googling, some of IT geeks have posted some solutions, so I want to share my implementation.
This is my HP G7 server, above. Once vmware 7.0 is being installed, the process will be rejected. However, by adding “allowLegacyCPU=True” command during boot process, it will solve the problem. It is persistent, so I do not need to add it every time. You can check this website as well.
Quick Tip – Allow unsupported CPUs when upgrading to ESXi 7.0
First of all, Vcenter should be upgraded before ESXI host.
Step 1. Upgrade Vcenter
It is straight forward to upgrade Vcenter. I have not faced with any problem regarding the compatibility. You can follow these link, below. If it is broken, jump into youtube channel.
Vcenter upgrade is broken into 2 parts. First part is to deployment of new Vcenter, while second part is about transferring its statistics and configurations.
However, I came across storage problem, as I selected thin provision installation to make less room, so I should point a specific location for the installation. I follow the same steps that are on this website, below. Check the disk usage and type a suitable partition path.
Finally, it is done.
Step 2. Ugrade ESXi host
I select reboot and fresh upgrade option. ESXI 6.7 is located first logical drive on rom configuration.
I prefer to use ILO management port of HP server for deployment using version 7.0 iso image, as shown below.
During its boot process, add the “allowLegacyCPU=True” command at the end of it. It will show only a notification instead of termination.
I can see how much data is being transferring from my computer to the server, below
Step 3. 503 Service Unavailable
A service should be checked because of this web browser error, below.
503 Service Unavailable (Failed to connect to endpoint: _serverNamespace = / action = Allow _port = 8309)
Using ESXTOP found VM that was throttling the MEM, killed it./etc/init.d/hostd STOP
/etc/init.d/vpxa stop
DCUI Restarted managment interface
/etc/init.d/hostd start
/etc/init.d/vpxa start
Access to esxi host via ssh, then restart a service that causes the problem.
Finally, I was able to see login section, above. I hope this is informative for you.