Pre-RequisitesUpgrading to vRealize Suite 8.2 involves deploying new components like Workspace One Access, vRealize Suite Lifecycle Manager 8.2 and vRealize Automation 8.2. The following pre-requisites need to be in place for successfully deploying these components:
- Host Names and IP Addresses
Host Names and IP Addresses for Cloud Operations and Cloud Automation |
Component Group | Host Name | DNS Zone | IP Address | Description |
Cross-Region Workspace ONE Access | wsa01svr01 | rainpole.local | 192.168.11.60 | External load balancer virtual server VIP for the Workspace ONE Access cluster |
wsa01svr01a | rainpole.local | 192.168.11.61 | Primary node of the cross-region Workspace ONE Access cluster |
wsa01svr01b | rainpole.local | 192.168.11.62 | Secondary node 1 of the cross-region Workspace ONE Access cluster |
wsa01svr01c | rainpole.local | 192.168.11.63 | Secondary node 2 of the cross-region Workspace ONE Access cluster |
n/a | n/a | 192.168.11.64 | Postgres Database IP of the cross-region Workspave ONE access cluster |
vRealize® Suite Lifecycle Manager 8.2 | vrslcm01svr01 | rainpole.local | 192.168.11.20 | vRealize Suite Lifecycle Manager 8.2 appliance. |
VMware vRealize® Automation 8.2 | vra01svr01 | rainpole.local | 192.168.11.50 | External load balancer virtual server VIP of vRealize Automation cluster |
vra01svr01a | rainpole.local | 192.168.11.51 | Node 1 of vRealize Automation cluster |
vra01svr01b | rainpole.local | 192.168.11.52 | Node 2 of vRealize Automation cluster |
vra01svr01c | rainpole.local | 192.168.11.53 | Node 3 of the vRealize Automation cluster |
Note: The host names, DNS zone and IP addresses above are only examples. Configure the actual values according to your environment, with the IP addresses being allocated from the X-Region application virtual network.
Resolution
- Disassociate the vRealize Suite 7.x Products from SDDC Manager by following KB81718
- Migrate vRealize Suite Lifecycle Manager to 8.2
- Configure User Access in vSphere for Integration with vRealize Suite Lifecycle Manager 8.2
- Follow this guide to migrate from vRealize Suite Lifecycle Manager 2.1 to vRealize Suite Lifecycle Manager 8.2.
Important: A single-node Workspace One Access instance will be deployed as part of this process. At Step 11 of the Easy Installer wizard - Identity Manager Configuration, select Install New VMware Identity Manager. For IP Address and Hostname provide the values reserved for the Primary node of the cross-region Workspace ONE Access cluster (wsa01svr01a.rainpole.local / 192.168.11.61 from the example table above).
-
- Increase the default vRealize Suite Lifecycle Manager storage by 100GB
- Configure the vSphere Service Account and Proxy Settings in vRealize Suite Lifecycle Manager 8.2
- Replace the Certificate of the vRealize Suite Lifecycle Manager 8.2
- Configure Log Forwarding for vRealize Suite Lifecycle Manager 8.2
- Upgrade vRealize Log Insight and vRealize Operations Manager to 8.2
Important: For vRealize Log Insight, there is no direct upgrade path from 4.8 to 8.2. You must upgrade vRealize Log Insight from 4.8 to 8.1.1 before upgrading to 8.2. For vRealize Operations Manager, you can upgrade directly from 7.5 to 8.2.
-
- Upload and Map Product Upgrade Binaries to vRealize Suite Lifecycle Manager. This can be done by either registering vRealize Suite Lifecycle Manager with Customer Connect or, if external access is restricted on the vRealize Suite Lifecycle Manager appliance, uploading and mapping the binaries to vRealize Suite Lifecycle Manager manually.
- Use vRealize Suite Lifecycle Manager to upgrade vRealize Log Insight and vRealize Operations Manager
4. Expand Workspace ONE Access to a highly-available cluster
-
Important: If vRealize Operations Manager 7.x or vRealize Automation 7.x were deployed using SDDC Manager, an NSX-V Edge Services Gateway for Load-Balancing vRealize Suite products is already available. In this case you configure the Workspace ONE Access Load Balancer on the vrealize-edge Edge Services Gateway (corresponding to sfo01m01lb01 in the guide above). The interface you configure the Load Balancer on is named mgmt-vnic-vrealize-edge (corresponds to the OneArmLB interface in the guide above).
If you do not have vRealize Operations Manager 7.x or vRealize Automation 7.x in your environment, you will need to