Replacing Existing Host with New Host/Hardware in a cluster and upgrade to 6.7 Update 1

[Prabasi]

Hello,

I am preparing for hardware refresh and upgrade to 6.7 update 1 from 6.5 U1. I plan to to replace the hosts first and do the vCSA and esxi host upgrade later.

I just have one cluster with three hosts. I am replacing all the esxi hosts with new hosts. I plan to keep all the configuration exactly the same - host name, management ips, luns etc.

Here is the plan:

1 . Change DRS setting to manual

2. vMotion VMs from existing host to another host

2. Bakup the ESXi host configuration

Backup using this arcticle https://www.virtuallyghetto.com/2013/02/how-to-backup-restore-free-esxi-host.html

The configuration file can be downloaded using a web browser or copied to a remote system using scp

scp configBundle-[hostname].tgz user@address:/tmp/

3. Shut down existing host, remove all the NIC and LUNs cables.

4. Connect NIC and LUNs cables to the new host excatly the same as old host.

5. Power on a new host

6. Install ESXi 6.5 U1, rename the host to match the old host and assign the management ip

7. Add the new host to vCenter cluster.

8.  Apply configuration changes to a new host

Follow the comments to restore esxi host configration to different esxi host https://www.virtuallyghetto.com/2013/02/how-to-backup-restore-free-esxi-host.html

Basically you just have to update the UUID # under Manifest.txt file.

Part 1
(1) Backup host config of new esxi host using this article. This will create a file named configBundle.tgz.
(2) Copy the tgz file to /tmp folder using cp command. Change directory to /tmp: cd /tmp
(3) Extract configBundle.tgz file: tar zxvf configBundle.tgz
(4) Open Manifest.txt file and write down the UUID: cat Manifest.txt
(5) Remove configBundle.tgz file, Manifest.txt file and state.tgz file using rm command.

Part 2
(1) Copy host config file downloaded from step 2 (old host) to /tmp folder under new host.
(2) Change directory to /tmp.
(3) Extract configBundle.tgz file: tar zxvf configBundle.tgz
(4) Open Manifest.txt file using vi and update the UUID with the one you wrote down for Server B. Save the file.
(5) Remove or rename configBundle.tgz file under /tmp.
(6) tar manifest.txt and state.tgz files: tar zcvf configBundle.tgz Manifest.txt state.tgz
(7) run the vim-cmd restore command to restore the config.

Reboot the host.

9. Verifiy the configurations.

10. vMotion VMs to new host

11. Follow the same steps on the next new host

Wait for couple of days and upgrade to 6.7 Update 1.

I would like the experts to chime in if there is any issue with the above upgrade process or if I missed any steps.

Thanks,

[a_p_ · Accepted solution]

IMO this procedure puts more complexity on the whole upgrade than necessary. ESXi will will most likely enumerate the NICs, and other hardware differently than on the old host, so you will need to verify each setting anyway. I don't know how complex your setup is, but with a 3 host setup, I'd go ahead and configure the hosts manually.

Since you're on vSphere 6.5U1, I'd probably upgrade directly to vSphere 6.7 U1a, by upgrading the vCSA first, followed by a rolling replacement of the host, which you may also setup with the current ESXi 6.7 build.

André

[Prabasi]

Thanks A.P. I was trying to see if I can replace the hardwares without having to manually reconfigure all the vSwitch and SAN LUNs. I want to keep all the configuration IPs, ESXi hostname etc. exatly the same.