The writers strike edition – Upgrading from vSphere 6.5 to 6.7

I guess it’s time for a totally derivative episode.

Today, on filler episodes, it’s upgrading from vSphere 6.5 to vSphere 6.7.

Woo.

Background

This was done in my lab. I needed to upgrade it. The PSC has already been done, so this will show VCSA1 being updated.

Load the UI interface from the vCentre 7 ISO

1 - iso menu

Click on Upgrade

So you may not be aware (I mean it’s not like there’s more important things going on) but VMware are currently moving most of the products away from the underlying Linux base to a Photon base. This has a number of advantages, but one of the most visual (apart from the natty Photon boot screen) is that upgrades now consist of deploying a new appliance, migrating data from the old to the new, and then shutting down the new. This is annoying for poor people like me who have limited resources, but, it does mean I have a complete fall-back: just boot the old appliance;

2 - Failout options

Anyway, onwards.

3 - wizard1

Ta-da, it’s a wizard, you know the deal: next, next, next, finish….

I’m not going to screenshot every screen, because:

4 - wizard2

Click Connect to Source to move forward. Ha, no Next box…

Next you need to provide some additional info.

5 - wizard3

Note: Here I’ve used an IP address for my ESXi host. This is partly because of my lab setup, and partly because I find vCentre deployments (and this is basically a deployment and file copy) work better when I point directly to the host I want to deploy to.

6 - wizard4

Give the VM a unique name. I’m a fan of self-documenting things.

7 - wizard5

Pick a size

8 - wizard6

Select a datastore

I’m sticking it on a datastore called _vRA because it’s got space, and once everything’s working I’ll move it to a SSD

9 - wizard7

Give it temporary IP settings

A few things here, the temporary IP address must be free. It doesn’t need a DNS entry.

10 - wizard8

The IP address is used during the upgrade but is released after the upgrade is complete. When doing my PSC I used .222:

11 - wizard9

And with no reboots or anything on my end, it’s nice and free.

And finally, Finish

12 - wizard10

And it so it begins

13 - deploy

14 - deploy2

Around this point, it boots the new VM

14 - deploy2

15 - deploy3

Waits for a long time and then deploys the settings configured during the wizard

16 - deploy4

Stops and starts various services and then the new appliance is online

17 - deploy5

18 - deploy6

Stage 1 complete.

19 - deploy7

Stage 2 begins

20 - upgrade1

Gah. Why is nothing ever easy.

21 - upgrade2

Seems ok

22 - upgrade3

Reboot and it worked.

23 - upgrade4

Oooh, more problems…

24 - upgrade5

25 - upgrade6

26 - upgrade7

Remove the 5.5 host I had lying around, and onwards dear fellow, onwards.

27 - upgrade8

I only want my lab configuration.

28 - upgrade9

And go go go

29 - migrate1

30 - migrate2

31 - migrate3

I know it’s a lab, but this isn’t quick

32 - migrate4

At some point it’s swapped my VC’s over

33 - migrate5

And finally

34 - migrate6

The PSC was roughly the same process. Took about 90 minutes for both the PSC and VC.

Leave a comment