This document is to assist with upgrading on-premises VMware Identity Manager appliances, including both the full on-premises appliance (commonly known as the Single Virtual Appliance - or SVA) and the on-premises standalone connector for a SaaS VMware Identity Manager tenant. It should be used with the official VMware Identity Manager upgrade documentation (NOTE: Select the version of the appliance you are upgrading to from the drop down menu).
Please note there are links embedded throughout the document below in reference to the documented procedures or other information.
NOTE: Document updated for VMware Identity Manager 2.9.x, 3.x, 19.03, and 20.01 as well as references for 2.8.x and older appliances.
You will find the following info within this document.
The following are settings to configure after the upgrade completes successfully. If you have set up a VMware Identity Manager cluster for failover, updating it to three nodes is recommended. This is because of a limitation of Elasticsearch, a search and analytics engine embedded in the VMware Identity Manager appliance. You may continue to use two nodes but you should be aware of a few limitations related to Elasticsearch. See "Configuring Failure and Redundancy" in Installing and Configuring VMware Identity Manager for more information.
Backup of IFCFG-ETH0
Make a copy of the IFCFG-ETH0 file before upgrading.
Make a VM snapshot before upgrading (no memory state needed unless you want one).
When upgrading the full VMware Identity Manager on-premises single virtual appliance (SVA), when taking a VM snapshot of appliance(s), it is also good practice to take a backup of the database or VM snapshot of the database server.
When doing an online update, you may need to set an outbound proxy within the appliance in order for it to reach the Internet and download the update packages. Essentially the appliance must be able to reach vapp-updates.vmware.com on TCP port 80 (HTTP). The latest instructions for setting a proxy for online upgrade can be found in the VMware Identity Manager Documentation online.
The procedure for setting a proxy is as follows:
Apply any necessary hot patches after upgrading.
The short version of the over-the-air procedure is…
Update, Update Check, Update Installer fail to run and/or show any outcome.
Not enough available inodes (number of allowed files).
Information courtesy of Wibowo Leksono
Update Installer runs on VMware Identity Manager On-Premises Connector Version 2016.11.1.0 but reports no updates are available.
Known Issue with VMware Identity Manager Connector version 2016.11.1.0.
No Networking Detected on Reboot After Upgrade
The upgraded SUSE appliance shows NO NETWORKING DETECTED errors. Logging in and looking at /etc/sysconfig/network (ls /etc/sysconfig/network -l -a) shows source file for ifcfg-eth0 is missing in /etc/sysconfig/networking/devices/ for /etc/sysconfig/network/ifcfg-eth0 link file.
Known Issue with upgrade process wiping ifcfg-eth0 information