This section covers the following topics: Load Balance API Gateways Setting up Microsoft Exchange Server 2016 with NSX Advanced Load Balancer Load Balance FTP Load Balancing Passive FTP on NSX Advanced Load Balancer Load Balancing RADIUS with Cisco ISE Load Balance API GatewaysIn microservice-based architectures, an API gateway enables easy consumption of services required for their client or server applications, by exposing a single end-point to those applications. The API gateway acts as a bridge between applications and microservices. Setting up Microsoft Exchange Server 2016 with NSX Advanced Load BalancerMicrosoft Exchange Server 2016 is an e-mail server solution, with a calendar and contact manager, which supports a variety of clients such as Outlook, web browser, and mobile devices. Load Balance FTPFor file transfer protocol (FTP) communication, clients open a TCP-based control channel on port 21. For active FTP, a second data channel is initiated from the server to the client via port 21. NSX Advanced Load Balancer only supports passive FTP, in which the client initiates the data channel via a high port negotiated with the server. Load Balancing Passive FTP on NSX Advanced Load BalancerThis section explains configuring NSX Advanced Load Balancer virtual service to load balance passive FTP. Load Balancing RADIUS with Cisco ISEThis section explains the steps to configure NSX Advanced Load Balancer to load balance RADIUS traffic to Cisco Identity Services Engine (ISE). NSX Advanced Load Balancer uses L4 DataScripts to achieve persistence using various RADIUS attributes and load balance DHCP profiling traffic to the same server as RADIUS. Parent topic: Load Balancing
