Tuesday, September 21, 2021, 1:09 AM
Integration of the NSX Advanced Load Balancer (AVI) with the vCloud Director 10.3
It is now possible to use the NSX Advanced Load Balancer (ALB), which was formerly known as the AVI Vantage Platform, with vCloud Director.
Integration with ALB 20.
1 was made possible by VCD 10.
2, which was the first version to enable the feature.
NSX ALB versions 20.
3 and 20.
4 are supported in the current VCD version 10.
3 (which is, at the time of writing this article, the most recent available).
If you are considering integrating VCD and NSX ALB, you should consult the VMware Interoperability Matrix to learn about the most recent supported combinations of the two technologies (as you do always).
https://interopmatrix. vmware. com/
When NSX-T is utilized as the network backing type for the OrgVDCs, the LBaaS option is made accessible via NSX ALB (NSX ALB). VCD does not make use of the NSX-T loadbalancer that comes with the operating system.
As part of this blog article, we will go through the NSX ALB design with VCD, the NSX-T setup, the vSphere configuration, and the integration of the ALB and VCD, as well as some additional points that we should be aware of.
Let's get this party started.
Design of the NSX ALB in vCloud Director
Two design options are available, which are determined by the resource guarantees and the degree of isolation needed for tenant applications. They are as follows:
Service Engine Group (SEG) Design Dedicated Service Engine Group (SEG) Design Shared Service Engine Group (SEG) Design
In a Shared SEG architecture, the VCD tenants (more particularly, the OrgVDC gateways) share the Service Engines from a common Service Engine Group in order to host their virtual services on the shared service engines. In order to keep all tenant apps on the same SEG, they share the data plane, and the app isolation is accomplished via the use of virtual router contexts. If you have an OrgVDC gateway that is activated with the load balancing service on a shared SEG architecture, each of the service engines will have a data nic plugged in. In the SEs, this data nic is associated with a specific vrf context. An SE may support a maximum of ten data nics, and therefore a maximum of ten OrgVDC gateways (unless limited by the hypervisor). Given that each tenant (in OrgVDCs) will have its own unique vrf context, the virtual services of each tenant (in OrgVDCs) will be limited to their own dedicated virtual resource frames in SE.
In a shared SEG architecture, an OrgVDC gateway usually receives a portion of the entire virtual server (VS) capacity of the SEG, which is determined by the tenant's needs.