To move on with the next phase of my migration, I needed a diagram from the VMware Virtual Infrastructure Navigator (VIN) showing the way vCenter is a central connectivity point for any VMware vCloud Suite. However, some time in the past VIN stopped working and I was unable to login to it to do a more traditional upgrade. In short VIN was broken.
Due to vCenter Operation Manager (vCops) migration issues when placing a node in maintenance mode, I also had a broken vCops.
Here's how I went about fixing both:
VIN was a complete loss, so I redeployed from the v1.2 OVA.
However, this did not quite do it, as you need to first connect the Web Client to the vCenter Web Server instance so that redirects for web client access work as expected on the server. This failed for me with an SSL error that was fixed by following KB 2036505.
When VIN v2.0 came out, I used the Web Console method to upgrade VIN. All you need to do is the following:
Login to Web Console (root and your password you supplied when deploying the OVA)
Select the Update Tab
Check for Updates
And when the new latest update appears then use Install Updates
VIN quickly found all my vCenter related connections, however I had to wait to overnight to find all the other application connections.
vCops however was more difficult, I had a ton of existing data I did not want to lose. However, when I went to go to the UI it said the two VMs (Analytics and UI) were not connected and needed repair. But first I needed to login to the UI VM web console and I forgot my password. The password-reset steps are in KB 2030185, and the repair steps are available once you login to the UI. But my problem was greater than just a repair: vCops also had to be resynced with vCenter and the admin page repair mechanism only works when vCenter is properly connected.
William Lam already solved this problem, but it requires access to the UI VMs Linux console to fix. In this case, we did not change the IP address, just repaired the UI to Analytics VM connection.
Now you can go back into the UI’s admin interface (http://vcops/admin) to deregister the exsting vCenter registration and then register vCenter into vCops. Yes, you have to delete the old and reregister the same vCenter server.
Once vCops is registered with vCenter, you can use the admin screen to perform the upgrade using the PAK file downloaded from VMware. The last step is to reboot the vCops vApp. While not strictly necessary I found it always helps with respect to licensing.
Speaking of licensing, if you had a vCops Enterprise license but only upgraded to vCloud Suite Standard, your vCops Enterprise license no longer applies. You need vCloud Suite Enterprise to get vCops Enterprise functionality. I am trying a number of different license keys but have not been able to go back to my existing vCops Enterprise license, something VMware will eventually have to fix.
Next up: More space for vSphere ISO Images