Installing Avi Load Balancer in VMware NSX-T Environments

Docs

Docs
(current)
VMware Communities

Twitter Facebook LinkedIn 微博

This section provides information about deploying Avi Load Balancer in VMware vSphere with NSX-T managed networking and security.

What to read next

Overview of NSX-T Integration with Avi Load Balancer
VMware NSX-T provides an agile software-defined infrastructure to build cloud-native application environments. It includes networking, security, automation, and operational simplicity for emerging application frameworks and architectures with heterogeneous endpoint environments and technology stacks. NSX-T supports cloud-native applications, bare metal workloads, multi-hypervisor environments, public clouds, and multiple clouds.
Installing the Controller
Follow these steps to install the Controller:
Configuring the Cloud Connector
The Avi Load Balancer SE management interface must be connected to a logical segment. The management-logical segment needs connectivity to be able to reach the Avi Load Balancer Controller management IP.
Migrating NSX-T Load Balancer to Avi Load Balancer
This guide provides information on how to migrate NSX-T Load Balancer to Avi Load Balancer.
Avi Load Balancer VLAN Logical Segment
Virtual LAN (VLAN)-backed logical segments are created in a VLAN transport zone, and are managed by the Avi Load Balancer. Most of the large brownfield deployments use VLAN-backed segments for configuring VLAN micro-segmentation with Avi Load Balancer, since it is simple and non-disruptive to the existing environment.
NSX-T Route Revocation
This section discusses the use of revoke_vip_route flag available under virtual service configuration for NSX-T cloud deployment.
Avi Load Balancer NSX-T over-the-top Deployment Design Guide
This section describes the installation design of Avi Load Balancer on NSX-T managed vSphere environments (vCenter + ESXi). Avi Load Balancer supports over-the-top, manual deployment in the NSX-T environment.
Multiple vCenters with NSX-T Cloud
As part of the NSX-T cloud configuration, multiple vCenters with stretched transport zone can be added.
SE Deployment in NSX-T with DFW
All the groups and service objects used for creating these Distributed Firewall (DFW) rules are auto-created by the Avi Load Balancer NSX-T cloud connector with the Object Name Prefix configured during the NSX-T cloud creation in the Avi Load Balancer Controller. Therefore, enabling the Service Engine virtual machines to be included in the DFW rules.
NSX-V to Avi Migration Tool
The NSX-V to Avi migration facilitates the transition from NSX's built-in NSX Advanced Load Balancer to the Avi Load Balancer. The tool retrieves the existing load balancer configurations from NSX and maps them to the Avi Load Balancer.
Preserve Client IP for NSX-T Overlay
This topic discusses the pre-requisites and steps to configure Preserve client IP for NSX-T overlay deployments
vCenter Cloud API - CLI
This section explains the API and CLI specifications that got added, updated or deprecated for vCenter Cloud due to the new implementation starting in 22.1.1.
NSX-T Design for Avi Load Balancer
VMware NSX-T provides an agile software-defined infrastructure to build cloud-native application environments. NSX-T is focused on providing networking, security, automation, and operational simplicity for emerging application frameworks and architectures that have heterogeneous endpoint environments and technology stacks. This topic describes the design details of the Avi Load Balancer - NSX-T integration.
Integration with NSX Multi-Tenancy
NSX introduced the multi-tenancy framework with NSX Projects and NSX Virtual Private Cloud (VPC), using which you can configure multiple tenants and specific role-based users on a single NSX deployment by delivering flexible resource allocation, management, and cloud-like consumption.
Conditional DFW Object creation in NSX cloud
When deploying generic rules, NSX Distributed Firewall (DFW) objects such as NS Groups and NS Services are automatically generated by the cloud connector for each virtual service or pool. However, not all of these automatically created objects may be necessary. The accumulation of unused objects can lead to reaching the scaling limits within NSX. This topic shows how to control DFW object creation.

Share on Social Media?

:

|

x

" "?