16 Nov 2016

vSphere 6.5 - External PSC Upgrade Issue

So with vSphere 6.5 now GA, I decided to upgrade my lab to vSphere 6.5. In my environment, I use a vCenter with an external Platform Services Controller (PSC). So as part of the upgrade, I have to upgrade the PSC first.

When you run the UI installer provided within the VCSA 6.5 Appliance ISO, you have the option to “Upgrade” a vCenter Server Appliance or a Platform Services Controller. The installer detects the component that you are trying to upgrade and prompts for settings appropriate to that upgrade.

During my first run of trying to upgrade the external PSC, I entered the PSC Appliance FQDN, HTTPS port, SSO user name, SSO password and the appliance root password. I filled in the information for the ESXi host that is managing the appliance and hit next.

After an SSL warning (to be expected) prompt, I saw the following screen with the heading “Upgrade - Stage 1: Deploy vCenter Server”

 

 

The upgrade wizard has detected my appliance as a vCenter server and not a PSC. That’s not right. So I went back and specified the source PSC’s IP address, hit next and was presented with the following screen with the heading “Upgrade – Stage 1: Deploy Platform Services Controller

 

And now it seems to work:

I’m not sure if it’s something in my environment or a bug in the install wizard, but this certainly had me confused for a short while.

Written by  1 comment
Tagged under
Last modified on Wednesday, 16 November 2016 11:23
Rate this item
(0 votes)

Latest from Rynardt Spies

Related items

More in this category: « Consolidation Button Missing in vCenter 2.5

Comments (1)

  1. Greg Streuber

Many thanks for this write up. Our team encountered this exact same issue today and using the IP of the External PSC instead of the FQDN resolved the issue for us as well. The weird thing is I have performed this exact same upgrade 3 times and at...

Many thanks for this write up. Our team encountered this exact same issue today and using the IP of the External PSC instead of the FQDN resolved the issue for us as well. The weird thing is I have performed this exact same upgrade 3 times and at different customer sites over the past few weeks and did not encounter the issue. Not sure if it is an environment related issue or software. Just plain weird! Either way....many thanks for the great write up.

Read More
  Attachments
 
  1. #114
There are no comments posted here yet

Leave your comments

Posting comment as a guest. Sign up or login to your account.
0 Characters
Attachments (0 / 3)
Share Your Location
back to top
About 16 hours ago
From Twitter for Android

Drawing near to 10pm here in the UK, which means it's almost time for that call to a product manager in Palo Alto...
Follow Rynardt Spies on Twitter