Considerations When Working With Upgraded or Migrated Endpoints
After you upgrade or migrate from a pre-vRealize Automation 7.3 release, the following considerations are important to understand and act on.
This information applies to endpoints that were upgraded or migrated to this vRealize Automation release.
- When you upgrade or migrate
from a pre-vRealize Automation 7.3 release, each
Director, and Amazon endpoint that contains proxy settings is
associated to a new proxy endpoint that contains its proxy settings.
After upgrade or migration, the new Proxy endpoint name is Proxy_YYYYY where YYYYY is a hash of the proxy's URL, port, and credentials. If you used the same proxy settings (for example the same URL, port, and credentials) for a different endpoint (for example, a vCloud Air or Amazon endpoint), after upgrade or migration there is only one Proxy endpoint and an association between the vCloud Air and Amazon endpoint and the new Proxy endpoint. A proxy endpoint can be associated to more than one Amazon, vCloud Air or vCloud Director endpoint.
- When you upgrade or migrate
endpoints that contain
endpoint is associated to a new
that contains its
After upgrade or migration, the NSX endpoint name is NSX_XXXXX where XXXXX is the name of the parent vSphere endpoint in the pre-vRealize Automation 7.3 release.
When vRealize Automation upgrade or migration is finished, an infrastructure administrator can change the new NSX and Proxy endpoint names.
The default security setting for upgraded or migrated endpoints is not to accept untrusted certificates.
After upgrading or migrating from an earlier vRealize Automation installation, if you were using untrusted certificates you must perform the following steps for all vSphere and NSX endpoints to enable certificate validation. Otherwise, the endpoint operations fail with certificate errors. For more information, see VMware Knowledge Base articles Endpoint communication is broken after upgrade to vRA 7.3 (2150230) at http://kb.vmware.com/kb/2150230 and How to download and install vCenter Server root certificates to avoid Web Browser certificate warnings (2108294) at http://kb.vmware.com/kb/2108294.
- After upgrade or
migration, log in to the
machine and restart your
by using the
Migration might not restart all agents, so manually restart them if needed.
- Wait for at least one ping report to finish. It takes a minute or two for a ping report to finish.
- When the vSphere agents have started data collection, log in to vRealize Automation as an IaaS administrator.
- Click .
- Edit a vSphere endpoint and click Test Connection.
- If a certificate prompt
OK to accept the
If a certificate prompt does not appear, the certificate might currently be correctly stored in a trusted root authority of the Windows machine hosting service for the endpoint, for example as a proxy agent machine or DEM machine.
- Click OK to apply the certificate acceptance and save the endpoint.
- Repeat this procedure for each vSphere endpoint.
- Repeat this procedure for each NSX endpoint.
- Navigate to Infrastructure > Compute Resources and right click on your vCenter Compute resource and run Data Collection..
If the Test Connection action is successful but some data collection or provisioning operations fail, you can install the same certificate on all the agent machines that serve the endpoint and on all DEM machines. Alternatively, you can uninstall the certificate from existing machines and repeat the preceding procedure for the failing endpoint.
- After upgrade or migration, log in to the vRealize Automation vSphere agent machine and restart your vSphere agents by using the Services tab.
- The vRealize Automation REST APIs that were used to programmatically create, edit, and delete endpoints in vRealize Automation 7.2 and earlier are no longer supported in vRealize Automation 7.3 and later. To programmatically create, edit, and delete endpoints in vRealize Automation 7.3 or later you must use either new vRealize Automation endpoint-configuration-service REST APIs or use vRealize CloudClient.
After you upgrade or migrate from an earlier vRealize Automation installation, if data collection fails for OpenStack endpoints you can add the VMware.Endpoint.Openstack.IdentityProvider.Domain.Name custom property to each Keystone V3 OpenStack endpoint to specify a valid domain name and enable data collection.
- When you upgrade a third-party IPAM endpoint, such as Infoblox IPAM, the vRealize Orchestrator package that contains the RegisterIPAMEndpoint workflow is upgraded. You might need to rerun the workflow in vRealize Orchestrator when the vRealize Automation upgrade is finished.
- To make a credentials change to multiple endpoints, you can either edit the endpoints individually or use vRealize CloudClient to perform a bulk update.
- Some endpoint types, such as vCloud Air and vCloud Director, cannot be upgraded or migrated directly from vRealize Automation 6.2.x to vRealize Automation 7.3 or greater.
- After a successful upgrade or migration to vRealize Automation 7.3, if the page does not show any endpoints or only shows some endpoint types and endpoints, see Knowledge Base Article 2150252 for a suggested workaround.