Skip to content

Commit f93747b

Browse files
authored
Merge pull request #111414 from anavinahar/patch-239
Update load-balancer-outbound-connections.md
2 parents 363e9c2 + 5ecc678 commit f93747b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/load-balancer/load-balancer-outbound-connections.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ The following table shows the SNAT port preallocations for tiers of backend pool
163163
| 801-1,000 | 32 |
164164

165165
>[!NOTE]
166-
> When using Standard Load Balancer with [multiple frontends](load-balancer-multivip-overview.md), each frontend IP address multiplies the number of available SNAT ports in the previous table. For example, a backend pool of 50 VM's with 2 load balancing rules, each with a separate frontend IP address, will use 2048 (2x 1024) SNAT ports per IP configuration. See details for [multiple frontends](#multife).
166+
> When using Standard Load Balancer with [multiple frontends](load-balancer-multivip-overview.md), each frontend IP address multiplies the number of available SNAT ports in the previous table. For example, a backend pool of 50 VM's with 2 load balancing rules, each with a separate frontend IP address, will use 2048 (2x 1024) SNAT ports per rule. See details for [multiple frontends](#multife).
167167
168168
Remember that the number of SNAT ports available does not translate directly to number of flows. A single SNAT port can be reused for multiple unique destinations. Ports are consumed only if it's necessary to make flows unique. For design and mitigation guidance, refer to the section about [how to manage this exhaustible resource](#snatexhaust) and the section that describes [PAT](#pat).
169169

0 commit comments

Comments
 (0)