Skip to content

Commit 2c511f4

Browse files
Tweak
1 parent e3e8957 commit 2c511f4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -120,21 +120,21 @@ When a public Load Balancer resource is associated with VM instances, each outbo
120120

121121
Ephemeral ports (SNAT ports) are used to achieve this after rewriting the private source IP address, because multiple flows originate from a single public IP address. The port masquerading SNAT algorithm allocates SNAT ports differently for UDP versus TCP.
122122

123-
#### TCP SNAT Ports
123+
#### <a name="tcp"></a>TCP SNAT Ports
124124

125125
One SNAT port is consumed per flow to a single destination IP address, port. For multiple TCP flows to the same destination IP address, port, and protocol, each TCP flow consumes a single SNAT port. This ensures that the flows are unique when they originate from the same public IP address and go to the same destination IP address, port, and protocol.
126126

127127
Multiple flows, each to a different destination IP address, port, and protocol, share a single SNAT port. The destination IP address, port, and protocol make flows unique without the need for additional source ports to distinguish flows in the public IP address space.
128128

129-
#### UDP SNAT Ports
129+
#### <a name="udp"></a> UDP SNAT Ports
130130

131131
UDP SNAT ports are managed by a different algorithm than TCP SNAT ports. Load Balancer uses an algorithm known as "port-restricted cone NAT" for UDP. One SNAT port is consumed for each flow, irrespective of destination IP address, port.
132132

133133
#### Exhaustion
134134

135135
When SNAT port resources are exhausted, outbound flows fail until existing flows release SNAT ports. Load Balancer reclaims SNAT ports when the flow closes and uses a [4-minute idle timeout](#idletimeout) for reclaiming SNAT ports from idle flows.
136136

137-
UDP SNAT ports generally exhaust much faster than TCP SNAT ports due to the difference in algorithm. You must design and scale test with this difference in mind.
137+
UDP SNAT ports generally exhaust much faster than TCP SNAT ports due to the difference in algorithm used. You must design and scale test with this difference in mind.
138138

139139
For patterns to mitigate conditions that commonly lead to SNAT port exhaustion, review the [Managing SNAT](#snatexhaust) section.
140140

0 commit comments

Comments
 (0)