vCSA 6.0 to 6.5 Upgrade Fail – Migration Assistant on VUM Server

Upgrading PSC 6.0 appliance to 6.5 worked like a charm.
Next step was vCenter appliance upgrade,which would now consolidate Windows based VUM server to the vCenter appliance. So this requires you to run VMware Migration Assistant on the Windows VUM server.

Every time I start the Migration Assistant it failed with an below error

Error: A problem occurred during authentication to the legacy vCenter Server using the provided credentials. Resolution make sure the vCenter Server is up and running. Verify you have entered the correct credentials.


I was sure that the SSO password is correct. 

Looking at the logs
UpgradeRunner log mentions

2018-06-20T21:48:04.483Z INFO utils.featureState_utils Found FSS AUTOMATED_VUM_UPGRADE=True
2018-06-20T21:48:04.513Z WARNING bindings.vc_binding Cannot get access to VC Inventory http://<VCIP>:80, because of Error: Server has wrong SHA1 thumbprint: 7aa2612f090cdd1212sqw216943489ada70019 (required) != b3de7868330f12511b767a122abb245448d5d (server).
2018-06-20T21:48:04.515Z ERROR UpgradeRunner Cannot log in to legacy vCenter Server
2018-06-20T21:48:04.516Z INFO output.requirements_result_producer Repository is not set, not adding SSO information.
2018-06-20T21:48:04.529Z INFO output.requirements_result_producer Persisting preupgrade result :

FIX
1) Navigate to C:\Program Files (x86)\VMware\Infrastructure\Update Manager
2) Open "VMwareUpdateManagerUtility"
3) Provide vCenter FQDN or IP and Login with "administrator@vsphere.local" & SSO Password
4) Under the left side options list, click on "Re-register to vCenter server" and provide SSO credentials again (administrator@vsphere.local and password)
5) Once done, restart "VMware vSphere Update Manager Service"
6) Try Migration Assistant again

It's happy this time!!



Comments

Post a Comment

Popular posts from this blog

vCenter Maintenance - Issue Non-ephemeral Portgroup

Image
Hi Friends, We had a issue last day due a miss configuration. We used to keep our vCenters on ephemeral port groups for troubleshooting purposes in case of any issue. We have a new vCenter now and as per standards our project team put that on a portgroup which was named as "ephemeral", but it was quiet late we found it was not actually setup as an ephemeral port group, but static instead :(. So issue was a config issue, but I wanted to share how we solved it hopping it might help someone in other situations too. The story is like this.  We planned to test an outage situation, by bringing down vCenter, to test if our VRA pre-build check can identify it. One of our lazy engineers went to Web Client of the ESXi server hosting vCenter and decided to turn the NIC off for the test. He received below error while turning it back on Description :- Reconfigure this virtual machine Virtual machine :- Non-PROD_vCenter State -: Failed - Invalid configuration for device '3
Read more

vMotion Failing at 21% with error ""The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct."

Image
vMotion Failing at 21% with error ""The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct." Scenario We built a new ESXi 6.7 Cluster and we couldn't make vMotions work there Troubleshooting steps 1) Make sure there is no IP address conflict. 2) SSH to ESXi and do a VMK Ping check For Default TCP/IP Stack vmkping 10.11.7.188 Or If you are using Multi NIC vMotion, you might want to specify which VMK interface to use vmkping -I vmk<vmkinterfacenumber> <Destination VMK IP to Ping> Eg -:  vmkping -I vmk3 192.168.1.1 For vMotion Stack I f you try above vmkping command on a ESXi host with VMK interfaces on VMK stack, they will fail with an error  Unknown interface 'vmk': Invalid argument Because the command is looking for TCP/IP stack by default and this VMK wont be listed there. So you need
Read more

applmgmt service wont start on PSC Appliace post converge operation

Scenario We had a vCenter with External PSC. We converged them and converge job was successful execpt a cert warning. After a week we tried to decommission the old PSC appliance and found that the status is shown in WebClient as "Unknown" Up on checking we found  applmgmt in stopped state. Tried to start it but it failed with below error [ ~ ]# service-control --status Running:  lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-rhttpproxy vmware-sca vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon Stopped:  applmgmt vmware-statsmonitor [ ~ ]# service-control --start applmgmt Operation not cancellable. Please wait for it to finish... Performing start operation on service applmgmt... Error executing start on service applmgmt. Details {     "detail": [         {             "translatable": "An error occurred while starting service '%(0)s'",        
Read more