Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to upgrade vRealize Automation from version 7.4 to 7.5 in VMware Cloud Foundation 3.5.x (65101)

Last Updated: 7/15/2020Categories: How toTotal Views: 4352Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

This article provides instructions for how to upgrade vRealize Automation in VMware Cloud Foundation 3.5.

Impact / Risks

It is not supported to update vRealize Automation beyond version 7.5. Doing so my negatively affect VMware Cloud Foundation's ability to manage this product.

Resolution

Notes:

Ensure VMware Cloud Foundation has been upgraded to version 3.5.

Ensure that all prerequisites are satisfied as documented in Prerequisites for Upgrading vRealize Automation.

Download the VMware vRealize Automation 7.5.0 Update Repository package (VMware-vR-Appliance-7.5.0.458-10053539-updaterepo.iso) from customerconnect.vmware.com.

Verify all third-party integrations that might have been configured for use with vRealize Automation are compatible with vRealize Automation version 7.5. Contact the third-party integration vendor or developer to ensure compatibility.

Verify that current backups of the vRealize Automation virtual appliances and the Infrastructure-as-a-Service (IaaS) virtual machines exist.

Verify that a current backup of the external vRealize Automation database exists.

Open a Web browser and log in to the VAMI management interfaces by navigating to https://<vRA Appliance FQDN>:5480 (repeat for each vRA Appliance). Select vRA Settings > Cluster and verify that all vRealize Automation IaaS Windows Server nodes meet the following requirements:

Have a Last Connected status of less than 30 seconds.

Have a Time Offset status of less than 1 second.

Open a web browser and log in to the VAMI management interfaces by navigating to https://<vRA Appliance FQDN>:5480 (repeat for each vRA Appliance). Select vRA Settings > Cluster and verify that all vRealize Automation virtual appliances meet the following requirements:

Have a Last Connected status of less than 10 minutes.

The PostgreSQL database is connected and reporting a Status state of Up, indicating that the primary and replica nodes are running.

The PostgreSQL database is connected and reporting a Valid state of Yes, indicating synchronization between the primary and replica nodes.

Open a Web browser and log in to the VAMI management interfaces by navigating to https://<vRA Appliance FQDN>:5480 (repeat for each vRA Appliance)0. Select Services and verify that all Services are reporting a status of REGISTERED.

Make the vRealize Automation environment unavailable to end users and any automated integrations during the upgrade maintenance window.

Verify that the vRealize Automation environment has been quiesced for all activities, including but not limited to, users ordering new virtual machines and third-party integrations that may automate the ordering of new virtual machines. Without quiescing the environment, rollback operations may be disruptive, generating orphaned objects after snapshots have been created. Remediating such situation might require extending the maintenance window.

Verify that you have access to all databases and load balancers that are impacted by, or participate in, the vRealize Automation upgrade.

Direct Traffic to the Primary Nodes and Disable Health Monitoring for vRealize Automation on the Load Balancer

Notes:

Before you upgrade the vRealize Automation virtual appliances and the vRealize Automation IaaS nodes, direct all traffic to the primary node and disable the health check on the NSX load balancer for vRealize Suite applications.

The configuration change disables the additional pool members for the vRealize Automation VIPs. During an upgrade, the services inside the additional nodes might not be upgraded or initialized because of installation or power cycle operations. If the load balancer passes a request to one of the additional nodes, the request will fail. If the additional pool members remains enabled, you might experience failures during vRealize Automation upgrade, and service initialization or registration failures during a vRealize Automation appliance power cycle operations.

On the NSX load balancer, you disable the additional vRealize Automation nodes and deselect the monitor for the associated traffic in the pools.

Log in to the first vRealize Automation appliance via the VAMI interface (https://<vRA Appliance FQDN>:5480).

On vRA Settings tab, click the Database tab and check which nodes have the REPLICA label. The REPLICA label indicates which vRealize Appliances are secondary.

Log in to vCenter Server by using the vSphere Web Client.

From the Home menu of the vSphere Web Client, select Networking & Security.

In the Navigator, click NSX Edges.

From the NSX Manager drop-down menu, select the NSX Manager IP Address corresponding to the NSX Manager for the management workload domain and double-click the NSX edge device for vRealize Suite to open its network settings.

On the Manage tab, click the Load Balancer tab and click Pools.

Select the vra-svr-443 pool that contains the vRealize Automation appliances and click Edit.

In the Edit Pool dialog box, select the secondary node, click Edit, select Disable from the State drop-down menu, and click OK. Repeat this step for the third node.

In the Edit Pool dialog box, select NONE from the Monitors drop-down menu and click OK.

Repeat the procedure on the remaining load balancer pools.

To verify that the load balancer redirects the traffic to the primary node of the vRealize Automation virtual appliance, open a Web browser and go to https://<vRA primary appliance FQDN>/vcac to verify that the login page of the vRealize Automation administration portal appears.

Take Snapshots of the vRealize Automation Virtual Machines

Log in to the Management vCenter Server by using the vSphere Web Client.

Shut down the vRealize Automation virtual machines in the environment according to Shutdown Order of the Management Virtual Machines.

Shut down the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation agents in any order and wait for all components to finish shutting down.

Shut down virtual machines that are running the Manager Service and wait for the shutdown to finish.

Shut down the secondary Web node and wait for the shutdown to finish.

Shut down the primary Web node, and wait for the shutdown to finish.

Shut down all secondary vRealize Automation appliance instances and wait for the shutdown to finish.

Shut down the primary vRealize Automation appliance and wait for the shutdown to finish. The primary vRealize Automation appliance is the one that contains the primary, or writeable, appliance database. Make a note of the name of the primary vRealize Automation appliance. You use this information when you restart vRealize Automation.

Shut down the MSSQL virtual machine(s) in any order and wait for the shutdown to finish.

Take a snapshot of the vRealize Automation virtual machines in the environment.

Power on the vRealize Automation virtual machines in the environment according to Startup Order of the Management Virtual Machines.

Start the MS SQL database virtual machine(s).

In vSphere, disable the NSX Manager health checks before you start the vRealize Automation appliance. Only ping health check should be enabled.

In vSphere, start the primary vRealize Automation appliance.

Wait until the licensing service is running and REGISTERED in the primary appliance management interface.

Start the remaining vRealize Automation appliances at the same time.

Wait for the appliances to start, and verify that services are running and listed as REGISTERED in the appliance management interface. It might take 15 or more minutes for appliances to start.

Start the primary Web node and wait for the startup to finish.

Start the secondary Web node and wait 5 minutes.

Start the primary Manager Service machine and wait for 2 to 5 minutes.

Start secondary Manager Service machine and wait 2 to 5 minutes.

Start the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation proxy agents. You can start these components in any order and you do not need to wait for one startup to finish before you start another.

In vSphere, ensable the NSX Manager health checks that were disabled in Step 4b.

Verify that the startup succeeded.

Open a Web browser to the vRealize Automation appliance management interface URL.

Click the Services tab.

Click the Refresh tab to monitor the progress of service startup. When all services are listed as registered, the system is ready to use.

Set the vRealize Automation PostgreSQL Replication Mode to Asynchronous

Log in to the first vRealize Automation appliance via the VAMI interface (https://<vRA Appliance FQDN>:5480).

Click Cluster.

Click Async Mode and wait until the action completes.

Verify that all nodes in the Sync State column display Async status.

Unregister vRealize Automation from vRealize Business

Note: These steps are only needed if vRealize Business is deployed and vRealize Automation is registered with it.

Log in to the vRealize Business Server appliance management console (https://<vRB IP>:5480).

Unregister vRealize Business from the default tenant (usually vsphere.local) in vRealize Automation.

On the Registration tab, click the vRA tab.

Enter the appropriate values and click Unregister.

Note: An Unregistered from vRealize Automation message appears at the top of the page.

Configure the Authentication Provider of vRealize Orchestrator with the Default Tenant

Note: Make a note of the currently configured tenant and group as they will be used after the upgrade to restore the configuration to its pre-upgrade state.

Log in to vRealize Orchestrator Control Center

Under the Manage group of settings, click Configure Authentication Provider.

On the Configure Authentication Provider page, click Change next to Default tenant, enter vsphere.local (or the name of the default tenant if different), and click Apply.

Click Change next to Admin group, enter vsphere.local (or the name of the default tenant if different), select the vcoadmins group, and click Apply.

Click Save Changes.

Upgrade the vRealize Automation Appliances and IaaS Components

Notes:

Verify that the primary IaaS Web Server virtual machine satisfies the following requirements:

Java SE Runtime Environment 8 64-bit update 161 or later is installed.

JAVA_HOME environment variable is set to the Java directory path.

Mount the upgrade .iso file, VMware-vR-Appliance-7.5.0.458-10053539-updaterepo.iso, on the primary vRealize Automation virtual appliance.

Log in to the first vRealize Automation appliance via the VAMI interface (https://<vRA Appliance FQDN>:5480).

Click the Update tab and click the Settings button.

Under the Update Repository section, select Use CD-ROM Updates and click Save Settings.

Click the Status tab and click Check Updates to load the update from the upgrade .iso file.

Verify that the update listed in Available Updates is 7.5, click Install Updates and click OK in the Install Updates dialog box.

Notes:

You can also follow the upgrade process within the logs on the vRealize Automation virtual appliance:

/opt/vmware/var/log/vami/vami.log - Logs the initial unpacking and staging of the upgrade bundle to the primary vRealize Automation virtual appliance.

Once completed, additional logging is available in the updatecli.log:

/opt/vmware/var/log/vami/updatecli.log - Logs the additional vRealize Automation upgrade processes, such as, the upgrade script execution.

On the Status page, monitor the Update Status.

Note: After the upgrade completes, the System reboot is required to complete the update message appears on the Status page.

On the System tab, click Reboot and click Reboot in the confirmation dialog box to restart the primary vRealize Automation appliance.

Note: Additional vRealize Automation virtual appliances restart automatically.

Log in to the first vRealize Automation appliance via the VAMI interface (https://<vRA Appliance FQDN>:5480).

On the Update tab, click the Status button, and monitor the vRealize Automation IaaS upgrade for each Windows Server-based component.

After the upgrade completes for the vRealize Automation IaaS components, use the vRA Settings > Cluster tab to verify that each vRealize Automation IaaS nodes and components are version 7.5.0.xxxxx.

On the vRA Settings > Licensing tab, verify that the vRealize Automation product license information remains and a valid license is still available.

If the upgrade process has removed the license, re-enter the license key.

Enter the license key in the New License Key text box and click Submit Key.

Verify that the license has been applied.

Repeat this step on other vRA virtual appliances.

Restore the Configuration of the vRealize Orchestrator Authentication Provider

Log in to the vRealize Automation appliance by using Secure Shell (SSH) client to configure the embedded vRealize Orchestrator.

Verify that the vRealize Orchestrator user interface service is running.

Run the following command to verify that the service is set to automatically start:

chkconfig vco-configurator

If the service reports Off, run the following command to enable an automatic restart of the Orchestrator user interface service upon subsequent reboots of the vRealize Automation appliance:

chkconfig vco-configurator on

Verify the status of Orchestrator User Interface by running the following command:

service vco-configurator status

Repeat the procedure to configure vRealize Orchestrator for the other vRA appliances.

Log in to vRealize Orchestrator Control Center to change the default tenant and admin group for the authentication provider.

Associate the default tenant and admin group for the vRealize Orchestrator authentication provider with the tenant configured prior to the upgrade.

Under the Manage group of settings, select Configure Authentication Provider.

On the Configure Autenthication Provider page, click Change next to Default tenant, enter the name of the tenant configured prior to the upgrade, and click Apply.

Click Change next to Admin group, enter the name of the group used/configured prior to the upgrade, and click Search.

From the drop-down menu, select the the name of the group used/configured prior to the upgrade, and click Apply.

Click Save Changes.

Register vRealize Business Back with vRealize Automation

Note: These steps are only needed if the steps under Unregister vRealize Automation from vRealize Business were followed.

Log in to the vRealize Business Server appliance management console (https://<vRB IP>:5480).

On the Registration tab, click the vRA tab.

Enter the appropriate values and click Unregister.

Note: A Registered with vRealize Automation message appears at the top of the page.

Re-Enable Traffic to the Secondary Nodes and Health Monitoring for vRealize Automation on the Load Balancer

Log in to vCenter Server by using the vSphere Web Client.

From the Home menu of the vSphere Web Client, select Networking & Security.

In the Navigator, click NSX Edges.

From the NSX Manager drop-down menu, select the NSX Manager IP Address corresponding to the NSX Manager for the management workload domain and double-click the vRA edge device to open its network settings.

On the Manage tab, click the Load Balancer tab and click Pools.

Select the vra-svr-443 pool that contains the vRealize Automation appliances and click Edit.

In the Edit Pool dialog box, select the secondary node, click Edit, select Enable from the State drop-down menu, and click OK. Repeat this step for the third node.

In the Edit Pool dialog box, select NONE from the Monitors drop-down menu and click OK.

Repeat the procedure on the remaining load balancer pools.

Note: Once the upgrade is completed and validated, any snapshots taken of the vRealize Automation nodes should be deleted.

Update the vRealize Automation version recorded in SDDC Manager

Download the attached 65101_vra_version_updater.zip file.

Use a file transfer utility to copy the downloaded file to the /tmp folder on the SDDC Manager VM.

SSH to the SDDC Manager VM as the vcf user and use the su - command to switch to the root user.

Issue the following command to extract the contents of /tmp/65101_vra_version_updater.zip file:

unzip -d /tmp/ /tmp/65101_vra_version_updater.zip

Issue the following command to execute the /tmp/vra_version_updater.py script:

python /tmp/vra_version_updater.py

Important Note: Ensure that the items noted in Post-Upgrade Tasks for Upgrading vRealize Automation are completed once the upgrade is finished.

Related Information

Please reference Troubleshooting the vRealize Automation Upgrade for any issues encountered during the vRealize Automation upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

65101_vra_version_updater.zip

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
确定从基于文件的备份还原 SDDC Manager 的 OVA 下载位置 (70522)

KB
•
管理 vSphere 6.0 Update 3 的 TLS 协议配置 (2148819)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.5.x

Take Our Survey

Support Assistant