Browse Month

August 2021

Upgrading vRA (vRealize Automation) to 8.5

In this post i will go over upgrading my 8.x vRA appliance to 8.5. As a pre requirement we do need to have vRSLCM (vRealize Lifecycle Manager) upgraded to 8.4.1. Instructions can be found here. You will also need to apply the latest Product Support Pack (version 8.4.1.4). The instructions can be found here.

To get started we can go to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> Binary Mapping. (If you havent added your My VMware credentials you will need to do that first by going to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> My VMware)

Click on Add Binaries under Product Binaries

Select My VMware and click on Discover

We can see a list of binaries that have been discovered. We can select what we need and click on Add

This will create a request and start downloading the package. To view the progress we can click on the Click Here hyperlink

Click on the in Progress button to view the details

We now have to wait for the download to complete

After the download is complete we can go to Environments -> View Details on the environment that includes vRA

Click on Upgrade

An Inventory sync is recommended if the environment has changed since LCM performed the last sync. We trigger the sync from the UI or click on Proceed to continue

Select product Version 8.4.0 and click Next. We can also review the compatibility matrix to make sure the environment is compatible.

Since we already checked the sizing while the download was occurring we can check the check box for I took care of the manual steps above and am ready to proceed and click on run precheck

Run the Precheck to make sure there are no errors

Once the check is complete, click on Next. Review the upgrade details and click on Next. We are taken to the progress screen where we can follow the progress.

The system will get rebooted and once its back up we will be on 8.5

vRSLCM (vRealize Lifecycle Manager) Product Support Pack

In this guide i will go over the steps of getting an existing 8.x vRSLCM appliance to support the latest product releases available. Here is a great blog that goes in to the details about what the Product Support Pack is https://blogs.vmware.com/management/2019/01/vrslcm-pspak.html. Typically the newer Product Support Pack is included part of the upgrade for LCM, however sometimes there are product releases in between releases where product support packs come in handy.

The first step is to log in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section

Go to settings -> Product Support Pack

We can see that i recently upgraded to 8.4.1.2 however a new update is available 8.4.1.3. Based on what we can see in the details the new support pack adds support for network insight 6.3.0.

Click on Apply Version

Verify that a snapshot or a backup exists and click Submit

We can view the progress by clicking on the Click Here link after submitting the request

Once the process is complete the system will most likely reboot. To check the status we can go back to settings -> Product Support Pack. As we can see we are now at the updated patch level

If you get the below error clear the browser cache and try again

Patching vRSLCM (vRealize Lifecycle Manager) to 8.4.1.1 Patch 1

In this guide i will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.4.1 Patch 1 release. The release notes can be found here

The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section

Go to settings -> Binary Mapping

Click on Patch Binaries up top and click on Check Patches Online

We can see that the check found a new patch

Click on download button under Action. We can follow the process by clicking on Click here to check request status

Wait till the download is complete and go back to settings

Go to Settings -> System Patches

Click on New patch on the right side of the screen

Select the newly downloaded patch and click Next

Review the details and click Install

This will fire up the patch process and start the patching.

The system will automatically reboot on 8.4.1.1 Patch 1 once completed. We can check the version by going to Settings -> System Details

If you get the below error clear the browser cache and try again

vROps cloud API getting started

I wanted to keep track of what needs to be done prior to actually being able to query API on vROps cloud. Ive been having a hard time finding the documentation i needed in the past

First step is to get an API token for the specific username. We can do this by going to My account under User Settings in vROps Cloud

Go to API Tokens and click on Generate a new API token

Give it a name and select what it will have access to and click on Generate

Once we have the api token generated we can use it to generate an access token by running 

curl -k -X POST "https://console.cloud.vmware.com/csp/gateway/am/api/auth/api-tokens/authorize" -H "accept: application/json" -H "Content-Type: application/x-www-form-urlencoded" -d "refresh_token=token_generated_earlier"

Now we can use the output from “access_token”. vROps Swagger API can be found here

Here is an example to get the current logged on user

curl -X GET "https://www.mgmt.cloud.vmware.com/vrops-cloud/suite-api/api/auth/currentuser?_no_links=true" -H "accept: application/json" -H "Authorization: CSPToken <access-token>"

Full guide from VMware available here

Upgrading vRSLCM (vRealize Lifecycle Manager) to 8.4.1.1

In this guide i will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.4 release. The release notes can be found here

The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section

Go to settings -> System Upgrade

Click on Check for Upgrade

We can see that the check found a new version available for 8.4.1.1

Click on Upgrade

This will fire up the upgrade process and start upgrading packages. The system will automatically reboot on 8.4.1.1 once completed. We can check the version by going to Settings -> System Details

If you get the below error clear the browser cache and try again