elb_umn_20230303

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>

docs/elb/umn/elb_faq_0024.html

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

docs/elb/umn/elb_faq_0040.html

@@ -1,11 +1,11 @@
 <a name="elb_faq_0040"></a><a name="elb_faq_0040"></a>
 
-<h1 class="topictitle1">How Do I Check the Network Configuration of a Backend Server?</h1>
-<div id="body8662426"><ol id="elb_faq_0040__en-us_topic_0100578555_ol51835414175346"><li id="elb_faq_0040__en-us_topic_0100578555_li26028006175346">Check whether the security group of the server is correctly configured.<ol type="a" id="elb_faq_0040__en-us_topic_0100578555_ol15120255104222"><li id="elb_faq_0040__en-us_topic_0100578555_li8965360104233">On the server details page, view the security group.</li><li id="elb_faq_0040__li1256125092715">Check whether the security group rules allow access from the corresponding IP address range.<ul id="elb_faq_0040__ul18999115652214"><li id="elb_faq_0040__li2330162013231">Dedicated load balancers: Check whether the security group containing the backend server has inbound rules to allow traffic from the VPC where the load balancer works. If traffic is not allowed, add an inbound rule to allow traffic from the VPC to the backend server.</li><li id="elb_faq_0040__li613813371268"><span id="elb_faq_0040__ph988272093916">Shared</span> load balancers: Check whether the security group containing the backend server has inbound rules to allow traffic from the 100.125.0.0/16. If traffic is not allowed, add an inbound rule to allow traffic from 100.125.0.0/16<span id="elb_faq_0040__ph1944315364202"></span> to the backend server.</li></ul>
-<div class="caution" id="elb_faq_0040__note888257101120"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0040__en-us_topic_0052569751_ul6236111617482"><li id="elb_faq_0040__en-us_topic_0052569751_li9236141624819"><span id="elb_faq_0040__en-us_topic_0052569751_ph5236916144812">Shared</span> load balancers: If <strong id="elb_faq_0040__en-us_topic_0052569751_b64011211441">Obtain Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__en-us_topic_0052569751_ph3592063517">firewall</span> rules to allow traffic from 100.125.0.0/16<span id="elb_faq_0040__en-us_topic_0052569751_ph2236716134818"></span> and client IP addresses to backend servers.</li></ul>
+<h1 class="topictitle1">How Can I Check the Network Configuration of a Backend Server?</h1>
+<div id="body8662426"><ol id="elb_faq_0040__en-us_topic_0100578555_ol51835414175346"><li id="elb_faq_0040__en-us_topic_0100578555_li26028006175346">Check whether the security group of the server is correctly configured.<ol type="a" id="elb_faq_0040__en-us_topic_0100578555_ol15120255104222"><li id="elb_faq_0040__en-us_topic_0100578555_li8965360104233">On the server details page, view the security group.</li><li id="elb_faq_0040__li1256125092715">Check whether the security group rules allow access from the corresponding IP address range.<ul id="elb_faq_0040__ul18999115652214"><li id="elb_faq_0040__li2330162013231">Dedicated load balancers: Check whether the security group of the backend server has inbound rules to allow traffic from the VPC where the load balancer works. If traffic is not allowed, add an inbound rule to allow traffic from the VPC to the backend server.</li><li id="elb_faq_0040__li613813371268"><span id="elb_faq_0040__ph988272093916">Shared</span> load balancers: Check whether the security group of the backend server has inbound rules to allow traffic from the 100.125.0.0/16. If traffic is not allowed, add an inbound rule to allow traffic from 100.125.0.0/16<span id="elb_faq_0040__ph1944315364202"></span> to the backend server.</li></ul>
+<div class="caution" id="elb_faq_0040__note888257101120"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0040__en-us_topic_0052569751_ul6236111617482"><li id="elb_faq_0040__en-us_topic_0052569751_li9236141624819"><span id="elb_faq_0040__en-us_topic_0052569751_ph5236916144812">Shared</span> load balancers: If <strong id="elb_faq_0040__en-us_topic_0052569751_b64011211441">Transfer Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__en-us_topic_0052569751_ph3592063517">firewall</span> rules to allow traffic from 100.125.0.0/16<span id="elb_faq_0040__en-us_topic_0052569751_ph2236716134818"></span> and client IP addresses to backend servers.</li><li id="elb_faq_0040__en-us_topic_0052569751_li523691644811"><span id="elb_faq_0040__en-us_topic_0052569751_ph687514266355">Dedicated load balancer</span>: If <strong id="elb_faq_0040__en-us_topic_0052569751_b16338185211569">IP as a Backend</strong> is not enabled for a load balancer that has a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0040__en-us_topic_0052569751_ph19572195414362">firewall</span> rules to allow traffic from the VPC where the load balancer works to the backend servers associated with TCP or UDP listener.</li></ul>
 </div></div>
 </li></ol>
-</li><li id="elb_faq_0040__en-us_topic_0100578555_li2154564893111">Ensure that the network ACLfirewalls of the subnet where the server resides does not intercept the traffic.<p id="elb_faq_0040__en-us_topic_0100578555_p2017488793128"><a name="elb_faq_0040__en-us_topic_0100578555_li2154564893111"></a><a name="en-us_topic_0100578555_li2154564893111"></a>In the navigation pane of the VPC console, choose <strong id="elb_faq_0040__b855515395272">Access Control</strong> &gt; <strong id="elb_faq_0040__b116901318153311">Firewalls</strong> and check whether the subnet allows traffic.</p>
+</li><li id="elb_faq_0040__en-us_topic_0100578555_li2154564893111">Ensure that the firewalls of the subnet where the server resides does not intercept the traffic.<p id="elb_faq_0040__en-us_topic_0100578555_p2017488793128"><a name="elb_faq_0040__en-us_topic_0100578555_li2154564893111"></a><a name="en-us_topic_0100578555_li2154564893111"></a>In the navigation pane of the VPC console, choose <strong id="elb_faq_0040__b855515395272">Access Control</strong> &gt; <strong id="elb_faq_0040__b116901318153311">Firewalls</strong> and check whether the subnet allows traffic.</p>
 </li></ol>
 </div>
 <div>

docs/elb/umn/elb_faq_0060.html

@@ -2,7 +2,7 @@
 
 <h1 class="topictitle1">Can ELB Be Used Separately?</h1>
 <div id="body1525858887209"><p id="elb_faq_0060__p18255193114219">ELB cannot be used alone.</p>
-<p id="elb_faq_0060__p8060118">ELB is a service that distributes incoming traffic across servers and is generally used together with the ECS or BMS service.</p>
+<p id="elb_faq_0060__p8060118">ELB distributes incoming traffic to multiple backend servers based on the forwarding policy to balance workloads. So, it can expand external service capabilities of your applications and eliminate single points of failure (SPOFs) to improve service availability. To use a load balancer, you must associated backend servers (such as ECSs) with it.</p>
 </div>
 <div>
 <div class="familylinks">

docs/elb/umn/elb_faq_0074.html

@@ -0,0 +1,11 @@
+<a name="elb_faq_0074"></a><a name="elb_faq_0074"></a>
+
+<h1 class="topictitle1">Can ELB Route Traffic Across Regions?</h1>
+<div id="body1568692772111"><ul id="elb_faq_0074__ul122945544419"><li id="elb_faq_0074__li7475741155511">No. <span id="elb_faq_0074__ph14189143975516">Shared</span> load balancers cannot distribute traffic across regions.</li><li id="elb_faq_0074__li131216557333">No, but dedicated load balancers can distribute traffic across VPCs. For details about how to add backend servers in a different VPC or an on-premises data center, see <a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a>.</li></ul>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_faq_0080.html

@@ -0,0 +1,11 @@
+<a name="elb_faq_0080"></a><a name="elb_faq_0080"></a>
+
+<h1 class="topictitle1">How Can I Access a Load Balancer Across VPCs?</h1>
+<div id="body1568787676032"><p id="elb_faq_0080__p193656276212">VPC Peering can help you achieve this. For example, if another user has created load balancer ELB01 in VPC01, and you are in VPC02 and want to access ELB01, you just need to set up a VPC peering connection between VPC01 and VPC02 and add a route for the connection.</p>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0201.html">Load Balancers</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_faq_0090.html

@@ -1,8 +1,10 @@
 <a name="elb_faq_0090"></a><a name="elb_faq_0090"></a>
 
-<h1 class="topictitle1">How Can I Obtain the IP Address of a Client?</h1>
-<div id="body1437669816817"><p id="elb_faq_0090__p126130261229">When you use ELB to route requests to backend servers, IP addresses of the clients will be translated by the ELB system. This FAQ provides the operations for obtaining the IP addresses of the clients.</p>
-<div class="section" id="elb_faq_0090__section13394124610518"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_faq_0090__ul104521513161519"><li id="elb_faq_0090__li13452113161512">If Network Address Translation (NAT) is used, you cannot obtain the IP addresses of the clients.</li><li id="elb_faq_0090__li9274171501517">If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.</li><li id="elb_faq_0090__li9335359112219">If <strong id="elb_faq_0090__b352118212323">Obtain Client IP Address</strong> is enabled for TCP or UDP listeners, a cloud server cannot be used as a backend server and a client at the same time. </li><li id="elb_faq_0090__li983412419371">By default, the <strong id="elb_faq_0090__b149753488323">Obtain Client IP Address</strong> function is enabled for TCP and UDP listeners of dedicated load balancers and cannot be disabled.</li></ul>
+<h1 class="topictitle1">How Can I Transfer the IP Address of a Client?</h1>
+<div id="body1437669816817"><p id="elb_faq_0090__p126130261229">When you use ELB to route requests to backend servers, IP addresses of the clients will be translated by the ELB. This FAQ guides you to obtain the IP addresses of the clients.</p>
+<ul id="elb_faq_0090__ul083915176263"><li id="elb_faq_0090__li10839121712614">Load balancing at Layer 7 (HTTP or HTTPS listeners): Configure the application server and obtain the IP address of a client from the HTTP header.<p id="elb_faq_0090__p67604963112"><a name="elb_faq_0090__li10839121712614"></a><a name="li10839121712614"></a>For details, see <a href="#elb_faq_0090__section12598161410315">Layer 7 Load Balancing</a>.</p>
+</li><li id="elb_faq_0090__li82841612175818">For load balancing at Layer 4 (TCP/UDP), you can enable <strong id="elb_faq_0090__b3216413303">Transfer Client IP Address</strong> to obtain the source IP address.</li></ul>
+<div class="section" id="elb_faq_0090__section13394124610518"><h4 class="sectiontitle">Constraints and Limitations</h4><ul id="elb_faq_0090__ul104521513161519"><li id="elb_faq_0090__li13452113161512">If Network Address Translation (NAT) is used, you cannot obtain the IP addresses of the clients.</li><li id="elb_faq_0090__li9274171501517">If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.</li><li id="elb_faq_0090__li9335359112219">If <strong id="elb_faq_0090__b352118212323">Transfer Client IP Address</strong> is enabled for TCP or UDP listeners, a cloud server cannot be used as a backend server and a client at the same time. </li><li id="elb_faq_0090__li983412419371">By default, the <strong id="elb_faq_0090__b149753488323">Transfer Client IP Address</strong> function is enabled for TCP and UDP listeners of dedicated load balancers and cannot be disabled.</li></ul>
 </div>
 <div class="section" id="elb_faq_0090__section12598161410315"><a name="elb_faq_0090__section12598161410315"></a><a name="section12598161410315"></a><h4 class="sectiontitle">Layer 7 Load Balancing</h4><p id="elb_faq_0090__p1023417204310">Configure the application server and obtain the IP address of a client from the HTTP header.</p>
 </div>
@@ -17,7 +19,7 @@ RemoteIPHeader X-Forwarded-For
 RemoteIPInternalProxy <strong id="elb_faq_0090__b1977615149432"><em id="elb_faq_0090__i1777601412436">100.125.0.0/16</em></strong></pre>
 <div class="fignone" id="elb_faq_0090__fig1553761545210"><span class="figcap"><b>Figure 1 </b>Content to be added</span><br><span><img id="elb_faq_0090__image1368125117439" src="en-us_image_0174899056.jpg"></span></div>
 <div class="note" id="elb_faq_0090__note135510197505"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p11969135614319">Add the IP address range of the proxy server after <strong id="elb_faq_0090__b110010178155">RemoteIPInternalProxy</strong>.</p>
-<ul id="elb_faq_0090__ul5985165818319"><li id="elb_faq_0090__li49865581436"><span id="elb_faq_0090__ph1911810238">Shared</span> load balancers: 100.125.0.0/16<span id="elb_faq_0090__ph1820812303110"></span> and the IP address range used by the AAD service. Load balancers use IP addresses in 100.125.0.0/16 to communicate with backend servers, and there are no security risks. Use commas (,) to separate multiple entries.</li><li id="elb_faq_0090__li6194337848">Dedicated load balancers: CIDR block of the subnet where the load balancer resides</li></ul>
+<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>
 </li><li id="elb_faq_0090__li10895421174213">Change the log output format in the Apache configuration file to the following (<strong id="elb_faq_0090__b1311681216319">%a</strong> indicates the source IP address):<pre class="screen" id="elb_faq_0090__screen13565739124411">LogFormat "<em id="elb_faq_0090__i18199122934118"><strong id="elb_faq_0090__b5762132774111">%</strong><strong id="elb_faq_0090__b194131533162710">a</strong></em> %l %u %t \"%r\" %&gt;s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined</pre>
 </li><li id="elb_faq_0090__li1851619394515">Restart Apache.<pre class="screen" id="elb_faq_0090__screen108061723195117">systemctl restart httpd</pre>
@@ -73,16 +75,15 @@ cat localhost_access_log..2021-11-29.txt</pre>
 </li><li id="elb_faq_0090__li16707014261">Click <strong id="elb_faq_0090__b8679927125015">Restart</strong> on the homepage to restart IIS. The configuration will take effect after the restart.<div class="fignone" id="elb_faq_0090__fig116681600263"><span class="figcap"><b>Figure 13 </b>Restarting IIS</span><br><span><img id="elb_faq_0090__image8470105182515" src="en-us_image_0267446611.png"></span></div>
 </li></ol>
 <div class="section" id="elb_faq_0090__section867518427319"><h4 class="sectiontitle">Layer 4 Load Balancing</h4><p id="elb_faq_0090__p10578835171913"></p>
-<p id="elb_faq_0090__p1337010443011">For load balancing at Layer 4 (TCP or UDP listeners), use either of the following methods to obtain the real IP address of a client:</p>
-<ul id="elb_faq_0090__ul3140135223013"><li id="elb_faq_0090__li13140155233012"><strong id="elb_faq_0090__b6980112313279">Method 1 (for TCP or UDP listeners)</strong>: Enable the function of obtaining IP addresses of the clients.<ol id="elb_faq_0090__ol730222417346"><li id="elb_faq_0090__li330222433410">Perform the following steps to enable the function:<ol type="a" id="elb_faq_0090__ol16390953185514"><li id="elb_faq_0090__li677391520332">Log in to the management console.</li><li id="elb_faq_0090__li675519100420">In the upper left corner of the page, click <span><img id="elb_faq_0090__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_faq_0090__li335918093210">Click <strong id="elb_faq_0090__b1662070101">Service List</strong>. Under <strong id="elb_faq_0090__b2034119728"><span id="elb_faq_0090__ph321897927">Network</span></strong>, click <strong id="elb_faq_0090__b1837452777">Elastic Load Balance</strong>.</li><li id="elb_faq_0090__li1379615339436">In the load balancer list, click the name of the load balancer.</li><li id="elb_faq_0090__li475294174319">Click <strong id="elb_faq_0090__b1638472470">Listeners</strong>.<ul id="elb_faq_0090__ul124372032185517"><li id="elb_faq_0090__li543763255519">To add a listener, click <strong id="elb_faq_0090__b1377149182415">Add Listener</strong>.</li><li id="elb_faq_0090__li12437132115511">To modify a listener, locate the listener and click <span><img id="elb_faq_0090__image135811568494" src="en-us_image_0255608096.png"></span> on the right of its name.</li></ul>
-</li><li id="elb_faq_0090__li3100135715344">Enable <strong id="elb_faq_0090__b745821111385">Obtain Client IP Address</strong>.</li></ol>
-</li><li id="elb_faq_0090__li99008095116">Configure security groups, network ACLs, and OS and software security policies so that IP addresses of the clients can access these backend servers.<div class="caution" id="elb_faq_0090__note9310112602213"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0090__en-us_topic_0052569751_ul6236111617482"><li id="elb_faq_0090__en-us_topic_0052569751_li9236141624819"><span id="elb_faq_0090__en-us_topic_0052569751_ph5236916144812">Shared</span> load balancers: If <strong id="elb_faq_0090__en-us_topic_0052569751_b64011211441">Obtain Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0090__en-us_topic_0052569751_ph3592063517">firewall</span> rules to allow traffic from 100.125.0.0/16<span id="elb_faq_0090__en-us_topic_0052569751_ph2236716134818"></span> and client IP addresses to backend servers.</li></ul>
+<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>.<ol id="elb_faq_0090__ol730222417346"><li id="elb_faq_0090__li330222433410">Perform the following steps to enable the function:<ol type="a" id="elb_faq_0090__ol16390953185514"><li id="elb_faq_0090__li677391520332">Log in to the management console.</li><li id="elb_faq_0090__li675519100420">In the upper left corner of the page, click <span><img id="elb_faq_0090__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_faq_0090__li335918093210">Click <strong id="elb_faq_0090__b667829828">Service List</strong>. Under <strong id="elb_faq_0090__b1119839681"><span id="elb_faq_0090__ph395765684">Network</span></strong>, click <strong id="elb_faq_0090__b1994239027">Elastic Load Balance</strong>.</li><li id="elb_faq_0090__li1379615339436">In the load balancer list, click the name of the load balancer.</li><li id="elb_faq_0090__li475294174319">Click <strong id="elb_faq_0090__b417418053">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>
+</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="caution" id="elb_faq_0090__note9310112602213"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="elb_faq_0090__en-us_topic_0052569751_ul6236111617482"><li id="elb_faq_0090__en-us_topic_0052569751_li9236141624819"><span id="elb_faq_0090__en-us_topic_0052569751_ph5236916144812">Shared</span> load balancers: If <strong id="elb_faq_0090__en-us_topic_0052569751_b64011211441">Transfer Client IP Address</strong> is enabled for a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0090__en-us_topic_0052569751_ph3592063517">firewall</span> rules to allow traffic from 100.125.0.0/16<span id="elb_faq_0090__en-us_topic_0052569751_ph2236716134818"></span> and client IP addresses to backend servers.</li><li id="elb_faq_0090__en-us_topic_0052569751_li523691644811"><span id="elb_faq_0090__en-us_topic_0052569751_ph687514266355">Dedicated load balancer</span>: If <strong id="elb_faq_0090__en-us_topic_0052569751_b16338185211569">IP as a Backend</strong> is not enabled for a load balancer that has a TCP or UDP listener, there is no need to configure security group rules and <span id="elb_faq_0090__en-us_topic_0052569751_ph19572195414362">firewall</span> rules to allow traffic from the VPC where the load balancer works to the backend servers associated with TCP or UDP listener.</li></ul>
 </div></div>
-<div class="p" id="elb_faq_0090__p3759133762118"><div class="note" id="elb_faq_0090__note9800635192119"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p17774359172118">If you enable this function, a server cannot be used as both the client and the backend server. If the client and the backend server use the same server and the <strong id="elb_faq_0090__b1447693595">Obtain Client IP Address</strong> option is enabled, the backend server will think the packet from the client is sent by itself and will not return a response packet to the load balancer. As a result, the return traffic will be interrupted.</p>
+<div class="p" id="elb_faq_0090__p3759133762118"><div class="note" id="elb_faq_0090__note9800635192119"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_faq_0090__p17774359172118">If you enable this function, a server cannot be used as both the client and the backend server. If the client and the backend server use the same server and the <strong id="elb_faq_0090__b735926965">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>
 </div>
 </li></ol>
-</li><li id="elb_faq_0090__li198181611346"><strong id="elb_faq_0090__b922631014271">Method 2 (for TCP listeners)</strong>: Configure the TOA plug-in.<p id="elb_faq_0090__p4144133031314">TCP listeners require the TOA plug-in to obtain real IP addresses. For details, see <a href="en-us_elb_06_0001.html">Configuring the TOA Module</a>.</p>
 </li></ul>
 </div>
 </div>

docs/elb/umn/elb_faq_0112.html

@@ -1,6 +1,6 @@
 <a name="elb_faq_0112"></a><a name="elb_faq_0112"></a>
 
-<h1 class="topictitle1">Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Configured?</h1>
+<h1 class="topictitle1">Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Have Configured?</h1>
 <div id="body1575703621396"><p id="elb_faq_0112__p1294414571272">Each LVS node and Nginx node in the ELB system send detection packets to backend servers at the health check interval that you have specified for the backend server group.</p>
 <p id="elb_faq_0112__p8060118">During this period, backend servers receive multiple detection packets from LVS and Nginx nodes. This makes it seem like backend servers are receiving packets at intervals shorter than the specified health check interval.</p>
 </div>

docs/elb/umn/elb_faq_0131.html

@@ -0,0 +1,11 @@
+<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>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0203.html">Backend Servers</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_faq_0135.html

@@ -0,0 +1,11 @@
+<a name="elb_faq_0135"></a><a name="elb_faq_0135"></a>
+
+<h1 class="topictitle1">Can ELB Be Used Across Accounts or VPCs?</h1>
+<div id="body1590464381352"><ul id="elb_faq_0135__ul1875610623020"><li id="elb_faq_0135__li89051910123112">Your <span id="elb_faq_0135__ph660616083117">Shared</span> load balancers cannot be used by another account, and you cannot associate backend servers whose VPCs are not the same as the load balancers.</li><li id="elb_faq_0135__li17784848448">For <span id="elb_faq_0135__ph48931152183716">Dedicated load balancer</span>s, you can add servers in a VPC connected using a VPC peering connection, in a VPC in another region and connected through a cloud connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses. For details, see <a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a>.</li></ul>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0211.html">ELB Functionality</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_faq_0170.html

@@ -1,14 +1,10 @@
 <a name="elb_faq_0170"></a><a name="elb_faq_0170"></a>
 
-
-  <h1 class="topictitle1">Obtaining Source IP Addresses</h1>
-
-  <div id="body1590575971687"><p id="elb_faq_0170__p8060118"></p>
-</div>
-
+<h1 class="topictitle1">Obtaining Source IP Addresses</h1>
+<div id="body1590575971687"></div>
 <div>
 <ul class="ullinks">
-<li class="ulchildlink"><strong><a href="elb_faq_0090.html">How Can I Obtain the IP Address of a Client?</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_faq_0090.html">How Can I Transfer the IP Address of a Client?</a></strong><br>
 </li>
 </ul>
 

docs/elb/umn/elb_faq_0180.html

@@ -1,7 +1,7 @@
 <a name="elb_faq_0180"></a><a name="elb_faq_0180"></a>
 
 <h1 class="topictitle1">HTTP/HTTPS Listeners</h1>
-<div id="body1590575971687"><p id="elb_faq_0180__p8060118"></p>
+<div id="body1590575971687"><p id="elb_faq_0180__p962411440229"></p>
 </div>
 <div>
 <ul class="ullinks">

docs/elb/umn/elb_faq_0200.html

@@ -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 Obtain the IP Address of a Client?</a></li><li id="elb_faq_0200__li11561850133210"><a href="en-us_topic_0018127975.html">How Do I Troubleshoot an Unhealthy Backend Server?</a></li><li id="elb_faq_0200__li1176130193315"><a href="elb_faq_0024.html">How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?</a></li><li id="elb_faq_0200__li31438516331"><a href="elb_faq_0085.html">What Types of Sticky Sessions Does ELB Support?</a></li><li id="elb_faq_0200__li1385051016337"><a href="elb_faq_0111.html">How Is WebSocket Used?</a></li><li id="elb_faq_0200__li911814137339"><a href="elb_faq_0046.html">How Do I Check If Sticky Sessions Failed to Take Effect?</a></li><li id="elb_faq_0200__li1077718234335"><a href="en-us_elb_05_0008.html">What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?</a></li><li id="elb_faq_0200__li191851335103319"><a href="elb_faq_0038.html">How Does ELB Distribute Traffic?</a></li></ul>
+<div 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>
 <div>
 <div class="familylinks">

docs/elb/umn/elb_faq_0201.html

@@ -6,7 +6,9 @@
 <ul class="ullinks">
 <li class="ulchildlink"><strong><a href="elb_faq_0038.html">How Does ELB Distribute Traffic?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="elb_faq_210307.html">Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load BalancerLoad Balancer?</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_faq_0080.html">How Can I Access a Load Balancer Across VPCs?</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="elb_faq_210307.html">Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load Balancer?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_210310.html">Do Shared Load Balancers Have Specifications?</a></strong><br>
 </li>

docs/elb/umn/elb_faq_0202.html

@@ -4,12 +4,14 @@
 <div id="body1575701761779"></div>
 <div>
 <ul class="ullinks">
-<li class="ulchildlink"><strong><a href="en-us_elb_05_0008.html">What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_faq_05_0008.html">What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_0084.html">Does ELB Have Restrictions on the File Upload Speed and Size?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_0111.html">How Is WebSocket Used?</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="elb_faq_210409.html">Why Can't I Select the Target Backend Server Group When Adding or Modifying a Listener?</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="elb_faq_210410.html">Why Cannot I Add a Listener to a Dedicated Load Balancer?</a></strong><br>
 </li>
 </ul>

docs/elb/umn/elb_faq_0203.html

@@ -4,18 +4,22 @@
 <div id="body1575701762331"></div>
 <div>
 <ul class="ullinks">
-<li class="ulchildlink"><strong><a href="elb_faq_0112.html">Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Configured?</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_faq_0112.html">Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Have Configured?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="elb_faq_099.html">Can Servers Access the Internet After They Are Associated with a Load Balancer?</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_faq_099.html">Can Backend Servers Access the Internet After They Are Associated with a Load Balancer?</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="elb_faq_0074.html">Can ELB Route Traffic Across Regions?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_0039.html">How Do I Check the Network Conditions of a Backend Server?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="elb_faq_0040.html">How Do I Check the Network Configuration of a Backend Server?</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_faq_0040.html">How Can I Check the Network Configuration of a Backend Server?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_0041.html">How Do I Check the Status of a Backend Server?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_0001.html">When Is a Backend Server Considered Healthy?</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="elb_faq_0131.html">Why Must the Subnet Where the Load Balancer Resides Have at Least 16 Available IP Addresses for Enabling IP as a Backend?</a></strong><br>
+</li>
 </ul>
 
 <div class="familylinks">

docs/elb/umn/elb_faq_0211.html

@@ -8,12 +8,14 @@
 </li>
 <li class="ulchildlink"><strong><a href="en-us_elb_05_0011.html">Is an EIP Assigned Exclusively to a Load Balancer?</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="en-us_elb_05_0004.html">How Many Load Balancers and Listeners Can I Have?</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_faq_05_0004.html">How Many Load Balancers and Listeners Can I Have?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_0062.html">Can I Adjust the Number of Backend Servers When a Load Balancer is Running?</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_faq_0064.html">Can Backend Servers Run Different OSs?</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="elb_faq_0135.html">Can ELB Be Used Across Accounts or VPCs?</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="elb_faq_21020221.html">Can I Upgrade a Shared Load Balancer to a Dedicated Load Balancer Without Interrupting Traffic Routing?</a></strong><br>
 </li>
 </ul>

docs/elb/umn/elb_faq_05_0004.html

@@ -0,0 +1,12 @@
+<a name="elb_faq_05_0004"></a><a name="elb_faq_05_0004"></a>
+
+<h1 class="topictitle1">How Many Load Balancers and Listeners Can I Have?</h1>
+<div id="body1437669816816"><p id="elb_faq_05_0004__p634223815288">By default, an account can create up to 50 load balancers, including both <span id="elb_faq_05_0004__ph18691335092">shared</span> and dedicated load balancers and 100 listeners. If you need more load balancers or listeners, apply for higher quotas.</p>
+<p id="elb_faq_05_0004__p156794518262">All load balancers in your account share the same quota for listeners.</p>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0211.html">ELB Functionality</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_faq_099.html

@@ -1,7 +1,7 @@
 <a name="elb_faq_099"></a><a name="elb_faq_099"></a>
 
-<h1 class="topictitle1">Can Servers Access the Internet After They Are Associated with a Load Balancer?</h1>
-<div id="body1566463582245"><p id="elb_faq_099__p8060118">Yes. Servers can access the Internet regardless of if they are associated with a load balancer.</p>
+<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>
 <div>
 <div class="familylinks">

docs/elb/umn/elb_faq_210307.html

@@ -1,8 +1,8 @@
 <a name="elb_faq_210307"></a><a name="elb_faq_210307"></a>
 
-<h1 class="topictitle1">Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load BalancerLoad Balancer?</h1>
+<h1 class="topictitle1">Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load Balancer?</h1>
 <div id="body0000001191123875"><p id="elb_faq_210307__p82254326153">These IP addresses are used by underlying resources.</p>
-<p id="elb_faq_210307__p8060118">Generally, 2 IP addresses are required for creating a dedicated load balancer in a single AZ, and 6 IP addresses are required for creating a dedicated load balancer with cross-VPC backend enabled. If you create a dedicated load balancer in multiple AZs, more IP addresses will be required. There is an algorithm to determine how many IP addresses are required.</p>
+<p id="elb_faq_210307__p8060118">Generally, 2 IP addresses are required for creating a dedicated load balancer in a single AZ, and 6 IP addresses are required for creating a dedicated load balancer with 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 determine how many IP addresses are required.</p>
 </div>
 <div>
 <div class="familylinks">

docs/elb/umn/elb_faq_210409.html

@@ -0,0 +1,71 @@
+<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 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>
+<th align="left" class="cellrowborder" valign="top" width="59.64%" id="mcps1.3.2.2.3.1.2"><p id="elb_faq_210409__p6803193816339">Backend Protocol</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="elb_faq_210409__row1480333819339"><td class="cellrowborder" valign="top" width="40.36%" headers="mcps1.3.2.2.3.1.1 "><p id="elb_faq_210409__p12803133816336">TCP</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.64%" headers="mcps1.3.2.2.3.1.2 "><p id="elb_faq_210409__p158039381334">TCP</p>
+</td>
+</tr>
+<tr id="elb_faq_210409__row1680311388338"><td class="cellrowborder" valign="top" width="40.36%" headers="mcps1.3.2.2.3.1.1 "><p id="elb_faq_210409__p480363813335">UDP</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.64%" headers="mcps1.3.2.2.3.1.2 "><p id="elb_faq_210409__p18031838123312">UDP/QUIC</p>
+</td>
+</tr>
+<tr id="elb_faq_210409__row4634173915342"><td class="cellrowborder" valign="top" width="40.36%" headers="mcps1.3.2.2.3.1.1 "><p id="elb_faq_210409__p363523963411">HTTP</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.64%" headers="mcps1.3.2.2.3.1.2 "><p id="elb_faq_210409__p3635163923414">HTTP</p>
+</td>
+</tr>
+<tr id="elb_faq_210409__row118036384336"><td class="cellrowborder" valign="top" width="40.36%" headers="mcps1.3.2.2.3.1.1 "><p id="elb_faq_210409__p5803183843312">HTTPS</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.64%" headers="mcps1.3.2.2.3.1.2 "><p id="elb_faq_210409__p48031038123313">HTTP/HTTPS</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_faq_210409__table72272618376" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Frontend and backend protocols of shared load balancers</caption><thead align="left"><tr id="elb_faq_210409__row112283617377"><th align="left" class="cellrowborder" valign="top" width="40.31%" id="mcps1.3.3.2.3.1.1"><p id="elb_faq_210409__p32281368378">Frontend Protocol</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="59.69%" id="mcps1.3.3.2.3.1.2"><p id="elb_faq_210409__p122291761373">Backend Protocol</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="elb_faq_210409__row18229269376"><td class="cellrowborder" valign="top" width="40.31%" headers="mcps1.3.3.2.3.1.1 "><p id="elb_faq_210409__p722914623718">TCP</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.69%" headers="mcps1.3.3.2.3.1.2 "><p id="elb_faq_210409__p568635243911">TCP</p>
+</td>
+</tr>
+<tr id="elb_faq_210409__row22291763376"><td class="cellrowborder" valign="top" width="40.31%" headers="mcps1.3.3.2.3.1.1 "><p id="elb_faq_210409__p82299614375">UDP</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.69%" headers="mcps1.3.3.2.3.1.2 "><p id="elb_faq_210409__p2068655273916">UDP</p>
+</td>
+</tr>
+<tr id="elb_faq_210409__row122913616372"><td class="cellrowborder" valign="top" width="40.31%" headers="mcps1.3.3.2.3.1.1 "><p id="elb_faq_210409__p1322917623714">HTTP</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.69%" headers="mcps1.3.3.2.3.1.2 "><p id="elb_faq_210409__p368618524395">HTTP</p>
+</td>
+</tr>
+<tr id="elb_faq_210409__row822926143712"><td class="cellrowborder" valign="top" width="40.31%" headers="mcps1.3.3.2.3.1.1 "><p id="elb_faq_210409__p42291693711">HTTPS</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.69%" headers="mcps1.3.3.2.3.1.2 "><p id="elb_faq_210409__p156866524399">HTTP</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_faq_0202.html">Listeners</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_faq_210410.html

@@ -1,7 +1,7 @@
 <a name="elb_faq_210410"></a><a name="elb_faq_210410"></a>
 
 <h1 class="topictitle1">Why Cannot I Add a Listener to a Dedicated Load Balancer?</h1>
-<div id="body0000001194920880"><p id="elb_faq_210410__p573834519438">If you select either network load balancing (TCP/UDP) or application load balancing (HTTP/HTTPS) when creating the load balancer, you can only add listeners of the corresponding protocol.</p>
+<div id="body0000001194920880"><p id="elb_faq_210410__p573834519438">If you select either network load balancing (TCP/UDP) or application load balancing (HTTP/HTTPS) when creating the load balancer, you can only add listeners of the matched protocol.</p>
 <p id="elb_faq_210410__p8060118">The load balancing type cannot be changed after being selected. For example, if you have selected network load balancing during load balancer creation, you cannot change it to application load balancing and you cannot add HTTP or HTTPS listeners.</p>
 
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_faq_210410__table158021438173312" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Protocols and load balancing types</caption><thead align="left"><tr id="elb_faq_210410__row1580353819330"><th align="left" class="cellrowborder" valign="top" width="29.99%" id="mcps1.3.3.2.4.1.1"><p id="elb_faq_210410__p1480319381335">Load Balancing Type</p>

docs/elb/umn/elb_lb_000010.html

@@ -1,9 +1,10 @@
 <a name="elb_lb_000010"></a><a name="elb_lb_000010"></a>
 
 <h1 class="topictitle1">Changing an IP Address</h1>
-<div id="body8662426"><div class="section" id="elb_lb_000010__en-us_topic_0172882190_section57040304257"><h4 class="sectiontitle">Scenarios</h4><p id="elb_lb_000010__en-us_topic_0172882190_p9663124616522">ELB allows you to change private IPv4 addresses of load balancers. New private IPv4 addresses can be from the current subnet or other subnets. </p>
+<div 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>
-<div class="section" id="elb_lb_000010__en-us_topic_0172882190_section465072113222"><h4 class="sectiontitle">Changing a Private IPv4 Address</h4><ol id="elb_lb_000010__en-us_topic_0172882190_ol10560182413"><li id="elb_lb_000010__en-us_topic_0172882190_li677391520332">Log in to the management console.</li><li id="elb_lb_000010__en-us_topic_0172882190_li675519100420">In the upper left corner of the page, click <span><img id="elb_lb_000010__en-us_topic_0240829509_image1542118117117" src="en-us_image_0000001211126503.png"></span> and select the desired region and project.</li><li id="elb_lb_000010__li83736197297">Hover on <span><img id="elb_lb_000010__en-us_topic_0052569751_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.png"></span> in the upper left corner to display <strong id="elb_lb_000010__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_lb_000010__en-us_topic_0052569751_b61222025142217">Network</strong> &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__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>
 </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>

docs/elb/umn/elb_pro_0000.html

@@ -16,7 +16,7 @@
 </li>
 <li class="ulchildlink"><strong><a href="en-us_topic_0287737145.html">Specifications of Dedicated Load Balancers</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="en-us_elb_01_0004.html">Load Balancing on a Public or Private Network</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_pro_01_0004.html">Load Balancing on a Public or Private Network</a></strong><br>
 </li>
 <li class="ulchildlink"><strong><a href="elb_ug_fz_0003_01.html">Network Traffic Paths</a></strong><br>
 </li>

docs/elb/umn/elb_pro_0002.html

@@ -11,7 +11,7 @@
 <div class="section" id="elb_pro_0002__en-us_topic_0184026189_section193971112578"><h4 class="sectiontitle">Selecting an AZ</h4><p id="elb_pro_0002__en-us_topic_0184026189_p859161416717">When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.</p>
 <ul id="elb_pro_0002__en-us_topic_0184026189_ul157203571473"><li id="elb_pro_0002__en-us_topic_0184026189_li7720175710711">For high DR capability, deploy resources in different AZs within the same region.</li><li id="elb_pro_0002__en-us_topic_0184026189_li109763595719">For lower network latency, deploy resources in the same AZ.</li></ul>
 </div>
-<div class="section" id="elb_pro_0002__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="elb_pro_0002__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/en-us/endpoint/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
+<div class="section" id="elb_pro_0002__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="elb_pro_0002__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/additional/endpoints.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
 </div>
 </div>
 <div>

docs/elb/umn/elb_pro_0003.html

@@ -3,8 +3,8 @@
 <h1 class="topictitle1">How ELB Works</h1>
 <div id="body1516070328064"><div class="fignone" id="elb_pro_0003__fig34721951104111"><span class="figcap"><b>Figure 1 </b>How ELB works</span><br><span><img id="elb_pro_0003__image1847295194110" src="en-us_image_0000001253004159.png"></span></div>
 <p id="elb_pro_0003__p158481225105114">The following describes how ELB works:</p>
-<ol id="elb_pro_0003__ol16216341115120"><li id="elb_pro_0003__li1121634118515">A client sends a request to your application.</li><li id="elb_pro_0003__li14626175511549">The listeners added to your load balancer use the protocols and ports you configure to receive the request.</li><li id="elb_pro_0003__li13200162614554">The listener forwards the request to the associated backend server group based on your configuration. If you have configured a forwarding policy for the listener, the listener evaluates the request based on the forwarding policy. If the request matches the forwarding policy, the listener forwards the request to the backend server group configured for the forwarding policy.</li><li id="elb_pro_0003__li19582026583">Health backend servers in the backend server group receive the request based on the load balancing algorithm and the routing rules you specify in the forwarding policy, handle the request, and return a result to the client.</li></ol>
-<p id="elb_pro_0003__p511191615473">How requests are routed depends on the <strong id="elb_pro_0003__b137115714517"><a href="#elb_pro_0003__section12605144013346">load balancing algorithms</a></strong> configured for each backend server group. If the listener uses HTTP or HTTPS, how requests are routed also depends on the <strong id="elb_pro_0003__b176419294333">forwarding policies</strong> configured for the listener.</p>
+<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__p126518420210">Both dedicated and <span id="elb_pro_0003__ph1365217417216">shared</span> load balancers support weighted round robin, weighted least connections, and source IP hash.</p>
 <div class="p" id="elb_pro_0003__p1625369143019"><ul id="elb_pro_0003__ul62874421822"><li id="elb_pro_0003__li1728610427215">Weighted round robin: Requests are routed to backend servers using the round robin algorithm. Backend servers with higher weights receive proportionately more requests, whereas equal-weighted servers receive the same number of requests. This algorithm is often used for short connections, such as HTTP connections.<p id="elb_pro_0003__p16438104524911"><a name="elb_pro_0003__li1728610427215"></a><a name="li1728610427215"></a>The following figure shows an example of how requests are distributed using the weighted round robin algorithm. Two backend <span id="elb_pro_0003__text1263703874517">server</span>s are in the same AZ and have the same weight, and each <span id="elb_pro_0003__text7688194514452">server</span> receives the same proportion of requests.</p>
 <div class="fignone" id="elb_pro_0003__fig7538148162412"><span class="figcap"><b>Figure 2 </b>Traffic distribution using the weighted round robin algorithm</span><br><span><img id="elb_pro_0003__image173432046115015" src="en-us_image_0000001160373426.png"></span></div>

docs/elb/umn/elb_pro_0005.html

@@ -1,21 +1,20 @@
 <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 and can provide guaranteed performance, 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>
+<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.</li><li id="elb_pro_0005__li0765191117216">For requests from a private network:<ul id="elb_pro_0005__ul187611211172118"><li id="elb_pro_0005__li933021614230">If clients are in an AZ you select when you create the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ you select.</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></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>Dedicated load balancers can route traffic uninterruptedly. If your servers in one AZ are unhealthy, dedicated load balancers automatically route traffic to healthy servers in other AZs. Dedicated load balancers provide 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 security<p id="elb_pro_0005__p16773129816"><a name="elb_pro_0005__li6423824716"></a><a name="li6423824716"></a>Dedicated load balancers support TLS 1.3 and can route HTTPS requests to backend servers. Dedicated load balancers also allow you to select security policies that fit your security requirements.</p>
-</li><li id="elb_pro_0005__li248013404119">Multiple protocols<p id="elb_pro_0005__p92691543417"><a name="elb_pro_0005__li248013404119"></a><a name="li248013404119"></a>Dedicated load balancers support the following protocols, including TCP, UDP, HTTP, and HTTPS, so that they can route requests from different types of applications.</p>
-</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>Dedicated 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__li678521215145">High reliability<p id="elb_pro_0005__p147852122146"><a name="elb_pro_0005__li678521215145"></a><a name="li678521215145"></a>Dedicated load balancers can be deployed across AZs and can distribute traffic more evenly.</p>
+</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>
+</li><li id="elb_pro_0005__li248013404119">Multiple protocols<p id="elb_pro_0005__p92691543417"><a name="elb_pro_0005__li248013404119"></a><a name="li248013404119"></a>ELB supports , TCP, UDP, HTTP, and HTTPS, so that they can route requests to different types of applications.</p>
+</li><li id="elb_pro_0005__li108770162710">No limits<p id="elb_pro_0005__p987204271"><a name="elb_pro_0005__li108770162710"></a><a name="li108770162710"></a>ELB can route requests to both servers on the cloud and on premises, allowing you to leverage cloud resources to handle burst traffic.</p>
+</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__li65684418329">Robust performance<p id="elb_pro_0005__p25611444324"><a name="elb_pro_0005__li65684418329"></a><a name="li65684418329"></a><span id="elb_pro_0005__ph187162200239">Shared</span> load balancers are deployed in clusters, which can handle up to 100 million concurrent connections and 1 million new connections per second, meeting your requirements for handling huge numbers of concurrent requests.</p>
-</li><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>
-</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><span id="elb_pro_0005__ph5591180735">Shared</span> load balancers support the following protocols: TCP, UDP, HTTP, and HTTPS, so that they can route requests from different types of applications.</p>
+<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>
+</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></ul>

docs/elb/umn/elb_pro_0006.html

@@ -8,7 +8,7 @@
 <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>
-<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 healthy state. If any backend server is detected unhealthy, ELB will not route requests to this server until it recovers.</p>
+<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>

docs/elb/umn/elb_pro_0008.html

@@ -5,8 +5,6 @@
 </li><li id="elb_pro_0008__li877828094211">Auto Scaling (AS)<p id="elb_pro_0008__p14926099"><a name="elb_pro_0008__li877828094211"></a><a name="li877828094211"></a>Works with ELB to automatically scale the number of backend servers for faster traffic distribution.</p>
 </li><li id="elb_pro_0008__li28091464165756">Identity and Access Management (IAM)<p id="elb_pro_0008__p2332656216588"><a name="elb_pro_0008__li28091464165756"></a><a name="li28091464165756"></a>Provides authentication for ELB.</p>
 </li><li id="elb_pro_0008__li15363634211">Elastic Cloud Server (ECS)<p id="elb_pro_0008__p152695491733"><a name="elb_pro_0008__li15363634211"></a><a name="li15363634211"></a>Provides cloud servers to run your applications in the cloud. Configure load balancers to route traffic to the servers or containers.</p>
-</li><li id="elb_pro_0008__li8230187323">Log Tank Service (LTS)<p id="elb_pro_0008__p8728191934"><a name="elb_pro_0008__li8230187323"></a><a name="li8230187323"></a>Stores access logs of HTTP or HTTPS requests to your load balancer for query and analysis later if you have enabled access logging.</p>
-</li><li id="elb_pro_0008__li3628756017026">Cloud Trace Service (CTS)<p id="elb_pro_0008__p3187313017149"><a name="elb_pro_0008__li3628756017026"></a><a name="li3628756017026"></a>Records the operations performed on ELB resources.</p>
 </li><li id="elb_pro_0008__li41153227165811">Cloud Eye<p id="elb_pro_0008__p4197074717056"><a name="elb_pro_0008__li41153227165811"></a><a name="li41153227165811"></a>Monitors the status of load balancers and listeners, without any additional plug-in.</p>
 </li></ul>
 </div>

docs/elb/umn/elb_pro_01_0004.html

@@ -0,0 +1,67 @@
+<a name="elb_pro_01_0004"></a><a name="elb_pro_01_0004"></a>
+
+<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>
+<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>
+<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>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="16.79167916791679%" id="mcps1.3.4.2.2.4.1.2"><p id="elb_pro_01_0004__p117121372470">Network Type</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="63.19631963196319%" id="mcps1.3.4.2.2.4.1.3"><p id="elb_pro_01_0004__p071210774720">Description</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="elb_pro_01_0004__row1271247194717"><td class="cellrowborder" rowspan="2" valign="top" width="20.01200120012001%" headers="mcps1.3.4.2.2.4.1.1 "><p id="elb_pro_01_0004__p9712187154711">Dedicated load balancers</p>
+</td>
+<td class="cellrowborder" valign="top" width="16.79167916791679%" headers="mcps1.3.4.2.2.4.1.2 "><p id="elb_pro_01_0004__p1971212724712">Public IPv4 network</p>
+</td>
+<td class="cellrowborder" valign="top" width="63.19631963196319%" headers="mcps1.3.4.2.2.4.1.3 "><p id="elb_pro_01_0004__p14712107144714">Each load balancer has an IPv4 EIP bound to enable it to route requests over the Internet.</p>
+</td>
+</tr>
+<tr id="elb_pro_01_0004__row1571287184718"><td class="cellrowborder" valign="top" headers="mcps1.3.4.2.2.4.1.1 "><p id="elb_pro_01_0004__p1271237144714">Private IPv4 network</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.3.4.2.2.4.1.2 "><p id="elb_pro_01_0004__p19713107154713">Each load balancer has only a private IPv4 address and can route requests in a VPC.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="elb_pro_01_0004__table17299338192413" frame="border" border="1" rules="all"><caption><b>Table 2 </b><span id="elb_pro_01_0004__ph122521083017">Shared</span> load balancers and their network types</caption><thead align="left"><tr id="elb_pro_01_0004__row229915389243"><th align="left" class="cellrowborder" valign="top" width="25.002500250025%" id="mcps1.3.4.3.2.4.1.1"><p id="elb_pro_01_0004__p1629913812420">Load Balancer Type</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="13.991399139913991%" id="mcps1.3.4.3.2.4.1.2"><p id="elb_pro_01_0004__p5299173872410">Network Type</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="61.00610061006101%" id="mcps1.3.4.3.2.4.1.3"><p id="elb_pro_01_0004__p52991238112412">Description</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="elb_pro_01_0004__row8299143822415"><td class="cellrowborder" rowspan="2" valign="top" width="25.002500250025%" headers="mcps1.3.4.3.2.4.1.1 "><p id="elb_pro_01_0004__p8299203813247"><span id="elb_pro_01_0004__ph143143917124">Shared</span> load balancers</p>
+</td>
+<td class="cellrowborder" valign="top" width="13.991399139913991%" headers="mcps1.3.4.3.2.4.1.2 "><p id="elb_pro_01_0004__p18299338102418">Public network</p>
+</td>
+<td class="cellrowborder" valign="top" width="61.00610061006101%" headers="mcps1.3.4.3.2.4.1.3 "><p id="elb_pro_01_0004__p93361054203415">Load balancers can route requests on both public and private networks.</p>
+<ul id="elb_pro_01_0004__ul11227131163518"><li id="elb_pro_01_0004__li15228171112359">Each load balancer has an EIP bound to enable it to route requests over the Internet.</li><li id="elb_pro_01_0004__li19228811183512">The load balancer also has a private IP address and can route requests in a VPC.</li></ul>
+</td>
+</tr>
+<tr id="elb_pro_01_0004__row15299103832419"><td class="cellrowborder" valign="top" headers="mcps1.3.4.3.2.4.1.1 "><p id="elb_pro_01_0004__p172992384249">Private network</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.3.4.3.2.4.1.2 "><p id="elb_pro_01_0004__p6299153815244">Each load balancer has only a private IP address and can route requests in a VPC.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_pro_0000.html">Service Overview</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_qs_0000.html

@@ -8,9 +8,13 @@
 </li>
 <li class="ulchildlink"><strong><a href="elb_qs_0005.html">Process Flowchart</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="en-us_topic_0052569751.html">Using Shared Load Balancers — Entry Level</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_qs_0002.html">Using Dedicated Load Balancers (Entry Level)</a></strong><br>
 </li>
-<li class="ulchildlink"><strong><a href="en-us_elb_02_0001.html">Using Shared Load Balancers — Advanced Level</a></strong><br>
+<li class="ulchildlink"><strong><a href="elb_qs_0003.html">Using Dedicated Load Balancers (Advanced Level)</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="en-us_topic_0052569751.html">Using Shared Load Balancers (Entry Level)</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="en-us_elb_02_0001.html">Using Shared Load Balancers (Advanced Level)</a></strong><br>
 </li>
 </ul>
 </div>

docs/elb/umn/elb_qs_0005.html

@@ -1,7 +1,7 @@
 <a name="elb_qs_0005"></a><a name="elb_qs_0005"></a>
 
 <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 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 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>

docs/elb/umn/elb_ug_bq_0000.html

@@ -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 either of the following scenarios:</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__p940413817534"><a name="elb_ug_bq_0000__li9839628155019"></a><a name="li9839628155019"></a>For details about the procedure and parameters, see <a href="elb_lb_000006.html">Creating a Dedicated Load Balancer</a> and <a href="en-us_topic_0015479967.html#en-us_topic_0015479967__section19343262431">Creating a Shared Load Balancera 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_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.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__p940413817534"><a name="elb_ug_bq_0000__li9839628155019"></a><a name="li9839628155019"></a>For details about the procedure and parameters, 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>
 </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_en-us_topic_0052569751_image616618613_1" src="en-us_image_0000001120894978.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__b1029299342">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b1050483489">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 1020 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__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__b636463348">Add Tag</strong> dialog box, enter a tag key and value and click <strong id="elb_ug_bq_0000__b1889967732">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_en-us_topic_0052569751_image616618613_2" src="en-us_image_0000001120894978.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__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></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_en-us_topic_0052569751_image616618613_3" src="en-us_image_0000001120894978.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__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>
 <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>

docs/elb/umn/elb_ug_fz_0004.html

@@ -1,13 +1,13 @@
 <a name="elb_ug_fz_0004"></a><a name="elb_ug_fz_0004"></a>
 
 <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 <span id="elb_ug_fz_0004__text799514911493">server</span>s.</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></ul>
+<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>
 </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 <span id="elb_ug_fz_0004__text612661125417">server</span>s reside to reduce network latency and improve access speed.</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>
 <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>
@@ -25,7 +25,7 @@
 </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 <span id="elb_ug_fz_0004__text14441101117504">server</span>s. 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>
+<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>
 </li></ul>
 </div>

docs/elb/umn/elb_ug_fz_0005.html

@@ -0,0 +1,16 @@
+<a name="elb_ug_fz_0005"></a><a name="elb_ug_fz_0005"></a>
+
+<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__en-us_topic_0000001124473719_li1444815951216">Hover on <span><img id="elb_ug_fz_0005__en-us_topic_0236111236_image616618613" src="en-us_image_0000001167509179.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0005__en-us_topic_0236111236_b12775132613145">Service List</strong> and choose <strong id="elb_ug_fz_0005__en-us_topic_0236111236_b99836011156">Network</strong> &gt; <strong id="elb_ug_fz_0005__en-us_topic_0236111236_b139524583194">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>
+</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>
+

docs/elb/umn/elb_ug_fz_0006.html

@@ -3,12 +3,12 @@
 <h1 class="topictitle1">Modifying Load Balancer Settings</h1>
 <div id="body1555913901702"><div class="section" id="elb_ug_fz_0006__section57040304257"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_fz_0006__p0795439102515">You can modify the bandwidth used by the EIP bound to the load balancer as required.</p>
 </div>
-<div class="section" id="elb_ug_fz_0006__section1414224462710"><h4 class="sectiontitle">Modifying the Bandwidth</h4><ol id="elb_ug_fz_0006__ol1889111542441"><li id="elb_ug_fz_0006__li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0006__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0006__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_0006__li83736197297">Hover on <span><img id="elb_ug_fz_0006__en-us_topic_0052569751_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0006__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0006__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0006__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0006__li8639162635917">On the <strong id="elb_ug_fz_0006__b7215740182117">Load Balancers</strong> page:<p id="elb_ug_fz_0006__p168247101510">Dedicated load balancers: Click <strong id="elb_ug_fz_0006__b535212248226">Elastic Load Balancers</strong>, locate the load balancer whose bandwidth you want to modify and click <strong id="elb_ug_fz_0006__b6394165114224">Modify IPv4 Bandwidth</strong> or <strong id="elb_ug_fz_0006__b102751614237">More</strong> &gt; <strong id="elb_ug_fz_0006__b523745172318">Modify IPv6 Bandwidth</strong> in the <strong id="elb_ug_fz_0006__b0527171258">Operation</strong> column (if the load balancer has an IPv6 address that has been added to a shared bandwidth).</p>
+<div class="section" id="elb_ug_fz_0006__section1414224462710"><h4 class="sectiontitle">Modifying the Bandwidth</h4><ol id="elb_ug_fz_0006__ol1889111542441"><li id="elb_ug_fz_0006__li677391520332">Log in to the management console.</li><li id="elb_ug_fz_0006__li675519100420">In the upper left corner of the page, click <span><img id="elb_ug_fz_0006__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_0006__li83736197297">Hover on <span><img id="elb_ug_fz_0006__en-us_topic_0052569751_image762510132322" src="en-us_image_0000001417088430.png"></span> in the upper left corner to display <strong id="elb_ug_fz_0006__en-us_topic_0052569751_b9121102522212">Service List</strong> and choose <strong id="elb_ug_fz_0006__en-us_topic_0052569751_b61222025142217">Network</strong> &gt; <strong id="elb_ug_fz_0006__en-us_topic_0052569751_b4124425142210">Elastic Load Balancing</strong>.</li><li id="elb_ug_fz_0006__li8639162635917">On the <strong id="elb_ug_fz_0006__b7215740182117">Load Balancers</strong> page:<p id="elb_ug_fz_0006__p168247101510">Dedicated load balancers: Click <strong id="elb_ug_fz_0006__b535212248226">Elastic Load Balancers</strong>, locate the load balancer whose bandwidth you want to modify and click <strong id="elb_ug_fz_0006__b6394165114224">Modify IPv4 Bandwidth</strong> or <strong id="elb_ug_fz_0006__b102751614237">More</strong> &gt; <strong id="elb_ug_fz_0006__b523745172318">Modify IPv6 Bandwidth</strong> in the <strong id="elb_ug_fz_0006__b0527171258">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_0006__p551912271218">Shared load balancers: Click <strong id="elb_ug_fz_0006__b1717051182319">Elastic Load Balancers</strong>, locate the load balancer whose bandwidth you want to modify and click <strong id="elb_ug_fz_0006__b1571865115239">Modify Bandwidth</strong> or <strong id="elb_ug_fz_0006__b107191051122314">Modify IPv4 Bandwidth</strong> in the <strong id="elb_ug_fz_0006__b15525141218259">Operation</strong> column (in regions where either dedicated load balancers or both shared and dedicated load balancers are available).</p>
 </li><li id="elb_ug_fz_0006__li112257373413">In the <strong id="elb_ug_fz_0006__b11756555165919">New Configuration</strong> area, change the bandwidth and click <strong id="elb_ug_fz_0006__b482021520111">Next</strong>.<p id="elb_ug_fz_0006__p2383161311456">Select the bandwidth defined by the system or enter a value from 5 Mbit/s to 2,000 Mbit/s.</p>
 <div class="note" id="elb_ug_fz_0006__note18198113853814"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0006__p9198203823818">You can also change the bandwidth name.</p>
 </div></div>
-</li><li id="elb_ug_fz_0006__li153832355312">Confirm the modified bandwidth and click <strong id="elb_ug_fz_0006__b158311215266">Submit</strong>.</li></ol>
+</li><li id="elb_ug_fz_0006__li153832355312">Confirm the modified bandwidth and click <strong id="elb_ug_fz_0006__b1630241315124">Submit</strong>.</li></ol>
 </div>
 </div>
 <div>

docs/elb/umn/elb_ug_fz_0008.html

@@ -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_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.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_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>
 </div>
 <div>

docs/elb/umn/elb_ug_fz_0009.html

@@ -3,21 +3,26 @@
 <h1 class="topictitle1">Binding an IP Address to or Unbinding an IP Address from a Load Balancer</h1>
 <div id="body1555913901702"><div class="section" id="elb_ug_fz_0009__section172463310816"><h4 class="sectiontitle">Scenarios</h4><p id="elb_ug_fz_0009__en-us_topic_0172664831_p28601116191710">You can bind an IP address to a load balancer or unbind the IP address from a load balancer based on service requirements.</p>
 <ul id="elb_ug_fz_0009__en-us_topic_0172664831_ul1955113165814"><li id="elb_ug_fz_0009__li13197103915372">An IPv4 EIP or a private IPv4 address can be bound to or unbound from a dedicated load balancer.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li15985123945811">Only an IPv4 EIP can be bound to or unbound from a shared load balancer.</li></ul>
-<div class="note" id="elb_ug_fz_0009__en-us_topic_0172664831_note522075917118"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_ug_fz_0009__en-us_topic_0172664831_ul81289311216"><li id="elb_ug_fz_0009__en-us_topic_0172664831_li111281932219">Load balancers without IPv4 EIPs cannot route requests over the public IPv4 network.</li><li id="elb_ug_fz_0009__en-us_topic_0172664831_li13657112017214">Load balancers without private IPv4 addresses cannot route requests over the private IPv4 network.</li></ul>
+<div class="note" id="elb_ug_fz_0009__note44361517229"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="elb_ug_fz_0009__p18581415711">Note the following before unbinding an IP address:</p>
+<ul id="elb_ug_fz_0009__ul13295152421313"><li id="elb_ug_fz_0009__li729522491310">Load balancers without IPv4 EIPs cannot route requests over the public IPv4 network.</li><li id="elb_ug_fz_0009__li2697183610159">Load balancers without private IPv4 addresses cannot route requests over the private IPv4 network.<p id="elb_ug_fz_0009__p686615720259"><a name="elb_ug_fz_0009__li2697183610159"></a><a name="li2697183610159"></a></p>
+</li></ul>
+<div class="p" id="elb_ug_fz_0009__p39817577485">Note the following when you use EIPs of dedicated load balancers (<strong id="elb_ug_fz_0009__b10597830785">5_gray</strong>):<ul id="elb_ug_fz_0009__en-us_topic_0118498850_ul18141507494"><li id="elb_ug_fz_0009__en-us_topic_0118498850_li86521438154">In <strong id="elb_ug_fz_0009__b789753217499">eu-de</strong>, EIPs of dedicated load balancers (<strong id="elb_ug_fz_0009__b10664175516498">5_gray</strong>) type cannot be created. The optimal <strong id="elb_ug_fz_0009__b1888515618018">5_bgp</strong> EIP is recommended.</li><li id="elb_ug_fz_0009__en-us_topic_0118498850_li1194114411236">Existing EIPs of dedicated load balancers (<strong id="elb_ug_fz_0009__b596156106">5_gray</strong>) type can be bound to dedicated or shared load balancers.<ul id="elb_ug_fz_0009__en-us_topic_0118498850_ul2044703613155"><li id="elb_ug_fz_0009__en-us_topic_0118498850_li1222113518159">You cannot bind EIPs to or unbind them from dedicated load balancers on ELB console.</li><li id="elb_ug_fz_0009__en-us_topic_0118498850_li1688013347356">You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see "Binding an EIP" and "Unbinding an EIP" in "API V3" section in the <em id="elb_ug_fz_0009__i7583124415847">Elastic IP API Reference</em>.</li><li id="elb_ug_fz_0009__en-us_topic_0118498850_li15559236131711">EIPs can be bound to or unbound from shared load balancers using the ELB console or EIP APIs.</li></ul>
+</li><li id="elb_ug_fz_0009__en-us_topic_0118498850_li1468695512506">Do not add EIPs of the dedicated load balancers (<strong id="elb_ug_fz_0009__b876453965847">5_gray</strong>) and EIPs bound to other instances to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.</li></ul>
+</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_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.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_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>
 <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_en-us_topic_0052569751_image616618613_1" src="en-us_image_0000001120894978.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__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>
 </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_en-us_topic_0052569751_image616618613_2" src="en-us_image_0000001120894978.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__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></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_en-us_topic_0052569751_image616618613_3" src="en-us_image_0000001120894978.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__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>
 </div></div>
 </li></ol>
 </div>

docs/elb/umn/elb_ug_fz_0011.html

@@ -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_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.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_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>
 </div>
 <div>

docs/elb/umn/elb_ug_hc_0000.html

@@ -8,6 +8,8 @@
 </li>
 <li class="ulchildlink"><strong><a href="en-us_topic_0162227063.html">Configuring a Health Check</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="elb_ug_hc_0005.html">Changing the Health Check Protocol</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="elb_ug_hc_0003.html">Disabling a Health Check</a></strong><br>
 </li>
 </ul>

docs/elb/umn/elb_ug_hc_0003.html

@@ -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_en-us_topic_0052569751_image616618613" src="en-us_image_0000001120894978.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__b9336151553319">Basic Information</strong> area, click <strong id="elb_ug_hc_0003__b10337101573319">Configure</strong> next to <strong id="elb_ug_hc_0003__b73381115123316">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_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__b9336151553319">Basic Information</strong> area, click <strong id="elb_ug_hc_0003__b10337101573319">Configure</strong> next to <strong id="elb_ug_hc_0003__b73381115123316">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>

docs/elb/umn/elb_ug_hc_0005.html

@@ -0,0 +1,15 @@
+<a name="elb_ug_hc_0005"></a><a name="elb_ug_hc_0005"></a>
+
+<h1 class="topictitle1">Changing the Health Check Protocol</h1>
+<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__b9336151553319">Basic Information</strong> area, click <strong id="elb_ug_hc_0005__b10337101573319">Configure</strong> next to <strong id="elb_ug_hc_0005__b73381115123316">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>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_ug_hc_0000.html">Health Check</a></div>
+</div>
+</div>
+

docs/elb/umn/elb_ug_hd_0000.html

@@ -14,8 +14,14 @@
 </li>
 <li class="ulchildlink"><strong><a href="en-us_topic_0052569729.html">Adding or Removing Backend Servers (Shared Load Balancers)</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="elb_ug_hd_0005.html">Configuring Hybrid Load Balancing</a></strong><br>
+</li>
 <li class="ulchildlink"><strong><a href="elb_ug_hd_0008.html">Configuring Weights for Backend Servers</a></strong><br>
 </li>
+<li class="ulchildlink"><strong><a href="elb_ug_hd_0006.html">Configuring Slow Start (Dedicated Load Balancers)</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="elb_ug_hd_0004.html">Enabling Removal Protection for Backend Servers</a></strong><br>
+</li>
 </ul>
 </div>