Configuring Load Balancer in Inline Mode

C.

To configure a load balancer in inline mode, the following are required:

B. SNAT: The load balancer in inline mode uses SNAT (Source Network Address Translation) to change the source IP address of the packets. This ensures that when the load balancer sends packets to the server, the server responds back to the load balancer and not directly to the client. This helps to ensure that the load balancer is in the path of the traffic.

C. Client and server connected to different Tier-1 Gateways: In inline mode, the client and server should be connected to different Tier-1 Gateways. This ensures that the traffic between the client and server goes through the load balancer. The load balancer is connected to both Tier-1 Gateways and is responsible for forwarding the traffic between the client and server.

Additionally, it is worth noting that the load balancer in inline mode can be configured in two ways:

1. Transparent Mode: In this mode, the load balancer is transparent to the client and server. The client and server are not aware of the load balancer's presence in the network.

2. Service Insertion Mode: In this mode, the load balancer is inserted into the traffic flow between the client and server. The client and server are aware of the load balancer's presence in the network. This mode allows for more advanced load balancing features such as SSL offloading and URL filtering.

A. DNAT: DNAT (Destination Network Address Translation) is not required to configure a load balancer in inline mode. DNAT is used in NAT mode, where the load balancer changes the destination IP address of the packets.

D. Client and server running on different transport nodes: In inline mode, the client and server do not need to be running on different transport nodes. Transport nodes are responsible for forwarding traffic to the appropriate destination, but in inline mode, the traffic goes through the load balancer, which is responsible for forwarding the traffic.