The other day I was upgrading VIDM (now called Workspace One Access) from 3.3.2 (SLES based) to VIDM 3.3.4 (Photon OS Based) and during the upgrade all my VIDM appliances lost their IP Configuration / Network Settings. I was performing this upgrade as part of the vRealize Automation 8.1 Upgrade to vRealize Automation 8.4.
It turns out that the Network Settings are not taken from the OS itself but from the vApp options configured in your vCenter for your VIDM appliances / VMs. The vCenter server crashed a while back and had to be rebuilt. Due to this the vApp Configuration was lost for each of the VIDM VMs and the Network Settings were lost during the VIDM upgrade.
In this blog post I’ll provide you with the default VIDM vApp Properties for your VIDM VMs in vCenter, make sure to set them before upgrading your VIDM Appliances! See the following KB for more information: https://kb.vmware.com/s/article/83587
General vApp Options
Let’s start with the General vApp options.
In vCenter go to your VIDM Virtual Machine, select Configure and click on Edit as shown below:
These general vApp properties can be set as shown below:
|IP allocation scheme||All UNchecked|
|IP allocation||Static – Manuel|
|OVF environment transport||VMware Tools|
|Installation boot||enable UNchecked|
The next thing to do is to set the vApp Properties on your VIDM Virtual Machines.
In vCenter go to your VIDM Virtual Machine, select Configure and scroll down to the Properties section. To add properties click add:
The VIDM vApp Properties can be set as follows (please set the ‘Value’ field to your Environment’s Value):
|Category||Label||Key class ID||Key ID||Key Instance ID||Description||Type||Choice List||User configurable||Default Value||Value|
|Application||Join the VMware Customer Experience Improvement Program||ceip.enabled||Send anonymous customer experience data to VMware.||Boolean||Yes||True||False|
|Application||Timezone setting||vamitimezone||Sets the selected timezone.||String Choice||“Pacific/Samoa”, “US/Hawaii”, “US/Alaska”, “US/Pacific”, “US/Mountain”, “US/Central”, “US/Eastern”, “America/Caracas”, “America/Argentina/Buenos_Aires”, “America/Recife”, “Etc/GMT-1”, “Etc/UTC”, “Europe/London”, “Europe/Paris”, “Africa/Cairo”, “Europe/Moscow”, “Asia/Baku”, “Asia/Karachi”, “Asia/Calcutta”, “Asia/Dacca”, “Asia/Bangkok”, “Asia/Hong_Kong”, “Asia/Tokyo”, “Australia/Sydney”, “Pacific/Noumea”, “Pacific/Fiji”||Yes||Etc/UTC||Europe/Paris|
|Networking Properties||DNS||vami||DNS||IdentityManager||The domain name servers for this VM (comma separated). Leave blank if DHCP is desired. All fields but hostname are required for static IP.||String||Yes||10.10.2.9,10.10.5.9|
|Networking Properties||Default Gateway||vami||gateway||IdentityManager||The default gateway address for this VM. Leave blank if DHCP is desired. All fields but hostname are required for static IP.||String||Yes||10.10.2.1|
|Networking Properties||Domain Name||vami||domain||IdentityManager||The domain name of this VM. Leave blank if DHCP is desired.||String||Yes||mikelab.local|
|Networking Properties||Domain Search Path||vami||searchpath||IdentityManager||The domain search path (comma or space separated domain names) for this VM. Leave blank if DHCP is desired.||String||Yes||mikelab.local|
|Networking Properties||Host Name (FQDN)||vami.hostname||The FQDN name for this VM. Leave blank for DHCP or reverse DNS to be used to lookup hostname.||String||Yes||vidm-01.mikelab.local|
|Networking Properties||IP Address||vami||ip0||IdentityManager||The IP address for this interface. Leave blank if DHCP is desired. All fields but hostname are required for static IP.||String||Yes||10.10.2.20|
|Networking Properties||Netmask||vami||netmask0||IdentityManager||The netmask or prefix for this interface. Leave blank if DHCP is desired. All fields but hostname are required for static IP.||String||Yes||255.255.255.0|
Hope this post was of help for you.
Have a nice day!