In this blog I’ll continue to show how I upgraded my Aria Suite Lifecycle Manager (ASLCM) to Patch 5. In Part 1 of the blog, I upgraded my VMware Identity Manager (vIDM) with the CSP-102092 patch because was installed and is managed by VMware Aria Suite Lifecycle.

In this Part 2 of the blog I’ll cover the steps I have taken VMware Aria Suite Lifecycle 8.18 Patch 5 Installation Runbook

Similar to Part 1, first I made sure to backup my ASLCM appliance (I use Veeam) and also took a VM snapshot. Also, just following all the guidance in the runbook, be sure to do step 1 and upgrade vIDM first, then ASLCM. And be sure DO NOT DELETE your snapshots early! Be sure all of the environment is functional and verify before deleting.

From the KB, I downloaded the upgrade prep patch at the bottom of the KB called prep-for-upgrade-lcm.sh and used WinSCP to transfer the file to my ASLSM box to the /data folder

Then I cd’d to the ‘/data’ directory, made the chmod change, and ran the script

And then all the prep is complete.

I’m not upgrading from Patch 3 to Patch 5, so I skipped step 3 in the runbook.

I then downloaded the vrslcm-8.18.0-PATCH5.patch file and used WinSCP to transfer it over to my ASLCM box.

Then I logged into my ASLCM UI and wnet to Lifecycle Operations -> Settings -> Binary Mapping

Then to the Patch Binaries tab, and Add Patch Binary

I added the /data in the source location, selected the Patch 5 binary, and clicked ADD

Once the patch was added and verified (see status in the request details pane), I then verifed the Patch 5 file was in the patch binary list (pro tip: refesh the binary mapping page and filter by Name using “Lifecycle”)

Then I navigated to Lifecycle Operations > Settings > System Patches and click on NEW PATCH

Then in the new window, I selected PATACH5 and clicked NEXT

Reviewed the information and clicked INSTALL

I then waited for the installation to complete. The KB states the process takes approximately 20 minutes and will conclude with the appliance rebooting. So I grabbed some coffee and did some other tasks…

ASLCM will eventually reboot…

Another tip…to check ASCLM services status, SSH or console to the VM and type

vrlcm-cli --health-status

Took a bit, but when it came back up, I logged in to the VMware Aria Suite Lifecycle UI, navigated to the About page, and verified that the version showed as 8.18.0 Patch 5.

Hopefully having this information helped make a better outcome. Have you hit snags with ASCLM upgrades? Drop a comment with your tips or questions—I’d love to hear from you!