Menu
Can someone explain to me what actually happens in the back-end to the load balancer (v2) for the two scenarios:
Applying Inbound NAT rules.
Applying Load Balancing Rules.
530
There are two types of inbound NAT rule: Single virtual machine - An inbound NAT rule that targets a single machine in the backend pool of the load balancer. Multiple virtual machines - An inbound NAT rule that targets multiple virtual machines in the backend pool of the load balancer.
An inbound NAT rule forwards incoming traffic sent to frontend IP address and port combination. The traffic is sent to a specific virtual machine or instance in the backend pool.
To sum it up, we learned that the Azure Traffic Manager has been designed to distribute traffic globally (Multiregional environments). Nevertheless, the Azure Load Balancer can only route traffic inside an Azure region, as it only works with Virtual Machines in the same region.
Load-balancing rules - A load balancer rule is used to define how incoming traffic is distributed to the all the instances within the backend pool. A load-balancing rule maps a given frontend IP configuration and port to multiple backend IP addresses and ports.
You would use NAT rule when you have 1 backend server or you know which backend server to get to and loadbalancing rule when you want to loadbalance to multiple backend servers.
92
NAT rule must be explicitly attached to a VM (or network interface) to complete the path to the target; whereas Load Balancing rule need not be. In the latter case, a VM is selected (from the back-end address pool or VMs) to complete the path to the target.
30
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
