Upgrading VCSA from 6.0u3 to 6.5u1

Stage 1: Platform Services Controller

Browse to D:\migration-assistant

Launch VMware-Migration-Assistant

The migration assistant launches. This needs to be run on each VUM server that has a vCenter attached and that you are upgrading.

Browse to D:\vcsa-ui-installer\win32 and launch installer.exe

Click on Upgrade

Click Next

Accept the terms and click Next

Fill in the FQDN of the PSC and click on Connect to Source

Fill in all the relevant source information, and remember, by this time DRS should be set to manual on the cluster, all VCSA systems on the same host, so you can connect directly to the ESXi host. Click Next.

Click Yes to accept the certificate warning.

Enter the target information. Again, DRS should be set to manual on the cluster. Connect directly to the ESXi host the VCSAs are located.  Click Next.

Again, click Yes to accept the warning.

Over here, I kept the VM names as I originally had, except I appended “-new” to the VM name. This is the visible name in vCenter. We will rename those later. Assign a root password and click Next.

Select a datastore and click Next.

Fill in some TEMPORARY ip information. Remember, it HAS TO BE on the SAME subnet as the source VM. Click Next.

Review the information, if it is all correct, click Finish to begin the upgrade.

The install begins. Let me sit back, relax, and grab a coffee. This will take approx 10-20 min depending on the performance of your environment.

The deployment of the VM is now complete. Click Continue to move to Stage 2 of the VM deployment. The migration.

2 Comments

    Ytsejamer1

    This was a fantastic series! Thank you for the detail and full context of the steps for a project of this sort.

    One thing I ran into is when the stage 1 deployment created the new VCSA VM. It was unable to set some VM property, but had no idea which one. It went through and completed Stage 1 but it failed moving to Stage 2 because the migration couldn’t contact the new VCSA. The issue was that the vNIC was not set as connected.

    What was nice is that the migration application gave me the appliance link where I could manually kick off the Stage 2 portion of the migration. It worked without issue and was a mirror of what the migration would have presented. In fact, it worked a lot faster through the browser.

      Raymond

      Hi,

      I am glad you found this post useful. Let me know if there is anything else you are interested in me blogging about.

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*