Skip to content

Commit 44a592b

Browse files
Merge pull request #247867 from mahipdeora/main
update
2 parents 48064c5 + e955519 commit 44a592b

File tree

2 files changed

+4
-1
lines changed

2 files changed

+4
-1
lines changed

articles/load-balancer/backend-pool-management.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -224,6 +224,7 @@ az vm create \
224224
* You can configure IP based and NIC based backend pools for the same load balancer. You can’t create a single backend pool that mixes backed addresses targeted by NIC and IP addresses within the same pool.
225225
* A virtual machine in the same virtual network as an internal load balancer can't access the frontend of the ILB and its backend VMs simultaneously.
226226
* Internet routing preference IPs are currently not supported with IP based backend pools. Any Internet routing preference IPs in IP based backend pools will be billed and routed via the default Microsoft global network.
227+
* If backend pools are constantly changing (due to the constant addition or removal of backend resources), there is a chance that existing connections may get rehashed. During this process, the backend resource may send a reset signal to the source. A workaround is to utilize retries to avoid the reset signal.
227228

228229
>[!Important]
229230
> When a backend pool is configured by IP address, it will behave as a Basic Load Balancer with default outbound enabled. For secure by default configuration and applications with demanding outbound needs, configure the backend pool by NIC.

articles/load-balancer/manage-inbound-nat-rules.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,12 +102,13 @@ $lb | Set-AzLoadBalancer
102102

103103
[!INCLUDE [azure-cli-prepare-your-environment.md](~/articles/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
104104

105-
In this example, you create an inbound NAT rule to forward port **500** to backend port **443**.
105+
In this example, you will create an inbound NAT rule to forward port **500** to backend port **443**. You will then attach the inbound NAT rule to a VM's NIC
106106

107107
Use [az network lb inbound-nat-rule create](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-create) to create the NAT rule.
108108

109109
Use [az network nic ip-config inbound-nat-rule add](/cli/azure/network/nic/ip-config/inbound-nat-rule) to add the inbound NAT rule to a VM's NIC
110110

111+
111112
```azurecli
112113
az network lb inbound-nat-rule create \
113114
--backend-port 443 \
@@ -124,6 +125,7 @@ Use [az network nic ip-config inbound-nat-rule add](/cli/azure/network/nic/ip-co
124125
--ip-config-name MyIpConfig \
125126
--inbound-nat-rule MyNatRule \
126127
--lb-name myLoadBalancer
128+
127129
```
128130
---
129131

0 commit comments

Comments
 (0)