Which mode can the NSX Edge Load Balancer can be deploy…

A company hosts an internal website on multiple virtual machines on a Logical Switch with VNI 7321. A Distributed Router serves as the virtual machines’ default
gateway. When an user resolves the URL for the website, the internal DNS server responds with the IP address of one of the virtual machine’s IP addresses in a
round robin fashion. The company wants to deploy an NSX Edge Service Load Balancer and maintain the use of the Distributed Router for the virtual machines’
default gateway.
Which mode can the NSX Edge Load Balancer can be deployed to meet the Company’s needs?

A company hosts an internal website on multiple virtual machines on a Logical Switch with VNI 7321. A Distributed Router serves as the virtual machines’ default
gateway. When an user resolves the URL for the website, the internal DNS server responds with the IP address of one of the virtual machine’s IP addresses in a
round robin fashion. The company wants to deploy an NSX Edge Service Load Balancer and maintain the use of the Distributed Router for the virtual machines’
default gateway.
Which mode can the NSX Edge Load Balancer can be deployed to meet the Company’s needs?

A.
One-Arm

B.
Transparent

C.
Local

D.
Global



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Catalin

Catalin

NSX Logical Load Balancing: One-Armed Topology

One-Armed or Proxy mode consists of deploying an NSX edge directly connected to the logical network where load-balancing services are required.

The external client sends traffic to the Virtual IP address (VIP) exposed by the load balancer.

The load balancer performs two address translations on the original packets received from the client: destination NAT (DNAT) to replace the VIP with the IP address of one of the servers deployed in the server farm, and source NAT (SNAT) to replace the client IP address with the IP address identifying the load balancer itself. SNAT is required to force through the load balancer the return traffic from the server farm to the client.

The server in the server farm replies by sending the traffic to the load balancer per SNAT functionality.

The load balancer again performs a source and destination NAT service to send traffic to the external client, leveraging its VIP as source IP address.