7.4

Reconfigure a Load Balancer in a Deployment
You can add, edit, or delete a virtual server in a deployed NSX load balancer.
The following considerations apply to deployments that originated in vRealize Automation 7.2 or earlier:
n
Load balancer reconfiguration is limited to deployments that contain a single load balancer.
n
The Items detail page for any load balancer in a deployment displays the virtual servers that are used
by all the load balancers in the deployment. For more information, see Knowledge Base Article
2150276.
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.
For upgraded load balancers and load balancers deployed in the current vRealize Automation release, do
not edit a virtual server and add a virtual server in the same request. For more information, see
Knowledge Base Article 2150240.
If you submit a request to reconfigure a load balancer while another action is being performed on the
deployment, for example when a scale out operation on the deployment is in progress, reconfiguration
fails with a supporting message. In this situation, you can wait until the action is finished and then submit
the reconfiguration request.
Note If the blueprint associated with the deployment is imported from a YAML file that contains an on-
demand load balancer with a value in the name field that is different from the value in the ID field, the
Reconfigure action fails. To enable the load balancer reconfiguration option for a deployment that is
based on an imported blueprint, perform the following steps in the blueprint to allow post-provisioning
actions for load balancer components in future deployments.
1 In the vRealize Automation consol, select the blueprint.
2 Click Edit and change the blueprint name. This sets the name and embedded ID to the same value.
3 Select the load balancer component in the blueprint.
4 Click Edit and re-enter the component name. This sets the name and embedded ID to the same
value.
5 Repeat for all load balancer components in the blueprint.
6 Save the blueprint.
When you provision a new deployment using the edited blueprint, the reconfigure load balancer action
works. To avoid this issue, ensure that all YAML files have identical name and ID values for all load
balancer, network, and security components prior to importing them.
You should not manage vRealize Automation-administered NSX objects outside of vRealize Automation.
For example, if you modify the member port of a deployed NSX load balancer in NSX, rather than in
vRealize Automation, then NSX data collection breaks association between the deployed machine and its
otherwise associated load balancer member pool. Scale in and scale out operations also produce
unexpected results if a deployed load balancer member port is changed outside of vRealize Automation.
Configuring vRealize Automation
VMware, Inc. 617