You can upgrade any outdated Software Agents on vSphere to TLS 1.2 after migration using vRealize Automation Appliance Management.
About this task
This procedure updates the outdated Software Agents on the virtual machines from your source environment to TLS 1.2 and is required for migration to vRealize Automation 7.4.
Apply Software Agent Patch if you migrated from vRealize Automation 7.1, or 7.3 to 7.4.
Successful migration from vRealize Automation 7.1, 7.2, 7.3 or 7.3.1 to 7.4.
You have used Health Service to identify virtual appliances with outdated Software Agents.
- On your primary vRealize Automation appliance, log in to vRealize Automation Appliance Management as root using the password you entered when you deployed the vRealize Automation appliance.
For a high-availability environment, open Appliance Management on the master appliance.
- Click .
- Click Toggle TLS 1.0, 1.1.
TLS v1.0, v1.1 Status is ENABLED.
- For Tenant credentials, enter the requested information for the source vRealize Automation appliance.
Name of tenant on the source vRealize Automation appliance.Note:
The tenant user must have the Software Architect role assigned.
Tenant administrator user name on the source vRealize Automation appliance.
Tenant administrator password.
- Click Test connection.
If a connection is established, a success message appears.
- For Source appliance, enter the IP address or fully qualified domain name of the source vRealize Automation appliance.
The source and the target appliance must both use the same tenant credentials.
- Click List batches.
The Batch Choice List table appears.
- Click Show.
A table appears with a list of virtual machines with outdated Software Agents.
- Upgrade the Software Agent for the virtual machines that are in the UPGRADABLE state.
To upgrade the Software Agent in an individual virtual machine, click Show for a group of virtual machines, identify the virtual machine you want to upgrade and click Run to start the upgrade process.
To upgrade the Software Agent for a batch of virtual machines, identify the group that you want to upgrade and click Run to start the upgrade process.
If you have more than 200 virtual machines to upgrade, you can control the batch upgrade process speed by entering values for these parameters.
The number of virtual machines selected for batch upgrade. You can vary this number to adjust the upgrade speed.
The number of parallel upgrade executions that take place at one time. For example, 20. You can vary this number to adjust the upgrade speed.
The REST error count causing batch upgrade to slow down. For example, if you want to stop the current batch upgrade after 5 failures to improve the stability of the upgrade, enter 5 in the text field.
The number of failed Software Agent upgrades causing batch processing to slow down. For example, if you want to stop the current batch upgrade after 5 failures to improve the stability of the upgrade, enter 5 in the text field.
How often the upgrade process is polled to check the upgrade process. You can vary this number to adjust the upgrade speed.
If the upgrade process is too slow or produces too many unsuccessful upgrades, you can adjust these parameters to improve upgrade performance.Note:
Clicking Refresh clears the list of batches. It does not affect the upgrade process. It also refreshes information about whether TLS 1.2 is set or not In addition, clicking Refresh also performs a health check of vRealize Automation services. If services are not running, the system displays an error message and inactivates all other action buttons.
- Click Toggle TLS 1.0, 1.1.
TLS v1.0, v1.1 Status is DISABLED.