vROps – Upgrading vRealize Operations Manager from 6.0.2 to 6.1

By | November 26, 2016
0 Comment
  1. Download the OS update and Application update pak files from VMware (read the “read more” section to determine exactly what you need). This was what I needed for our environment:

  2. Take a snapshot of all your nodes.
  3. Install the OS Update pak file 1st. (This step is very important and must be done before the application update.)
    1. Log into your vROps servers admin console (https://servername/admin)
    2. Click on Software Update in the left column
    3. Click on the “Install Software Update” button
    4. In the new “Add Software Update” popup window, browse to the folder where you’ve saved your OS update pak file
    5. Click the “Upload” button:

    6. At this point the installation hung, which led to a VMware technical support call, which led me to the following websites:
      1. http://thatvirtualboy.com/2015/10/26/upgrading-vrealize-operations/
      2. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2120616
      3. Eventually, after a Webex with @nakedhitman (the author of the article on thatvirtualboy.com) we were able to determine that communication between the master node and the remote collector was unstable. We could ping, but PAK transfers died before completing. This is what was causing the update to fail. As we weren’t using the remote collector, we ripped it out and proceeded with the OS update.

  1. Install the Application Update pak file.
    1. Ensure that you check both the boxes so that the “Reset out of the box content” option is selected. If you do not do this, some parts of the system may not be upgraded. This will not affect custom dashboards or other content, only the ones that ship with the system that you oughtn’t to have changed anyway 😉 If you have customizations to the built-in content, you can clone them to preserve your changes.

    2. The upgrade will churn for quite a while. I stepped away for lunch & when I came back it was all done:

  2. Log in to the product UI as admin and ensure that your dashboards, adapter instances, and other data are present and working as expected.
  3. Once you’re sure that everything is running OK, delete the snapshots.