| title | description | services | documentationcenter | author | ms.service | ms.devlang | ms.topic | ms.tgt_pltfrm | ms.workload | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|
Azure Load Balancer Floating IP configuration |
Overview of Azure Load Balancer Floating IP |
load-balancer |
na |
asudbring |
load-balancer |
na |
conceptual |
na |
infrastructure-services |
07/13/2020 |
allensu |
Load balancer provides several capabilities for both UDP and TCP applications.
Some application scenarios prefer or require the same port to be used by multiple application instances on a single VM in the backend pool. Common examples of port reuse include clustering for high availability, network virtual appliances, and exposing multiple TLS endpoints without re-encryption. If you want to reuse the backend port across multiple rules, you must enable Floating IP in the rule definition.
Floating IP is Azure's terminology for a portion of what is known as Direct Server Return (DSR). DSR consists of two parts:
- Flow topology
- An IP address mapping scheme
At a platform level, Azure Load Balancer always operates in a DSR flow topology regardless of whether Floating IP is enabled or not. This means that the outbound part of a flow is always correctly rewritten to flow directly back to the origin. Without Floating IP, Azure exposes a traditional load balancing IP address mapping scheme for ease of use (the VM instances' IP). Enabling Floating IP changes the IP address mapping to the Frontend IP of the load Balancer to allow for additional flexibility. Learn more here.
- Floating IP is not currently supported on secondary IP configurations for Load Balancing scenarios
- See Create a public Standard Load Balancer to get started with using a Load Balancer.
- Learn about Azure Load Balancer outbound connections.
- Learn more about Azure Load Balancer.
- Learn about Health Probes.
- Learn about Standard Load Balancer Diagnostics.
- Learn more about Network Security Groups.