7.3

Table Of Contents
n
If the pool network profile is routed, the VIP network profile can only be on the same routed network.
n
If the pool network profile is external, the VIP network profile can only be the same external network
profile.
Each load balancer component can have multiple virtual servers, which are also referred to as load
balancer services. Each virtual server in the load balancer component has one port and protocol. For
example, you can load balance an HTTP service or HTTPS service. A load balancer can have multiple
services that it is load balancing.
The NSX Edge is the network device that contains the load balancer virtual servers. While you can have
more than one load balancer component in a blueprint, when you provision the deployment, the virtual
servers defined in each load balancer component are contained in a single NSX Edge.
If a blueprint contains one or more load balancers and app isolation is enabled for the blueprint, the load
balancer VIPs are added to the app isolation security group as an IPSet. If a blueprints contains an on-
demand security group that is associated to a machine tier that is also associated to a load balancer, the
on-demand security group includes the machine tier and the IPSet with the load balancer VIP.
You can reconfigure load balancer settings in an existing deployment to add, edit, or remove virtual
servers. For information, see Reconfigure a Load Balancer in a Deployment.
For information about working with load balancer components after upgrade or migration, see
Considerations When Working With Upgraded or Migrated Load Balancer Components.
Considerations When Working With Upgraded or Migrated Load Balancer Components
The following considerations are important to understand and act on relative to NSX load balancer
components in the target vRealize Automation release.
This information applies to NSX load balancer components that were upgraded or migrated to this
vRealize Automation release.
n
You must run NSX Network and Security Inventory data collection before and after upgrading or
migrating to this release to avoid issues when running the Reconfigure Load Balancer action. The
Reconfigure Load Balancer action for new deployments is not affected.
For more information, see Upgrading from vRealize Automation 7.1 or 7.2 to 7.3 and Migrating
vRealize Automation to 7.3.
n
As of vRealize Automation 7.3, you can reconfigure a load balancer. The required catalog entitlement
is Reconfigure (Load Balancer). For related information, see Reconfigure a Load Balancer in a
Deployment.
n
For deployments that were upgraded or migrated from vRealize Automation 7.x to this
vRealize Automation release, load balancer reconfiguration is limited to deployments that contain a
single load balancer.
n
The Reconfigure Load Balancer operation is not supported for deployments that were upgraded or
migrated from vRealize Automation 6.2.x to this vRealize Automation release.
Configuring vRealize Automation
VMware, Inc. 395