You can add one or more on-demand NSX load balancer components to the design canvas to configure vSphere machine component settings in the blueprint.

The network and security component settings that you add to the design canvas are derived from your NSX configuration and require that you have run data collection for the NSX inventory for vSphere clusters. Network and security components are specific to NSX and are available for use with vSphere machine components only. For information about configuring NSX, see NSX Administration Guide.

The following rules apply to load balancer pools and VIP network settings in the blueprint.

  • If the pool network profile is NAT, the VIP network profile can be part of the NAT network profile.

  • If the pool network profile is routed, the VIP network profile can only be on the same routed network.

  • 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.

You can reconfigure load balancer settings in a 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.