In this blog will show how I upgraded my ASLCM, and when reading the patch release notes for ASLCM Patch 5 I found that because my VMware Identity Manager (vIDM) was installed and is managed by VMware Aria Suite Lifecycle, then I’ll need to first patch vIDM with the CSP-102092 patch. Also, for information on how to apply the security patch, go to KB 404054.

If you want to read about vIDM patching you can read this previous blog post. And if you are locked out or can’t remember the root account, take a look at this KB.

So, this blog will be split up in to a couple of parts where Part 1 will be upgrading vIDM, and Part 2 will be upgrading ASLCM to Patch 5.

Note that this upgrade supports Aria Ops 8.18.5 and Logs 8.18.5 and also allows for an upgrade path to VCF 9.0.1.

Update VMware Identity Manager 3.3.7 with the CSP-102092 patch

First, I made sure to backup my vIDM appliance (I use Veeam) and also took a VM snapshot

I downloaded the CSP-102092-Appliance-3.3.7-Patch.zip file

And moved it over using WinSCP to the /db/patch folder on my vIDM box

Then SSH’d into my vIDM box, and unzipped the file.

I then removed the .zip file to reclaim the disk space. NOTE: there needs to be at least 15GB of disk space available, so it may be required to remove this file.

Then I ran the patch automation script, per step 7 in the instructions

./CSP-102092-patch-automation.sh -f CSP-102092-Appliance-3.3.7.zip -r

And the vIDM appliance rebooted…

Note, that vIDM will not be operational until the ASLCM 8.18 Patch 5 is applied, so to get that done we’ll continue to part 2!

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!