7.1

Some multi-machine blueprint seings are not supported in the target vRealize Automation deployment,
including private network proles and routed network proles with associated PLR edge seings. Note that
if you have used a custom property to specify PLR edge seings (VCNS.LoadBalancerEdgePool.Names ),
the custom property is upgraded.
If the multi-machine blueprint uses vSphere endpoints and NSX network and security seings, the
upgraded composite blueprint also contains NSX network and security components in the design canvas.
N Routed gateway specications for multi-machine blueprints, as dened in reservations, are
upgraded. However, the target vRealize Automation deployment does not support reservations for routed
proles that contain associated PLR edge seings. If the source reservation contains a routed gateway value
for a PLR edge, the reservation is upgraded but the routed gateway seing is ignored. As a result, the
upgrade generates an error message in the log le and the reservation is disabled.
During upgrade, spaces and special characters are removed from referenced network and security
component names.
Depending on the seing type, the network and security information is captured as several seings in the
new blueprint.
n
Seings for the overall blueprint on its properties page. This information includes app isolation,
transport zone, and routed gateway or NSX edge reservation policy information.
n
Available seings for vSphere machine components in NSX network and security components in the
design canvas.
n
Seings in the network and security tabs of individual vSphere machine components in the design
canvas.
Upgrade and Physical Endpoints, Reservations, and Blueprints
You cannot upgrade a deployment that contains physical endpoints. The presence of endpoints of type
physical prevents the vRealize Automation upgrade process from completing.
When upgrade encounters a physical endpoint in the source deployment, upgrade fails on the master
virtual appliance and reports a message in the user interface and log. You can determine if your source
deployment contains physical endpoints by logging in to vRealize Automation with Iaas Administrator
privileges, selecting Infrastructure > Endponts and noting the platform type value in the endpoints list. If
the list contains endpoints of Platform Type Physical, upgrade is not supported.
Physical endpoints, reservations, and machine components in blueprints are not supported in the target
vRealize Automation deployment.
Upgrade and Network Profile Settings
Private network proles are not supported in the target deployment and are ignored during the upgrade.
Routed network proles with associated PLR edge seings are also not supported in the target deployment
and are also ignored during the upgrade.
The private network prole type is not supported in the target vRealize Automation deployment. When the
vRealize Automation upgrade executable encounters a private network prole in the source deployment, it
ignores the network prole. Load balancers that reference those private networks are also ignored during
upgrade. The same upgrade conditions are true for a routed network prole with associated PLR edge
seings. Neither network prole conguration is upgraded.
If a reservation contains a private network prole, the private network prole seing is ignored during
upgrade and the reservation is upgraded as disabled in the target deployment.
If a reservation contains a routed network prole with associated PLR edge seings, the routed network
prole specication is ignored during upgrade and the reservation is upgraded as disabled in the target
deployment.
Upgrading from vRealize Automation 6.2 to 7.1
12 VMware, Inc.