Monthly Archives: August 2014

V4V Upgrade from 1.5.1 to 1.6.0

I just tried to upgrade the V4V instance in my lab from v1.5.1 to v1.6.0. I found that it was a multi-step process, and so think it’s a good topic for the post of the week.

Here’s the full run through on what is needed.

First and foremost, my starting point was vCenter Operations for View v1.5.1. My installation was installed on vCenter Operations Manager 5.7.2.

The end state I wanted was V4V 1.6.0 which went GA together with Horizon 6.

The first due diligence I did was to find out what version(s) of vCOps are compatible with V4V 1.6.0. In case you are not aware, here is the link to check for such interoperability http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.

v4v_vs_vcops

As you can see, I would need to upgrade vCOps to 5.8.x. Here comes the follow up on how to upgrade vCOps from 5.7.2 to 5.8.x.

Typically, vCOps upgrade are simple .pak upgrades, like any appliance. However, it’s always prudent to check the release notes or upgrade/deployment guides to see if there is anything else extra.

Indeed, there is this time.

vCOps 5.8.x requires the OS of the appliance to be upgraded to SLES 11 SP2. Fortunately, it is also a simple .pak upgrade. The only twist is that the .pak file is so large that the process cannot be done via the web interface.

As you can see, there are nested pre-requisites to make the upgrade of V4V v1.5.1 up to V4V v1.6.

Here are the steps I took for the full upgrade.

Make sure the following files are on hand

  • VMware-vcops-5.8.0-1448123.pakUpgrade file to vCOps 5.8.0
  • VMware-vcops-SP2-1381807.pakUpgrade file to SLES 11 SP2
  • VMware-vcops-5.8.2-1885282.pakUpgrade file to vCOps 5.8.2
  • VMware-vcops-viewadapter-1.6.0-1867839.pakUpgrade file for V4V 1.6.0
  • VMware-v4vbrokeragent-x86_64-1.6.0-1867839.exeView Connection Server broker agent installer for V4V 1.6.0

Sequence of steps for the upgrade.

  1. took a backup of the existing vCOps vApp – Shutdown vApp and took a snapshot.
  2. Powered up the vApp, and applied the first pak file via vCOps Admin UI – VMware-vcops-5.8.0-1448123.pak.
  3. Check to ensure vCOps still runs fine.
  4. At this point, vCOps has been upgraded to 5.8.0.
  5. Proceed to upgrade SLES to 11 SP2, based on the procedures in KB 2063777.
  6. It is important to note that the upgrade script mentioned in the KB, did not exist in vCOps 5.7.2, and will be made available after the upgrade to 5.8.0.
  7. The installation will prompt with a message to reboot the vApp, do so. Then, after vCOps has started up, login to vCOps to verify that it still works normally.
  8. Return to the Admin UI and perform the upgrade of vCOps to 5.8.2, using the .pak file.
  9. Once done, again validate that vCOps is functional.
  10. At this point, vCops has been upgraded to 5.8.2; we can proceed to V4V upgrade, process can be found in the release notes.
  11. Head back to the vCOps Admin UI, and load the V4V .pak file.
  12. Access the View Connection Server installed with the v4v adaptor; uninstall the existing V4V Broker Agent.
  13. Install the V4V 1.6.0 Broker Agent, and walk through the configuration wizard once more.
  14. Validate that the upgrade is successful, login to vCOps Custom UI
  15. Check that the View Adaptor Status is reporting and collecting data.

Done!