vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

ELB_UMN_IPV6_1218

Browse Source 
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com>
Co-authored-by: zhoumeng <zhoumeng35@huawei.com>
Co-committed-by: zhoumeng <zhoumeng35@huawei.com>
This commit is contained in:
zhoumeng 2024-02-09 10:31:35 +00:00 committed by zuul
parent 89983bef36
commit 3275979377
236 changed files with 5278 additions and 2644 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2755
docs/elb/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

754
docs/elb/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

2
docs/elb/umn/elb_faq_0024.html
View File

@ -17,7 +17,7 @@
<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__b325887324">6168</strong>.</p>
<p id="elb_faq_0024__p52451533713">The default rate mask is <strong id="elb_faq_0024__b1590969366">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>

4
docs/elb/umn/elb_faq_0038.html
View File

@ -4,8 +4,8 @@
<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 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_0000001794819813.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_0000001747380980.jpg"></span></div>
</div>
<div>
<div class="familylinks">

4
docs/elb/umn/elb_faq_0041.html
View File

@ -2,12 +2,12 @@
<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 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_0000001794819597.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>
<p id="elb_faq_0041__p1711753185312"><span><img id="elb_faq_0041__image1711753125311" src="en-us_image_0000001794819593.jpg"></span></p>
</li></ol>
</div>
<div>

2
docs/elb/umn/elb_faq_0065.html
View File

@ -4,7 +4,7 @@
<div id="body1549953425249"><div class="section" id="elb_faq_0065__section6321311611"><h4 class="sectiontitle">What Is Quota?</h4><p id="elb_faq_0065__en-us_topic_0040259342_p1415804616467">Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.</p>
<p id="elb_faq_0065__en-us_topic_0040259342_p547171214515">If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.</p>
</div>
<div class="section" id="elb_faq_0065__section07760615438"><h4 class="sectiontitle">How Do I View My Quotas?</h4><ol id="elb_faq_0065__en-us_topic_0040259342_ol1222775692215"><li id="elb_faq_0065__en-us_topic_0040259342_li5648642910048">Log in to the management console.</li><li id="elb_faq_0065__en-us_topic_0040259342_li464234814566">Click <span><img id="elb_faq_0065__en-us_topic_0040259342_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0275513364.png"></span> in the upper left corner and select the desired region and project.</li><li id="elb_faq_0065__en-us_topic_0040259342_li3861581410048">In the upper right corner of the page, click <span><img id="elb_faq_0065__en-us_topic_0040259342_image99377514309" src="en-us_image_0152727234.png"></span>.<p id="elb_faq_0065__en-us_topic_0040259342_p1748884433119">The <strong id="elb_faq_0065__en-us_topic_0040259342_b695801964614">Service Quota</strong> page is displayed.</p>
<div class="section" id="elb_faq_0065__section07760615438"><h4 class="sectiontitle">How Do I View My Quotas?</h4><ol id="elb_faq_0065__en-us_topic_0040259342_ol1222775692215"><li id="elb_faq_0065__en-us_topic_0040259342_li5648642910048">Log in to the management console.</li><li id="elb_faq_0065__en-us_topic_0040259342_li464234814566">Click <span><img id="elb_faq_0065__en-us_topic_0040259342_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001794820065.png"></span> in the upper left corner and select the desired region and project.</li><li id="elb_faq_0065__en-us_topic_0040259342_li3861581410048">In the upper right corner of the page, click <span><img id="elb_faq_0065__en-us_topic_0040259342_image99377514309" src="en-us_image_0000001747740124.png"></span>.<p id="elb_faq_0065__en-us_topic_0040259342_p1748884433119">The <strong id="elb_faq_0065__en-us_topic_0040259342_b695801964614">Service Quota</strong> page is displayed.</p>
</li><li id="elb_faq_0065__en-us_topic_0040259342_li1579070183211">View the used and total quota of each type of resources on the displayed page.<p id="elb_faq_0065__en-us_topic_0040259342_p97891720193417"><a name="elb_faq_0065__en-us_topic_0040259342_li1579070183211"></a><a name="en-us_topic_0040259342_li1579070183211"></a>If a quota cannot meet service requirements, apply for a higher quota.</p>
</li></ol>
</div>

6
docs/elb/umn/elb_faq_0067.html
View File

@ -7,16 +7,16 @@
<p id="elb_faq_0067__p12376122895310"><strong id="elb_faq_0067__b437619286536">nohup python –m SimpleHTTPServer 80 &amp;</strong></p>
<p id="elb_faq_0067__p178484287221">Run the following command to check whether the HTTP service is normal:</p>
<p id="elb_faq_0067__p1484832814221"><strong id="elb_faq_0067__b16848152812210">curl http://127.0.0.1:80</strong></p>
<p id="elb_faq_0067__p10848102892216"><span><img id="elb_faq_0067__image2084892832218" src="en-us_image_0193109154.jpg"></span></p>
<p id="elb_faq_0067__p10848102892216"><span><img id="elb_faq_0067__image2084892832218" src="en-us_image_0000001747739620.jpg"></span></p>
<p id="elb_faq_0067__p594210402540">Log in to the other backend server and create a file named <strong id="elb_faq_0067__b73701131182114">2.file</strong> in the current directory.</p>
<p id="elb_faq_0067__p09821930195419">Run the following command in the current directory to start the HTTP service:</p>
<p id="elb_faq_0067__p1110713536548"><strong id="elb_faq_0067__b1107185325410">nohup python –m SimpleHTTPServer 80 &amp;</strong></p>
<p id="elb_faq_0067__p684820286228">Run the following command to check whether the HTTP service is normal:</p>
<p id="elb_faq_0067__p7848132882212"><strong id="elb_faq_0067__b284882842215">curl http://127.0.0.1:80</strong></p>
<p id="elb_faq_0067__p1584814283224"><span><img id="elb_faq_0067__image5848328102214" src="en-us_image_0193109171.jpg"></span></p>
<p id="elb_faq_0067__p1584814283224"><span><img id="elb_faq_0067__image5848328102214" src="en-us_image_0000001747380744.jpg"></span></p>
</li></ol><ol start="3" id="elb_faq_0067__ol3257182718553"><li id="elb_faq_0067__li72573275551">Access the load balancer from the client and specify the cookie value.<p id="elb_faq_0067__p184832815222"><a name="elb_faq_0067__li72573275551"></a><a name="li72573275551"></a>The following is an example command. Change the parameters as needed. Ensure that the returned file names of each request are the same.</p>
<p id="elb_faq_0067__p16848728112219"><strong id="elb_faq_0067__b580515476294">curl --cookie "name=abcd" <em id="elb_faq_0067__i580516478294"> </em>http://</strong><strong id="elb_faq_0067__b1996181615457">ELB_IP:Port</strong></p>
<p id="elb_faq_0067__p158481028202214"><span><img id="elb_faq_0067__image1884819289220" src="en-us_image_0193109172.jpg"></span></p>
<p id="elb_faq_0067__p158481028202214"><span><img id="elb_faq_0067__image1884819289220" src="en-us_image_0000001794819569.jpg"></span></p>
</li></ol>
</div>
<div>

30
docs/elb/umn/elb_faq_0090.html
View File

@ -17,7 +17,7 @@
</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="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_0000001794660973.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__ph1441134105011">Shared</span> load balancers: 100.125.0.0/16<span id="elb_faq_0090__ph126143415508"></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>
@ -37,7 +37,7 @@ make install</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="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_0000001794820077.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 &lt;IP_address&gt;</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>
@ -49,38 +49,38 @@ real_ip_header X-Forwarded-For;</pre>
<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>
<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_0000001747381248.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">&lt;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" /&gt;</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>
<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_0000001747381228.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 &amp;&amp; sh shutdown.sh &amp;&amp; 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>
<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_0000001747740104.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>
<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_0000001794660969.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> &gt; <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>
<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> &gt; <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_0000001747381224.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_0000001747740108.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_0000001794660981.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_0000001747381232.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_0000001747381236.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_0000001747381244.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_0000001747740120.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__p157754342011">For load balancing at Layer 4 (TCP/UDP), you can enable <strong id="elb_faq_0090__b16174151214303">Transfer Client IP Address</strong> to obtain the source IP address.</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 <strong id="elb_faq_0090__b101155618413">Transfer Client IP Address</strong>.<div class="caution" id="elb_faq_0090__note163721259193419"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0090__ul0161183124115"><li id="elb_faq_0090__li11982310114212">After this function is enabled, traffic, such as unidirectional download or push traffic, may be interrupted when backend servers are being migrated during the migration of the associated classic load balancer. After backend servers are migrated, retransmit the packets to restore the traffic.</li><li id="elb_faq_0090__li03069573459">After this function is enabled, the associated backend servers cannot be used as clients to access the listener.</li><li id="elb_faq_0090__li142889194478">If a backend server has been associated with the listener and health checks are enabled, enabling this function will check the health of the backend server, and traffic to this server will be interrupted for two health check intervals.</li></ul>
</div></div>
<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__li194625132711">Hover on <span><img id="elb_faq_0090__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_faq_0090__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_faq_0090__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_faq_0090__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</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__b393269167">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, click <span><img id="elb_faq_0090__image18771457113315" src="en-us_image_0000001454530030.png"></span> on the right of its name, and click <strong id="elb_faq_0090__b388015743316">Modify Listener</strong>. In the <strong id="elb_faq_0090__b6881165715337">Modify Listener</strong> dialog box, modify the parameters as needed.</li></ul>
<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_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_faq_0090__li194625132711">Hover on <span><img id="elb_faq_0090__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_faq_0090__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_faq_0090__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_faq_0090__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</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__b1858064398">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, click <span><img id="elb_faq_0090__image18771457113315" src="en-us_image_0000001747740100.png"></span> on the right of its name, and click <strong id="elb_faq_0090__b388015743316">Modify Listener</strong>. In the <strong id="elb_faq_0090__b6881165715337">Modify Listener</strong> dialog box, modify the parameters as needed.</li></ul>
</li><li id="elb_faq_0090__li3100135715344">Enable <strong id="elb_faq_0090__b745821111385">Transfer 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="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__b1738818185">Transfer 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>
</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="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__b1799864913">Transfer 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>
</li></ol>
</li></ul>

4
docs/elb/umn/elb_faq_0110.html
View File

@ -2,7 +2,9 @@
<h1 class="topictitle1">Which Protocol Should I Select for the Backend Server Group When Adding an HTTPS Listener?</h1>
<div id="body1574843372791"><p id="elb_faq_0110__p1136515819229">To use HTTPS at both the frontend and backend, you can create a dedicated load balancer, add an HTTPS listener to the load balancer, and set the backend protocol to HTTPS.</p>
<p id="elb_faq_0110__p01731216219">To use HTTPS at the frontend only, you can create a dedicated load balancer with HTTPS listener, and set the backend protocol to HTTP.</p>
<p id="elb_faq_0110__p01731216219">To use HTTPS at the frontend only, you can create a dedicated load balancer, add an HTTPS listener to the load balancer, and set the backend protocol to HTTP.</p>
<div class="note" id="elb_faq_0110__note112696133545"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0110__p72691413155411">Using HTTPS at both the frontend and backend only allows you to enable mutual authentication on the load balancer and backend servers.</p>
</div></div>
</div>
<div>
<div class="familylinks">

1
docs/elb/umn/elb_faq_0125.html
View File

@ -3,6 +3,7 @@
<h1 class="topictitle1">When Will Modified Weights Take Effect?</h1>
<div id="body1588062642982"><p id="elb_faq_0125__p966123218452">The new weights for backend servers take effect immediately after the weights are configured. Connections that have been established with backend servers will not be affected.</p>
<div class="note" id="elb_faq_0125__note195144217552"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0125__p695234265515">If the weight of a backend server is changed to 0, the new weight does not take effect immediately, and requests are still routed to this backend server. This is because a persistent connection is established between the load balancer and the backend server and requests are routed to this server until the connection times out.</p>
<ul id="elb_faq_0125__ul144031569501"><li id="elb_faq_0125__li1840345616502">TCP and UDP listeners: Persistent connections are disconnected after the idle timeout duration expires.</li><li id="elb_faq_0125__li9208153310513">HTTP and HTTPS listeners: Persistent connections are disconnected after the response timeout duration expires.</li></ul>
</div></div>
</div>
<div>

2
docs/elb/umn/elb_faq_0131.html
View File

@ -1,7 +1,7 @@
<a name="elb_faq_0131"></a><a name="elb_faq_0131"></a>
<h1 class="topictitle1">Why Must the Subnet Where the Load Balancer Resides Have at Least 16 Available IP Addresses for Enabling IP as a Backend?</h1>
<div id="body0000001181021511"><p id="elb_faq_0131__p8060118">These IP addresses are used by the ELB system. Generally, two IP addresses are required for creating a dedicated load balancer in a single AZ, and six IP addresses are required for creating a dedicated load balancer with IP as a backend enabled. If you create a dedicated load balancer in multiple AZs, more IP addresses will be required. There is an algorithm to calculate how many.</p>
<div id="body0000001181021511"><p id="elb_faq_0131__p8060118">These IP addresses are used by the ELB system. Generally, two IP addresses are required for creating a dedicated load balancer in a single AZ, and six IP addresses are required for creating a dedicated load balancer with IP as a backend enabled. If you create a dedicated load balancer in multiple AZs, more IP addresses will be required. There is an algorithm to calculate how many IP addresses are required.</p>
</div>
<div>
<div class="familylinks">

2
docs/elb/umn/elb_faq_0200.html
View File

@ -1,7 +1,7 @@
<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 Transfer 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="elb_faq_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 id="body1575692227488"><ul id="elb_faq_0200__ul206931331103214"><li id="elb_faq_0200__li669312314327"><a href="elb_faq_0090.html">How Can I Transfer the IP Address of a Client?</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="elb_faq_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">

2
docs/elb/umn/elb_faq_0201.html
View File

@ -12,7 +12,7 @@
</li>
<li class="ulchildlink"><strong><a href="elb_faq_210304.html">Why Can't I Delete My Load Balancer?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="elb_faq_210305.html">Do I Need to Configure Bandwidth for My Load Balancers?</a></strong><br>
<li class="ulchildlink"><strong><a href="elb_faq_210305.html">Do I Need to Configure EIP Bandwidth for My Load Balancers?</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="elb_faq_210306.html">Can I Bind Multiple EIPs to a Load Balancer?</a></strong><br>
</li>

6
docs/elb/umn/elb_faq_05_0008.html
View File

@ -86,13 +86,13 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_faq_05_0008__table44808652142126" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Sticky sessions supported by <span id="elb_faq_05_0008__ph669718389418">shared</span> load balancers</caption><thead align="left"><tr id="elb_faq_05_0008__row57750719142126"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.3.2.5.1.1"><p id="elb_faq_05_0008__p56688074142142"><strong id="elb_faq_05_0008__b1848222006">Load Balancing Algorithm</strong></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_faq_05_0008__table44808652142126" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Sticky sessions supported by <span id="elb_faq_05_0008__ph669718389418">shared</span> load balancers</caption><thead align="left"><tr id="elb_faq_05_0008__row57750719142126"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.3.2.5.1.1"><p id="elb_faq_05_0008__p56688074142142"><strong id="elb_faq_05_0008__b2066060555">Load Balancing Algorithm</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="31.95%" id="mcps1.3.3.2.5.1.2"><p id="elb_faq_05_0008__p52415961142126">Sticky Session Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="20.68%" id="mcps1.3.3.2.5.1.3"><p id="elb_faq_05_0008__p4883497514222"><strong id="elb_faq_05_0008__b1597668681">Layer 4 (TCP/UDP)</strong></p>
<th align="left" class="cellrowborder" valign="top" width="20.68%" id="mcps1.3.3.2.5.1.3"><p id="elb_faq_05_0008__p4883497514222"><strong id="elb_faq_05_0008__b1188056979">Layer 4 (TCP/UDP)</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="22.37%" id="mcps1.3.3.2.5.1.4"><p id="elb_faq_05_0008__p35305098142126"><strong id="elb_faq_05_0008__b460242441">Layer 7 (HTTP/HTTPS)</strong></p>
<th align="left" class="cellrowborder" valign="top" width="22.37%" id="mcps1.3.3.2.5.1.4"><p id="elb_faq_05_0008__p35305098142126"><strong id="elb_faq_05_0008__b763752430">Layer 7 (HTTP/HTTPS)</strong></p>
</th>
</tr>
</thead>

2
docs/elb/umn/elb_faq_099.html
View File

@ -1,7 +1,7 @@
<a name="elb_faq_099"></a><a name="elb_faq_099"></a>
<h1 class="topictitle1">Can Backend Servers Access the Internet After They Are Associated with a Load Balancer?</h1>
<div id="body1566463582245"><p id="elb_faq_099__p8060118">Yes. Backend servers can access the Internet whether or not they are associated with a load balancer.</p>
<div id="body1566463582245"><p id="elb_faq_099__p8060118">Yes. Backend servers can access the Internet whether they are associated with a load balancer.</p>
</div>
<div>
<div class="familylinks">

2
docs/elb/umn/elb_faq_210304.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">Why Can't I Delete My Load Balancer?</h1>
<div id="body0000001129457964"><ul id="elb_faq_210304__ul193081758839"><li id="elb_faq_210304__li13308145820318">There may be resources associated with the load balancer. Delete these resources first.<p id="elb_faq_210304__p1435273610474"><a name="elb_faq_210304__li13308145820318"></a><a name="li13308145820318"></a>Delete the resources configured for the load balancer in the following sequence:</p>
<ol id="elb_faq_210304__ol5438112011493"><li id="elb_faq_210304__elb_ug_fz_0008_li077312247434">Delete all the forwarding policies added to HTTP and HTTPS listeners of the load balancer.</li><li id="elb_faq_210304__elb_ug_fz_0008_li13773112484314">Delete the redirect created for each HTTP listener of the load balancer.</li><li id="elb_faq_210304__elb_ug_fz_0008_li777432411438">Remove all the backend servers from the backend server groups associated with each listener of the load balancer.</li><li id="elb_faq_210304__elb_ug_fz_0008_li777432414312">Delete all the listeners added to the load balancer.</li><li id="elb_faq_210304__elb_ug_fz_0008_li117741524104319">Delete all backend server groups associated with each listener of the load balancer.</li></ol>
<ol id="elb_faq_210304__ol5438112011493"><li id="elb_faq_210304__en-us_topic_0166333714_li077312247434">Delete all the forwarding policies added to HTTP and HTTPS listeners of the load balancer.</li><li id="elb_faq_210304__en-us_topic_0166333714_li13773112484314">Delete the redirect created for each HTTP listener of the load balancer.</li><li id="elb_faq_210304__en-us_topic_0166333714_li777432411438">Remove all the backend servers from the backend server groups associated with each listener of the load balancer.</li><li id="elb_faq_210304__en-us_topic_0166333714_li777432414312">Delete all the listeners added to the load balancer.</li><li id="elb_faq_210304__en-us_topic_0166333714_li117741524104319">Delete all backend server groups associated with each listener of the load balancer.</li></ol>
</li></ul>
<ul id="elb_faq_210304__ul13755247"><li id="elb_faq_210304__li19714519413">Deletion protection may have been enabled for the load balancer. Disable deletion protection first.</li><li id="elb_faq_210304__li172798431758">Removal protection may have been enabled for the load balancer. Disable removal protection first.</li></ul>
</div>

4
docs/elb/umn/elb_faq_210305.html
View File

@ -1,7 +1,7 @@
<a name="elb_faq_210305"></a><a name="elb_faq_210305"></a>
<h1 class="topictitle1">Do I Need to Configure Bandwidth for My Load Balancers?</h1>
<div id="body0000001175417665"><p id="elb_faq_210305__p8060118">If you use a load balancer on a private network, you do not need to configure bandwidth. You only need to bind an EIP to the load balancer and configure bandwidth if you are using the load balancer on the Internet.</p>
<h1 class="topictitle1">Do I Need to Configure EIP Bandwidth for My Load Balancers?</h1>
<div id="body0000001175417665"><p id="elb_faq_210305__p8060118">If you use a load balancer on a private network, you do not need to configure EIP bandwidth. You only need to bind an EIP and configure bandwidth if you are using a load balancer on a public network.</p>
</div>
<div>
<div class="familylinks">

2
docs/elb/umn/elb_faq_210313.html
View File

@ -1,7 +1,7 @@
<a name="elb_faq_210313"></a><a name="elb_faq_210313"></a>
<h1 class="topictitle1">What Is the Difference Between the Bandwidth Included in Each Specification of a Dedicated Load Balancer and the Bandwidth of an EIP?</h1>
<div id="body0000001242629073"><p id="elb_faq_210313__p491192211191">The bandwidth included in the specifications of dedicated load balancers is the maximum value of the total inbound and outbound traffic of the load balancer. The bandwidth of the EIP bound to the load balancer is the limit for traffic required by the clients to access the load balancer.</p>
<div id="body0000001242629073"><p id="elb_faq_210313__p491192211191">The bandwidth included in the specifications of dedicated load balancers is the upper limit of the inbound or the outbound traffic. The bandwidth of the EIP bound to the load balancer is the limit for traffic required by the clients to access the load balancer.</p>
</div>
<div>
<div class="familylinks">

2
docs/elb/umn/elb_faq_210409.html
View File

@ -1,7 +1,7 @@
<a name="elb_faq_210409"></a><a name="elb_faq_210409"></a>
<h1 class="topictitle1">Why Can't I Select the Target Backend Server Group When Adding or Modifying a Listener?</h1>
<div id="body0000001145044196"><p id="elb_faq_210409__p8060118">The backend server group's protocol (backend protocol) you want to select is not supported by the listener's protocol (frontend protocol). There are some constraints on the backend protocol when you associate a backend server group with a listener.</p>
<div id="body0000001145044196"><p id="elb_faq_210409__p8060118">The backend server group's protocol (backend protocol) you want to select is not supported by the listener protocol (frontend protocol). There are some constraints on the backend protocol when you associate a backend server group with a listener.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_faq_210409__table158021438173312" width="100%" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Frontend and backend protocols of dedicated load balancers</caption><thead align="left"><tr id="elb_faq_210409__row1580353819330"><th align="left" class="cellrowborder" valign="top" width="40.36%" id="mcps1.3.2.2.3.1.1"><p id="elb_faq_210409__p1480319381335">Frontend Protocol</p>
</th>

2
docs/elb/umn/elb_faq_210805.html
View File

@ -1,7 +1,7 @@
<a name="elb_faq_210805"></a><a name="elb_faq_210805"></a>
<h1 class="topictitle1">Why Can't I Add a Forwarding Policy to a Listener?</h1>
<div id="body0000001149807010"><p id="elb_faq_210805__p8060118">Check the listener's protocol.</p>
<div id="body0000001149807010"><p id="elb_faq_210805__p8060118">Check the listener protocol.</p>
<p id="elb_faq_210805__p119571916171914">Forwarding policies can only be added to HTTP and HTTPS listeners.</p>
</div>
<div>

277
docs/elb/umn/elb_lb_000006.html
View File

File diff suppressed because it is too large Load Diff

11
docs/elb/umn/elb_lb_000010.html
View File

@ -1,12 +1,17 @@
<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">You can change the private IPv4 IP address and IPv6 IP address bound to each load balancer.</p>
<p id="elb_lb_000010__en-us_topic_0172882190_p169881698186">Only dedicated load balancers support this function.</p>
<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__p1980852215207">You can change the private IPv4 address and IPv6 address bound to a load balancer.</p>
<ul id="elb_lb_000010__ul02281219182110"><li id="elb_lb_000010__li1622841972114">You can change the private IPv4 address into another IPv4 IP address in the current subnet or other subnets.</li><li id="elb_lb_000010__li113175442117">You can change the IPv6 address into another IPv6 IP address in other subnets.</li></ul>
<div class="note" id="elb_lb_000010__note16305618181810"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_lb_000010__p10169101571911">You can only change the IP address bound to a dedicated load balancer.</p>
</div></div>
</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_image762510132322" src="en-us_image_0000001417088430.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> &gt; <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> &gt; <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>
<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__image1457281761912" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_lb_000010__li83736197297">Hover on <span><img id="elb_lb_000010__image113066197191" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_lb_000010__b630613199193">Service List</strong> and choose <strong id="elb_lb_000010__b53081819131919">Network</strong> &gt; <strong id="elb_lb_000010__b20309141917196">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">Load Balancers</strong> 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> &gt; <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 assign 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 class="section" id="elb_lb_000010__section12802593153"><h4 class="sectiontitle">Changing an IPv6 Address</h4><ol id="elb_lb_000010__ol1277216158167"><li id="elb_lb_000010__li15772915141611">Log in to the management console.</li><li id="elb_lb_000010__li6772151561615">In the upper left corner of the page, click <span><img id="elb_lb_000010__image1489319221190" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_lb_000010__li10772121510167">Hover on <span><img id="elb_lb_000010__image1973614248192" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_lb_000010__b3736152491916">Service List</strong> and choose <strong id="elb_lb_000010__b273712491910">Network</strong> &gt; <strong id="elb_lb_000010__b1739224191914">Elastic Load Balancing</strong>.</li><li id="elb_lb_000010__li12772141531618">On the <strong id="elb_lb_000010__b61131815124915">Load Balancers</strong> page, locate the load balancer whose IP address you want to change, and click <strong id="elb_lb_000010__b011481516492">More</strong> &gt; <strong id="elb_lb_000010__b111431594910">Change IPv6 Address</strong> in the <strong id="elb_lb_000010__b81141115184916">Operation</strong> column.</li><li id="elb_lb_000010__li277218150168">In the <strong id="elb_lb_000010__b2028921812494">Change IPv6 Address</strong> dialog box, select a different subnet where the IP address resides and specify the IP address.<p id="elb_lb_000010__p718465161719">The system will automatically assign an IPv6 address to the load balancer from the subnet you select.</p>
</li><li id="elb_lb_000010__li2772161591613">Click <strong id="elb_lb_000010__b3834172318493">OK</strong>.</li></ol>
</div>
</div>
<div>
<div class="familylinks">

19
docs/elb/umn/elb_lb_000011.html Normal file
View File

@ -0,0 +1,19 @@
<a name="elb_lb_000011"></a><a name="elb_lb_000011"></a>
<h1 class="topictitle1">Adding to or Removing from an IPv6 Shared Bandwidth</h1>
<div id="body8662426"><div class="section" id="elb_lb_000011__en-us_topic_0195284111_section57040304257"><h4 class="sectiontitle">Scenarios</h4><p id="elb_lb_000011__en-us_topic_0195284111_p9663124616522">After you bind an IPv6 address to a <span id="elb_lb_000011__ph19311514345">dedicated load balancer</span>, you can add the load balancer to a shared bandwidth to enable it to route requests over the Internet. After you are finished with the shared bandwidth, you can remove the load balancer from the shared bandwidth, so that it can only route requests within a VPC.</p>
</div>
<div class="section" id="elb_lb_000011__en-us_topic_0195284111_section6757112293418"><h4 class="sectiontitle">Adding to an IPv6 Shared Bandwidth</h4><ol id="elb_lb_000011__en-us_topic_0195284111_ol12841946133714"><li id="elb_lb_000011__en-us_topic_0195284111_li1609750152920">Log in to the management console.</li><li id="elb_lb_000011__en-us_topic_0195284111_en-us_topic_0167652100_li66461182152949">In the upper left corner of the page, click <span><img id="elb_lb_000011__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_lb_000011__li78811227131312">Hover on <span><img id="elb_lb_000011__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_lb_000011__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_lb_000011__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_lb_000011__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_lb_000011__en-us_topic_0195284111_li132857467375">On the <strong id="elb_lb_000011__b186635914313">Load Balancers</strong> page, locate the load balancer that you want to add to a shared bandwidth, and click <strong id="elb_lb_000011__b1971125911432">More</strong> &gt; <strong id="elb_lb_000011__b8728593433">Add to IPv6 Shared Bandwidth</strong> in the <strong id="elb_lb_000011__b18721659154313">Operation</strong> column.</li><li id="elb_lb_000011__en-us_topic_0195284111_li16285546193712">In the <strong id="elb_lb_000011__b269014415444">Add to IPv6 Shared Bandwidth</strong> dialog box, select the shared bandwidth to which you want to add the dedicated load balancer.<p id="elb_lb_000011__en-us_topic_0195284111_p193851641162814">If no shared bandwidths are available, buy one as prompted.</p>
</li><li id="elb_lb_000011__en-us_topic_0195284111_li1285146153710">Click <strong id="elb_lb_000011__en-us_topic_0195284111_b118532122503">OK</strong>.</li></ol>
</div>
<div class="section" id="elb_lb_000011__en-us_topic_0195284111_section6550103182516"><h4 class="sectiontitle">Removing from an IPv6 Shared Bandwidth</h4><ol id="elb_lb_000011__en-us_topic_0195284111_ol17550113132512"><li id="elb_lb_000011__en-us_topic_0195284111_li4516759173014">Log in to the management console.</li><li id="elb_lb_000011__en-us_topic_0195284111_li1492114294188">In the upper left corner of the page, click <span><img id="elb_lb_000011__en-us_topic_0240829509_image1542118117117_1" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_lb_000011__li98744126361">Hover on <span><img id="elb_lb_000011__en-us_topic_0167652100_image762510132322_1" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_lb_000011__en-us_topic_0167652100_b9121102522212_1">Service List</strong> and choose <strong id="elb_lb_000011__en-us_topic_0167652100_b61222025142217_1">Network</strong> &gt; <strong id="elb_lb_000011__en-us_topic_0167652100_b4124425142210_1">Elastic Load Balancing</strong>. </li><li id="elb_lb_000011__en-us_topic_0195284111_li7550183152517">On the <strong id="elb_lb_000011__en-us_topic_0195284111_b879142218419">Load Balancers</strong> page, locate the load balancer that you want to remove from a shared bandwidth, and click <strong id="elb_lb_000011__en-us_topic_0195284111_b18793922544">More</strong> &gt; <strong id="elb_lb_000011__en-us_topic_0195284111_b47958223416">Remove from IPv6 Shared Bandwidth</strong> in the <strong id="elb_lb_000011__en-us_topic_0195284111_b87977227418">Operation</strong> column.</li><li id="elb_lb_000011__en-us_topic_0195284111_li1655014313253">In the displayed dialog box, confirm the shared bandwidth from which you want to remove the load balancer.<div class="note" id="elb_lb_000011__en-us_topic_0195284111_note16835115125512"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_lb_000011__en-us_topic_0195284111_p942923195615">After the load balancer is removed from the shared bandwidth, the load balancer cannot route requests over the Internet.</p>
</div></div>
</li><li id="elb_lb_000011__en-us_topic_0195284111_li655033102512">Click <strong id="elb_lb_000011__en-us_topic_0195284111_b952392235519">Yes</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>

4
docs/elb/umn/elb_pro_0000.html
View File

@ -20,9 +20,11 @@
</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="elb_pro_0019.html">Quotas and Constraints</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="en-us_topic_0171274900.html">Permissions</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="en-us_topic_0195131496.html">Product Concepts</a></strong><br>
<li class="ulchildlink"><strong><a href="elb_pro_0210.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>

6
docs/elb/umn/elb_pro_0001.html
View File

@ -20,7 +20,7 @@
</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 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__en-us_topic_0164706624_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__en-us_topic_0164706624_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__en-us_topic_0164706624_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>
@ -30,7 +30,7 @@
</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 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__en-us_topic_0164706629_text174345265419">server</span>s to check whether they can process requests. If a backend <span id="elb_pro_0001__en-us_topic_0164706629_text442602317545">server</span> is detected as unhealthy, the load balancer stops routing requests to it. After the backend <span id="elb_pro_0001__en-us_topic_0164706629_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>
@ -74,7 +74,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0195131496.html">Product Concepts</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_pro_0210.html">Product Concepts</a></div>
</div>
</div>

4
docs/elb/umn/elb_pro_0002.html
View File

@ -4,7 +4,7 @@
<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 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_0000001747739852.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>
@ -16,7 +16,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0195131496.html">Product Concepts</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_pro_0210.html">Product Concepts</a></div>
</div>
</div>

12
docs/elb/umn/elb_pro_0003.html
View File

@ -1,21 +1,21 @@
<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>
<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_0000001794819721.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 have configured 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">Healthy 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 forwarding policies 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__p1829390191019">Dedicated load balancers support four load balancing algorithms: weighted round robin, weighted least connections, source IP hash, and connection ID. <span id="elb_pro_0003__en-us_topic_0236111231_ph17638109145919">Shared</span> load balancers support three load balancing algorithms: weighted round robin, weighted least connections, and source IP hash.</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__p1829390191019">Dedicated load balancers support weighted round robin, weighted least connections, source IP hash, and connection ID algorithms. <span id="elb_pro_0003__ph11921845184415">Shared</span> load balancers support weighted round robin, weighted least connections, and source IP hash algorithms.</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>
<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_0000001794660629.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>
<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_0000001794819729.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>
<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_0000001747380892.png"></span></div>
</li><li id="elb_pro_0003__li16686103235516">Connection ID: The connection ID in the packet is calculated using the consistent hash algorithm to obtain a specific value, and backend servers are numbered. The generated value determines to which backend server the requests are routed. This allows requests with different connection IDs to be routed to different backend servers and ensures that requests with the same connection ID are routed to the same backend server. This algorithm applies to QUIC requests.<div class="note" id="elb_pro_0003__en-us_topic_0236111231_note252295316188"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_pro_0003__en-us_topic_0236111231_p1452215533184">Currently, only dedicated load balancers support the Connection ID algorithm.</p>
</div></div>
<p id="elb_pro_0003__en-us_topic_0236111231_p175371320817"><a href="#elb_pro_0003__en-us_topic_0236111231_fig3381171135617">Figure 5</a> shows an example of how requests are distributed using the connection ID algorithm. Two backend servers are in the same AZ and have the same weight. If backend server 01 has processed a request from client A, the load balancer will route new requests from client A to backend server 01.</p>
<div class="fignone" id="elb_pro_0003__en-us_topic_0236111231_fig3381171135617"><a name="elb_pro_0003__en-us_topic_0236111231_fig3381171135617"></a><a name="en-us_topic_0236111231_fig3381171135617"></a><span class="figcap"><b>Figure 5 </b>Traffic distribution using the connection ID algorithm</span><br><span><img id="elb_pro_0003__en-us_topic_0236111231_image11599531801" src="en-us_image_0000001205894887.png"></span></div>
<div class="fignone" id="elb_pro_0003__en-us_topic_0236111231_fig3381171135617"><a name="elb_pro_0003__en-us_topic_0236111231_fig3381171135617"></a><a name="en-us_topic_0236111231_fig3381171135617"></a><span class="figcap"><b>Figure 5 </b>Traffic distribution using the connection ID algorithm</span><br><span><img id="elb_pro_0003__en-us_topic_0236111231_image11599531801" src="en-us_image_0000001747739776.png"></span></div>
</li></ul>
</div>
</div>

57
docs/elb/umn/elb_pro_0004.html
View File

File diff suppressed because it is too large Load Diff

16
docs/elb/umn/elb_pro_0005.html
View File

@ -1,11 +1,11 @@
<a name="elb_pro_0005"></a><a name="elb_pro_0005"></a>
<h1 class="topictitle1">Product Advantages</h1>
<div id="body18191719"><div class="section" id="elb_pro_0005__section106161345824"><h4 class="sectiontitle">Advantages of Dedicated Load Balancers</h4><ul id="elb_pro_0005__ul4438681418511"><li id="elb_pro_0005__li61386558161449">Robust performance<p id="elb_pro_0005__p6263149193913"><a name="elb_pro_0005__li61386558161449"></a><a name="li61386558161449"></a>Each dedicated load balancer has exclusive use of isolated resources, meeting your requirements for handling a massive number of requests. A single dedicated load balancer deployed in one AZ can handle up to 20 million concurrent connections.</p>
<p id="elb_pro_0005__p41704924161458">If you deploy a dedicated load balancer in multiple AZs, its performance such as the number of new connections and the number of concurrent connections will multiply. For example, if you deploy a dedicated load balancer in two AZs, it can handle up to 40 million concurrent connections.</p>
<div class="note" id="elb_pro_0005__note1439316386124"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_pro_0005__ul923217451122"><li id="elb_pro_0005__li17232345111210">If requests are from the Internet, the load balancer in each AZ you select routes the requests based on source IP addresses. If you deploy a load balancer in two AZs, the requests the load balancers can handle will be doubled.</li><li id="elb_pro_0005__li0765191117216">For requests from a private network:<ul id="elb_pro_0005__ul187611211172118"><li id="elb_pro_0005__li13767152811815">If clients are in an AZ you have selected when you create the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer is unhealthy, requests are distributed by the load balancer in another AZ you have selected.<p id="elb_pro_0005__p93011631387"><a name="elb_pro_0005__li13767152811815"></a><a name="li13767152811815"></a>If the load balancer is healthy but the connections that the load balancer need to handle exceed the amount defined in the specifications, service may be interrupted. To address this issue, you need upgrade specifications. </p>
</li><li id="elb_pro_0005__li18762161119217">If clients are in an AZ that is not selected when you create the load balancer, requests are distributed by the load balancer in each AZ you select based on source IP addresses.</li></ul>
</li></ul>
<div id="body18191719"><div class="section" id="elb_pro_0005__section106161345824"><h4 class="sectiontitle">Advantages of Dedicated Load Balancers</h4><ul id="elb_pro_0005__ul4438681418511"><li id="elb_pro_0005__li61386558161449">Robust performance<p id="elb_pro_0005__p6263149193913"><a name="elb_pro_0005__li61386558161449"></a><a name="li61386558161449"></a>Each load balancer has exclusive use of isolated resources, meeting your requirements for handling a massive number of requests. A single load balancer deployed in one AZ can handle up to 20 million concurrent connections.</p>
<p id="elb_pro_0005__p41704924161458">If you deploy a load balancer in multiple AZs, its performance such as the number of new connections and the number of concurrent connections will multiply. For example, if you deploy a dedicated load balancer in two AZs, it can handle up to 40 million concurrent connections.</p>
<div class="note" id="elb_pro_0005__note1439316386124"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_pro_0005__ul923217451122"><li id="elb_pro_0005__li17232345111210">If requests are from the Internet, the load balancer in each AZ you select routes the requests based on source IP addresses. If you deploy a load balancer in two AZs, the requests the load balancers can handle will be doubled.</li><li id="elb_pro_0005__li0765191117216">For requests from a private network:<ul id="elb_pro_0005__ul187611211172118"><li id="elb_pro_0005__li13767152811815">If clients are in an AZ you have selected when you created the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer becomes unavailable, requests are distributed by the load balancer in another AZ you have selected.<p id="elb_pro_0005__p93011631387"><a name="elb_pro_0005__li13767152811815"></a><a name="li13767152811815"></a>If the load balancer is available but the connections that the load balancer needs to handle exceed the amount defined in the specifications, service may be interrupted. To address this issue, you need upgrade specifications. </p>
</li><li id="elb_pro_0005__li18762161119217">If clients are in an AZ that is not selected when you created the load balancer, requests are distributed by the load balancer in each AZ you select based on source IP addresses.</li></ul>
</li><li id="elb_pro_0005__li147061182517">If clients are in a VPC that is different from where the load balancer works, the load balancer in the AZ where the original VPC subnet resides routes the requests. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ.</li></ul>
</div></div>
</li><li id="elb_pro_0005__li910139118614">High availability<p id="elb_pro_0005__p1480365618614"><a name="elb_pro_0005__li910139118614"></a><a name="li910139118614"></a>ELB can route traffic uninterruptedly. If your servers in one AZ are unhealthy, it automatically routes traffic to healthy servers in other AZs. ELB provides a comprehensive health check system to ensure that incoming traffic is routed only to healthy backend servers, improving the availability of your applications.</p>
</li><li id="elb_pro_0005__li6423824716">Ultra-high security<p id="elb_pro_0005__p16773129816"><a name="elb_pro_0005__li6423824716"></a><a name="li6423824716"></a>ELB supports TLS 1.3 and can route HTTPS requests to backend servers. You can select security policies or customize security policies that fit your security requirements.</p>
@ -15,11 +15,11 @@
</li><li id="elb_pro_0005__li3657268018631">Ease-of-use<p id="elb_pro_0005__p6071866818631"><a name="elb_pro_0005__li3657268018631"></a><a name="li3657268018631"></a>ELB provides a diverse set of algorithms that allow you to configure different traffic routing policies to meet your requirements while keeping deployments simple.</p>
</li></ul>
</div>
<div class="section" id="elb_pro_0005__section956154410326"><h4 class="sectiontitle">Advantages of <span id="elb_pro_0005__ph1618614416413">Shared</span> Load Balancers</h4><ul id="elb_pro_0005__ul13561449326"><li id="elb_pro_0005__li9567443327">High availability<p id="elb_pro_0005__p756544163210"><a name="elb_pro_0005__li9567443327"></a><a name="li9567443327"></a><span id="elb_pro_0005__ph17252846245">Shared</span> load balancers can route traffic across AZs, ensuring that your services are uninterrupted. If servers in an AZ are unhealthy, ELB automatically routes traffic to healthy servers in other AZs. <span id="elb_pro_0005__ph126614207246">Shared</span> load balancers provide a comprehensive health check mechanism to ensure that incoming traffic is routed to only healthy backend servers, improving the availability of your applications.</p>
<div class="fignone" id="elb_pro_0005__fig20561944123219"><span class="figcap"><b>Figure 1 </b>High availability</span><br><span><img class="vsd" id="elb_pro_0005__image756204417322" src="en-us_image_0000001200220428.png"></span></div>
<div class="section" id="elb_pro_0005__section956154410326"><h4 class="sectiontitle">Advantages of <span id="elb_pro_0005__ph1356164414328">Shared</span> Load Balancers</h4><ul id="elb_pro_0005__ul13561449326"><li id="elb_pro_0005__li9567443327">High availability<p id="elb_pro_0005__p756544163210"><a name="elb_pro_0005__li9567443327"></a><a name="li9567443327"></a><span id="elb_pro_0005__ph17252846245">Shared</span> load balancers can route traffic across AZs, ensuring that your services are uninterrupted. If servers in an AZ are unhealthy, ELB automatically routes traffic to healthy servers in other AZs. <span id="elb_pro_0005__ph126614207246">Shared</span> load balancers provide a comprehensive health check mechanism to ensure that incoming traffic is routed to only healthy backend servers, improving the availability of your applications.</p>
<div class="fignone" id="elb_pro_0005__fig20561944123219"><span class="figcap"><b>Figure 1 </b>High availability</span><br><span><img class="vsd" id="elb_pro_0005__image756204417322" src="en-us_image_0000001794660657.png"></span></div>
</li><li id="elb_pro_0005__li356114417328">Multiple protocols<p id="elb_pro_0005__p185674414323"><a name="elb_pro_0005__li356114417328"></a><a name="li356114417328"></a>ELB supports TCP, UDP, HTTP, and HTTPS protocols to route requests to different types of applications.</p>
</li><li id="elb_pro_0005__li135694417324">Ease-of-use<p id="elb_pro_0005__p1656104453217"><a name="elb_pro_0005__li135694417324"></a><a name="li135694417324"></a><span id="elb_pro_0005__ph10613303257">Shared</span> load balancers provide a diverse set of algorithms that allow you to configure different traffic routing policies to meet your requirements while keeping deployments simple.</p>
</li><li id="elb_pro_0005__li85612449326">High reliability<p id="elb_pro_0005__p1456194433215"><a name="elb_pro_0005__li85612449326"></a><a name="li85612449326"></a><span id="elb_pro_0005__ph1790215558512">Shared</span> load balancers can be deployed across AZs and can distribute traffic more evenly.</p>
</li><li id="elb_pro_0005__li85612449326">High reliability<p id="elb_pro_0005__p1456194433215"><a name="elb_pro_0005__li85612449326"></a><a name="li85612449326"></a>Shared load balancers are deployed in two AZs by default and can distribute traffic more evenly.</p>
</li></ul>
</div>
</div>

8
docs/elb/umn/elb_pro_0006.html
View File

@ -3,18 +3,18 @@
<h1 class="topictitle1">Application Scenarios</h1>
<div id="body1516093773361"><div class="section" id="elb_pro_0006__section747414212515"><h4 class="sectiontitle">Heavy-Traffic Applications</h4><p id="elb_pro_0006__p1344111419235">For an application with heavy traffic, such as a large portal or mobile app store, ELB evenly distributes incoming traffic to multiple backend servers, balancing the load while ensuring steady performance.</p>
<p id="elb_pro_0006__p27855038171257">Sticky sessions ensure that requests from one client are always forwarded to the same backend server for fast processing.</p>
<div class="fignone" id="elb_pro_0006__fig145320429220"><span class="figcap"><b>Figure 1 </b>Session stickiness</span><br><span><img class="vsd" id="elb_pro_0006__image7238166114817" src="en-us_image_0202102748.png"></span></div>
<div class="fignone" id="elb_pro_0006__fig145320429220"><span class="figcap"><b>Figure 1 </b>Session stickiness</span><br><span><img class="vsd" id="elb_pro_0006__image7238166114817" src="en-us_image_0000001747739756.png"></span></div>
</div>
<div class="section" id="elb_pro_0006__section1151610117243"><h4 class="sectiontitle">Applications with Predictable Peaks and Troughs in Traffic</h4><p id="elb_pro_0006__p5408524171345">For an application that has predictable peaks and troughs in traffic volumes, ELB works with Auto Scaling to add or remove backend servers to keep up with changing demands. An example is flash sales, during which application traffic spikes in a short period. ELB can work with Auto Scaling to run only the required number of backend servers to handle the load of your application.</p>
<div class="fignone" id="elb_pro_0006__fig1927134415176"><span class="figcap"><b>Figure 2 </b>Flexible scalability</span><br><span><img class="vsd" id="elb_pro_0006__image533212444485" src="en-us_image_0198606821.png"></span></div>
<div class="fignone" id="elb_pro_0006__fig1927134415176"><span class="figcap"><b>Figure 2 </b>Flexible scalability</span><br><span><img class="vsd" id="elb_pro_0006__image533212444485" src="en-us_image_0000001747380872.png"></span></div>
</div>
<div class="section" id="elb_pro_0006__section430324872511"><h4 class="sectiontitle">Zero SPOFs</h4><p id="elb_pro_0006__p66668867171438">ELB routinely performs health checks on backend servers to monitor their health. If any backend server is detected unhealthy, ELB will not route requests to this server until it recovers.</p>
<p id="elb_pro_0006__p31765646171442">This makes ELB a good choice for running services that require high reliability, such as websites and toll collection systems.</p>
<div class="fignone" id="elb_pro_0006__fig158310309337"><span class="figcap"><b>Figure 3 </b>Eliminating SPOFs</span><br><span><img class="vsd" id="elb_pro_0006__image762485204912" src="en-us_image_0198606826.png"></span></div>
<div class="fignone" id="elb_pro_0006__fig158310309337"><span class="figcap"><b>Figure 3 </b>Eliminating SPOFs</span><br><span><img class="vsd" id="elb_pro_0006__image762485204912" src="en-us_image_0000001794660601.png"></span></div>
</div>
<div class="section" id="elb_pro_0006__section220419419265"><h4 class="sectiontitle">Cross-AZ Load Balancing</h4><p id="elb_pro_0006__p4089950317155">ELB can distribute traffic across AZs. When an AZ becomes faulty, ELB distributes traffic across backend servers in other AZs.</p>
<p id="elb_pro_0006__p99690131295">ELB is ideal for banking, policing, and large application systems that require high availability.</p>
<div class="fignone" id="elb_pro_0006__fig539117712156"><span class="figcap"><b>Figure 4 </b>Traffic distribution to servers in one or more AZs</span><br><span><img class="vsd" id="elb_pro_0006__image9155182417491" src="en-us_image_0198606850.png"></span></div>
<div class="fignone" id="elb_pro_0006__fig539117712156"><span class="figcap"><b>Figure 4 </b>Traffic distribution to servers in one or more AZs</span><br><span><img class="vsd" id="elb_pro_0006__image9155182417491" src="en-us_image_0000001794819713.png"></span></div>
</div>
</div>
<div>

211
docs/elb/umn/elb_pro_0019.html Normal file
View File

File diff suppressed because it is too large Load Diff

6
docs/elb/umn/elb_pro_01_0004.html
View File

@ -3,10 +3,10 @@
<h1 class="topictitle1">Load Balancing on a Public or Private Network</h1>
<div id="body8662426"><p id="elb_pro_01_0004__p66271919200">A load balancer can work on either a public or private network.</p>
<div class="section" id="elb_pro_01_0004__en-us_topic_0145103412_section3178376293631"><h4 class="sectiontitle">Load Balancing on a Public Network</h4><p id="elb_pro_01_0004__en-us_topic_0145103412_p4457188315333">You can bind an EIP to a load balancer so that it can receive requests from the Internet and route the requests to backend servers.</p>
<div class="fignone" id="elb_pro_01_0004__en-us_topic_0145103412_fig18748172215710"><span class="figcap"><b>Figure 1 </b>Load balancing on a public network</span><br><span><img class="vsd" id="elb_pro_01_0004__en-us_topic_0145103412_image15180012445" src="en-us_image_0000001135576038.png"></span></div>
<div class="fignone" id="elb_pro_01_0004__en-us_topic_0145103412_fig18748172215710"><span class="figcap"><b>Figure 1 </b>Load balancing on a public network</span><br><span><img class="vsd" id="elb_pro_01_0004__en-us_topic_0145103412_image15180012445" src="en-us_image_0000001794819705.png"></span></div>
</div>
<div class="section" id="elb_pro_01_0004__en-us_topic_0145103412_section1746893310736"><h4 class="sectiontitle">Load Balancing on a Private Network</h4><p id="elb_pro_01_0004__en-us_topic_0145103412_p4740880415353">A load balancer has only a private IP address to receive requests from clients in a VPC and route the requests to backend servers in the same VPC. This type of load balancer can only be accessed in a VPC.</p>
<div class="fignone" id="elb_pro_01_0004__en-us_topic_0145103412_fig8597926577"><span class="figcap"><b>Figure 2 </b>Load balancing on a private network</span><br><span><img class="vsd" id="elb_pro_01_0004__en-us_topic_0145103412_image189652253468" src="en-us_image_0000001181535567.png"></span></div>
<div class="section" id="elb_pro_01_0004__en-us_topic_0145103412_section1746893310736"><h4 class="sectiontitle">Load Balancing on a Private Network</h4><p id="elb_pro_01_0004__en-us_topic_0145103412_p4740880415353">A load balancer has only a private IP address to receive requests from clients in a VPC and routes the requests to backend servers in the same VPC. This type of load balancer can only be accessed in a VPC.</p>
<div class="fignone" id="elb_pro_01_0004__en-us_topic_0145103412_fig8597926577"><span class="figcap"><b>Figure 2 </b>Load balancing on a private network</span><br><span><img class="vsd" id="elb_pro_01_0004__en-us_topic_0145103412_image189652253468" src="en-us_image_0000001747739760.png"></span></div>
</div>
<div class="section" id="elb_pro_01_0004__section267291041110"><h4 class="sectiontitle">Network Types and Load Balancers</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_pro_01_0004__table8712177144719" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Dedicated load balancers and their network types</caption><thead align="left"><tr id="elb_pro_01_0004__row671217719475"><th align="left" class="cellrowborder" valign="top" width="20.01200120012001%" id="mcps1.3.4.2.2.4.1.1"><p id="elb_pro_01_0004__p97123714471">Load Balancer Type</p>

2
docs/elb/umn/en-us_topic_0195131496.html → docs/elb/umn/elb_pro_0210.html
View File

@ -1,4 +1,4 @@
<a name="en-us_topic_0195131496"></a><a name="en-us_topic_0195131496"></a>
<a name="elb_pro_0210"></a><a name="elb_pro_0210"></a>
<h1 class="topictitle1">Product Concepts</h1>
<div id="body1569552539941"></div>

4
docs/elb/umn/elb_qs_0001.html
View File

@ -3,9 +3,9 @@
<h1 class="topictitle1">Overview</h1>
<div id="body1567691173479"><p id="elb_qs_0001__p549023110456">To use ELB to distribute traffic across backend servers, you need to create a dedicated load balancer or <span id="elb_qs_0001__ph158971834164518">a shared</span> load balancer.</p>
<p id="elb_qs_0001__p8060118">Two examples are given to show how you can quickly create <span id="elb_qs_0001__ph1645535710329">a shared</span> load balancer to distribute incoming traffic across backend servers.</p>
<ul id="elb_qs_0001__ul1475054835218"><li id="elb_qs_0001__li9750748135219"><strong id="elb_qs_0001__b6873144712196">Entry level</strong>: An application deployed on separated ECSs needs to handle a large number of requests. Health checks are required to monitor the health of the servers to ensure that incoming traffic is routed only to healthy servers to eliminate SPOFs and improve service availability.<div class="fignone" id="elb_qs_0001__fig742033425910"><span class="figcap"><b>Figure 1 </b>Entry level</span><br><span><img class="vsd" id="elb_qs_0001__image171053318320" src="en-us_image_0198607819.png"></span></div>
<ul id="elb_qs_0001__ul1475054835218"><li id="elb_qs_0001__li9750748135219"><strong id="elb_qs_0001__b6873144712196">Entry level</strong>: An application deployed on separated ECSs needs to handle a large number of requests. Health checks are required to monitor the health of the servers to ensure that incoming traffic is routed only to healthy servers to eliminate SPOFs and improve service availability.<div class="fignone" id="elb_qs_0001__fig742033425910"><span class="figcap"><b>Figure 1 </b>Entry level</span><br><span><img class="vsd" id="elb_qs_0001__image171053318320" src="en-us_image_0000001794660637.png"></span></div>
<p id="elb_qs_0001__p275291135315">As the incoming traffic increases, you can add more <span id="elb_qs_0001__text7468955914">server</span>s to balance the load across backend servers.</p>
</li><li id="elb_qs_0001__li89701451819"><strong id="elb_qs_0001__b760175818196">Advanced level</strong>: An application deployed on separated servers uses one domain name but different URLs to provide services, and requests are routed to different servers based on the URLs. Forwarding policies are required to forward requests from different URLs to the servers in the corresponding backend server groups.<div class="fignone" id="elb_qs_0001__fig1797419417113"><span class="figcap"><b>Figure 2 </b>Advanced level</span><br><span><img class="vsd" id="elb_qs_0001__image1211651338" src="en-us_image_0198607873.png"></span></div>
</li><li id="elb_qs_0001__li89701451819"><strong id="elb_qs_0001__b760175818196">Advanced level</strong>: An application deployed on separated servers uses one domain name but different URLs to provide services, and requests are routed to different servers based on the URLs. Forwarding policies are required to forward requests from different URLs to the servers in the corresponding backend server groups.<div class="fignone" id="elb_qs_0001__fig1797419417113"><span class="figcap"><b>Figure 2 </b>Advanced level</span><br><span><img class="vsd" id="elb_qs_0001__image1211651338" src="en-us_image_0000001747380896.png"></span></div>
<p id="elb_qs_0001__p144871825123811">As the incoming traffic increases, you can add more backend servers to the two backend <span id="elb_qs_0001__text124874253385">server</span> groups. You can also configure health checks to monitor the health of backend <span id="elb_qs_0001__text1953021011224">server</span>s to ensure that incoming traffic is routed only to healthy backend <span id="elb_qs_0001__text17647819133720">server</span>s.</p>
</li></ul>
</div>

153
docs/elb/umn/elb_qs_0002.html
View File

File diff suppressed because it is too large Load Diff

179
docs/elb/umn/elb_qs_0003.html
View File

File diff suppressed because it is too large Load Diff

4
docs/elb/umn/elb_qs_0005.html
View File

@ -2,8 +2,8 @@
<h1 class="topictitle1">Process Flowchart</h1>
<div id="body0000001253135855"><p id="elb_qs_0005__p11155815125614"><a href="#elb_qs_0005__fig46765314196">Figure 1</a> shows how you can use basic functions of ELB to route requests when you are still new to ELB, and <a href="#elb_qs_0005__fig262625831911">Figure 2</a> shows how you can use domain name or URL-based forwarding of ELB to route requests more efficiently. </p>
<div class="fignone" id="elb_qs_0005__fig46765314196"><a name="elb_qs_0005__fig46765314196"></a><a name="fig46765314196"></a><span class="figcap"><b>Figure 1 </b>Getting started - entry level</span><br><span><img id="elb_qs_0005__image568185361914" src="en-us_image_0000001252868753.png"></span></div>
<div class="fignone" id="elb_qs_0005__fig262625831911"><a name="elb_qs_0005__fig262625831911"></a><a name="fig262625831911"></a><span class="figcap"><b>Figure 2 </b>Getting started - advanced level</span><br><span><img id="elb_qs_0005__image36261758131916" src="en-us_image_0000001253028753.png"></span></div>
<div class="fignone" id="elb_qs_0005__fig46765314196"><a name="elb_qs_0005__fig46765314196"></a><a name="fig46765314196"></a><span class="figcap"><b>Figure 1 </b>Getting started - entry level</span><br><span><img id="elb_qs_0005__image568185361914" src="en-us_image_0000001794660729.png"></span></div>
<div class="fignone" id="elb_qs_0005__fig262625831911"><a name="elb_qs_0005__fig262625831911"></a><a name="fig262625831911"></a><span class="figcap"><b>Figure 2 </b>Getting started - advanced level</span><br><span><img id="elb_qs_0005__image36261758131916" src="en-us_image_0000001747381000.png"></span></div>
</div>
<div>
<div class="familylinks">

10
docs/elb/umn/elb_ug_bq_0000.html
View File

@ -4,25 +4,25 @@
<div id="body1526970898002"><div class="section" id="elb_ug_bq_0000__section1143912015382"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_bq_0000__p1362702573816">If you have a large number of cloud resources, you can assign different tags to the resources to quickly identify them and use these tags to easily manage your resources.</p>
</div>
<div class="section" id="elb_ug_bq_0000__section1163718452455"><h4 class="sectiontitle">Adding a Tag to a Load Balancer</h4><p id="elb_ug_bq_0000__p16505195164615">You can add a tag to a load balancer in the following method:</p>
<ul id="elb_ug_bq_0000__ul28401728175019"><li id="elb_ug_bq_0000__li9839628155019">Add a tag when you create a load balancer.<p id="elb_ug_bq_0000__p108951505442"><a name="elb_ug_bq_0000__li9839628155019"></a><a name="li9839628155019"></a>For detailed operations, see <a href="elb_lb_000006.html">Creating a Dedicated Load Balancer</a> and <a href="en-us_topic_0015479967.html">Creating a Shared Load Balancer</a>.</p>
</li><li id="elb_ug_bq_0000__li583918282505">Add a tag to an existing load balancer.<ol id="elb_ug_bq_0000__ol11229133665417"><li id="elb_ug_bq_0000__li677391520332">Log in to the management console.</li><li id="elb_ug_bq_0000__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li83736197297">Hover on <span><img id="elb_ug_bq_0000__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_bq_0000__li1222911365545">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li7981103114568">Under <strong id="elb_ug_bq_0000__b84235270612121">Tags</strong>, click <strong id="elb_ug_bq_0000__b8423527061224">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li206491583010">In the <strong id="elb_ug_bq_0000__b2115587242165643">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b611835798165643">OK</strong>.<div class="note" id="elb_ug_bq_0000__note1649510311200"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul1459215541328"><li id="elb_ug_bq_0000__li3592854126">A maximum of 20 tags can be added to a load balancer.</li><li id="elb_ug_bq_0000__li1659275414213">Each tag is a key-value pair, and the tag key is unique.</li></ul>
<ul id="elb_ug_bq_0000__ul28401728175019"><li id="elb_ug_bq_0000__li9839628155019">Add a tag when you create a load balancer.<p id="elb_ug_bq_0000__p0711112119289"><a name="elb_ug_bq_0000__li9839628155019"></a><a name="li9839628155019"></a>For detailed operations, see <a href="elb_lb_000006.html">Creating a Dedicated Load Balancer</a> and <a href="en-us_topic_0015479967.html">Creating a Shared Load Balancer</a>.</p>
</li><li id="elb_ug_bq_0000__li583918282505">Add a tag to an existing load balancer.<ol id="elb_ug_bq_0000__ol11229133665417"><li id="elb_ug_bq_0000__li677391520332">Log in to the management console.</li><li id="elb_ug_bq_0000__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image35565756623028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li83736197297">Hover on <span><img id="elb_ug_bq_0000__image178568419323028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b62740478023028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b173622365723028">Network</strong> &gt; <strong id="elb_ug_bq_0000__b145758779423028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li1222911365545">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li7981103114568">Under <strong id="elb_ug_bq_0000__b84235270612121">Tags</strong>, click <strong id="elb_ug_bq_0000__b8423527061224">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li206491583010">In the <strong id="elb_ug_bq_0000__b2115587242165643">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b611835798165643">OK</strong>.<div class="note" id="elb_ug_bq_0000__note1649510311200"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul1459215541328"><li id="elb_ug_bq_0000__li3592854126">A maximum of 20 tags can be added to a load balancer.</li><li id="elb_ug_bq_0000__li1659275414213">Each tag is a key-value pair, and the tag key is unique.</li></ul>
</div></div>
</li></ol>
</li></ul>
</div>
<div class="section" id="elb_ug_bq_0000__section175469211735"><h4 class="sectiontitle">Adding a Tag to a Listener</h4><p id="elb_ug_bq_0000__p078516156810">You can add tags when you add listeners.</p>
<p id="elb_ug_bq_0000__p1868913231548">To add a tag to an existing listener, perform the following steps:</p>
<ol id="elb_ug_bq_0000__ol18792714101"><li id="elb_ug_bq_0000__li115212495820">Log in to the management console.</li><li id="elb_ug_bq_0000__li15529419589">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__en-us_topic_0240829509_image1542118117117_1" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li17301740102218">Hover on <span><img id="elb_ug_bq_0000__en-us_topic_0052569751_image762510132322_1" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b9121102522212_1">Service List</strong> and choose <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b61222025142217_1">Network</strong> &gt; <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b4124425142210_1">Elastic Load Balancing</strong>. </li><li id="elb_ug_bq_0000__li15101427161014">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li8487359151011">Click <strong id="elb_ug_bq_0000__b842352706163816">Listeners</strong>, locate the listener, and click its name.</li><li id="elb_ug_bq_0000__li8155171491312">Under <strong id="elb_ug_bq_0000__b842352706165356">Tags</strong>, click <strong id="elb_ug_bq_0000__b842352706165539">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li16111627151011">In the <strong id="elb_ug_bq_0000__b1101410959">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b61693239">OK</strong>.<div class="note" id="elb_ug_bq_0000__note12326124181515"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul332819417158"><li id="elb_ug_bq_0000__li932820411151">A maximum of 20 tags can be added to a listener.</li><li id="elb_ug_bq_0000__li132915415152">Each tag is a key-value pair, and the tag key is unique.</li></ul>
<ol id="elb_ug_bq_0000__ol18792714101"><li id="elb_ug_bq_0000__li115212495820">Log in to the management console.</li><li id="elb_ug_bq_0000__li15529419589">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image129670569320" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li17301740102218">Hover on <span><img id="elb_ug_bq_0000__image185212624323028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b80065074223028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b64618483823028">Network</strong> &gt; <strong id="elb_ug_bq_0000__b139029583023028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li15101427161014">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li8487359151011">Click <strong id="elb_ug_bq_0000__b842352706163816">Listeners</strong>, locate the listener, and click its name.</li><li id="elb_ug_bq_0000__li8155171491312">Under <strong id="elb_ug_bq_0000__b842352706165356">Tags</strong>, click <strong id="elb_ug_bq_0000__b842352706165539">Add Tag</strong>.</li><li id="elb_ug_bq_0000__li16111627151011">In the <strong id="elb_ug_bq_0000__b60865473">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b1610769486">OK</strong>.<div class="note" id="elb_ug_bq_0000__note12326124181515"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_bq_0000__ul332819417158"><li id="elb_ug_bq_0000__li932820411151">A maximum of 20 tags can be added to a listener.</li><li id="elb_ug_bq_0000__li132915415152">Each tag is a key-value pair, and the tag key is unique.</li></ul>
</div></div>
</li></ol>
<p id="elb_ug_bq_0000__p38741451272"></p>
</div>
<div class="section" id="elb_ug_bq_0000__section1432939104616"><h4 class="sectiontitle">Modifying a Tag</h4><ol id="elb_ug_bq_0000__ol1698016422035"><li id="elb_ug_bq_0000__li1780018151587">Log in to the management console.</li><li id="elb_ug_bq_0000__li480015155581">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__en-us_topic_0240829509_image1542118117117_2" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li3915642514">Hover on <span><img id="elb_ug_bq_0000__en-us_topic_0052569751_image762510132322_2" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b9121102522212_2">Service List</strong> and choose <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b61222025142217_2">Network</strong> &gt; <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b4124425142210_2">Elastic Load Balancing</strong>. </li><li id="elb_ug_bq_0000__li69321144732">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li39326442032">Click <strong id="elb_ug_bq_0000__b14429401261262">Tags</strong>, select the tag to be edited, and click <strong id="elb_ug_bq_0000__b8423527061276">Edit</strong> in the <strong id="elb_ug_bq_0000__b8423527061273">Operation</strong> column. In the <strong id="elb_ug_bq_0000__b8730353761262">Edit Tag</strong> dialog box, change the tag value.<div class="note" id="elb_ug_bq_0000__note1042524418619"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_bq_0000__p34251844869">The tag key cannot be changed.</p>
<div class="section" id="elb_ug_bq_0000__section1432939104616"><h4 class="sectiontitle">Modifying a Tag</h4><ol id="elb_ug_bq_0000__ol1698016422035"><li id="elb_ug_bq_0000__li1780018151587">Log in to the management console.</li><li id="elb_ug_bq_0000__li480015155581">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image200716150023028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li3915642514">Hover on <span><img id="elb_ug_bq_0000__image161362657223028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b59554934223028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b186906152123028">Network</strong> &gt; <strong id="elb_ug_bq_0000__b167678064123028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li69321144732">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li39326442032">Click <strong id="elb_ug_bq_0000__b14429401261262">Tags</strong>, select the tag to be edited, and click <strong id="elb_ug_bq_0000__b8423527061276">Edit</strong> in the <strong id="elb_ug_bq_0000__b8423527061273">Operation</strong> column. In the <strong id="elb_ug_bq_0000__b8730353761262">Edit Tag</strong> dialog box, change the tag value.<div class="note" id="elb_ug_bq_0000__note1042524418619"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_bq_0000__p34251844869">The tag key cannot be changed.</p>
</div></div>
</li><li id="elb_ug_bq_0000__li81253361963">Click <strong id="elb_ug_bq_0000__b842352706105230">OK</strong>.</li></ol>
<p id="elb_ug_bq_0000__p167794245223">The operations for modifying a listener tag are not detailed here. Refer to the operations of modifying a load balancer tag.</p>
</div>
<div class="section" id="elb_ug_bq_0000__section1864818172465"><h4 class="sectiontitle">Deleting a Tag</h4><ol id="elb_ug_bq_0000__ol14211132811713"><li id="elb_ug_bq_0000__li5274142820589">Log in to the management console.</li><li id="elb_ug_bq_0000__li72741528155818">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__en-us_topic_0240829509_image1542118117117_3" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li1168141913315">Hover on <span><img id="elb_ug_bq_0000__en-us_topic_0052569751_image762510132322_3" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b9121102522212_3">Service List</strong> and choose <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b61222025142217_3">Network</strong> &gt; <strong id="elb_ug_bq_0000__en-us_topic_0052569751_b4124425142210_3">Elastic Load Balancing</strong>. </li><li id="elb_ug_bq_0000__li1521392816713">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li182134280714">Click <strong id="elb_ug_bq_0000__b164336334112833">Tags</strong>, select the tag to be deleted, and click <strong id="elb_ug_bq_0000__b99785180512833">Delete</strong> in the <strong id="elb_ug_bq_0000__b30597287512833">Operation</strong> column.</li><li id="elb_ug_bq_0000__li1495110710912">In the <strong id="elb_ug_bq_0000__b146925785212912">Delete Tag</strong> dialog box, click <strong id="elb_ug_bq_0000__b84235270612924">Yes</strong>.</li></ol>
<div class="section" id="elb_ug_bq_0000__section1864818172465"><h4 class="sectiontitle">Deleting a Tag</h4><ol id="elb_ug_bq_0000__ol14211132811713"><li id="elb_ug_bq_0000__li5274142820589">Log in to the management console.</li><li id="elb_ug_bq_0000__li72741528155818">In the upper left corner of the page, click <span><img id="elb_ug_bq_0000__image80996007723028" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_bq_0000__li1168141913315">Hover on <span><img id="elb_ug_bq_0000__image78427240023028" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_bq_0000__b4948487623028">Service List</strong> and choose <strong id="elb_ug_bq_0000__b5594039123028">Network</strong> &gt; <strong id="elb_ug_bq_0000__b47076291323028">Elastic Load Balancing</strong>.</li><li id="elb_ug_bq_0000__li1521392816713">Locate the load balancer and click its name.</li><li id="elb_ug_bq_0000__li182134280714">Click <strong id="elb_ug_bq_0000__b164336334112833">Tags</strong>, select the tag to be deleted, and click <strong id="elb_ug_bq_0000__b99785180512833">Delete</strong> in the <strong id="elb_ug_bq_0000__b30597287512833">Operation</strong> column.</li><li id="elb_ug_bq_0000__li1495110710912">In the displayed dialog box, click <strong id="elb_ug_bq_0000__b84235270612924">Yes</strong>.</li></ol>
<p id="elb_ug_bq_0000__p836323472418">The operations for deleting a listener tag are not detailed here. Refer to the operations of deleting a load balancer tag.</p>
</div>
</div>

4
docs/elb/umn/elb_ug_fz_0003_01.html
View File

@ -3,14 +3,14 @@
<h1 class="topictitle1">Network Traffic Paths</h1>
<div id="body8662426"><p id="elb_ug_fz_0003_01__en-us_topic_0166333709_p6741227008">Load balancers communicate with backend <span id="elb_ug_fz_0003_01__en-us_topic_0166333709_text12861016154612">server</span>s over a private network.</p>
<ul id="elb_ug_fz_0003_01__en-us_topic_0166333709_ul1783718431264"><li id="elb_ug_fz_0003_01__en-us_topic_0166333709_li20837643172615">If backend <span id="elb_ug_fz_0003_01__en-us_topic_0166333709_text962105024612">server</span>s process only requests routed from load balancers, there is no need to assign EIPs or create NAT gateways.</li><li id="elb_ug_fz_0003_01__en-us_topic_0166333709_li8561715368">If backend <span id="elb_ug_fz_0003_01__en-us_topic_0166333709_text127813559469">server</span>s need to provide Internet-accessible services or access the Internet, you must assign EIPs or create NAT gateways.</li></ul>
<div class="section" id="elb_ug_fz_0003_01__en-us_topic_0166333709_section12884538197"><h4 class="sectiontitle">Inbound Network Traffic Paths</h4><div class="p" id="elb_ug_fz_0003_01__en-us_topic_0166333709_p1730711354418">The listeners' configurations determine how load balancers distribute incoming traffic.<div class="fignone" id="elb_ug_fz_0003_01__en-us_topic_0166333709_fig1920512561518"><span class="figcap"><b>Figure 1 </b>Inbound network traffic</span><br><span><img class="vsd" id="elb_ug_fz_0003_01__en-us_topic_0166333709_image5021893716" src="en-us_image_0000001181376003.png"></span></div>
<div class="section" id="elb_ug_fz_0003_01__en-us_topic_0166333709_section12884538197"><h4 class="sectiontitle">Inbound Network Traffic Paths</h4><div class="p" id="elb_ug_fz_0003_01__en-us_topic_0166333709_p1730711354418">The listeners' configurations determine how load balancers distribute incoming traffic.<div class="fignone" id="elb_ug_fz_0003_01__en-us_topic_0166333709_fig1920512561518"><span class="figcap"><b>Figure 1 </b>Inbound network traffic</span><br><span><img class="vsd" id="elb_ug_fz_0003_01__en-us_topic_0166333709_image5021893716" src="en-us_image_0000001747739656.png"></span></div>
</div>
<div class="p" id="elb_ug_fz_0003_01__en-us_topic_0166333709_p10196154123714">When a listener uses TCP or UDP to receive incoming traffic:<ul id="elb_ug_fz_0003_01__en-us_topic_0166333709_ul863417283383"><li id="elb_ug_fz_0003_01__en-us_topic_0166333709_li12421739938">Incoming traffic is routed only through the LVS cluster.</li><li id="elb_ug_fz_0003_01__en-us_topic_0166333709_li3634172853812">The LVS cluster directly routes incoming traffic to backend <span id="elb_ug_fz_0003_01__text1363314253911">server</span>s using the load balancing algorithm you select when you add the listener.</li></ul>
</div>
<div class="p" id="elb_ug_fz_0003_01__en-us_topic_0166333709_p8342131514383">When a listener uses HTTP or HTTPS to receive incoming traffic:<ul id="elb_ug_fz_0003_01__en-us_topic_0166333709_ul208003244417"><li id="elb_ug_fz_0003_01__en-us_topic_0166333709_li380012244414">Incoming traffic is routed first to the LVS cluster, then to the Nginx cluster, and finally across backend <span id="elb_ug_fz_0003_01__en-us_topic_0166333709_text19960153384810">server</span>s.</li><li id="elb_ug_fz_0003_01__en-us_topic_0166333709_li97801814194412">For HTTPS traffic, the Nginx cluster validates certificates and decrypts data packets before distributing the traffic across backend servers using HTTP.</li></ul>
</div>
</div>
<div class="section" id="elb_ug_fz_0003_01__en-us_topic_0166333709_section133601141145610"><h4 class="sectiontitle">Outbound Network Traffic Paths</h4><div class="p" id="elb_ug_fz_0003_01__en-us_topic_0166333709_p16360841125618">The outbound traffic is routed back the same way the traffic came in.<div class="fignone" id="elb_ug_fz_0003_01__en-us_topic_0166333709_fig7885192011517"><span class="figcap"><b>Figure 2 </b>Outbound network traffic</span><br><span><img class="vsd" id="elb_ug_fz_0003_01__en-us_topic_0166333709_image1079718394379" src="en-us_image_0000001135576398.png"></span></div>
<div class="section" id="elb_ug_fz_0003_01__en-us_topic_0166333709_section133601141145610"><h4 class="sectiontitle">Outbound Network Traffic Paths</h4><div class="p" id="elb_ug_fz_0003_01__en-us_topic_0166333709_p16360841125618">The outbound traffic is routed back the same way the traffic came in.<div class="fignone" id="elb_ug_fz_0003_01__en-us_topic_0166333709_fig7885192011517"><span class="figcap"><b>Figure 2 </b>Outbound network traffic</span><br><span><img class="vsd" id="elb_ug_fz_0003_01__en-us_topic_0166333709_image1079718394379" src="en-us_image_0000001794819605.png"></span></div>
<ul id="elb_ug_fz_0003_01__en-us_topic_0166333709_ul163609417566"><li id="elb_ug_fz_0003_01__li791381117196">Because the load balancer receives and responds to requests over the Internet, traffic transmission depends on the bandwidth, which is not limited by ELB. The load balancer communicates with backend servers over a private network.</li><li id="elb_ug_fz_0003_01__li8115174117209">If you have a NAT gateway, it receives and responds to incoming traffic. The NAT gateway has an EIP bound, through which backend servers can access the Internet and provide services accessible from the Internet. Although there is a restriction on the connections that can be processed by a NAT gateway, traffic transmission depends on the bandwidth</li><li id="elb_ug_fz_0003_01__en-us_topic_0166333709_li9346527125312">If each backend server has an EIP bound, they receive and respond to incoming traffic directly. Traffic transmission depends on the bandwidth.</li></ul>
</div>
</div>

28
docs/elb/umn/elb_ug_fz_0004.html
View File

@ -2,35 +2,35 @@
<h1 class="topictitle1">Preparations for Creating a Load Balancer</h1>
<div id="body1555913901701"><p id="elb_ug_fz_0004__p724713239412">Before creating a load balancer, you must plan its region, network, protocol, and backend servers.</p>
<div class="section" id="elb_ug_fz_0004__section12884538197"><h4 class="sectiontitle">Region</h4><div class="p" id="elb_ug_fz_0004__p1730711354418">When you select a region, note the following:<ul id="elb_ug_fz_0004__ul122945544419"><li id="elb_ug_fz_0004__li19327429145512">The region must be close to your users to reduce network latency and improve the download speed.</li><li id="elb_ug_fz_0004__li7475741155511"><span id="elb_ug_fz_0004__ph34814412554">Shared</span> load balancers cannot distribute traffic across regions. When creating <span id="elb_ug_fz_0004__ph52661119560">a shared</span> load balancer, select the same region as the backend servers.</li><li id="elb_ug_fz_0004__li15748513175618">Dedicated load balancers support adding backend servers across VPCs using the IP as a backend function. For details, see <a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a>.</li></ul>
<div class="section" id="elb_ug_fz_0004__section12884538197"><h4 class="sectiontitle">Region</h4><div class="p" id="elb_ug_fz_0004__p1730711354418">When you select a region, note the following:<ul id="elb_ug_fz_0004__ul122945544419"><li id="elb_ug_fz_0004__li19327429145512">The region must be close to your users to reduce network latency and improve the download speed.</li><li id="elb_ug_fz_0004__li7475741155511"><span id="elb_ug_fz_0004__ph1428172813214">Shared</span> load balancers cannot distribute traffic across regions. When creating a shared load balancer, select the same region as the backend servers.</li><li id="elb_ug_fz_0004__li15748513175618">Dedicated load balancers support adding backend servers across VPCs using the IP as a backend function. For details, see <a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a>.</li></ul>
</div>
</div>
<div class="section" id="elb_ug_fz_0004__section818284043213"><h4 class="sectiontitle">AZ</h4><p id="elb_ug_fz_0004__p8289152233211"><span id="elb_ug_fz_0004__ph128912215327">Dedicated load balancer</span>s can be deployed across AZs. If you select multiple AZs, a load balancer is created in each selected AZ.</p>
<p id="elb_ug_fz_0004__p134171339163317">Load balancers in these AZs work in active-active or multi-active mode and follow the proximity principle to route traffic. For example, traffic to backend servers in AZ 1 is distributed by the load balancer in AZ 1 or a load balancer in an AZ close to AZ 1.</p>
<p id="elb_ug_fz_0004__en-us_topic_0172664952_p39911823348">Select the AZ where backend servers reside to reduce network latency and improve access speed.</p>
<div class="section" id="elb_ug_fz_0004__section818284043213"><h4 class="sectiontitle">AZ</h4><p id="elb_ug_fz_0004__p8289152233211"><span id="elb_ug_fz_0004__ph15219124320582">Dedicated load balancers</span> can be deployed across AZs. If you select multiple AZs, a load balancer is created in each selected AZ.</p>
<p id="elb_ug_fz_0004__p213112547366">Load balancers in these AZs work in active-active or multi-active mode and requests are distributed by the nearest load balancer in the same AZ.</p>
<p id="elb_ug_fz_0004__p134171339163317">Select the AZ where backend servers reside to reduce network latency and improve access speed.</p>
<p id="elb_ug_fz_0004__p8823203712355">If disaster recovery is required, create load balancers based on the scenario:</p>
<ul id="elb_ug_fz_0004__ul8536816123610"><li id="elb_ug_fz_0004__li753620166368"><strong id="elb_ug_fz_0004__b16719232070">One load balancer in multiple AZs (disaster recovery at the AZ level)</strong><p id="elb_ug_fz_0004__p12536216103616">If the number of requests does not exceed what the largest specifications (large II) can handle, you can create a load balancer and select multiple AZs. In this way, if the load balancer in a single AZ is abnormal, the load balancer in other AZs can route the traffic, and disaster recovery can be implemented among multiple AZs.</p>
</li><li id="elb_ug_fz_0004__li45376166363"><strong id="elb_ug_fz_0004__b763205817718">Multiple load balancers and each load balancer in multiple AZs (disaster recovery at both the load balancer and AZ level)</strong><p id="elb_ug_fz_0004__p12374111214113">If the number of requests exceeds what the largest specifications (large II) can handle, you can create multiple load balancers and select multiple AZs for each load balancer. In this way, if a single load balancer is abnormal, other load balancers can distribute the traffic, and disaster recovery can be implemented among multiple load balancers and AZs.</p>
</li></ul>
<div class="note" id="elb_ug_fz_0004__note1439316386124"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_fz_0004__elb_pro_0005_ul923217451122"><li id="elb_ug_fz_0004__elb_pro_0005_li17232345111210">If requests are from the Internet, the load balancer in each AZ you select routes the requests based on source IP addresses. If you deploy a load balancer in two AZs, the requests the load balancers can handle will be doubled.</li><li id="elb_ug_fz_0004__elb_pro_0005_li0765191117216">For requests from a private network:<ul id="elb_ug_fz_0004__elb_pro_0005_ul187611211172118"><li id="elb_ug_fz_0004__elb_pro_0005_li13767152811815">If clients are in an AZ you have selected when you create the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer is unhealthy, requests are distributed by the load balancer in another AZ you have selected.<p id="elb_ug_fz_0004__elb_pro_0005_p93011631387"><a name="elb_ug_fz_0004__elb_pro_0005_li13767152811815"></a><a name="elb_pro_0005_li13767152811815"></a>If the load balancer is healthy but the connections that the load balancer need to handle exceed the amount defined in the specifications, service may be interrupted. To address this issue, you need upgrade specifications. </p>
</li><li id="elb_ug_fz_0004__elb_pro_0005_li18762161119217">If clients are in an AZ that is not selected when you create the load balancer, requests are distributed by the load balancer in each AZ you select based on source IP addresses.</li></ul>
</li><li id="elb_ug_fz_0004__li45376166363"><strong id="elb_ug_fz_0004__b763205817718">Multiple load balancers and each load balancer in multiple AZs (disaster recovery at both the load balancer and AZ level)</strong><p id="elb_ug_fz_0004__p12374111214113">If the number of requests exceeds what the largest specifications (large II) can handle, you can create multiple <span id="elb_ug_fz_0004__ph17701333806">dedicated load balancers</span> and select multiple AZs for each load balancer. In this way, if a single load balancer is abnormal, other load balancers can distribute the traffic, and disaster recovery can be implemented among multiple load balancers and AZs.</p>
</li></ul>
<div class="note" id="elb_ug_fz_0004__note1439316386124"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_fz_0004__en-us_topic_0091131368_ul923217451122"><li id="elb_ug_fz_0004__en-us_topic_0091131368_li17232345111210">If requests are from the Internet, the load balancer in each AZ you select routes the requests based on source IP addresses. If you deploy a load balancer in two AZs, the requests the load balancers can handle will be doubled.</li><li id="elb_ug_fz_0004__en-us_topic_0091131368_li0765191117216">For requests from a private network:<ul id="elb_ug_fz_0004__en-us_topic_0091131368_ul187611211172118"><li id="elb_ug_fz_0004__en-us_topic_0091131368_li13767152811815">If clients are in an AZ you have selected when you created the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer becomes unavailable, requests are distributed by the load balancer in another AZ you have selected.<p id="elb_ug_fz_0004__en-us_topic_0091131368_p93011631387"><a name="elb_ug_fz_0004__en-us_topic_0091131368_li13767152811815"></a><a name="en-us_topic_0091131368_li13767152811815"></a>If the load balancer is available but the connections that the load balancer needs to handle exceed the amount defined in the specifications, service may be interrupted. To address this issue, you need upgrade specifications.</p>
</li><li id="elb_ug_fz_0004__en-us_topic_0091131368_li18762161119217">If clients are in an AZ that is not selected when you created the load balancer, requests are distributed by the load balancer in each AZ you select based on source IP addresses.</li></ul>
</li><li id="elb_ug_fz_0004__en-us_topic_0091131368_li85501156567">If requests are from a Direct Connect connection, the load balancer in the same AZ as the Direct Connect connection routes the requests. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ.</li><li id="elb_ug_fz_0004__en-us_topic_0091131368_li147061182517">If clients are in a VPC that is different from where the load balancer works, the load balancer in the AZ where the original VPC subnet resides routes the requests. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ.</li></ul>
</div></div>
</div>
<div class="section" id="elb_ug_fz_0004__section107201113153315"><h4 class="sectiontitle">Network Type</h4><div class="p" id="elb_ug_fz_0004__en-us_topic_0172664952_p1806827135213">The network type can be any of the following:<ul id="elb_ug_fz_0004__en-us_topic_0172664952_ul188184512578"><li id="elb_ug_fz_0004__en-us_topic_0172664952_li6881104510577">If you select the public IPv4 network, the load balancer will have an IPv4 EIP bound to route requests over the Internet.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li1331010570575">If you select the private IPv4 network, a private IPv4 IP address will be assigned to the load balancer to route requests within a VPC.</li></ul>
<div class="section" id="elb_ug_fz_0004__section107201113153315"><h4 class="sectiontitle">Network Type</h4><div class="p" id="elb_ug_fz_0004__en-us_topic_0172664952_p1806827135213"><strong id="elb_ug_fz_0004__b0817650916"><span id="elb_ug_fz_0004__ph83363487214">Dedicated load balancers</span> support public IPv4 network, IPv6 network, and private IPv4 network.</strong><ul id="elb_ug_fz_0004__en-us_topic_0172664952_ul188184512578"><li id="elb_ug_fz_0004__en-us_topic_0172664952_li6881104510577">If you select the public IPv4 network, the load balancer will have an IPv4 EIP bound to route requests over the Internet.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li1331010570575">If you select the private IPv4 network, a private IPv4 address will be assigned to the load balancer to route requests within a VPC.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li16310184751517">If you select the IPv6 network, the load balancer will have an IPv6 address, which allows the load balancer to route requests within a VPC. If you add the IPv6 address to a shared bandwidth, the load balancer can also process requests over the Internet.</li></ul>
</div>
<div class="p" id="elb_ug_fz_0004__en-us_topic_0172664952_p8562957535">Shared load balancers can work in both public and private networks.<ul id="elb_ug_fz_0004__en-us_topic_0172664952_ul65661577311"><li id="elb_ug_fz_0004__en-us_topic_0172664952_li19566125715313">To route requests over the Internet, you need to bind an EIP to the load balancer. The load balancer also has a private IP address and can route requests in a VPC.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li14566175719319">To route requests in a VPC, bind only a private IP address to the load balancer.</li></ul>
<div class="p" id="elb_ug_fz_0004__en-us_topic_0172664952_p8562957535"><strong id="elb_ug_fz_0004__b1673694315599">Shared load balancers can work in both public IPv4 networks and private IPv4 networks.</strong><ul id="elb_ug_fz_0004__en-us_topic_0172664952_ul65661577311"><li id="elb_ug_fz_0004__en-us_topic_0172664952_li19566125715313">To route requests over the Internet, you need to bind an EIP to the load balancer. The load balancer also has a private IP address and can route requests in a VPC.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li14566175719319">To route requests in a VPC, bind only a private IP address to the load balancer.</li></ul>
</div>
</div>
<div class="section" id="elb_ug_fz_0004__section138810463337"><h4 class="sectiontitle">Specifications</h4><div class="p" id="elb_ug_fz_0004__en-us_topic_0172664952_p118761738103012"><span id="elb_ug_fz_0004__ph1512423211303">Dedicated load balancer</span>s provide a broad range of specifications to meet your requirements in different scenarios. Specifications for network load balancing are suitable for TCP or UDP requests, while specifications for application load balancing are broadly used to handle HTTP or HTTPS requests. Select appropriate specifications based on your traffic volume and service requirements. The following are some principles for you to select the specifications:<ul id="elb_ug_fz_0004__en-us_topic_0172664952_ul9876138193014"><li id="elb_ug_fz_0004__en-us_topic_0172664952_li5877138203011">For TCP or UDP load balancing, pay attention to the number of concurrent persistent connections, and consider Maximum Connections as a key metric. Estimate the maximum number of concurrent connections that a load balancer can handle in the actual service scenario and select the corresponding specification.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li88815913156">For HTTP or HTTPS load balancers, focus more on queries per second (QPS), which determines the service throughput of an application system. Estimate the QPS that a load balancer can handle in the actual service scenario and select the corresponding specification.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li118771389302">Use the monitoring data from Cloud Eye to analyze the peak traffic, trend and regularity of the traffic to select the specifications more accurately.</li></ul>
<div class="section" id="elb_ug_fz_0004__section138810463337"><h4 class="sectiontitle">Specifications</h4><div class="p" id="elb_ug_fz_0004__en-us_topic_0172664952_p118761738103012"><span id="elb_ug_fz_0004__ph16421123031">Dedicated load balancers</span> provide a broad range of specifications to meet your requirements in different scenarios. Specifications for network load balancing are suitable for TCP or UDP requests, while specifications for application load balancing are broadly used to handle HTTP or HTTPS requests. Select appropriate specifications based on your traffic volume and service requirements. The following are some principles for you to select the specifications:<ul id="elb_ug_fz_0004__en-us_topic_0172664952_ul9876138193014"><li id="elb_ug_fz_0004__en-us_topic_0172664952_li5877138203011">For TCP or UDP load balancing, pay attention to the number of concurrent persistent connections, and consider Maximum Connections as a key metric. Estimate the maximum number of concurrent connections that a load balancer can handle in the actual service scenario and select the corresponding specification.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li88815913156">For HTTP or HTTPS load balancing, focus more on queries per second (QPS), which determines the service throughput of an application system. Estimate the QPS that a load balancer can handle in the actual service scenario and select the corresponding specification.</li><li id="elb_ug_fz_0004__en-us_topic_0172664952_li118771389302">Use the monitoring data from Cloud Eye to analyze the peak traffic, trend and regularity of the traffic to select the specifications more accurately.</li></ul>
</div>
</div>
<div class="section" id="elb_ug_fz_0004__section05851991232"><h4 class="sectiontitle">Protocol</h4><p id="elb_ug_fz_0004__p136212239911">ELB provides load balancing at both Layer 4 and Layer 7.</p>
<ul id="elb_ug_fz_0004__ul92693811416"><li id="elb_ug_fz_0004__li1926123841410">If you choose TCP or UDP, the load balancer routes requests directly to backend servers. In this process, the destination IP address in the packets is changed to the IP address of the backend server, and the source IP address to the private IP address of the load balancer. A connection is established after a three-way handshake between the client and the backend server, and the load balancer only forwards the data.<div class="fignone" id="elb_ug_fz_0004__fig198312473301"><span class="figcap"><b>Figure 1 </b>Layer-4 load balancing</span><br><span><img id="elb_ug_fz_0004__image94091572359" src="en-us_image_0238395032.png"></span></div>
</li><li id="elb_ug_fz_0004__li11289161375414">Load balancing at Layer 7 is also called "content exchange". After the load balancer receives a request, it works as a proxy of backend <span id="elb_ug_fz_0004__text15404133255017">server</span>s to establish a connection (three-way handshake) with the client and then determines to which backend <span id="elb_ug_fz_0004__text1860995764312">server</span> the request is to be routed based on the fields in the HTTP/HTTPS request header and the load balancing algorithm you selected when you add the listener.<div class="fignone" id="elb_ug_fz_0004__fig12410839319"><span class="figcap"><b>Figure 2 </b>Layer-7 load balancing</span><br><span><img id="elb_ug_fz_0004__image491215548365" src="en-us_image_0238395033.png"></span></div>
<ul id="elb_ug_fz_0004__ul92693811416"><li id="elb_ug_fz_0004__li1926123841410">If you choose TCP or UDP, the load balancer routes requests directly to backend servers. In this process, the destination IP address in the packets is changed to the IP address of the backend server, and the source IP address to the private IP address of the load balancer. A connection is established after a three-way handshake between the client and the backend server, and the load balancer only forwards the data.<div class="fignone" id="elb_ug_fz_0004__fig198312473301"><span class="figcap"><b>Figure 1 </b>Layer-4 load balancing</span><br><span><img id="elb_ug_fz_0004__image94091572359" src="en-us_image_0000001794660761.png"></span></div>
</li><li id="elb_ug_fz_0004__li11289161375414">Load balancing at Layer 7 is also called "content exchange". After the load balancer receives a request, it works as a proxy of backend servers to establish a connection (three-way handshake) with the client and then determines to which backend server the request is to be routed based on the fields in the HTTP/HTTPS request header and the load balancing algorithm you selected when you add the listener.<div class="fignone" id="elb_ug_fz_0004__fig12410839319"><span class="figcap"><b>Figure 2 </b>Layer-7 load balancing</span><br><span><img id="elb_ug_fz_0004__image491215548365" src="en-us_image_0000001747381024.png"></span></div>
</li></ul>
</div>
<div class="section" id="elb_ug_fz_0004__section1824491002317"><h4 class="sectiontitle">Backend Servers</h4><p id="elb_ug_fz_0004__p19244151032311">Before you use ELB, you need to create cloud servers, deploy required applications on them, and add the cloud servers to one or more backend <span id="elb_ug_fz_0004__text88361130165115">server</span> groups. When you create ECSs or BMSs, note the following:</p>
<div class="section" id="elb_ug_fz_0004__section1824491002317"><h4 class="sectiontitle">Backend Servers</h4><p id="elb_ug_fz_0004__p19244151032311">Before you use ELB, you need to create cloud servers, deploy required applications on them, and add the cloud servers to one or more backend server groups. When you create ECSs or BMSs, note the following:</p>
<ul id="elb_ug_fz_0004__ul239818617405"><li id="elb_ug_fz_0004__li73980634016">Cloud servers must be in the same region as the load balancer.</li><li id="elb_ug_fz_0004__li183983674015">Cloud servers that run the same OS are recommended so that you can manage them more easily.</li></ul>
</div>
</div>

2
docs/elb/umn/elb_ug_fz_0005.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Configuring Deletion Protection for Load Balancers</h1>
<div id="body8662426"><div class="section" id="elb_ug_fz_0005__en-us_topic_0000001124473719_section1063251192613"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_fz_0005__en-us_topic_0000001124473719_p1071917299262">You can enable deletion protection for load balancers to prevent them from being deleted by accident.</p>
</div>
<div class="section" id="elb_ug_fz_0005__en-us_topic_0000001124473719_section199829311277"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_fz_0005__en-us_topic_0000001124473719_ol7973192482819"><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0005__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0005__li83736197297">Hover on <span><img id="elb_ug_fz_0005__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0005__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0005__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0005__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li786163214298">Locate the load balancer and click its name.</li><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li662115566309">In the <strong id="elb_ug_fz_0005__en-us_topic_0000001124473719_b8917204725112">Summary</strong> tab, enable <strong id="elb_ug_fz_0005__en-us_topic_0000001124473719_b880645835115">Deletion Protection</strong>.</li></ol>
<div class="section" id="elb_ug_fz_0005__en-us_topic_0000001124473719_section199829311277"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_fz_0005__en-us_topic_0000001124473719_ol7973192482819"><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0005__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0005__li83736197297">Hover on <span><img id="elb_ug_fz_0005__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0005__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0005__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0005__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li786163214298">Locate the load balancer and click its name.</li><li id="elb_ug_fz_0005__en-us_topic_0000001124473719_li662115566309">In the <strong id="elb_ug_fz_0005__en-us_topic_0000001124473719_b8917204725112">Summary</strong> tab, enable <strong id="elb_ug_fz_0005__en-us_topic_0000001124473719_b880645835115">Deletion Protection</strong>.</li></ol>
<div class="note" id="elb_ug_fz_0005__en-us_topic_0000001124473719_note8738203063713"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0005__en-us_topic_0000001124473719_p2738143013716">Disable deletion protection before you delete a load balancer.</p>
</div></div>
</div>

2
docs/elb/umn/elb_ug_fz_0008.html
View File

@ -9,7 +9,7 @@
<div class="section" id="elb_ug_fz_0008__section131941342381"><h4 class="sectiontitle">Prerequisites</h4><p id="elb_ug_fz_0008__p4144101553416">Delete the resources configured for the load balancer in the following sequence:</p>
<ol id="elb_ug_fz_0008__ol157731724204317"><li id="elb_ug_fz_0008__li077312247434">Delete all the forwarding policies added to HTTP and HTTPS listeners of the load balancer.</li><li id="elb_ug_fz_0008__li13773112484314">Delete the redirect created for each HTTP listener of the load balancer.</li><li id="elb_ug_fz_0008__li777432411438">Remove all the backend servers from the backend server groups associated with each listener of the load balancer.</li><li id="elb_ug_fz_0008__li777432414312">Delete all the listeners added to the load balancer.</li><li id="elb_ug_fz_0008__li117741524104319">Delete all backend server groups associated with each listener of the load balancer.</li></ol>
</div>
<div class="section" id="elb_ug_fz_0008__section13384917815"><h4 class="sectiontitle">Deleting a Load Balancer</h4><ol id="elb_ug_fz_0008__ol1889111542441"><li id="elb_ug_fz_0008__li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0008__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0008__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0008__li78811227131312">Hover on <span><img id="elb_ug_fz_0008__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0008__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0008__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0008__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0008__li786163214298">Locate the load balancer and click <strong id="elb_ug_fz_0008__b176641686335">Delete</strong> in the <strong id="elb_ug_fz_0008__b8608101218338">Operation</strong> column.</li><li id="elb_ug_fz_0008__li649416466551">Click <strong id="elb_ug_fz_0008__b16243731133212">Yes</strong>.</li></ol>
<div class="section" id="elb_ug_fz_0008__section13384917815"><h4 class="sectiontitle">Deleting a Load Balancer</h4><ol id="elb_ug_fz_0008__ol1889111542441"><li id="elb_ug_fz_0008__li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0008__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0008__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0008__li78811227131312">Hover on <span><img id="elb_ug_fz_0008__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0008__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0008__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0008__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0008__li786163214298">Locate the load balancer and click <strong id="elb_ug_fz_0008__b176641686335">Delete</strong> in the <strong id="elb_ug_fz_0008__b8608101218338">Operation</strong> column.</li><li id="elb_ug_fz_0008__li649416466551">Click <strong id="elb_ug_fz_0008__b16243731133212">Yes</strong>.</li></ol>
</div>
</div>
<div>

8
docs/elb/umn/elb_ug_fz_0009.html
View File

@ -11,18 +11,18 @@
</div>
</div></div>
</div>
<div class="section" id="elb_ug_fz_0009__section13341182783"><h4 class="sectiontitle">Binding an IPv4 EIP</h4><ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol20603410102311"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0009__li83208325272">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li2096635210332">Hover on <span><img id="elb_ug_fz_0009__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li786163214298">On the <strong id="elb_ug_fz_0009__b17330537134419">Elastic Load Balancers</strong> tab page, locate the load balancer to which you want to bind an IPv4 EIP and click <strong id="elb_ug_fz_0009__b1933011370446">More</strong> &gt; <strong id="elb_ug_fz_0009__b4331537174410">Bind IPv4 EIP</strong> in the <strong id="elb_ug_fz_0009__b9331163710449">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li649416466551">In the <strong id="elb_ug_fz_0009__b8629539104419">Bind IPv4 EIP</strong> dialog box, select the EIP you want to bind to the load balancer.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li12533510121215">Click <strong id="elb_ug_fz_0009__b3984154014418">OK</strong>.</li></ol>
<div class="section" id="elb_ug_fz_0009__section13341182783"><h4 class="sectiontitle">Binding an IPv4 EIP</h4><ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol20603410102311"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0009__li83208325272">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li2096635210332">Hover on <span><img id="elb_ug_fz_0009__image1511402402117" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__b5114112422114">Service List</strong> and choose <strong id="elb_ug_fz_0009__b5117524182112">Network</strong> &gt; <strong id="elb_ug_fz_0009__b14119122414214">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li786163214298">On the <strong id="elb_ug_fz_0009__b17330537134419">Load Balancers</strong> page, locate the load balancer to which you want to bind an IPv4 EIP and click <strong id="elb_ug_fz_0009__b1933011370446">More</strong> &gt; <strong id="elb_ug_fz_0009__b4331537174410">Bind IPv4 EIP</strong> in the <strong id="elb_ug_fz_0009__b9331163710449">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li649416466551">In the <strong id="elb_ug_fz_0009__b8629539104419">Bind IPv4 EIP</strong> dialog box, select the EIP you want to bind to the load balancer.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li12533510121215">Click <strong id="elb_ug_fz_0009__b3984154014418">OK</strong>.</li></ol>
</div>
<div class="section" id="elb_ug_fz_0009__section17312512812"><h4 class="sectiontitle">Binding a Private IPv4 Address</h4><p id="elb_ug_fz_0009__en-us_topic_0172664831_p1259023124210">Only dedicated load balancers support this function.</p>
<ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol18296355163819"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li37675401136">Log in to the management console.</li><li id="elb_ug_fz_0009__li17843943182710">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__en-us_topic_0240829509_image1542118117117_1" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li156061052181215">Hover on <span><img id="elb_ug_fz_0009__en-us_topic_0052569751_image762510132322_1" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b9121102522212_1">Service List</strong> and choose <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b61222025142217_1">Network</strong> &gt; <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b4124425142210_1">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li1429618557382">On the <strong id="elb_ug_fz_0009__b891067114519">Elastic Load Balancers</strong> tab page, locate the load balancer to which you want to bind a private IPv4 address and click <strong id="elb_ug_fz_0009__b9911167104512">More</strong> &gt; <strong id="elb_ug_fz_0009__b1491111714512">Bind Private IPv4 Address</strong> in the <strong id="elb_ug_fz_0009__b1391287184515">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li5296355203820">In the <strong id="elb_ug_fz_0009__b481913512479">Bind Private IPv4 Address</strong> dialog box, select the subnet where the IP address resides and specify the IP address.<ul id="elb_ug_fz_0009__en-us_topic_0172664831_ul516613191983"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li18166419380">By default, the system automatically assigns an IP address. To manually specify an IP address, deselect <strong id="elb_ug_fz_0009__b17819134219473">Automatically-assigned IP address</strong> and enter the IP address.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li47512331581">Ensure that the entered IP address belongs to the selected subnet and is not in use.</li></ul>
<ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol18296355163819"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li37675401136">Log in to the management console.</li><li id="elb_ug_fz_0009__li17843943182710">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__image6310182822119" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li156061052181215">Hover on <span><img id="elb_ug_fz_0009__image1615123162112" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__b116161231142111">Service List</strong> and choose <strong id="elb_ug_fz_0009__b126181311210">Network</strong> &gt; <strong id="elb_ug_fz_0009__b1262043132114">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li1429618557382">On the <strong id="elb_ug_fz_0009__b891067114519">Load Balancers</strong> page, locate the load balancer to which you want to bind a private IPv4 address and click <strong id="elb_ug_fz_0009__b9911167104512">More</strong> &gt; <strong id="elb_ug_fz_0009__b1491111714512">Bind Private IPv4 Address</strong> in the <strong id="elb_ug_fz_0009__b1391287184515">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li5296355203820">In the <strong id="elb_ug_fz_0009__b481913512479">Bind Private IPv4 Address</strong> dialog box, select the subnet where the IP address resides and specify the IP address.<ul id="elb_ug_fz_0009__en-us_topic_0172664831_ul516613191983"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li18166419380">By default, the system automatically assigns an IP address. To manually specify an IP address, deselect <strong id="elb_ug_fz_0009__b17819134219473">Automatically assign IP address</strong> and enter the IP address.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li47512331581">Ensure that the entered IP address belongs to the selected subnet and is not in use.</li></ul>
</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li1112318495510">Click <strong id="elb_ug_fz_0009__b206461541124420">OK</strong>.</li></ol>
</div>
<div class="section" id="elb_ug_fz_0009__section19128133115911"><h4 class="sectiontitle">Unbinding an IPv4 EIP</h4><ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol1136841116257"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li1231311543">Log in to the management console.</li><li id="elb_ug_fz_0009__li159382027102812">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__en-us_topic_0240829509_image1542118117117_2" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li1968721220130">Hover on <span><img id="elb_ug_fz_0009__en-us_topic_0052569751_image762510132322_2" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b9121102522212_2">Service List</strong> and choose <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b61222025142217_2">Network</strong> &gt; <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b4124425142210_2">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__li45781403520">On the <strong id="elb_ug_fz_0009__b107394416114">Load Balancers</strong> page, locate the load balancer from which you want to unbind the IPv4 EIP and click <strong id="elb_ug_fz_0009__b87538491111">More</strong> &gt; <strong id="elb_ug_fz_0009__b117531044119">Unbind IPv4 EIP</strong> in the <strong id="elb_ug_fz_0009__b275484101111">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li11371411182511">In the <strong id="elb_ug_fz_0009__b172091757195813">Unbind IPv4 EIP</strong> dialog box, confirm the IPv4 EIP that you want to unbind and click <strong id="elb_ug_fz_0009__b17223257175819">Yes</strong>.<div class="note" id="elb_ug_fz_0009__en-us_topic_0172664831_note16835115125512"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0009__en-us_topic_0172664831_p942923195615">After the IPv4 EIP is unbound, the load balancer cannot route requests over the Internet.</p>
<div class="section" id="elb_ug_fz_0009__section19128133115911"><h4 class="sectiontitle">Unbinding an IPv4 EIP</h4><ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol1136841116257"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li1231311543">Log in to the management console.</li><li id="elb_ug_fz_0009__li159382027102812">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__image1254984022110" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li1968721220130">Hover on <span><img id="elb_ug_fz_0009__image650934312216" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__b13509443142114">Service List</strong> and choose <strong id="elb_ug_fz_0009__b35111243182110">Network</strong> &gt; <strong id="elb_ug_fz_0009__b10512343192111">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__li45781403520">On the <strong id="elb_ug_fz_0009__b107394416114">Load Balancers</strong> page, locate the load balancer from which you want to unbind the IPv4 EIP and click <strong id="elb_ug_fz_0009__b87538491111">More</strong> &gt; <strong id="elb_ug_fz_0009__b117531044119">Unbind IPv4 EIP</strong> in the <strong id="elb_ug_fz_0009__b275484101111">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li11371411182511">In the displayed dialog box, confirm the IPv4 EIP that you want to unbind and click <strong id="elb_ug_fz_0009__b17223257175819">Yes</strong>.<div class="note" id="elb_ug_fz_0009__en-us_topic_0172664831_note16835115125512"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0009__en-us_topic_0172664831_p942923195615">After the IPv4 EIP is unbound, the load balancer cannot route requests over the Internet.</p>
</div></div>
</li></ol>
</div>
<div class="section" id="elb_ug_fz_0009__section115181654695"><h4 class="sectiontitle">Unbinding a Private IPv4 Address</h4><p id="elb_ug_fz_0009__en-us_topic_0172664831_p13555111224016">Only dedicated load balancers support this function.</p>
<ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol5691112365719"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li112186251146">Log in to the management console.</li><li id="elb_ug_fz_0009__li15642143122818">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__en-us_topic_0240829509_image1542118117117_3" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li4903111991314">Hover on <span><img id="elb_ug_fz_0009__en-us_topic_0052569751_image762510132322_3" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b9121102522212_3">Service List</strong> and choose <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b61222025142217_3">Network</strong> &gt; <strong id="elb_ug_fz_0009__en-us_topic_0052569751_b4124425142210_3">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li3691172375717">On the <strong id="elb_ug_fz_0009__b910617291592">Elastic Load Balancers</strong> tab page, locate the load balancer from which you want to unbind the private IPv4 address and click <strong id="elb_ug_fz_0009__b111081229185912">More</strong> &gt; <strong id="elb_ug_fz_0009__b1910922975916">Unbind Private IPv4 Address</strong> in the <strong id="elb_ug_fz_0009__b111092975918">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li4692423105711">In the <strong id="elb_ug_fz_0009__b840723265914">Unbind Private IPv4 Address</strong> dialog box, confirm the private IPv4 IP address that you want to unbind and click <strong id="elb_ug_fz_0009__b15408163205917">Yes</strong>.<div class="note" id="elb_ug_fz_0009__en-us_topic_0172664831_note888559124617"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0009__en-us_topic_0172664831_p28815593463">After the private IPv4 address is unbound, the load balancer cannot route requests over the private IPv4 network.</p>
<ol id="elb_ug_fz_0009__en-us_topic_0172664831_ol5691112365719"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li112186251146">Log in to the management console.</li><li id="elb_ug_fz_0009__li15642143122818">In the upper left corner of the page, click <span><img id="elb_ug_fz_0009__image33555486217" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0009__li4903111991314">Hover on <span><img id="elb_ug_fz_0009__image9710352132119" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0009__b971095214215">Service List</strong> and choose <strong id="elb_ug_fz_0009__b16712165292117">Network</strong> &gt; <strong id="elb_ug_fz_0009__b17141452162119">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li3691172375717">On the <strong id="elb_ug_fz_0009__b910617291592">Load Balancers</strong> page, locate the load balancer from which you want to unbind the private IPv4 address and click <strong id="elb_ug_fz_0009__b111081229185912">More</strong> &gt; <strong id="elb_ug_fz_0009__b1910922975916">Unbind Private IPv4 Address</strong> in the <strong id="elb_ug_fz_0009__b111092975918">Operation</strong> column.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li4692423105711">In the displayed dialog box, confirm the private IPv4 address that you want to unbind and click <strong id="elb_ug_fz_0009__b15408163205917">Yes</strong>.<div class="note" id="elb_ug_fz_0009__en-us_topic_0172664831_note888559124617"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0009__en-us_topic_0172664831_p28815593463">After the private IPv4 address is unbound, the load balancer cannot route requests over the private IPv4 network.</p>
</div></div>
</li></ol>
</div>

2
docs/elb/umn/elb_ug_fz_0011.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Exporting the Load Balancer List</h1>
<div id="body0000001149193504"><div class="section" id="elb_ug_fz_0011__section20538244111217"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_fz_0011__p1668911345208">You can export the load balancer list for backup.</p>
</div>
<div class="section" id="elb_ug_fz_0011__section19169366120"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_fz_0011__en-us_topic_0093321970_ol18971723131315"><li id="elb_ug_fz_0011__li104062575369">Log in to the management console.</li><li id="elb_ug_fz_0011__li640635753619">In the upper left corner of the page, click <span><img id="elb_ug_fz_0011__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0011__li17301740102218">Hover on <span><img id="elb_ug_fz_0011__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0011__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0011__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0011__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0011__en-us_topic_0093321970_li162431917151414">In the upper right corner of the load balancer list, click <span><img id="elb_ug_fz_0011__en-us_topic_0093321970_image56755919206" src="en-us_image_0000001195393079.png"></span>.</li></ol>
<div class="section" id="elb_ug_fz_0011__section19169366120"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_fz_0011__en-us_topic_0093321970_ol18971723131315"><li id="elb_ug_fz_0011__li104062575369">Log in to the management console.</li><li id="elb_ug_fz_0011__li640635753619">In the upper left corner of the page, click <span><img id="elb_ug_fz_0011__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0011__li17301740102218">Hover on <span><img id="elb_ug_fz_0011__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0011__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0011__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0011__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0011__en-us_topic_0093321970_li162431917151414">In the upper right corner of the load balancer list, click <span><img id="elb_ug_fz_0011__en-us_topic_0093321970_image56755919206" src="en-us_image_0000001794660541.png"></span>.</li></ol>
</div>
</div>
<div>

5
docs/elb/umn/elb_ug_fz_0015.html
View File

@ -2,12 +2,11 @@
<h1 class="topictitle1">Modifying the Bandwidth</h1>
<div id="body0000001352206466"><div class="section" id="elb_ug_fz_0015__section57040304257"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_fz_0015__p1675614461112">If you set the <strong id="elb_ug_fz_0015__b99141079445840">Network Type</strong> of a load balancer to <strong id="elb_ug_fz_0015__b50179153545840">Public IPv4 network</strong> or <strong id="elb_ug_fz_0015__b199301792845840">IPv6 network</strong>, the load balancer can route requests over the Internet and you can modify the bandwidth used by the EIP bound to the load balancer as required.</p>
<div class="note" id="elb_ug_fz_0015__note18994194512814"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0015__p27312045113516">When changing bandwidth, you need to change the specifications of the dedicated load balancer to avoid speed limit due to insufficient bandwidth.</p>
<ul id="elb_ug_fz_0015__ul36261732162913"><li id="elb_ug_fz_0015__li11626732182912">The bandwidth of the EIP bound to the load balancer is the limit for traffic required by the clients to access the load balancer.</li><li id="elb_ug_fz_0015__li75191593120">The bandwidth of dedicated load balancers is the maximum value of the total inbound and outbound traffic of the load balancer.</li></ul>
<div class="note" id="elb_ug_fz_0015__note18994194512814"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_fz_0015__ul179871773321"><li id="elb_ug_fz_0015__li398711717324">When changing bandwidth, you need to change the specifications of the dedicated load balancer to avoid speed limit due to insufficient bandwidth.</li><li id="elb_ug_fz_0015__li1712816100325">The bandwidth of the EIP bound to the load balancer is the limit for traffic required by the clients to access the load balancer.</li></ul>
</div></div>
</div>
<div class="section" id="elb_ug_fz_0015__section12411142510365"><h4 class="sectiontitle">Modifying the Bandwidth</h4><p id="elb_ug_fz_0015__p241118251361">When you modify the bandwidth, traffic routing will not be interrupted.</p>
<ol id="elb_ug_fz_0015__ol16411125143617"><li id="elb_ug_fz_0015__li741120255362">Log in to the management console.</li><li id="elb_ug_fz_0015__li4412162513614">In the upper left corner of the page, click <span><img id="elb_ug_fz_0015__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0015__li4412192563615">Hover on <span><img id="elb_ug_fz_0015__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0015__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0015__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0015__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0015__li7413142519362">On the <strong id="elb_ug_fz_0015__b118309556645840">Load Balancers</strong> page:<p id="elb_ug_fz_0015__p941317251361">Dedicated load balancers: Locate the load balancer and click <strong id="elb_ug_fz_0015__b67783518845840">Modify IPv4 Bandwidth</strong> or choose <strong id="elb_ug_fz_0015__b68593305245840">More</strong> &gt; <strong id="elb_ug_fz_0015__b110385578745840">Modify IPv6 Bandwidth</strong> in the <strong id="elb_ug_fz_0015__b101129305745840">Operation</strong> column (if the load balancer has an IPv6 address that has been added to a shared bandwidth).</p>
<ol id="elb_ug_fz_0015__ol16411125143617"><li id="elb_ug_fz_0015__li741120255362">Log in to the management console.</li><li id="elb_ug_fz_0015__li4412162513614">In the upper left corner of the page, click <span><img id="elb_ug_fz_0015__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0015__li4412192563615">Hover on <span><img id="elb_ug_fz_0015__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0015__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0015__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0015__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0015__li7413142519362">On the <strong id="elb_ug_fz_0015__b118309556645840">Load Balancers</strong> page:<p id="elb_ug_fz_0015__p941317251361">Dedicated load balancers: Locate the load balancer and click <strong id="elb_ug_fz_0015__b67783518845840">Modify IPv4 Bandwidth</strong> or choose <strong id="elb_ug_fz_0015__b68593305245840">More</strong> &gt; <strong id="elb_ug_fz_0015__b110385578745840">Modify IPv6 Bandwidth</strong> in the <strong id="elb_ug_fz_0015__b101129305745840">Operation</strong> column (if the load balancer has an IPv6 address that has been added to a shared bandwidth).</p>
<p id="elb_ug_fz_0015__p44139252365">Shared load balancers: Locate the load balancer and click <strong id="elb_ug_fz_0015__b29647971545840">Modify IPv4 Bandwidth</strong> in the <strong id="elb_ug_fz_0015__b175441670145840">Operation</strong> column.</p>
</li><li id="elb_ug_fz_0015__li154131425193614">In the <strong id="elb_ug_fz_0015__b107169693445840">New Configuration</strong> area, modify the bandwidth and click <strong id="elb_ug_fz_0015__b100774143045840">Next</strong>.<p id="elb_ug_fz_0015__p13413825143618">You can select the bandwidth defined by the system or customize the bandwidth. The bandwidth ranges from 1 Mbit/s to 1,000 Mbit/s.</p>
</li><li id="elb_ug_fz_0015__li8413192523612">Confirm the modified bandwidth and click <strong id="elb_ug_fz_0015__b1034754613366">Submit</strong>.</li></ol>

9
docs/elb/umn/elb_ug_fz_0016.html
View File

@ -2,7 +2,6 @@
<h1 class="topictitle1">Changing the Specifications of a Dedicated Load Balancer</h1>
<div id="body0000001402845637"><div class="section" id="elb_ug_fz_0016__section57040304257"><h4 class="sectiontitle">Scenario</h4><p id="elb_ug_fz_0016__p1631419211398">This section guides you on how to change the specifications of a dedicated load balancer.</p>
<p id="elb_ug_fz_0016__p532017492504">You can change the specifications of a dedicated load balancer as required on the console.</p>
<div class="note" id="elb_ug_fz_0016__note18990172591918"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0016__p16745736194013">You can only change the specifications of dedicated load balancers.</p>
</div></div>
</div>
@ -17,7 +16,8 @@
</th>
</tr>
</thead>
<tbody><tr id="elb_ug_fz_0016__row1730114232913"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.5.1.1 "><p id="elb_ug_fz_0016__p1630112102911">Network load balancing (TCP/UDP)</p>
<tbody><tr id="elb_ug_fz_0016__row1730114232913"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.5.1.1 "><p id="elb_ug_fz_0016__p2719633605">Network load balancing (TCP/UDP)</p>
<p id="elb_ug_fz_0016__p1630112102911"> </p>
</td>
<td class="cellrowborder" valign="top" width="14.99%" headers="mcps1.3.2.2.2.5.1.2 "><p id="elb_ug_fz_0016__p19301112122913">√</p>
</td>
@ -39,7 +39,10 @@
</tbody>
</table>
</div>
<ol id="elb_ug_fz_0016__ol1583571253"><li id="elb_ug_fz_0016__li1499011972516">Log in to the management console.</li><li id="elb_ug_fz_0016__li1991159172516">In the upper left corner of the page, click <span><img id="elb_ug_fz_0016__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0016__li17301740102218">Hover on <span><img id="elb_ug_fz_0016__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0016__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0016__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0016__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_fz_0016__li467515291339">On the <strong id="elb_ug_fz_0016__b179016643745830">Load Balancers</strong> page, locate the load balancer whose specifications you want to modify, click <strong id="elb_ug_fz_0016__b85235419645830">More</strong> in the <strong id="elb_ug_fz_0016__b111184359245830">Operation</strong> column, and select <strong id="elb_ug_fz_0016__b134845194045830">Change Specifications</strong>.</li><li id="elb_ug_fz_0016__li119912913258">Select the new specifications and click <strong id="elb_ug_fz_0016__b69404554745830">Next</strong>.</li><li id="elb_ug_fz_0016__li11654104818397">Confirm the information and click <strong id="elb_ug_fz_0016__b31651356345830">Submit</strong>.</li></ol>
<div class="note" id="elb_ug_fz_0016__note176121233"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><div class="p" id="elb_ug_fz_0016__p277419221935">Downgrading specifications will temporarily affect services.<ul id="elb_ug_fz_0016__ul203162131837"><li id="elb_ug_fz_0016__li93164131634">Network load balancing (TCP/UDP): New connections may fail to establish.</li><li id="elb_ug_fz_0016__li53162013433">Application load balancing (HTTP/HTTPS): New connections may not be able to be established and some persistent connections may be interrupted.</li></ul>
</div>
</div></div>
<ol id="elb_ug_fz_0016__ol1583571253"><li id="elb_ug_fz_0016__li1499011972516">Log in to the management console.</li><li id="elb_ug_fz_0016__li1991159172516">In the upper left corner of the page, click <span><img id="elb_ug_fz_0016__image02015242137" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_fz_0016__li17301740102218">Hover on <span><img id="elb_ug_fz_0016__image174731025151311" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0016__b1747315252138">Service List</strong> and choose <strong id="elb_ug_fz_0016__b1847592561320">Network</strong> &gt; <strong id="elb_ug_fz_0016__b15478172571313">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0016__li467515291339">On the <strong id="elb_ug_fz_0016__b179016643745830">Load Balancers</strong> page, locate the load balancer whose specifications you want to modify, click <strong id="elb_ug_fz_0016__b85235419645830">More</strong> in the <strong id="elb_ug_fz_0016__b111184359245830">Operation</strong> column, and select <strong id="elb_ug_fz_0016__b134845194045830">Change Specifications</strong>.</li><li id="elb_ug_fz_0016__li119912913258">Select the new specifications and click <strong id="elb_ug_fz_0016__b69404554745830">Next</strong>.</li><li id="elb_ug_fz_0016__li11654104818397">Confirm the information and click <strong id="elb_ug_fz_0016__b31651356345830">Submit</strong>.</li></ol>
</div>
</div>
<div>

8
docs/elb/umn/elb_ug_hc_0001.html
View File

@ -6,7 +6,7 @@
<div class="section" id="elb_ug_hc_0001__section12439163915214"><h4 class="sectiontitle">Prerequisites</h4><p id="elb_ug_hc_0001__p454075510528">If HTTP health checks are configured, HTTP/1.1 has been used for TCP or UDP listeners of both types of load balancers as well as HTTP or HTTPS listeners of <span id="elb_ug_hc_0001__ph34977345260">shared</span> load balancers, and that HTTP/1.0 has been used only for HTTP or HTTPS listeners of dedicated load balancers.</p>
</div>
<div class="section" id="elb_ug_hc_0001__section446512341505"><h4 class="sectiontitle">TCP Health Check</h4><p id="elb_ug_hc_0001__p13385615103815">For TCP, HTTP, and HTTPS listeners, you can use TCP to initiate three-way handshakes to obtain the statuses of backend <span id="elb_ug_hc_0001__text88231939105510">server</span>s.</p>
<div class="fignone" id="elb_ug_hc_0001__fig3642114224015"><span class="figcap"><b>Figure 1 </b>TCP health check</span><br><span><img id="elb_ug_hc_0001__image4558163712403" src="en-us_image_0164706640.png"></span></div>
<div class="fignone" id="elb_ug_hc_0001__fig3642114224015"><span class="figcap"><b>Figure 1 </b>TCP health check</span><br><span><img id="elb_ug_hc_0001__image4558163712403" src="en-us_image_0000001794819841.png"></span></div>
<p id="elb_ug_hc_0001__p12279553193810">The TCP health check process is as follows:</p>
<ol id="elb_ug_hc_0001__ol132664315385"><li id="elb_ug_hc_0001__li926143163810">ELB sends an SYN packet to the backend <span id="elb_ug_hc_0001__text91684811558">server</span> (in the format of {<em id="elb_ug_hc_0001__i1917716341637">Private IP address</em>}:{<em id="elb_ug_hc_0001__i1893012294317">Health check port</em>}).</li><li id="elb_ug_hc_0001__li14427451388">The backend server returns an SYN-ACK packet.<ul id="elb_ug_hc_0001__ul683551013121"><li id="elb_ug_hc_0001__li16836161091215">If ELB does not receive the SYN-ACK packet within the health check timeout duration, the backend server is declared unhealthy. Then, ELB sends an RST packet to the backend server to terminate the TCP connection.</li><li id="elb_ug_hc_0001__li49641915111210">If ELB receives the SYN-ACK packet from the backend server within the health check timeout duration, it sends an ACK packet to the backend server and declares that the backend server is healthy. After that, ELB sends an RST packet to the backend server to terminate the TCP connection.</li></ul>
</li></ol>
@ -15,13 +15,13 @@
</div></div>
</div>
<div class="section" id="elb_ug_hc_0001__section10955155531412"><h4 class="sectiontitle">UDP Health Check</h4><p id="elb_ug_hc_0001__p417216598406">For UDP listeners, ELB sends ICMP and UDP probe packets to backend <span id="elb_ug_hc_0001__text054210336589">server</span>s to check their health.</p>
<div class="fignone" id="elb_ug_hc_0001__fig10983238164318"><span class="figcap"><b>Figure 2 </b>UDP health check</span><br><span><img id="elb_ug_hc_0001__image3439075410" src="en-us_image_0164706641.png"></span></div>
<div class="fignone" id="elb_ug_hc_0001__fig10983238164318"><span class="figcap"><b>Figure 2 </b>UDP health check</span><br><span><img id="elb_ug_hc_0001__image3439075410" src="en-us_image_0000001794660753.png"></span></div>
<p id="elb_ug_hc_0001__p169471530104117">The UDP health check process is as follows:</p>
<ol id="elb_ug_hc_0001__ol16835151919397"><li id="elb_ug_hc_0001__li11835719143910">ELB sends an ICMP Echo Request packet to the backend server.<ul id="elb_ug_hc_0001__ul953917195313"><li id="elb_ug_hc_0001__li0539121993116">If ELB does not receive the ICMP Echo Reply packet within the health check timeout duration, the backend server is declared unhealthy.</li><li id="elb_ug_hc_0001__li1957212343112">If ELB receives the ICMP Echo Reply packet within the health check timeout duration, it sends a UDP probe packet to the backend <span id="elb_ug_hc_0001__text0468112155915">server</span>.</li></ul>
</li><li id="elb_ug_hc_0001__li174541285394">If ELB does not receive an ICMP Port Unreachable error within the health check timeout duration, the backend <span id="elb_ug_hc_0001__text89276895917">server</span> is declared healthy. If ELB receives an ICMP Port Unreachable error, the backend server is declared unhealthy.</li></ol>
</div>
<div class="section" id="elb_ug_hc_0001__section759675115508"><h4 class="sectiontitle">HTTP Health Check</h4><p id="elb_ug_hc_0001__p1677212511421">You can also configure HTTP health checks for TCP, HTTP, or HTTPS listeners. ELB uses HTTP GET requests to obtain the health statuses of backend servers. For HTTPS listeners, ELB offloads the SSL/TLS encryption and decryption processing from backend servers and uses HTTP to communicate with backend servers by default.</p>
<div class="fignone" id="elb_ug_hc_0001__fig18544191717440"><span class="figcap"><b>Figure 3 </b>HTTP health check</span><br><span><img id="elb_ug_hc_0001__image719551314443" src="en-us_image_0164706642.png"></span></div>
<div class="fignone" id="elb_ug_hc_0001__fig18544191717440"><span class="figcap"><b>Figure 3 </b>HTTP health check</span><br><span><img id="elb_ug_hc_0001__image719551314443" src="en-us_image_0000001794660745.png"></span></div>
<p id="elb_ug_hc_0001__p1417742134213">The HTTP health check process is as follows:</p>
<ol id="elb_ug_hc_0001__ol11850742163919"><li id="elb_ug_hc_0001__li685119429399">ELB sends an HTTP GET request to the backend server (in format of <em id="elb_ug_hc_0001__i13228615192719">{Private IP address}</em>:<em id="elb_ug_hc_0001__i1448314513288">{Health check port}</em>/<em id="elb_ug_hc_0001__i1048272972714">{Health check path}</em>). (You can specify a domain name when configuring a health check.)</li><li id="elb_ug_hc_0001__li99041244183912">The backend <span id="elb_ug_hc_0001__text1375282645914">server</span> returns an HTTP status code to ELB.<ul id="elb_ug_hc_0001__ul20356194219304"><li id="elb_ug_hc_0001__li235674213016">If ELB receives the status code within the health check timeout duration, it compares the status code with the preset status code. If the status codes are the same, the backend server is declared healthy.</li><li id="elb_ug_hc_0001__li20520124913020">If ELB does not receive any response from the backend <span id="elb_ug_hc_0001__text9470173895912">server</span> within the health check timeout duration, the backend <span id="elb_ug_hc_0001__text14153125715554">server</span> is declared unhealthy.</li></ul>
</li></ol>
@ -32,7 +32,7 @@
<p id="elb_ug_hc_0001__p75331926131911">The following is a formula for you to calculate the health check time window:</p>
<ul id="elb_ug_hc_0001__ul465944712013"><li id="elb_ug_hc_0001__li1165914715014">Time window for a backend server to be considered healthy = Timeout x Maximum retries + Interval x (Maximum retries – 1)</li><li id="elb_ug_hc_0001__li1765914718018">Time window for a backend server to be considered unhealthy = Timeout x 3 + Interval x (3 – 1)<p id="elb_ug_hc_0001__p1379433374711"><a name="elb_ug_hc_0001__li1765914718018"></a><a name="li1765914718018"></a>The backend server can be declared unhealthy when three consecutive health checks detect it unhealthy, regardless of the value configured for <strong id="elb_ug_hc_0001__b157941133194710">Maximum Retries</strong>.</p>
</li></ul>
<div class="p" id="elb_ug_hc_0001__p8419125220201">As shown in <a href="#elb_ug_hc_0001__fig7858105712204">Figure 4</a>, if the health check interval is 4s, the health check timeout duration is 2s, and 3 health check retries are performed, the time window for a backend server to be considered unhealthy is calculated as follows: 2 x 3 + 4 x (3 – 1) = 14s.<div class="fignone" id="elb_ug_hc_0001__fig7858105712204"><a name="elb_ug_hc_0001__fig7858105712204"></a><a name="fig7858105712204"></a><span class="figcap"><b>Figure 4 </b>Health check time window</span><br><span><img id="elb_ug_hc_0001__image1427785716477" src="en-us_image_0227675449.png"></span></div>
<div class="p" id="elb_ug_hc_0001__p8419125220201">As shown in <a href="#elb_ug_hc_0001__fig7858105712204">Figure 4</a>, if the health check interval is 4s, the health check timeout duration is 2s, and 3 health check retries are performed, the time window for a backend server to be considered unhealthy is calculated as follows: 2 x 3 + 4 x (3 – 1) = 14s.<div class="fignone" id="elb_ug_hc_0001__fig7858105712204"><a name="elb_ug_hc_0001__fig7858105712204"></a><a name="fig7858105712204"></a><span class="figcap"><b>Figure 4 </b>Health check time window</span><br><span><img id="elb_ug_hc_0001__image1427785716477" src="en-us_image_0000001794819845.png"></span></div>
</div>
</div>
<div class="section" id="elb_ug_hc_0001__section3193637194320"><h4 class="sectiontitle">Rectifying an Unhealthy Backend Server</h4><p id="elb_ug_hc_0001__p6623952415337">If a backend server is detected unhealthy, see <a href="en-us_topic_0018127975.html">How Do I Troubleshoot an Unhealthy Backend Server?</a></p>

2
docs/elb/umn/elb_ug_hc_0003.html
View File

@ -4,7 +4,7 @@
<div id="body1554880418073"><div class="section" id="elb_ug_hc_0003__section1481212713114"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_hc_0003__p12671131175110">If you do not require health check, you can disable it when you add listeners. If you have already added listeners with health check enabled, you can also disable it when you modify the listeners.</p>
<p id="elb_ug_hc_0003__p4302165719110">After health check is disabled, the load balancer will consider all backend servers healthy and will still route requests to backend servers even if they are not working normally. As a result, applications on these servers are inaccessible. If this happens, ensure that the ports used by the backend servers are normal. Do not disable health check unless necessary.</p>
</div>
<div class="section" id="elb_ug_hc_0003__section3986711219"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hc_0003__ol89376506300"><li id="elb_ug_hc_0003__li677391520332">Log in to the management console.</li><li id="elb_ug_hc_0003__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hc_0003__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_hc_0003__li83736197297">Hover on <span><img id="elb_ug_hc_0003__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_hc_0003__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_hc_0003__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_hc_0003__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_hc_0003__li826120259204">Locate the load balancer and click its name.</li></ol><ol start="5" id="elb_ug_hc_0003__ol19800720131219"><li id="elb_ug_hc_0003__li207994203124">Click <strong id="elb_ug_hc_0003__b919914515157">Backend Server Groups</strong>, locate the backend <span id="elb_ug_hc_0003__text10799152018124">server</span> group, and click its name.</li><li id="elb_ug_hc_0003__li10799142011214">In the <strong id="elb_ug_hc_0003__b1776814399236">Basic Information</strong> area, click <strong id="elb_ug_hc_0003__b10769439202312">Configure</strong> next to <strong id="elb_ug_hc_0003__b15769113962312">Health Check</strong>.</li></ol><ol start="7" id="elb_ug_hc_0003__ol1658400181413"><li id="elb_ug_hc_0003__li1858317091415">In the <strong id="elb_ug_hc_0003__b085196191617">Configure Health Check</strong> dialog box, disable the health check.</li></ol><ol start="8" id="elb_ug_hc_0003__ol1986661951414"><li id="elb_ug_hc_0003__li1086614191148">Click <strong id="elb_ug_hc_0003__b207371201552">OK</strong>.</li></ol>
<div class="section" id="elb_ug_hc_0003__section3986711219"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hc_0003__ol89376506300"><li id="elb_ug_hc_0003__li677391520332">Log in to the management console.</li><li id="elb_ug_hc_0003__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hc_0003__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hc_0003__li83736197297">Hover on <span><img id="elb_ug_hc_0003__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hc_0003__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_hc_0003__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_ug_hc_0003__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_hc_0003__li826120259204">Locate the load balancer and click its name.</li></ol><ol start="5" id="elb_ug_hc_0003__ol19800720131219"><li id="elb_ug_hc_0003__li207994203124">Click <strong id="elb_ug_hc_0003__b919914515157">Backend Server Groups</strong>, locate the backend <span id="elb_ug_hc_0003__text10799152018124">server</span> group, and click its name.</li><li id="elb_ug_hc_0003__li10799142011214">In the <strong id="elb_ug_hc_0003__b1776814399236">Basic Information</strong> area, click <strong id="elb_ug_hc_0003__b10769439202312">Configure</strong> next to <strong id="elb_ug_hc_0003__b15769113962312">Health Check</strong>.</li></ol><ol start="7" id="elb_ug_hc_0003__ol1658400181413"><li id="elb_ug_hc_0003__li1858317091415">In the <strong id="elb_ug_hc_0003__b085196191617">Configure Health Check</strong> dialog box, disable the health check.</li></ol><ol start="8" id="elb_ug_hc_0003__ol1986661951414"><li id="elb_ug_hc_0003__li1086614191148">Click <strong id="elb_ug_hc_0003__b207371201552">OK</strong>.</li></ol>
</div>
</div>
<div>

2
docs/elb/umn/elb_ug_hc_0005.html
View File

@ -4,7 +4,7 @@
<div id="body1599790719987"><div class="section" id="elb_ug_hc_0005__section1121010331536"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_hc_0005__p10969115116258">You can change the health check protocol as required. After the protocol is changed, the load balancer uses the new protocol to detect the health of backend servers, and it continues to route traffic to the backend servers after they are detected healthy.</p>
<p id="elb_ug_hc_0005__p56365397479">During this period, the load balancer may return the HTTP 503 error code to the clients.</p>
</div>
<div class="section" id="elb_ug_hc_0005__section126005588310"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hc_0005__ol5312821122018"><li id="elb_ug_hc_0005__li677391520332">Log in to the management console.</li><li id="elb_ug_hc_0005__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hc_0005__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_ug_hc_0005__li83736197297">Hover on <span><img id="elb_ug_hc_0005__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_hc_0005__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_hc_0005__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_hc_0005__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_hc_0005__li826120259204">Locate the load balancer and click its name.</li><li id="elb_ug_hc_0005__li119961554152810">Click <strong id="elb_ug_hc_0005__b197034217173">Backend Server Groups</strong>, locate the backend server group, and click its name.</li><li id="elb_ug_hc_0005__li416017569309">Click <strong id="elb_ug_hc_0005__b1051863016179">More</strong> in the <strong id="elb_ug_hc_0005__b951953010173">Operation</strong> column.</li><li id="elb_ug_hc_0005__li1438812372133">Select <strong id="elb_ug_hc_0005__b85441132121712">Configure Health Check</strong> from the drop-down list.</li><li id="elb_ug_hc_0005__li1623598131117">In the <strong id="elb_ug_hc_0005__b17337634122312">Basic Information</strong> area, click <strong id="elb_ug_hc_0005__b4337173442319">Configure</strong> next to <strong id="elb_ug_hc_0005__b2338153414233">Health Check</strong>.</li><li id="elb_ug_hc_0005__li353264814359">Change the health check protocol.</li><li id="elb_ug_hc_0005__li1884133194615">Click <strong id="elb_ug_hc_0005__b207371201552">OK</strong>.</li></ol>
<div class="section" id="elb_ug_hc_0005__section126005588310"><h4 class="sectiontitle">Procedure</h4><ol id="elb_ug_hc_0005__ol5312821122018"><li id="elb_ug_hc_0005__li677391520332">Log in to the management console.</li><li id="elb_ug_hc_0005__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_hc_0005__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001747739624.png"></span> and select the desired region and project.</li><li id="elb_ug_hc_0005__li83736197297">Hover on <span><img id="elb_ug_hc_0005__en-us_topic_0167652100_image762510132322" src="en-us_image_0000001794660485.png"></span> in the upper left corner to display <strong id="elb_ug_hc_0005__en-us_topic_0167652100_b9121102522212">Service List</strong> and choose <strong id="elb_ug_hc_0005__en-us_topic_0167652100_b61222025142217">Network</strong> &gt; <strong id="elb_ug_hc_0005__en-us_topic_0167652100_b4124425142210">Elastic Load Balancing</strong>. </li><li id="elb_ug_hc_0005__li826120259204">Locate the load balancer and click its name.</li><li id="elb_ug_hc_0005__li119961554152810">Click <strong id="elb_ug_hc_0005__b197034217173">Backend Server Groups</strong>, locate the backend server group, and click its name.</li><li id="elb_ug_hc_0005__li416017569309">Click <strong id="elb_ug_hc_0005__b1051863016179">More</strong> in the <strong id="elb_ug_hc_0005__b951953010173">Operation</strong> column.</li><li id="elb_ug_hc_0005__li1438812372133">Select <strong id="elb_ug_hc_0005__b85441132121712">Configure Health Check</strong> from the drop-down list.</li><li id="elb_ug_hc_0005__li1623598131117">In the <strong id="elb_ug_hc_0005__b17337634122312">Basic Information</strong> area, click <strong id="elb_ug_hc_0005__b4337173442319">Configure</strong> next to <strong id="elb_ug_hc_0005__b2338153414233">Health Check</strong>.</li><li id="elb_ug_hc_0005__li353264814359">Change the health check protocol.</li><li id="elb_ug_hc_0005__li1884133194615">Click <strong id="elb_ug_hc_0005__b207371201552">OK</strong>.</li></ol>
</div>
</div>
<div>

6
docs/elb/umn/elb_ug_hd_0001.html
View File

@ -9,14 +9,14 @@
<div class="section" id="elb_ug_hd_0001__section9765648163914"><h4 class="sectiontitle">Notes</h4><p id="elb_ug_hd_0001__p39801457124614">When you add backend <span id="elb_ug_hd_0001__text1464419382514">server</span>s, note the following:</p>
<ul id="elb_ug_hd_0001__ul239818617405"><li id="elb_ug_hd_0001__li73980634016">Backend servers must be in the same VPC as the load balancer if IP as a backend is not enabled.</li><li id="elb_ug_hd_0001__li183983674015">For ease of management and maintenance, backend <span id="elb_ug_hd_0001__text1487084671110">server</span>s must run the same OS.</li><li id="elb_ug_hd_0001__li1399166134017">You can set a weight for each server in the backend <span id="elb_ug_hd_0001__text8503125112613">server</span> group. The larger the weight is, the higher proportion of requests the backend <span id="elb_ug_hd_0001__text2797123062610">server</span> receives.</li><li id="elb_ug_hd_0001__li1439920620407">If you enable sticky sessions, the proportions of requests processed by backend <span id="elb_ug_hd_0001__text15786540172820">server</span>s may become unbalanced. In this case, disable sticky sessions and check the requests received by each backend server.</li></ul>
</div>
<div class="section" id="elb_ug_hd_0001__section196816516169"><h4 class="sectiontitle">Slow Start</h4><p id="elb_ug_hd_0001__en-us_topic_0236111261_en-us_topic_0052569729_p148351859155716">After you enable slow start, the load balancer linearly increases the proportion of requests to send to backend servers in this mode. When the slow start duration elapses, the load balancer sends full share of requests to backend servers and exits the slow start mode.</p>
<div class="section" id="elb_ug_hd_0001__section196816516169"><h4 class="sectiontitle">Slow Start</h4><p id="elb_ug_hd_0001__en-us_topic_0236111261_en-us_topic_0164706626_p148351859155716">After you enable slow start, the load balancer linearly increases the proportion of requests to send to backend servers in this mode. When the slow start duration elapses, the load balancer sends full share of requests to backend servers and exits the slow start mode.</p>
</div>
<div class="p" id="elb_ug_hd_0001__p187471544136">When you enable slow start, note the following:<ul id="elb_ug_hd_0001__en-us_topic_0236111261_ul512118279397"><li id="elb_ug_hd_0001__en-us_topic_0236111261_li103585207417">Slow start can only be enabled for HTTP and HTTPS backend server groups.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li576916302045">If slow start is enabled, only the weighted round robin algorithm can be used.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li191885612382">Slow start can be enabled only for new backend servers. If a backend server group has no backend servers, slow start will not take effect for the first backend server added to the backend server group.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li5449663391">When the health check function is enabled, slow start takes effect after backend servers are detected healthy. The slow start duration will not stop even if the health check is abnormal due to network exceptions or other reasons.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li19788110396">When the health check function is disabled, slow start takes effect immediately.</li><li id="elb_ug_hd_0001__en-us_topic_0236111261_li1856810328391">After the slow start duration elapses, backend servers will not enter the slow start mode again.</li></ul>
</div>
<div class="note" id="elb_ug_hd_0001__note01614312493"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd_0001__p1716115315493">The slow start function applies only to dedicated load balancers.</p>
</div></div>
<div class="section" id="elb_ug_hd_0001__section201861524101718"><h4 class="sectiontitle">IP as Backend Servers</h4><p id="elb_ug_hd_0001__en-us_topic_0236111261_p1326872512913">If you enable IP as a backend, you can add backend servers that are not in the VPC of the load balancer, using their private IP addresses. The backend servers can be in a VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection.</p>
<div class="p" id="elb_ug_hd_0001__p4240181011357">When you add IP as backend servers, note the following:<ul id="elb_ug_hd_0001__ul1124091083511"><li id="elb_ug_hd_0001__li224018103355">If you do not enable the function when you create a load balancer, you can still enable it on the <strong id="elb_ug_hd_0001__b12229759123016">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd_0001__li72401109355">IP as backend servers must use IPv4 addresses.</li><li id="elb_ug_hd_0001__li6240610193517">Configure the VPC routes correctly to ensure that backend servers are reachable. For details, see <a href="elb_ug_hd_0003.html">Adding or Removing Backend Servers (Dedicated Load Balancers)</a>.</li><li id="elb_ug_hd_0001__li16240210173513">If you enable IP as a backend for a load balancer, you can add only TCP, HTTP, and HTTPS listeners to the load balancer.</li><li id="elb_ug_hd_0001__li9240201010354">The subnet where the load balancer works must have sufficient IP addresses (at least 16 IP addresses). You can add more subnets for more IP addresses on the <strong id="elb_ug_hd_0001__b3259172819326">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd_0001__li9240810163510">Security group rules of IP as backend servers must allow traffic from the subnet of the load balancer. Otherwise, health checks will fail.</li><li id="elb_ug_hd_0001__li6240810153514">IP as backend cannot be disabled after it is enabled.</li><li id="elb_ug_hd_0001__li112411310143517">A maximum of 492 servers can be associated with a load balancer.</li><li id="elb_ug_hd_0001__li479093210352">Source IP addresses of the clients cannot be passed to IP as backend servers. </li></ul>
<div class="section" id="elb_ug_hd_0001__section201861524101718"><h4 class="sectiontitle">IP as Backend Servers</h4><p id="elb_ug_hd_0001__en-us_topic_0236111261_p1326872512913">If you enable the IP as a Backend feature, in addition to ECSs and BMSs, you can also add IP as backend servers that are NOT in the VPC of the load balancer. The backend servers can be in a VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection.</p>
<div class="p" id="elb_ug_hd_0001__p4240181011357">When you add IP as backend servers, note the following:<ul id="elb_ug_hd_0001__ul1124091083511"><li id="elb_ug_hd_0001__li224018103355">If you do not enable the function when you create a load balancer, you can still enable it on the <strong id="elb_ug_hd_0001__b12229759123016">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd_0001__li72401109355">Only IPv4 addresses can be added as backend servers.</li><li id="elb_ug_hd_0001__li6240610193517">Configure the VPC routes correctly to ensure that backend servers are reachable. For details, see <a href="elb_ug_hd_0003.html">Adding or Removing Backend Servers (Dedicated Load Balancers)</a>.</li><li id="elb_ug_hd_0001__li16240210173513">If you enable IP as a backend for a load balancer, you can add only TCP, HTTP, and HTTPS listeners to the load balancer.</li><li id="elb_ug_hd_0001__li9240201010354">The subnet where the load balancer works must have sufficient IP addresses (at least 16 IP addresses). You can add more subnets for more IP addresses on the <strong id="elb_ug_hd_0001__b3259172819326">Summary</strong> page of the load balancer.</li><li id="elb_ug_hd_0001__li9240810163510">Security group rules of IP as backend servers must allow traffic from the subnet of the load balancer. Otherwise, health checks will fail.</li><li id="elb_ug_hd_0001__li6240810153514">IP as backend cannot be disabled after it is enabled.</li><li id="elb_ug_hd_0001__li112411310143517">A maximum of 492 servers can be associated with a load balancer.</li><li id="elb_ug_hd_0001__li479093210352">Source IP addresses of the clients cannot be passed to IP as backend servers. </li></ul>
</div>
<div class="note" id="elb_ug_hd_0001__note1630361504"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_hd_0001__p1463012614507">The IP as a backend function applies only to dedicated load balancers.</p>
</div></div>

Some files were not shown because too many files have changed in this diff Show More