forked from docs/doc-exports
ELB UMN initial upload
Reviewed-by: gtema <artem.goncharov@gmail.com> Co-authored-by: zhoumeng <zhoumeng35@huawei.com> Co-committed-by: zhoumeng <zhoumeng35@huawei.com>
This commit is contained in:
parent
698057ca30
commit
f3b45a2c45
1202
docs/elb/umn/ALL_META.TXT.json
Normal file
1202
docs/elb/umn/ALL_META.TXT.json
Normal file
File diff suppressed because it is too large
Load Diff
1082
docs/elb/umn/CLASS.TXT.json
Normal file
1082
docs/elb/umn/CLASS.TXT.json
Normal file
File diff suppressed because it is too large
Load Diff
3
docs/elb/umn/PARAMETERS.txt
Normal file
3
docs/elb/umn/PARAMETERS.txt
Normal file
@ -0,0 +1,3 @@
|
||||
version=""
|
||||
language="en-us"
|
||||
type=""
|
||||
29
docs/elb/umn/elb_faq_0000.html
Normal file
29
docs/elb/umn/elb_faq_0000.html
Normal file
@ -0,0 +1,29 @@
|
||||
<a name="elb_faq_0000"></a><a name="elb_faq_0000"></a>
|
||||
|
||||
<h1 class="topictitle1">FAQ</h1>
|
||||
<div id="body1434096191980"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0200.html">Popular Questions</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0212.html">ELB Use</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0201.html">Load Balancers</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0202.html">Listeners</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0203.html">Backend Servers</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0204.html">Health Checks</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0170.html">Obtaining Source IP Addresses</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0180.html">HTTP/HTTPS Listeners</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0190.html">Sticky Sessions</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0205.html">Certificates</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0001.html
Normal file
11
docs/elb/umn/elb_faq_0001.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0001"></a><a name="elb_faq_0001"></a>
|
||||
|
||||
<h1 class="topictitle1">When Is a Backend Server Considered Healthy?</h1>
|
||||
<div id="body1576051097345"><p id="elb_faq_0001__p1380411575918">When a backend server is associated with a load balancer for the first time, the backend server is considered healthy after one health check. After this, the server is considered healthy only after the maximum number of health checks has been attempted.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
41
docs/elb/umn/elb_faq_0024.html
Normal file
41
docs/elb/umn/elb_faq_0024.html
Normal file
@ -0,0 +1,41 @@
|
||||
<a name="elb_faq_0024"></a><a name="elb_faq_0024"></a>
|
||||
|
||||
<h1 class="topictitle1">How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?</h1>
|
||||
<div id="body8662426"><div class="section" id="elb_faq_0024__section53210693319"><h4 class="sectiontitle">How UDP Health Checks Work</h4><p id="elb_faq_0024__p594001812332">UDP is a connectionless protocol. A UDP health check is implemented as follows:</p>
|
||||
</div>
|
||||
<ul id="elb_faq_0024__ul118961151152216"><li id="elb_faq_0024__li1896125120229">The health check node sends an ICMP request to the backend server based on the health check configuration.<ul id="elb_faq_0024__ul202464854211"><li id="elb_faq_0024__li624114811423">If the health check node receives an ICMP reply from the backend <span id="elb_faq_0024__text1730504215713">server</span>, it considers the backend server healthy and continues the health check.</li><li id="elb_faq_0024__li1644615164212">If the health check node does not receive an ICMP reply from the backend <span id="elb_faq_0024__text166053611810">server</span>, it considers the backend server unhealthy.</li></ul>
|
||||
</li><li id="elb_faq_0024__li14896651122210">After receiving the ICMP reply, the health check node sends a UDP probe packet to the backend <span id="elb_faq_0024__text279319651018">server</span>.<ul id="elb_faq_0024__ul1611085454217"><li id="elb_faq_0024__li211065416424">If the health check node receives an ICMP Port Unreachable message from the backend <span id="elb_faq_0024__text73403324109">server</span> within the timeout duration, the backend server is considered unhealthy.</li><li id="elb_faq_0024__li9969105615423">If the health check node does not receive an ICMP Port Unreachable message from the backend <span id="elb_faq_0024__text02196153811">server</span> within the timeout duration, the backend server is considered healthy.</li></ul>
|
||||
</li></ul>
|
||||
<p id="elb_faq_0024__p20843183062817">When you use UDP for health checks, retain default parameter settings.</p>
|
||||
<div class="section" id="elb_faq_0024__section1651117513338"><h4 class="sectiontitle">Troubleshooting</h4><p id="elb_faq_0024__p1290856173312">If the backend server is unhealthy, use either of the following methods to locate the fault:</p>
|
||||
</div>
|
||||
<ul id="elb_faq_0024__ul3578201317447"><li id="elb_faq_0024__li257910131449">Check whether the timeout duration is too short.<p id="elb_faq_0024__p1247644393018"><a name="elb_faq_0024__li257910131449"></a><a name="li257910131449"></a>One possible cause is that the ICMP Echo Reply or ICMP Port Unreachable message returned by the backend <span id="elb_faq_0024__text11635124113813">server</span> does not reach the health check node within the timeout duration. As a result, the health check result is inaccurate.</p>
|
||||
<p id="elb_faq_0024__p747610439305">It is recommended that you change the timeout duration to a larger value.</p>
|
||||
<p id="elb_faq_0024__p18541632193414">UDP health checks are different from other health checks. If the health check timeout duration is too short, the health check result of the backend <span id="elb_faq_0024__text13586581185">server</span> frequently toggles back and forth between <strong id="elb_faq_0024__b44605421747">Healthy</strong> and <strong id="elb_faq_0024__b1292844517410">Unhealthy</strong>.</p>
|
||||
</li><li id="elb_faq_0024__li1957901310440">Check whether the backend <span id="elb_faq_0024__text257519920910">server</span> restricts the rate at which ICMP messages are generated.</li></ul>
|
||||
<p id="elb_faq_0024__p1647644393017">For Linux servers, run the following commands to query the rate limit and rate mask:</p>
|
||||
<pre class="screen" id="elb_faq_0024__screen4768112823913">sysctl -q net.ipv4.icmp_ratelimit</pre>
|
||||
<p id="elb_faq_0024__p1811918431964">The default rate limit is <strong id="elb_faq_0024__b842352706193458">1000</strong>.</p>
|
||||
<pre class="screen" id="elb_faq_0024__screen7265195210611">sysctl -q net.ipv4.icmp_ratemask</pre>
|
||||
<p id="elb_faq_0024__p52451533713">The default rate mask is <strong id="elb_faq_0024__b274412535">6168</strong>.</p>
|
||||
<p id="elb_faq_0024__p74763433302">If the returned value of the first command is the default value or <strong id="elb_faq_0024__b842352706103935">0</strong>, run the following command to remove the rate limit of Port Unreachable messages:</p>
|
||||
<pre class="screen" id="elb_faq_0024__screen187541426251">sysctl -w net.ipv4.icmp_ratemask=6160</pre>
|
||||
<p id="elb_faq_0024__p178268102918">For more information, see the <em id="elb_faq_0024__i842352697103837">Linux Programmer's Manual</em>. On the Linux CLI, run the following command to display the manual:</p>
|
||||
<pre class="screen" id="elb_faq_0024__screen58180101999">man 7 icmp</pre>
|
||||
<p id="elb_faq_0024__p184947035312">Alternatively, visit <a href="http://man7.org/linux/man-pages/man7/icmp.7.html" target="_blank" rel="noopener noreferrer">http://man7.org/linux/man-pages/man7/icmp.7.html</a>.</p>
|
||||
<div class="note" id="elb_faq_0024__note472385163512"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0024__p07231750353">Once the rate limit is lifted, the number of ICMP Port Unreachable messages on the backend server will not be limited.</p>
|
||||
</div></div>
|
||||
<div class="section" id="elb_faq_0024__section1386314212366"><h4 class="sectiontitle">Precautions</h4><p id="elb_faq_0024__p07313917363">Note the following when you configure UDP health checks:</p>
|
||||
</div>
|
||||
<ul id="elb_faq_0024__en-us_topic_0044589572_ul39655260125151"><li id="elb_faq_0024__en-us_topic_0044589572_li21353022125151">UDP health checks use ping packets to check the health of the backend <span id="elb_faq_0024__text4243511499722">server</span>. To ensure smooth transmission of these packets, ensure that ICMP is enabled on the backend <span id="elb_faq_0024__text9486641229734">server</span> by performing the following:<p id="elb_faq_0024__en-us_topic_0044589572_p57959472125151">Log in to the <span id="elb_faq_0024__text2377681409836">server</span> and run the following command as user <strong id="elb_faq_0024__b8423527069814">root</strong>:</p>
|
||||
<p id="elb_faq_0024__en-us_topic_0044589572_p51873203125151"><strong id="elb_faq_0024__en-us_topic_0044589572_b65813485141827">cat /proc/sys/net/ipv4/icmp_echo_ignore_all</strong></p>
|
||||
<ul id="elb_faq_0024__ul5991332115413"><li id="elb_faq_0024__li5383645415427">If the returned value is <strong id="elb_faq_0024__b2702449915427">1</strong>, ICMP is disabled.</li><li id="elb_faq_0024__li234898115413">If the returned value is <strong id="elb_faq_0024__b46864838191253">0</strong>, ICMP is enabled.</li></ul>
|
||||
</li><li id="elb_faq_0024__en-us_topic_0044589572_li33275046125151">The health check result may be different from the actual health of the backend server.<p id="elb_faq_0024__en-us_topic_0044589572_p31039959125151"><a name="elb_faq_0024__en-us_topic_0044589572_li33275046125151"></a><a name="en-us_topic_0044589572_li33275046125151"></a>If the backend server runs Linux, the rate of ICMP packets may be limited due to Linux's defense against ping flood attacks when there is a large number of concurrent requests. In this case, if a service exception occurs, the load balancer will not receive error message <strong id="elb_faq_0024__b84235270615853">port XX unreachable</strong> and will consider the health check to be successful. As a result, there is an inconsistency between the health check result and the actual server health.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0204.html">Health Checks</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
15
docs/elb/umn/elb_faq_0038.html
Normal file
15
docs/elb/umn/elb_faq_0038.html
Normal file
@ -0,0 +1,15 @@
|
||||
<a name="elb_faq_0038"></a><a name="elb_faq_0038"></a>
|
||||
|
||||
<h1 class="topictitle1">How Does ELB Distribute Traffic?</h1>
|
||||
<div id="body8662426"><p id="elb_faq_0038__en-us_topic_0100578533_p42330367111657">ELB uses FullNAT to forward the incoming traffic. For load balancing at Layer 4, LVS forwards the incoming traffic to backend servers directly. For load balancing at Layer 7, LVS forwards the incoming traffic to Nginx, which then forwards the traffic to backend servers.</p>
|
||||
<div class="note" id="elb_faq_0038__note1646334617596"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0038__p114641546175911">In FullNAT, LVS translates source IP addresses and destination IP addresses of the clients.</p>
|
||||
</div></div>
|
||||
<div class="fignone" id="elb_faq_0038__en-us_topic_0100578533_fig41212694173712"><span class="figcap"><b>Figure 1 </b>Load balancing at Layer 4</span><br><span><img id="elb_faq_0038__en-us_topic_0100578533_image49893921173712" src="en-us_image_0168438373.jpg"></span></div>
|
||||
<div class="fignone" id="elb_faq_0038__en-us_topic_0100578533_fig15312593173922"><span class="figcap"><b>Figure 2 </b>Load balancing at Layer 7</span><br><span><img id="elb_faq_0038__en-us_topic_0100578533_image32360488173922" src="en-us_image_0168438378.jpg"></span></div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0201.html">Load Balancers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
15
docs/elb/umn/elb_faq_0039.html
Normal file
15
docs/elb/umn/elb_faq_0039.html
Normal file
@ -0,0 +1,15 @@
|
||||
<a name="elb_faq_0039"></a><a name="elb_faq_0039"></a>
|
||||
|
||||
<h1 class="topictitle1">How Do I Check the Network Conditions of a Backend Server?</h1>
|
||||
<div id="body8662426"><ol id="elb_faq_0039__en-us_topic_0100578534_ol43143701174341"><li id="elb_faq_0039__en-us_topic_0100578534_li62098667174341">Verify that an IP address has been assigned to the server's primary NIC.<ol type="a" id="elb_faq_0039__en-us_topic_0100578534_ol58104270174422"><li id="elb_faq_0039__en-us_topic_0100578534_li26117718174419">Log in to the server. (An ECS is used as an example here.)</li><li id="elb_faq_0039__en-us_topic_0100578534_li63468792174419">Use <strong id="elb_faq_0039__en-us_topic_0100578534_b84235270614498">ifconfig</strong> or <strong id="elb_faq_0039__en-us_topic_0100578534_b842352706144912">ip address</strong> to view the IP address.<div class="note" id="elb_faq_0039__en-us_topic_0100578534_note46668364174530"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0039__en-us_topic_0100578534_p40184371174333">For Windows ECSs, use <strong id="elb_faq_0039__en-us_topic_0100578534_b842352706145011">ipconfig</strong> on the CLI.</p>
|
||||
</div></div>
|
||||
</li></ol>
|
||||
</li><li id="elb_faq_0039__en-us_topic_0100578534_li44262848174829">Ping the gateway of the subnet where the ECS resides to check for network connectivity.<ol type="a" id="elb_faq_0039__en-us_topic_0100578534_ol8442521174940"><li id="elb_faq_0039__en-us_topic_0100578534_li44715074174835">On the VPC details page, locate the subnet and view the gateway address in the <strong id="elb_faq_0039__b136011758174">Gateway</strong> column. Generally, the gateway address ends with <strong id="elb_faq_0039__b17295732101712">.1</strong>.</li><li id="elb_faq_0039__en-us_topic_0100578534_li234301174759">Ping the gateway from the ECS. If the gateway cannot be pinged, check the networks at Layer 2 and Layer 3.</li></ol>
|
||||
</li></ol>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
16
docs/elb/umn/elb_faq_0040.html
Normal file
16
docs/elb/umn/elb_faq_0040.html
Normal file
@ -0,0 +1,16 @@
|
||||
<a name="elb_faq_0040"></a><a name="elb_faq_0040"></a>
|
||||
|
||||
<h1 class="topictitle1">How Do I Check the Network Configuration of a Backend Server?</h1>
|
||||
<div id="body8662426"><ol id="elb_faq_0040__en-us_topic_0100578555_ol51835414175346"><li id="elb_faq_0040__en-us_topic_0100578555_li26028006175346">Check whether the security group of the server is correctly configured.<ol type="a" id="elb_faq_0040__en-us_topic_0100578555_ol15120255104222"><li id="elb_faq_0040__en-us_topic_0100578555_li8965360104233">On the server details page, view the security group.</li><li id="elb_faq_0040__li1256125092715">Check whether the security group rules allow access from the corresponding IP address range.<ul id="elb_faq_0040__ul18999115652214"><li id="elb_faq_0040__li2330162013231">Dedicated load balancers: Check whether the security group containing the backend server has inbound rules to allow traffic from the VPC where the load balancer works. If traffic is not allowed, add an inbound rule to allow traffic from the VPC to the backend server.</li><li id="elb_faq_0040__li613813371268"><span id="elb_faq_0040__ph988272093916">Shared</span> load balancers: Check whether the security group containing the backend server has inbound rules to allow traffic from the 100.125.0.0/16. If traffic is not allowed, add an inbound rule to allow traffic from 100.125.0.0/16<span id="elb_faq_0040__ph1944315364202"></span> to the backend server.</li></ul>
|
||||
<div class="caution" id="elb_faq_0040__note888257101120"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0040__en-us_topic_0052569751_ul6236111617482"><li id="elb_faq_0040__en-us_topic_0052569751_li9236141624819"><span id="elb_faq_0040__en-us_topic_0052569751_ph5236916144812">Shared</span> load balancers: If <strong id="elb_faq_0040__en-us_topic_0052569751_b64011211441">Obtain Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__en-us_topic_0052569751_ph3592063517">firewall</span> rules to allow traffic from 100.125.0.0/16<span id="elb_faq_0040__en-us_topic_0052569751_ph2236716134818"></span> and client IP addresses to backend servers.</li></ul>
|
||||
</div></div>
|
||||
</li></ol>
|
||||
</li><li id="elb_faq_0040__en-us_topic_0100578555_li2154564893111">Ensure that the network ACLfirewalls of the subnet where the server resides does not intercept the traffic.<p id="elb_faq_0040__en-us_topic_0100578555_p2017488793128"><a name="elb_faq_0040__en-us_topic_0100578555_li2154564893111"></a><a name="en-us_topic_0100578555_li2154564893111"></a>In the navigation pane of the VPC console, choose <strong id="elb_faq_0040__b855515395272">Access Control</strong> > <strong id="elb_faq_0040__b116901318153311">Firewalls</strong> and check whether the subnet allows traffic.</p>
|
||||
</li></ol>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
18
docs/elb/umn/elb_faq_0041.html
Normal file
18
docs/elb/umn/elb_faq_0041.html
Normal file
@ -0,0 +1,18 @@
|
||||
<a name="elb_faq_0041"></a><a name="elb_faq_0041"></a>
|
||||
|
||||
<h1 class="topictitle1">How Do I Check the Status of a Backend Server?</h1>
|
||||
<div id="body8662426"><ol id="elb_faq_0041__en-us_topic_0101328255_ol2879999611816"><li id="elb_faq_0041__en-us_topic_0101328255_li6248705311816">Verify that the applications on the backend server are enabled.<ol type="a" id="elb_faq_0041__en-us_topic_0101328255_ol4122204711912"><li id="elb_faq_0041__en-us_topic_0101328255_li6552894411916">Log in to the backend server. (An ECS is used as an example here.)</li><li id="elb_faq_0041__en-us_topic_0101328255_li3517118211943">Check the port status.<p id="elb_faq_0041__en-us_topic_0101328255_p568284811944"><a name="elb_faq_0041__en-us_topic_0101328255_li3517118211943"></a><a name="en-us_topic_0101328255_li3517118211943"></a><strong id="elb_faq_0041__en-us_topic_0101328255_b420613211943">netstat -ntpl</strong></p>
|
||||
<div class="note" id="elb_faq_0041__en-us_topic_0101328255_note26440757111028"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><div class="p" id="elb_faq_0041__en-us_topic_0101328255_p51410770111031">For Windows ECSs, use <strong id="elb_faq_0041__en-us_topic_0101328255_b842352706152848">netstat -ano</strong> on the CLI to view the port status or server software status.<div class="fignone" id="elb_faq_0041__en-us_topic_0101328255_fig4990866211124"><span class="figcap"><b>Figure 1 </b>Port status</span><br><span><img id="elb_faq_0041__en-us_topic_0101328255_image1606983511124" src="en-us_image_0168612036.jpg"></span></div>
|
||||
</div>
|
||||
</div></div>
|
||||
</li></ol>
|
||||
</li><li id="elb_faq_0041__en-us_topic_0101328255_li16052523112231">Check the network communication of the ECS.<p id="elb_faq_0041__en-us_topic_0101328255_p12721331114814"><a name="elb_faq_0041__en-us_topic_0101328255_li16052523112231"></a><a name="en-us_topic_0101328255_li16052523112231"></a>For example, if the ECS uses port 80, use <strong id="elb_faq_0041__en-us_topic_0101328255_b842352706153210">curl</strong> to check whether network connectivity is normal.</p>
|
||||
<p id="elb_faq_0041__p1711753185312"><span><img id="elb_faq_0041__image1711753125311" src="en-us_image_0238256358.jpg"></span></p>
|
||||
</li></ol>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0046.html
Normal file
11
docs/elb/umn/elb_faq_0046.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0046"></a><a name="elb_faq_0046"></a>
|
||||
|
||||
<h1 class="topictitle1">How Do I Check If Sticky Sessions Failed to Take Effect?</h1>
|
||||
<div id="body1537450788437"><ol id="elb_faq_0046__ol627910268405"><li id="elb_faq_0046__li0279112615402">Check whether sticky sessions are enabled for the backend server group. If sticky sessions are enabled, go to the next step.</li><li id="elb_faq_0046__li327913260407">Check the health check result of the backend server. If the health check result is <strong id="elb_faq_0046__b579774331811">Unhealthy</strong>, traffic is routed to other backend servers and sticky sessions become invalid.</li><li id="elb_faq_0046__li1727982616408">If you select the source IP hash algorithm, check whether the IP address of the request changes before the load balancer receives the request.</li><li id="elb_faq_0046__li122791326124013">If sticky sessions are enabled for an HTTP or HTTPS listener, check whether the request carries a cookie. If they are, check whether the cookie value changed (because load balancing at Layer 7 uses cookies to maintain sessions).</li></ol>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0190.html">Sticky Sessions</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0049.html
Normal file
11
docs/elb/umn/elb_faq_0049.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0049"></a><a name="elb_faq_0049"></a>
|
||||
|
||||
<h1 class="topictitle1">How Do I Check for Traffic Inconsistencies?</h1>
|
||||
<div id="body1537450788437"><p id="elb_faq_0049__p1693782873219">Check for failed requests on the clients, especially when <em id="elb_faq_0049__i842352697102856">4xx</em> status codes are returned. One possible cause is that the requests are not being routed to backend servers because ELB considers these requests abnormal.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0127.html">Service Performance and Load</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
13
docs/elb/umn/elb_faq_0050.html
Normal file
13
docs/elb/umn/elb_faq_0050.html
Normal file
@ -0,0 +1,13 @@
|
||||
<a name="elb_faq_0050"></a><a name="elb_faq_0050"></a>
|
||||
|
||||
<h1 class="topictitle1">How Do I Check If Traffic Is Being Evenly Distributed?</h1>
|
||||
<div id="body1537450788438"><ol id="elb_faq_0050__ol7137172232919"><li id="elb_faq_0050__li31371522152912">Check whether sticky sessions are enabled. If sticky sessions are enabled and there are few clients, traffic may be unevenly distributed.</li><li id="elb_faq_0050__li1113872252910">Check the health of backend servers, especially those whose health changes over time. If a backend server is <strong id="elb_faq_0050__b84235270612021">Unhealthy</strong> or its health switches between <strong id="elb_faq_0050__b62279156712054">Healthy</strong> and <strong id="elb_faq_0050__b196399472312054">Unhealthy</strong>, traffic is unbalanced.</li><li id="elb_faq_0050__li15138222122920">Check whether the <strong id="elb_faq_0050__b84235270614950">Source IP hash</strong> algorithm is used. If the algorithm is used, requests sent from the same IP address are routed to the same backend server, resulting in unbalanced traffic.</li><li id="elb_faq_0050__li513814222293">Check whether applications on the backend server use keepalive to maintain TCP persistent connections. If keepalive is used, traffic may be unbalanced because the number of requests on persistent connections is different.</li><li id="elb_faq_0050__li18138522192914">Check whether different weights are assigned to backend servers. The traffic varies according to the weights.</li></ol>
|
||||
<div class="note" id="elb_faq_0050__note1482118916346"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0050__p66213356328">Generally, in addition to the load balancing algorithm, factors that affect load balancing include connection type, session stickiness, and server weights.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0127.html">Service Performance and Load</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
13
docs/elb/umn/elb_faq_0052.html
Normal file
13
docs/elb/umn/elb_faq_0052.html
Normal file
@ -0,0 +1,13 @@
|
||||
<a name="elb_faq_0052"></a><a name="elb_faq_0052"></a>
|
||||
|
||||
<h1 class="topictitle1">What Do I Do If a Load Balancer Fails a Stress Test?</h1>
|
||||
<div id="body1537450788438"><ol id="elb_faq_0052__ol140474553419"><li id="elb_faq_0052__li640464543416">Check the load of backend servers. If their vCPU usage reaches 100%, applications may have performance bottlenecks.</li><li id="elb_faq_0052__li1640419457346">Check the incoming traffic. If burst traffic exceeds the bandwidth set for the EIP, a large number of packets will be lost and requests will not be responded to, thereby affecting the load balancer's performance.<div class="note" id="elb_faq_0052__note87571310132318"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0052__p5757610192318">If burst traffic exceeds the available bandwidth, it does not mean that the bandwidth is fully used. In this case, you need perform further operations to locate the fault or increase the bandwidth.</p>
|
||||
</div></div>
|
||||
</li><li id="elb_faq_0052__li791993451610">Check the number of short connections in the <strong id="elb_faq_0052__b1531518182445">time_wait</strong> state on the clients. One possible cause is that there are insufficient client ports.</li><li id="elb_faq_0052__li1140474503412">The listening queue backlog of the backend servers may be full. If this happens, the backend server will not respond to SYN ACK packets, and the client will time out. You can increase the maximum allowed of the backlog by adjusting the <strong id="elb_faq_0052__b8423527061595">net.core.somaxconn</strong> parameter.</li></ol>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0127.html">Service Performance and Load</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
12
docs/elb/umn/elb_faq_0060.html
Normal file
12
docs/elb/umn/elb_faq_0060.html
Normal file
@ -0,0 +1,12 @@
|
||||
<a name="elb_faq_0060"></a><a name="elb_faq_0060"></a>
|
||||
|
||||
<h1 class="topictitle1">Can ELB Be Used Separately?</h1>
|
||||
<div id="body1525858887209"><p id="elb_faq_0060__p18255193114219">ELB cannot be used alone.</p>
|
||||
<p id="elb_faq_0060__p8060118">ELB is a service that distributes incoming traffic across servers and is generally used together with the ECS or BMS service.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0211.html">ELB Functionality</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0062.html
Normal file
11
docs/elb/umn/elb_faq_0062.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0062"></a><a name="elb_faq_0062"></a>
|
||||
|
||||
<h1 class="topictitle1">Can I Adjust the Number of Backend Servers When a Load Balancer is Running?</h1>
|
||||
<div id="body1525921979190"><p id="elb_faq_0062__p8060118">You can adjust the number of backend servers associated with a load balancer at any time. You can also change the type of backend servers according to your service needs. To ensure service stability, ensure that health checks are normal and that at least one healthy backend server is associated with the load balancer.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0211.html">ELB Functionality</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
12
docs/elb/umn/elb_faq_0064.html
Normal file
12
docs/elb/umn/elb_faq_0064.html
Normal file
@ -0,0 +1,12 @@
|
||||
<a name="elb_faq_0064"></a><a name="elb_faq_0064"></a>
|
||||
|
||||
<h1 class="topictitle1">Can Backend Servers Run Different OSs?</h1>
|
||||
<div id="body1437669816815"><p id="elb_faq_0064__p2957467704537">Yes.</p>
|
||||
<p id="elb_faq_0064__p6484550904537">ELB does not restrict OSs of backend servers as long as applications on these servers are the same and the data is consistent. However, it is recommended that you install the same OS on backend servers to simplify management.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0211.html">ELB Functionality</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0072.html
Normal file
11
docs/elb/umn/elb_faq_0072.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0072"></a><a name="elb_faq_0072"></a>
|
||||
|
||||
<h1 class="topictitle1">How Can I Create Server Certificates and CA Certificates?</h1>
|
||||
<div id="body1568692772111"><p id="elb_faq_0072__p18155131874711">Refer to <a href="en_us_elb_03_0006.html">Mutual Authentication</a> to create server certificates and CA certificates. Generally, only backend servers need to be authenticated. You only need to configure server certificates.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0205.html">Certificates</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0084.html
Normal file
11
docs/elb/umn/elb_faq_0084.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0084"></a><a name="elb_faq_0084"></a>
|
||||
|
||||
<h1 class="topictitle1">Does ELB Have Restrictions on the File Upload Speed and Size?</h1>
|
||||
<div id="body1571991977241"><ul id="elb_faq_0084__ul144379478419"><li id="elb_faq_0084__li115851925451">ELB has no restrictions on the file upload speed on the clients. However, the bandwidth may limit the upload speed.</li><li id="elb_faq_0084__li14306142151514">For HTTP or HTTPS listeners, the maximum file size is 10 GB. However, TCP or UDP listeners have no limit on the file size.</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0202.html">Listeners</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
12
docs/elb/umn/elb_faq_0085.html
Normal file
12
docs/elb/umn/elb_faq_0085.html
Normal file
@ -0,0 +1,12 @@
|
||||
<a name="elb_faq_0085"></a><a name="elb_faq_0085"></a>
|
||||
|
||||
<h1 class="topictitle1">What Types of Sticky Sessions Does ELB Support?</h1>
|
||||
<div id="body1437669816817"><p id="elb_faq_0085__p8292617145212">Dedicated load balancers: <strong id="elb_faq_0085__b230520591448">Source IP address</strong> and <strong id="elb_faq_0085__b1131715911446">Load balancer cookie</strong></p>
|
||||
<p id="elb_faq_0085__p528462741203"><span id="elb_faq_0085__ph15170164618279">Shared</span> load balancers: <strong id="elb_faq_0085__b3335228194515">Source IP address</strong>, <strong id="elb_faq_0085__b333113404510">Load balancer cookie</strong>, and <strong id="elb_faq_0085__b910418384459">Application cookie</strong></p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0190.html">Sticky Sessions</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
94
docs/elb/umn/elb_faq_0090.html
Normal file
94
docs/elb/umn/elb_faq_0090.html
Normal file
@ -0,0 +1,94 @@
|
||||
<a name="elb_faq_0090"></a><a name="elb_faq_0090"></a>
|
||||
|
||||
<h1 class="topictitle1">How Can I Obtain the IP Address of a Client?</h1>
|
||||
<div id="body1437669816817"><p id="elb_faq_0090__p126130261229">When you use ELB to route requests to backend servers, IP addresses of the clients will be translated by the ELB system. This FAQ provides the operations for obtaining the IP addresses of the clients.</p>
|
||||
<div class="section" id="elb_faq_0090__section13394124610518"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_faq_0090__ul104521513161519"><li id="elb_faq_0090__li13452113161512">If Network Address Translation (NAT) is used, you cannot obtain the IP addresses of the clients.</li><li id="elb_faq_0090__li9274171501517">If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.</li><li id="elb_faq_0090__li9335359112219">If <strong id="elb_faq_0090__b352118212323">Obtain Client IP Address</strong> is enabled for TCP or UDP listeners, a cloud server cannot be used as a backend server and a client at the same time. </li><li id="elb_faq_0090__li983412419371">By default, the <strong id="elb_faq_0090__b149753488323">Obtain Client IP Address</strong> function is enabled for TCP and UDP listeners of dedicated load balancers and cannot be disabled.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="elb_faq_0090__section12598161410315"><a name="elb_faq_0090__section12598161410315"></a><a name="section12598161410315"></a><h4 class="sectiontitle">Layer 7 Load Balancing</h4><p id="elb_faq_0090__p1023417204310">Configure the application server and obtain the IP address of a client from the HTTP header.</p>
|
||||
</div>
|
||||
<p id="elb_faq_0090__p831417121548">The real IP address is placed in the X-Forwarded-For header field by the load balancer in the following format:</p>
|
||||
<pre class="screen" id="elb_faq_0090__screen1187691785410">X-Forwarded-For: <em id="elb_faq_0090__i1750233911017">IP address of the client</em>,<em id="elb_faq_0090__i1750311398014">Proxy server 1-IP address</em>,<em id="elb_faq_0090__i5504183920016">Proxy server 2-IP address</em>,...</pre>
|
||||
<p id="elb_faq_0090__p20617125125319">If you use this method, the first IP address obtained is the IP address of the client.</p>
|
||||
<p id="elb_faq_0090__p19756101917416"><strong id="elb_faq_0090__b10993195705216">Apache Server</strong></p>
|
||||
<ol id="elb_faq_0090__ol6308148164116"><li id="elb_faq_0090__li12308194814416">Install Apache 2.4.<p id="elb_faq_0090__p730884864117"><a name="elb_faq_0090__li12308194814416"></a><a name="li12308194814416"></a>For example, if CentOS 7.5 is used as the OS, run the following command to install the software:</p>
|
||||
<pre class="screen" id="elb_faq_0090__screen179405819412">yum install httpd</pre>
|
||||
</li><li id="elb_faq_0090__li119211618194213">Add the following content to the end of Apache configuration file <strong id="elb_faq_0090__b17513185075513">/etc/httpd/conf/httpd.conf</strong>:<pre class="screen" id="elb_faq_0090__screen777611144433">LoadModule remoteip_module modules/mod_remoteip.so
|
||||
RemoteIPHeader X-Forwarded-For
|
||||
RemoteIPInternalProxy <strong id="elb_faq_0090__b1977615149432"><em id="elb_faq_0090__i1777601412436">100.125.0.0/16</em></strong></pre>
|
||||
<div class="fignone" id="elb_faq_0090__fig1553761545210"><span class="figcap"><b>Figure 1 </b>Content to be added</span><br><span><img id="elb_faq_0090__image1368125117439" src="en-us_image_0174899056.jpg"></span></div>
|
||||
<div class="note" id="elb_faq_0090__note135510197505"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p11969135614319">Add the IP address range of the proxy server after <strong id="elb_faq_0090__b110010178155">RemoteIPInternalProxy</strong>.</p>
|
||||
<ul id="elb_faq_0090__ul5985165818319"><li id="elb_faq_0090__li49865581436"><span id="elb_faq_0090__ph1911810238">Shared</span> load balancers: 100.125.0.0/16<span id="elb_faq_0090__ph1820812303110"></span> and the IP address range used by the AAD service. Load balancers use IP addresses in 100.125.0.0/16 to communicate with backend servers, and there are no security risks. Use commas (,) to separate multiple entries.</li><li id="elb_faq_0090__li6194337848">Dedicated load balancers: CIDR block of the subnet where the load balancer resides</li></ul>
|
||||
</div></div>
|
||||
</li><li id="elb_faq_0090__li10895421174213">Change the log output format in the Apache configuration file to the following (<strong id="elb_faq_0090__b1311681216319">%a</strong> indicates the source IP address):<pre class="screen" id="elb_faq_0090__screen13565739124411">LogFormat "<em id="elb_faq_0090__i18199122934118"><strong id="elb_faq_0090__b5762132774111">%</strong><strong id="elb_faq_0090__b194131533162710">a</strong></em> %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined</pre>
|
||||
</li><li id="elb_faq_0090__li1851619394515">Restart Apache.<pre class="screen" id="elb_faq_0090__screen108061723195117">systemctl restart httpd</pre>
|
||||
</li><li id="elb_faq_0090__li156661737145114">Obtain the actual IP address of the client from the httpd access logs.</li></ol>
|
||||
<p id="elb_faq_0090__p6714439135314"><strong id="elb_faq_0090__b577241918535">Nginx Server</strong></p>
|
||||
<p id="elb_faq_0090__p155321736613">For example, if CentOS 7.5 is used as the OS, run the following command to install the software:</p>
|
||||
<ol id="elb_faq_0090__ol7358205916533"><li id="elb_faq_0090__li0358155914534">Run the following commands to install http_realip_module:<pre class="screen" id="elb_faq_0090__screen1882810131546">yum -y install gcc pcre pcre-devel zlib zlib-devel openssl openssl-devel
|
||||
wget http://nginx.org/download/nginx-1.17.0.tar.gz
|
||||
tar zxvf nginx-1.17.0.tar.gz
|
||||
cd nginx-1.17.0
|
||||
./configure --prefix=/path/server/nginx --with-http_stub_status_module --without-http-cache --with-http_ssl_module --with-http_realip_module
|
||||
make
|
||||
make install</pre>
|
||||
</li><li id="elb_faq_0090__li157133719579">Run the following command to open the <strong id="elb_faq_0090__b284014426589">nginx.conf</strong> file:<pre class="screen" id="elb_faq_0090__screen168161722125710">vi /path/server/nginx/conf/nginx.conf</pre>
|
||||
</li><li id="elb_faq_0090__li08471939155717">Add new fields and information to the end of the following configuration information:<p id="elb_faq_0090__p884763985718"><a name="elb_faq_0090__li08471939155717"></a><a name="li08471939155717"></a>Add the following information under <strong id="elb_faq_0090__b1184175194119">http</strong> or <strong id="elb_faq_0090__b161003844114">server</strong>:</p>
|
||||
<pre class="screen" id="elb_faq_0090__screen114715217570">set_real_ip_from <em id="elb_faq_0090__i486310577577"><strong id="elb_faq_0090__b3978993586">100.125.0.0/16</strong></em>;
|
||||
real_ip_header X-Forwarded-For;</pre>
|
||||
<div class="fignone" id="elb_faq_0090__fig5645153575820"><span class="figcap"><b>Figure 2 </b>Adding information</span><br><span><img id="elb_faq_0090__image117512241589" src="en-us_image_0174914269.jpg"></span></div>
|
||||
<div class="note" id="elb_faq_0090__note627612152062"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p66517423613">Add the IP address range of the proxy server after <strong id="elb_faq_0090__b19751172824110">set_real_ip_from <IP_address></strong>.</p>
|
||||
<ul id="elb_faq_0090__ul382910413719"><li id="elb_faq_0090__li13829341171"><span id="elb_faq_0090__ph17309135819617">Shared</span> load balancers: 100.125.0.0/16<span id="elb_faq_0090__ph5282205074611"></span> and the IP address range used by the AAD service. Load balancers use IP addresses in 100.125.0.0/16<span id="elb_faq_0090__ph1317615314424"></span> to communicate with backend servers, and there are no security risks. Use commas (,) to separate multiple entries.</li></ul>
|
||||
<ul id="elb_faq_0090__ul410015111674"><li id="elb_faq_0090__li14373314679">Dedicated load balancers: CIDR block of the subnet where the load balancer resides</li></ul>
|
||||
</div></div>
|
||||
</li><li id="elb_faq_0090__li641018965916">Start Nginx.<pre class="screen" id="elb_faq_0090__screen578563035916">/path/server/nginx/sbin/nginx</pre>
|
||||
</li><li id="elb_faq_0090__li148240105591">Obtain the actual IP address of the client from the Nginx access logs.<pre class="screen" id="elb_faq_0090__screen8367134511812">cat /path/server/nginx/logs/access.log</pre>
|
||||
</li></ol>
|
||||
<p id="elb_faq_0090__p480771725215"><strong id="elb_faq_0090__b16433239142610">Tomcat Servers</strong></p>
|
||||
<p id="elb_faq_0090__p1680781711526">In the following operations, the Tomcat installation path is <strong id="elb_faq_0090__b944410301920">/usr/tomcat/tomcat8/</strong>.</p>
|
||||
<ol id="elb_faq_0090__ol78072171526"><li id="elb_faq_0090__li2497621114416">Log in to a server on which Tomcat is installed.</li><li id="elb_faq_0090__li20249121115120">Check whether Tomcat is running properly.<pre class="screen" id="elb_faq_0090__screen44802295146">ps -ef|grep tomcat
|
||||
netstat -anpt|grep java</pre>
|
||||
<div class="fignone" id="elb_faq_0090__fig4744183111150"><span class="figcap"><b>Figure 3 </b>Tomcat running properly</span><br><span><img id="elb_faq_0090__image12991039151611" src="en-us_image_0276143526.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li19727103382213">Modify <strong id="elb_faq_0090__b1571331418">className="org.apache.catalina.valves.AccessLogValve"</strong> in the <strong id="elb_faq_0090__b665121219558">server.xml</strong> file as follows:<pre class="screen" id="elb_faq_0090__screen129226593219">vim /usr/tomcat/tomcat8/conf/server.xml</pre>
|
||||
<pre class="screen" id="elb_faq_0090__screen19630859193119"><Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
|
||||
prefix="localhost_access_log." suffix=".txt"
|
||||
pattern="%{X-FORWARDED-FOR}i %l %u %t %r %s %b %D %q %{User-Agent}i %T" resolveHosts="false" /></pre>
|
||||
<div class="fignone" id="elb_faq_0090__fig2631165993110"><span class="figcap"><b>Figure 4 </b>Example configuration</span><br><span><img id="elb_faq_0090__image1863114595314" src="en-us_image_0276220702.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li10807317205216">Restart the Tomcat service.<pre class="screen" id="elb_faq_0090__screen1289953143813">cd /usr/tomcat/tomcat8/bin && sh shutdown.sh && sh startup.sh</pre>
|
||||
<p id="elb_faq_0090__p7855124164517"><strong id="elb_faq_0090__b1160153111279">/usr/tomcat/tomcat8/</strong> is where Tomcat is installed. Change it based on site requirements.</p>
|
||||
<div class="fignone" id="elb_faq_0090__fig109361744202020"><span class="figcap"><b>Figure 5 </b>Restarting the Tomcat service</span><br><span><img id="elb_faq_0090__image1537214114202" src="en-us_image_0276225173.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li52307461589">View the latest logs.<p id="elb_faq_0090__p6782174619819"><a name="elb_faq_0090__li52307461589"></a><a name="li52307461589"></a>As highlighted in the following figure, IP addresses that are not in the IP address range starting with 100.125 are the source IP addresses.</p>
|
||||
<pre class="screen" id="elb_faq_0090__screen5699423179">cd /usr/tomcat/tomcat8/logs/
|
||||
cat localhost_access_log..2021-11-29.txt</pre>
|
||||
<p id="elb_faq_0090__p1499318356184">In this command, <strong id="elb_faq_0090__b1309101394310">localhost_access_log..2021-11-29.txt</strong> indicates the log path of the current day. Change it based on site requirements.</p>
|
||||
<div class="fignone" id="elb_faq_0090__fig9930423101711"><span class="figcap"><b>Figure 6 </b>Querying the source IP address</span><br><span><img id="elb_faq_0090__image360791441717" src="en-us_image_0276223899.png"></span></div>
|
||||
</li></ol>
|
||||
<p id="elb_faq_0090__p16107922101012">Windows Server with IIS Deployed</p>
|
||||
<p id="elb_faq_0090__p68600531213">The following uses Windows Server 2012 with IIS7 as an example to describe how to obtain the source IP address.</p>
|
||||
<ol id="elb_faq_0090__ol610718229101"><li id="elb_faq_0090__li76432018259">Download and install IIS.</li><li id="elb_faq_0090__li91351915183019">Download the <strong id="elb_faq_0090__b14943951164816">F5XForwardedFor.dll</strong> plug-in and copy the plug-ins in the <strong id="elb_faq_0090__b622893114919">x86</strong> and <strong id="elb_faq_0090__b8309153684912">x64</strong> directories to a directory for which IIS has the access permission, for example, <strong id="elb_faq_0090__b1610019581407">C:\F5XForwardedFor2008</strong>.</li><li id="elb_faq_0090__li656010311115">Open the Server Manager and choose <strong id="elb_faq_0090__b71521450114319">Modules</strong> > <strong id="elb_faq_0090__b4123165611432">Configure Native Modules</strong>.<div class="fignone" id="elb_faq_0090__fig10558133715"><span class="figcap"><b>Figure 7 </b>Selecting modules</span><br><span><img id="elb_faq_0090__image555920581104" src="en-us_image_0267429969.png"></span></div>
|
||||
<div class="fignone" id="elb_faq_0090__fig1274418810319"><span class="figcap"><b>Figure 8 </b>Configure Native Modules</span><br><span><img id="elb_faq_0090__image19181513320" src="en-us_image_0267431325.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li158981131057">Click <strong id="elb_faq_0090__b10305101117465">Register</strong> to register the x86 and x64 plug-ins.<div class="fignone" id="elb_faq_0090__fig1889691316517"><span class="figcap"><b>Figure 9 </b>Registering plug-ins</span><br><span><img id="elb_faq_0090__image8335241059" src="en-us_image_0267432483.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li14440312814">In the <strong id="elb_faq_0090__b104651358134613">Modules</strong> dialog box, verify that the registered plug-ins are displayed in the list.<div class="fignone" id="elb_faq_0090__fig164424311181"><span class="figcap"><b>Figure 10 </b>Confirming the registration</span><br><span><img id="elb_faq_0090__image14574191416814" src="en-us_image_0267434399.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li2088319001410">Select <strong id="elb_faq_0090__b1076244794818">ISAPI Filters</strong> on the Server Manager homepage and authorize two plug-ins to run ISAPI and CGI extensions.<div class="fignone" id="elb_faq_0090__fig1288010019142"><span class="figcap"><b>Figure 11 </b>Adding authorization</span><br><span><img id="elb_faq_0090__image121471154181314" src="en-us_image_0267440227.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li1522516511177">Select <strong id="elb_faq_0090__b97915442492">ISAPI and CGI Restriction</strong> to set the execution permission for the two plug-ins.<div class="fignone" id="elb_faq_0090__fig4223651171710"><span class="figcap"><b>Figure 12 </b>Allowing the plug-ins to execute</span><br><span><img id="elb_faq_0090__image18752134415175" src="en-us_image_0267442311.png"></span></div>
|
||||
</li><li id="elb_faq_0090__li16707014261">Click <strong id="elb_faq_0090__b8679927125015">Restart</strong> on the homepage to restart IIS. The configuration will take effect after the restart.<div class="fignone" id="elb_faq_0090__fig116681600263"><span class="figcap"><b>Figure 13 </b>Restarting IIS</span><br><span><img id="elb_faq_0090__image8470105182515" src="en-us_image_0267446611.png"></span></div>
|
||||
</li></ol>
|
||||
<div class="section" id="elb_faq_0090__section867518427319"><h4 class="sectiontitle">Layer 4 Load Balancing</h4><p id="elb_faq_0090__p10578835171913"></p>
|
||||
<p id="elb_faq_0090__p1337010443011">For load balancing at Layer 4 (TCP or UDP listeners), use either of the following methods to obtain the real IP address of a client:</p>
|
||||
<ul id="elb_faq_0090__ul3140135223013"><li id="elb_faq_0090__li13140155233012"><strong id="elb_faq_0090__b6980112313279">Method 1 (for TCP or UDP listeners)</strong>: Enable the function of obtaining IP addresses of the clients.<ol id="elb_faq_0090__ol730222417346"><li id="elb_faq_0090__li330222433410">Perform the following steps to enable the function:<ol type="a" id="elb_faq_0090__ol16390953185514"><li id="elb_faq_0090__li677391520332">Log in to the management console.</li><li id="elb_faq_0090__li675519100420">In the upper left corner of the page, click <span><img id="elb_faq_0090__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_faq_0090__li335918093210">Click <strong id="elb_faq_0090__b1662070101">Service List</strong>. Under <strong id="elb_faq_0090__b2034119728"><span id="elb_faq_0090__ph321897927">Network</span></strong>, click <strong id="elb_faq_0090__b1837452777">Elastic Load Balance</strong>.</li><li id="elb_faq_0090__li1379615339436">In the load balancer list, click the name of the load balancer.</li><li id="elb_faq_0090__li475294174319">Click <strong id="elb_faq_0090__b1638472470">Listeners</strong>.<ul id="elb_faq_0090__ul124372032185517"><li id="elb_faq_0090__li543763255519">To add a listener, click <strong id="elb_faq_0090__b1377149182415">Add Listener</strong>.</li><li id="elb_faq_0090__li12437132115511">To modify a listener, locate the listener and click <span><img id="elb_faq_0090__image135811568494" src="en-us_image_0255608096.png"></span> on the right of its name.</li></ul>
|
||||
</li><li id="elb_faq_0090__li3100135715344">Enable <strong id="elb_faq_0090__b745821111385">Obtain Client IP Address</strong>.</li></ol>
|
||||
</li><li id="elb_faq_0090__li99008095116">Configure security groups, network ACLs, and OS and software security policies so that IP addresses of the clients can access these backend servers.<div class="caution" id="elb_faq_0090__note9310112602213"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0090__en-us_topic_0052569751_ul6236111617482"><li id="elb_faq_0090__en-us_topic_0052569751_li9236141624819"><span id="elb_faq_0090__en-us_topic_0052569751_ph5236916144812">Shared</span> load balancers: If <strong id="elb_faq_0090__en-us_topic_0052569751_b64011211441">Obtain Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0090__en-us_topic_0052569751_ph3592063517">firewall</span> rules to allow traffic from 100.125.0.0/16<span id="elb_faq_0090__en-us_topic_0052569751_ph2236716134818"></span> and client IP addresses to backend servers.</li></ul>
|
||||
</div></div>
|
||||
<div class="p" id="elb_faq_0090__p3759133762118"><div class="note" id="elb_faq_0090__note9800635192119"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p17774359172118">If you enable this function, a server cannot be used as both the client and the backend server. If the client and the backend server use the same server and the <strong id="elb_faq_0090__b1447693595">Obtain Client IP Address</strong> option is enabled, the backend server will think the packet from the client is sent by itself and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</li></ol>
|
||||
</li><li id="elb_faq_0090__li198181611346"><strong id="elb_faq_0090__b922631014271">Method 2 (for TCP listeners)</strong>: Configure the TOA plug-in.<p id="elb_faq_0090__p4144133031314">TCP listeners require the TOA plug-in to obtain real IP addresses. For details, see <a href="en-us_elb_06_0001.html">Configuring the TOA Module</a>.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0170.html">Obtaining Source IP Addresses</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0111.html
Normal file
11
docs/elb/umn/elb_faq_0111.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0111"></a><a name="elb_faq_0111"></a>
|
||||
|
||||
<h1 class="topictitle1">How Is WebSocket Used?</h1>
|
||||
<div id="body1563972092059"><p id="elb_faq_0111__p8060118">For HTTP listeners, unencrypted WebSocket (ws://) is supported by default. For HTTPS listeners, encrypted WebSocket (wss://) is supported by default.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0202.html">Listeners</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
12
docs/elb/umn/elb_faq_0112.html
Normal file
12
docs/elb/umn/elb_faq_0112.html
Normal file
@ -0,0 +1,12 @@
|
||||
<a name="elb_faq_0112"></a><a name="elb_faq_0112"></a>
|
||||
|
||||
<h1 class="topictitle1">Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Configured?</h1>
|
||||
<div id="body1575703621396"><p id="elb_faq_0112__p1294414571272">Each LVS node and Nginx node in the ELB system send detection packets to backend servers at the health check interval that you have specified for the backend server group.</p>
|
||||
<p id="elb_faq_0112__p8060118">During this period, backend servers receive multiple detection packets from LVS and Nginx nodes. This makes it seem like backend servers are receiving packets at intervals shorter than the specified health check interval.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0114.html
Normal file
11
docs/elb/umn/elb_faq_0114.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0114"></a><a name="elb_faq_0114"></a>
|
||||
|
||||
<h1 class="topictitle1">Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?</h1>
|
||||
<div id="body1566463545231"><p id="elb_faq_0114__p089414334718">ELB is deployed in clusters, and all nodes for request forwarding in the cluster send requests to backend servers at the same time. If the health check interval is too short, health checks are performed once every few seconds, and a large number of packets are sent to backend servers. To control the frequency of access to backend servers, change the health check interval by referring to <a href="en-us_topic_0162227063.html">Configuring a Health Check</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0204.html">Health Checks</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
13
docs/elb/umn/elb_faq_0118.html
Normal file
13
docs/elb/umn/elb_faq_0118.html
Normal file
@ -0,0 +1,13 @@
|
||||
<a name="elb_faq_0118"></a><a name="elb_faq_0118"></a>
|
||||
|
||||
<h1 class="topictitle1">Why Is There a Security Warning After a Certificate Is Configured?</h1>
|
||||
<div id="body1591066778258"><p id="elb_faq_0118__p157971251144618">The following may cause the Not Secure warning even after a certificate is configured:</p>
|
||||
<ul id="elb_faq_0118__ul0569141813473"><li id="elb_faq_0118__li5871122364718">The domain name used by the certificate is different from the domain name accessed by users. (If this is the case, check the domain name used the certificate to ensure that the domain names are the same or create a self-signed certificate.)</li><li id="elb_faq_0118__li17569418164712">SNI is configured, but the specified domain name is different from the one used by the certificate.</li><li id="elb_faq_0118__li1163891134818">The domain name level is inconsistent with the certificate level.</li></ul>
|
||||
<p id="elb_faq_0118__p8060118">If the problem persists, run the <strong id="elb_faq_0118__b744514119112">curl</strong> <em id="elb_faq_0118__i12667151215118">{Domain name}</em> command to locate the fault based on the error information returned by the system.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0180.html">HTTP/HTTPS Listeners</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
20
docs/elb/umn/elb_faq_0127.html
Normal file
20
docs/elb/umn/elb_faq_0127.html
Normal file
@ -0,0 +1,20 @@
|
||||
<a name="elb_faq_0127"></a><a name="elb_faq_0127"></a>
|
||||
|
||||
<h1 class="topictitle1">Service Performance and Load</h1>
|
||||
<div id="body1590575971687"><p id="elb_faq_0127__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0049.html">How Do I Check for Traffic Inconsistencies?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0050.html">How Do I Check If Traffic Is Being Evenly Distributed?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0052.html">What Do I Do If a Load Balancer Fails a Stress Test?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0212.html">ELB Use</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
19
docs/elb/umn/elb_faq_0170.html
Normal file
19
docs/elb/umn/elb_faq_0170.html
Normal file
@ -0,0 +1,19 @@
|
||||
<a name="elb_faq_0170"></a><a name="elb_faq_0170"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Obtaining Source IP Addresses</h1>
|
||||
|
||||
<div id="body1590575971687"><p id="elb_faq_0170__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0090.html">How Can I Obtain the IP Address of a Client?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
16
docs/elb/umn/elb_faq_0180.html
Normal file
16
docs/elb/umn/elb_faq_0180.html
Normal file
@ -0,0 +1,16 @@
|
||||
<a name="elb_faq_0180"></a><a name="elb_faq_0180"></a>
|
||||
|
||||
<h1 class="topictitle1">HTTP/HTTPS Listeners</h1>
|
||||
<div id="body1590575971687"><p id="elb_faq_0180__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0118.html">Why Is There a Security Warning After a Certificate Is Configured?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
18
docs/elb/umn/elb_faq_0190.html
Normal file
18
docs/elb/umn/elb_faq_0190.html
Normal file
@ -0,0 +1,18 @@
|
||||
<a name="elb_faq_0190"></a><a name="elb_faq_0190"></a>
|
||||
|
||||
<h1 class="topictitle1">Sticky Sessions</h1>
|
||||
<div id="body1590575971687"><p id="elb_faq_0190__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0046.html">How Do I Check If Sticky Sessions Failed to Take Effect?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0085.html">What Types of Sticky Sessions Does ELB Support?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_0200.html
Normal file
11
docs/elb/umn/elb_faq_0200.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_0200"></a><a name="elb_faq_0200"></a>
|
||||
|
||||
<h1 class="topictitle1">Popular Questions</h1>
|
||||
<div id="body1575692227488"><ul id="elb_faq_0200__ul206931331103214"><li id="elb_faq_0200__li669312314327"><a href="elb_faq_0090.html">How Can I Obtain the IP Address of a Client?</a></li><li id="elb_faq_0200__li11561850133210"><a href="en-us_topic_0018127975.html">How Do I Troubleshoot an Unhealthy Backend Server?</a></li><li id="elb_faq_0200__li1176130193315"><a href="elb_faq_0024.html">How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?</a></li><li id="elb_faq_0200__li31438516331"><a href="elb_faq_0085.html">What Types of Sticky Sessions Does ELB Support?</a></li><li id="elb_faq_0200__li1385051016337"><a href="elb_faq_0111.html">How Is WebSocket Used?</a></li><li id="elb_faq_0200__li911814137339"><a href="elb_faq_0046.html">How Do I Check If Sticky Sessions Failed to Take Effect?</a></li><li id="elb_faq_0200__li1077718234335"><a href="en-us_elb_05_0008.html">What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?</a></li><li id="elb_faq_0200__li191851335103319"><a href="elb_faq_0038.html">How Does ELB Distribute Traffic?</a></li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
21
docs/elb/umn/elb_faq_0201.html
Normal file
21
docs/elb/umn/elb_faq_0201.html
Normal file
@ -0,0 +1,21 @@
|
||||
<a name="elb_faq_0201"></a><a name="elb_faq_0201"></a>
|
||||
|
||||
<h1 class="topictitle1">Load Balancers</h1>
|
||||
<div id="body1575704958391"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0038.html">How Does ELB Distribute Traffic?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_210307.html">Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load BalancerLoad Balancer?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_210310.html">Do Shared Load Balancers Have Specifications?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_210312.html">Will Traffic Routing Be Interrupted If the Load Balancing Algorithm Is Changed?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
21
docs/elb/umn/elb_faq_0202.html
Normal file
21
docs/elb/umn/elb_faq_0202.html
Normal file
@ -0,0 +1,21 @@
|
||||
<a name="elb_faq_0202"></a><a name="elb_faq_0202"></a>
|
||||
|
||||
<h1 class="topictitle1">Listeners</h1>
|
||||
<div id="body1575701761779"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="en-us_elb_05_0008.html">What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0084.html">Does ELB Have Restrictions on the File Upload Speed and Size?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0111.html">How Is WebSocket Used?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_210410.html">Why Cannot I Add a Listener to a Dedicated Load Balancer?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
25
docs/elb/umn/elb_faq_0203.html
Normal file
25
docs/elb/umn/elb_faq_0203.html
Normal file
@ -0,0 +1,25 @@
|
||||
<a name="elb_faq_0203"></a><a name="elb_faq_0203"></a>
|
||||
|
||||
<h1 class="topictitle1">Backend Servers</h1>
|
||||
<div id="body1575701762331"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0112.html">Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Configured?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_099.html">Can Servers Access the Internet After They Are Associated with a Load Balancer?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0039.html">How Do I Check the Network Conditions of a Backend Server?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0040.html">How Do I Check the Network Configuration of a Backend Server?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0041.html">How Do I Check the Status of a Backend Server?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0001.html">When Is a Backend Server Considered Healthy?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
19
docs/elb/umn/elb_faq_0204.html
Normal file
19
docs/elb/umn/elb_faq_0204.html
Normal file
@ -0,0 +1,19 @@
|
||||
<a name="elb_faq_0204"></a><a name="elb_faq_0204"></a>
|
||||
|
||||
<h1 class="topictitle1">Health Checks</h1>
|
||||
<div id="body1575703621403"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="en-us_topic_0018127975.html">How Do I Troubleshoot an Unhealthy Backend Server?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0024.html">How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0114.html">Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
15
docs/elb/umn/elb_faq_0205.html
Normal file
15
docs/elb/umn/elb_faq_0205.html
Normal file
@ -0,0 +1,15 @@
|
||||
<a name="elb_faq_0205"></a><a name="elb_faq_0205"></a>
|
||||
|
||||
<h1 class="topictitle1">Certificates</h1>
|
||||
<div id="body1575704100484"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0072.html">How Can I Create Server Certificates and CA Certificates?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
25
docs/elb/umn/elb_faq_0211.html
Normal file
25
docs/elb/umn/elb_faq_0211.html
Normal file
@ -0,0 +1,25 @@
|
||||
<a name="elb_faq_0211"></a><a name="elb_faq_0211"></a>
|
||||
|
||||
<h1 class="topictitle1">ELB Functionality</h1>
|
||||
<div id="body1576142955491"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0060.html">Can ELB Be Used Separately?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="en-us_elb_05_0011.html">Is an EIP Assigned Exclusively to a Load Balancer?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="en-us_elb_05_0004.html">How Many Load Balancers and Listeners Can I Have?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0062.html">Can I Adjust the Number of Backend Servers When a Load Balancer is Running?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0064.html">Can Backend Servers Run Different OSs?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_21020221.html">Can I Upgrade a Shared Load Balancer to a Dedicated Load Balancer Without Interrupting Traffic Routing?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0212.html">ELB Use</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
18
docs/elb/umn/elb_faq_0212.html
Normal file
18
docs/elb/umn/elb_faq_0212.html
Normal file
@ -0,0 +1,18 @@
|
||||
<a name="elb_faq_0212"></a><a name="elb_faq_0212"></a>
|
||||
|
||||
<h1 class="topictitle1">ELB Use</h1>
|
||||
<div id="body1590575971686"><p id="elb_faq_0212__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0211.html">ELB Functionality</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_faq_0127.html">Service Performance and Load</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0000.html">FAQ</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_099.html
Normal file
11
docs/elb/umn/elb_faq_099.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_099"></a><a name="elb_faq_099"></a>
|
||||
|
||||
<h1 class="topictitle1">Can Servers Access the Internet After They Are Associated with a Load Balancer?</h1>
|
||||
<div id="body1566463582245"><p id="elb_faq_099__p8060118">Yes. Servers can access the Internet regardless of if they are associated with a load balancer.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_21020221.html
Normal file
11
docs/elb/umn/elb_faq_21020221.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_21020221"></a><a name="elb_faq_21020221"></a>
|
||||
|
||||
<h1 class="topictitle1">Can I Upgrade a Shared Load Balancer to a Dedicated Load Balancer Without Interrupting Traffic Routing?</h1>
|
||||
<div id="body0000001239938081"><p id="elb_faq_21020221__p652461555620">No. <span id="elb_faq_21020221__ph84821558185815">Shared</span> load balancers cannot be upgraded to dedicated load balancers.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0211.html">ELB Functionality</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
12
docs/elb/umn/elb_faq_210307.html
Normal file
12
docs/elb/umn/elb_faq_210307.html
Normal file
@ -0,0 +1,12 @@
|
||||
<a name="elb_faq_210307"></a><a name="elb_faq_210307"></a>
|
||||
|
||||
<h1 class="topictitle1">Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load BalancerLoad Balancer?</h1>
|
||||
<div id="body0000001191123875"><p id="elb_faq_210307__p82254326153">These IP addresses are used by underlying resources.</p>
|
||||
<p id="elb_faq_210307__p8060118">Generally, 2 IP addresses are required for creating a dedicated load balancer in a single AZ, and 6 IP addresses are required for creating a dedicated load balancer with cross-VPC backend enabled. If you create a dedicated load balancer in multiple AZs, more IP addresses will be required. There is an algorithm to determine how many IP addresses are required.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0201.html">Load Balancers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
12
docs/elb/umn/elb_faq_210310.html
Normal file
12
docs/elb/umn/elb_faq_210310.html
Normal file
@ -0,0 +1,12 @@
|
||||
<a name="elb_faq_210310"></a><a name="elb_faq_210310"></a>
|
||||
|
||||
<h1 class="topictitle1">Do Shared Load Balancers Have Specifications?</h1>
|
||||
<div id="body0000001215061331"><p id="elb_faq_210310__p17551181282311">No.</p>
|
||||
<p id="elb_faq_210310__p2391181152311"><span id="elb_faq_210310__ph1645535710329">Shared</span> load balancers share underlying resources, and the performance of one load balancer is affected by other load balancers. Only dedicated load balancers have exclusive use of their underlying resources. The performance of a dedicated load balancer is not affected by other dedicated load balancers on the Internet.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0201.html">Load Balancers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
11
docs/elb/umn/elb_faq_210312.html
Normal file
11
docs/elb/umn/elb_faq_210312.html
Normal file
@ -0,0 +1,11 @@
|
||||
<a name="elb_faq_210312"></a><a name="elb_faq_210312"></a>
|
||||
|
||||
<h1 class="topictitle1">Will Traffic Routing Be Interrupted If the Load Balancing Algorithm Is Changed?</h1>
|
||||
<div id="body0000001188951516"><p id="elb_faq_210312__p491192211191">No. If the load balancing algorithm is changed, established connections will not be affected. Therefore, traffic routing will not be interrupted.</p>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0201.html">Load Balancers</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
38
docs/elb/umn/elb_faq_210410.html
Normal file
38
docs/elb/umn/elb_faq_210410.html
Normal file
@ -0,0 +1,38 @@
|
||||
<a name="elb_faq_210410"></a><a name="elb_faq_210410"></a>
|
||||
|
||||
<h1 class="topictitle1">Why Cannot I Add a Listener to a Dedicated Load Balancer?</h1>
|
||||
<div id="body0000001194920880"><p id="elb_faq_210410__p573834519438">If you select either network load balancing (TCP/UDP) or application load balancing (HTTP/HTTPS) when creating the load balancer, you can only add listeners of the corresponding protocol.</p>
|
||||
<p id="elb_faq_210410__p8060118">The load balancing type cannot be changed after being selected. For example, if you have selected network load balancing during load balancer creation, you cannot change it to application load balancing and you cannot add HTTP or HTTPS listeners.</p>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_faq_210410__table158021438173312" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Protocols and load balancing types</caption><thead align="left"><tr id="elb_faq_210410__row1580353819330"><th align="left" class="cellrowborder" valign="top" width="29.99%" id="mcps1.3.3.2.4.1.1"><p id="elb_faq_210410__p1480319381335">Load Balancing Type</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="28.76%" id="mcps1.3.3.2.4.1.2"><p id="elb_faq_210410__p6803193816339">Protocol</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="41.25%" id="mcps1.3.3.2.4.1.3"><p id="elb_faq_210410__p246615244358">Listener Types</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="elb_faq_210410__row1480333819339"><td class="cellrowborder" valign="top" width="29.99%" headers="mcps1.3.3.2.4.1.1 "><p id="elb_faq_210410__p12803133816336">Network load balancing</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="28.76%" headers="mcps1.3.3.2.4.1.2 "><p id="elb_faq_210410__p158039381334">TCP/UDP</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="41.25%" headers="mcps1.3.3.2.4.1.3 "><p id="elb_faq_210410__p164664242350">TCP and UDP listeners</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_faq_210410__row4634173915342"><td class="cellrowborder" valign="top" width="29.99%" headers="mcps1.3.3.2.4.1.1 "><p id="elb_faq_210410__p363523963411">Application load balancing</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="28.76%" headers="mcps1.3.3.2.4.1.2 "><p id="elb_faq_210410__p3635163923414">HTTP/HTTPS</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="41.25%" headers="mcps1.3.3.2.4.1.3 "><p id="elb_faq_210410__p12825193673620">HTTP and HTTPS listeners</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0202.html">Listeners</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
176
docs/elb/umn/elb_lb_000006.html
Normal file
176
docs/elb/umn/elb_lb_000006.html
Normal file
File diff suppressed because it is too large
Load Diff
15
docs/elb/umn/elb_lb_000010.html
Normal file
15
docs/elb/umn/elb_lb_000010.html
Normal file
@ -0,0 +1,15 @@
|
||||
<a name="elb_lb_000010"></a><a name="elb_lb_000010"></a>
|
||||
|
||||
<h1 class="topictitle1">Changing an IP Address</h1>
|
||||
<div id="body8662426"><div class="section" id="elb_lb_000010__en-us_topic_0172882190_section57040304257"><h4 class="sectiontitle">Scenarios</h4><p id="elb_lb_000010__en-us_topic_0172882190_p9663124616522">ELB allows you to change private IPv4 addresses of load balancers. New private IPv4 addresses can be from the current subnet or other subnets. </p>
|
||||
</div>
|
||||
<div class="section" id="elb_lb_000010__en-us_topic_0172882190_section465072113222"><h4 class="sectiontitle">Changing a Private IPv4 Address</h4><ol id="elb_lb_000010__en-us_topic_0172882190_ol10560182413"><li id="elb_lb_000010__en-us_topic_0172882190_li677391520332">Log in to the management console.</li><li id="elb_lb_000010__en-us_topic_0172882190_li675519100420">In the upper left corner of the page, click <span><img id="elb_lb_000010__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_lb_000010__li83736197297">Hover on <span><img id="elb_lb_000010__en-us_topic_0052569751_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.png"></span> in the upper left corner to display <strong id="elb_lb_000010__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_lb_000010__en-us_topic_0052569751_b61222025142217">Network</strong> > <strong id="elb_lb_000010__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>.</li><li id="elb_lb_000010__en-us_topic_0172882190_li108498223247">On the <strong id="elb_lb_000010__en-us_topic_0172882190_b741114234520">Elastic Load Balancers</strong> tab page, locate the load balancer whose IP address you want to change, and click <strong id="elb_lb_000010__en-us_topic_0172882190_b29442711514">More</strong> > <strong id="elb_lb_000010__en-us_topic_0172882190_b881413415114">Change Private IPv4 Address</strong> in the <strong id="elb_lb_000010__en-us_topic_0172882190_b1931314482519">Operation</strong> column.</li><li id="elb_lb_000010__en-us_topic_0172882190_li1047496259">In the <strong id="elb_lb_000010__en-us_topic_0172882190_b17283122905218">Change Private IPv4 Address</strong> dialog box, select the subnet where the IP address resides and specify the IP address.<ul id="elb_lb_000010__en-us_topic_0172882190_ul18547655162812"><li id="elb_lb_000010__en-us_topic_0172882190_li1158214102915">To use an IP address from another subnet, select <strong id="elb_lb_000010__en-us_topic_0172882190_b77951912547">Automatically-assigned IPv4 address</strong>. The system automatically assigns an IPv4 address for your load balancer.</li><li id="elb_lb_000010__en-us_topic_0172882190_li1547205522818">To use another IP address from the current subnet, specify an IP address.</li></ul>
|
||||
</li><li id="elb_lb_000010__en-us_topic_0172882190_li18101322172713">Click <strong id="elb_lb_000010__en-us_topic_0172882190_b1131715315553">OK</strong>.</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_elb_03_0001.html">Load Balancer</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
29
docs/elb/umn/elb_pro_0000.html
Normal file
29
docs/elb/umn/elb_pro_0000.html
Normal file
@ -0,0 +1,29 @@
|
||||
<a name="elb_pro_0000"></a><a name="elb_pro_0000"></a>
|
||||
|
||||
<h1 class="topictitle1">Service Overview</h1>
|
||||
<div id="body15047603"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="en-us_topic_0015479966.html">What Is ELB?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_pro_0005.html">Product Advantages</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_pro_0003.html">How ELB Works</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_pro_0006.html">Application Scenarios</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_pro_0004.html">Differences Between Dedicated and Shared Load Balancers</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="en-us_topic_0287737145.html">Specifications of Dedicated Load Balancers</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="en-us_elb_01_0004.html">Load Balancing on a Public or Private Network</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_ug_fz_0003_01.html">Network Traffic Paths</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="en-us_topic_0195131496.html">Product Concepts</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="elb_pro_0008.html">How ELB Works with Other Services</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
80
docs/elb/umn/elb_pro_0001.html
Normal file
80
docs/elb/umn/elb_pro_0001.html
Normal file
@ -0,0 +1,80 @@
|
||||
<a name="elb_pro_0001"></a><a name="elb_pro_0001"></a>
|
||||
|
||||
<h1 class="topictitle1">Basic Concepts</h1>
|
||||
<div id="body1567992509085">
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_pro_0001__table17643195014453" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Some concepts about ELB</caption><thead align="left"><tr id="elb_pro_0001__row1644350164511"><th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.1.2.3.1.1"><p id="elb_pro_0001__p864415064515">Term</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="82%" id="mcps1.3.1.2.3.1.2"><p id="elb_pro_0001__p96442503458">Definition</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="elb_pro_0001__row864475011450"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p4644135024515">Load balancer</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p3644250144511">A load balancer distributes incoming traffic across backend servers.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row17644115034512"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p186441250134518">Listener</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p2644950114515">A listener listens on requests from clients and routes the requests to backend <span id="elb_pro_0001__text64561152173613">server</span>s based on the settings that you configure when you add the listener.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row1364411502455"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p15644155084519">Backend server</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p1464425016457">A backend server is a cloud server added to a backend <span id="elb_pro_0001__elb_ug_hd_0001_text134779184156">server</span> group associated with a load balancer. When you add a listener to a load balancer, you can create or select a backend <span id="elb_pro_0001__elb_ug_hd_0001_text01565413152">server</span> group to receive requests from the load balancer by using the port and protocol you specify for the backend <span id="elb_pro_0001__elb_ug_hd_0001_text12774182671815">server</span> group and the load balancing algorithm you select.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row19644950204515"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p156441850134517">Backend server group</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p20644145034510">A backend server group is a collection of cloud servers that have same features. When you add a listener, you select a load balancing algorithm and create or select a backend server group. Incoming traffic is routed to the corresponding backend server group based on the listener's configuration.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row7644165084514"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p4644205015458">Health check</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p9644125014451">ELB periodically sends requests to backend <span id="elb_pro_0001__elb_ug_hc_0001_text174345265419">server</span>s to check whether they can process requests. If a backend <span id="elb_pro_0001__elb_ug_hc_0001_text442602317545">server</span> is detected as unhealthy, the load balancer stops routing requests to it. After the backend <span id="elb_pro_0001__elb_ug_hc_0001_text854154645414">server</span> recovers, the load balancer will resume routing requests to it.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row20644450204518"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p1964418505454">Redirect</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p5644135015457">HTTPS is an extension of HTTP. HTTPS encrypts data between a web server and a browser.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row364405094516"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p5462101841813">Sticky session</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p1564418504452">Sticky sessions ensure that requests from a client always get routed to the same backend server before a session elapses.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row564410505454"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p7644750164517">WebSocket</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p17963155112120">WebSocket is a new HTML5 protocol that provides full-duplex communication between the browser and the server. WebSocket saves server resources and bandwidth, and enables real-time communication. Both WebSocket and HTTP depend on TCP to transmit data. A handshake connection is required between the browser and server, so that they can communicate with each other only after the connection is established. However, as a bidirectional communication protocol, WebSocket is different from HTTP. After the handshake succeeds, both the server and browser (or client agent) can actively send data to or receive data from each other.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row3644145013456"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p064585018451">SNI</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p564595064516">SNI, an extension to Transport Layer Security (TLS), enables a server to present multiple certificates on the same IP address and port number. SNI allows the client to indicate the domain name of the website while sending an SSL handshake request. Once receiving the request, the load balancer queries the right certificate based on the hostname or domain name and returns the certificate to the client. If no certificate is found, the load balancer will return the default certificate.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row1264545054512"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p1764525015454">Persistent connection</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p96451550104515">A persistent connection allows multiple data packets to be sent continuously over a TCP connection. If no data packet is sent during the connection, the client and server send link detection packets to each other to maintain the connection.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row46458501457"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p26451050184518">Short connection</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p15645125017455">A short connection is a connection established when data is exchanged between the client and server and immediately closed after the data is sent.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="elb_pro_0001__row91101346807"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.2.3.1.1 "><p id="elb_pro_0001__p1811116467011">Concurrent connection</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="82%" headers="mcps1.3.1.2.3.1.2 "><p id="elb_pro_0001__p7111134616018">Concurrent connections are total number of TCP connections initiated by clients and routed to backend servers by a load balancer per second.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0195131496.html">Product Concepts</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
22
docs/elb/umn/elb_pro_0002.html
Normal file
22
docs/elb/umn/elb_pro_0002.html
Normal file
@ -0,0 +1,22 @@
|
||||
<a name="elb_pro_0002"></a><a name="elb_pro_0002"></a>
|
||||
|
||||
<h1 class="topictitle1">Region and AZ</h1>
|
||||
<div id="body8662426"><div class="section" id="elb_pro_0002__en-us_topic_0184026189_section388255972712"><h4 class="sectiontitle">Concept</h4><p id="elb_pro_0002__en-us_topic_0184026189_p212716216381">A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.</p>
|
||||
<ul id="elb_pro_0002__en-us_topic_0184026189_ul86578533460"><li id="elb_pro_0002__en-us_topic_0184026189_li14657175334618">A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.</li><li id="elb_pro_0002__en-us_topic_0184026189_li45875020473">An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.</li></ul>
|
||||
<p id="elb_pro_0002__en-us_topic_0184026189_p1479174514614"><a href="#elb_pro_0002__en-us_topic_0184026189_fig8747114281212">Figure 1</a> shows the relationship between regions and AZs.</p>
|
||||
<div class="fignone" id="elb_pro_0002__en-us_topic_0184026189_fig8747114281212"><a name="elb_pro_0002__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="elb_pro_0002__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="elb_pro_0002__en-us_topic_0184026189_section67281149192216"><h4 class="sectiontitle">Selecting a Region</h4><p id="elb_pro_0002__en-us_topic_0184026189_p68521454132212">Select a region closest to your target users for lower network latency and quick access.</p>
|
||||
</div>
|
||||
<div class="section" id="elb_pro_0002__en-us_topic_0184026189_section193971112578"><h4 class="sectiontitle">Selecting an AZ</h4><p id="elb_pro_0002__en-us_topic_0184026189_p859161416717">When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.</p>
|
||||
<ul id="elb_pro_0002__en-us_topic_0184026189_ul157203571473"><li id="elb_pro_0002__en-us_topic_0184026189_li7720175710711">For high DR capability, deploy resources in different AZs within the same region.</li><li id="elb_pro_0002__en-us_topic_0184026189_li109763595719">For lower network latency, deploy resources in the same AZ.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="elb_pro_0002__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="elb_pro_0002__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/en-us/endpoint/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0195131496.html">Product Concepts</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
24
docs/elb/umn/elb_pro_0003.html
Normal file
24
docs/elb/umn/elb_pro_0003.html
Normal file
@ -0,0 +1,24 @@
|
||||
<a name="elb_pro_0003"></a><a name="elb_pro_0003"></a>
|
||||
|
||||
<h1 class="topictitle1">How ELB Works</h1>
|
||||
<div id="body1516070328064"><div class="fignone" id="elb_pro_0003__fig34721951104111"><span class="figcap"><b>Figure 1 </b>How ELB works</span><br><span><img id="elb_pro_0003__image1847295194110" src="en-us_image_0000001253004159.png"></span></div>
|
||||
<p id="elb_pro_0003__p158481225105114">The following describes how ELB works:</p>
|
||||
<ol id="elb_pro_0003__ol16216341115120"><li id="elb_pro_0003__li1121634118515">A client sends a request to your application.</li><li id="elb_pro_0003__li14626175511549">The listeners added to your load balancer use the protocols and ports you configure to receive the request.</li><li id="elb_pro_0003__li13200162614554">The listener forwards the request to the associated backend server group based on your configuration. If you have configured a forwarding policy for the listener, the listener evaluates the request based on the forwarding policy. If the request matches the forwarding policy, the listener forwards the request to the backend server group configured for the forwarding policy.</li><li id="elb_pro_0003__li19582026583">Health backend servers in the backend server group receive the request based on the load balancing algorithm and the routing rules you specify in the forwarding policy, handle the request, and return a result to the client.</li></ol>
|
||||
<p id="elb_pro_0003__p511191615473">How requests are routed depends on the <strong id="elb_pro_0003__b137115714517"><a href="#elb_pro_0003__section12605144013346">load balancing algorithms</a></strong> configured for each backend server group. If the listener uses HTTP or HTTPS, how requests are routed also depends on the <strong id="elb_pro_0003__b176419294333">forwarding policies</strong> configured for the listener.</p>
|
||||
<div class="section" id="elb_pro_0003__section12605144013346"><a name="elb_pro_0003__section12605144013346"></a><a name="section12605144013346"></a><h4 class="sectiontitle">Load Balancing Algorithms</h4><p id="elb_pro_0003__p126518420210">Both dedicated and <span id="elb_pro_0003__ph1365217417216">shared</span> load balancers support weighted round robin, weighted least connections, and source IP hash.</p>
|
||||
<div class="p" id="elb_pro_0003__p1625369143019"><ul id="elb_pro_0003__ul62874421822"><li id="elb_pro_0003__li1728610427215">Weighted round robin: Requests are routed to backend servers using the round robin algorithm. Backend servers with higher weights receive proportionately more requests, whereas equal-weighted servers receive the same number of requests. This algorithm is often used for short connections, such as HTTP connections.<p id="elb_pro_0003__p16438104524911"><a name="elb_pro_0003__li1728610427215"></a><a name="li1728610427215"></a>The following figure shows an example of how requests are distributed using the weighted round robin algorithm. Two backend <span id="elb_pro_0003__text1263703874517">server</span>s are in the same AZ and have the same weight, and each <span id="elb_pro_0003__text7688194514452">server</span> receives the same proportion of requests.</p>
|
||||
<div class="fignone" id="elb_pro_0003__fig7538148162412"><span class="figcap"><b>Figure 2 </b>Traffic distribution using the weighted round robin algorithm</span><br><span><img id="elb_pro_0003__image173432046115015" src="en-us_image_0000001160373426.png"></span></div>
|
||||
</li><li id="elb_pro_0003__li06431114312">Weighted least connections: In addition to the weight assigned to each server, the number of connections being processed by each backend server is also considered. Requests are routed to the server with the lowest connections-to-weight ratio. In addition to the number of connections, each server is assigned a weight based on its capacity. Requests are routed to the server with the lowest connections-to-weight ratio. This algorithm is often used for persistent connections, such as connections to a database.<p id="elb_pro_0003__p7925102765415"><a name="elb_pro_0003__li06431114312"></a><a name="li06431114312"></a>The following figure shows an example of how requests are distributed using the weighted least connections algorithm. Two backend servers are in the same AZ and have the same weight, 100 connections have been established with backend server 01, and 50 connections have been connected with backend server 02. New requests are preferentially routed to backend server 02.</p>
|
||||
<div class="fignone" id="elb_pro_0003__fig193917324513"><span class="figcap"><b>Figure 3 </b>Traffic distribution using the weighted least connections algorithm</span><br><span><img id="elb_pro_0003__image12716112911553" src="en-us_image_0000001160533378.png"></span></div>
|
||||
</li><li id="elb_pro_0003__li1028712421427">Source IP hash: The source IP address of each request is calculated using the consistent hashing algorithm to obtain a unique hashing key, and all backend servers are numbered. The generated key is used to allocate the client to a particular server. This allows requests from different clients to be routed based on source IP addresses and ensures that a client is directed to the same server that it was using previously. This algorithm works well for TCP connections of load balancers that do not use cookies.<p id="elb_pro_0003__p166892034185613"><a name="elb_pro_0003__li1028712421427"></a><a name="li1028712421427"></a>The following figure shows an example of how requests are distributed using the source IP hash algorithm. Two backend servers are in the same AZ and have the same weight. If backend server 01 has processed a request from IP address A, the load balancer will route new requests from IP address A to backend server 01.</p>
|
||||
<div class="fignone" id="elb_pro_0003__fig3381171135617"><span class="figcap"><b>Figure 4 </b>Traffic distribution using the source IP hash algorithm</span><br><span><img id="elb_pro_0003__image1784771565717" src="en-us_image_0000001205974859.png"></span></div>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_pro_0000.html">Service Overview</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
306
docs/elb/umn/elb_pro_0004.html
Normal file
306
docs/elb/umn/elb_pro_0004.html
Normal file
File diff suppressed because it is too large
Load Diff
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user