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

ELB_UMN_20250220 VERSION

Browse Source 
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com>
Co-authored-by: zhoumeng35 <zhoumeng35@huawei.com>
Co-committed-by: zhoumeng35 <zhoumeng35@huawei.com>
This commit is contained in:
zhoumeng35
2025-02-21 13:20:47 +00:00
committed by zuul
parent 121e69b195
commit 233637c500
8 changed files with 1114 additions and 942 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

File diff suppressed because it is too large Load Diff

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

File diff suppressed because it is too large Load Diff

208
docs/elb/umn/elb_billing_0003.html Normal file
View File

File diff suppressed because it is too large Load Diff

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

@ -20,6 +20,8 @@
</li>
<li class="ulchildlink"><strong><a href="en-us_topic_0287737145.html">Specifications of Dedicated Load Balancers</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="elb_billing_0003.html">Billing Items (Dedicated Load Balancers)</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="elb_pro_0019.html">Quotas and Constraints</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="en-us_topic_0171274900.html">Permissions</a></strong><br>

594
docs/elb/umn/elb_ug_jt_0022.html
View File

File diff suppressed because it is too large Load Diff

8
docs/elb/umn/en-us_topic_0018127975.html
View File

@ -2,12 +2,12 @@
<h1 class="topictitle1">How Do I Troubleshoot an Unhealthy Backend Server?</h1>
<div id="body1437669816816"><div class="section" id="en-us_topic_0018127975__section193727466285"><h4 class="sectiontitle">Symptom</h4><p id="en-us_topic_0018127975__p956761115240">If a client cannot access a backend server through a load balancer, the backend server is declared unhealthy. You can view the health check results for a backend server on the ELB console.</p>
<ul id="en-us_topic_0018127975__ul167861954134714"><li id="en-us_topic_0018127975__li178615414713">Dedicated load balancers<p id="en-us_topic_0018127975__p0575143712564"><a name="en-us_topic_0018127975__li178615414713"></a><a name="li178615414713"></a>On the <strong id="en-us_topic_0018127975__b93124741434020">Load Balancers</strong> page, click the name of the load balancer to view its details. Click <strong id="en-us_topic_0018127975__b89224636534020">Backend Server Groups</strong> and locate the server group. You can find the health check results for backend servers in the <strong id="en-us_topic_0018127975__b191929478634020">Basic Information</strong> area.</p>
<ul id="en-us_topic_0018127975__ul167861954134714"><li id="en-us_topic_0018127975__li178615414713">Dedicated load balancers<p id="en-us_topic_0018127975__p0575143712564"><a name="en-us_topic_0018127975__li178615414713"></a><a name="li178615414713"></a>On the <strong id="en-us_topic_0018127975__b93124741434020">Load Balancers</strong> page, click the name of the load balancer to view its details. Click <strong id="en-us_topic_0018127975__b89224636534020">Backend Server Groups</strong> and locate the server group. You can view the health check results for backend servers in the <strong id="en-us_topic_0018127975__b191929478634020">Basic Information</strong> area.</p>
</li></ul>
<ul id="en-us_topic_0018127975__ul654511504309"><li id="en-us_topic_0018127975__li1044984322517"><span id="en-us_topic_0018127975__ph525424317296">Shared</span> load balancers<p id="en-us_topic_0018127975__p3414151710266">On the <strong id="en-us_topic_0018127975__b88486316308">Load Balancers</strong> page, click the name of the load balancer to view its details. Click <strong id="en-us_topic_0018127975__b198501831308">Backend Server Groups</strong> and locate the server group. You can find the health check results for backend servers in the <strong id="en-us_topic_0018127975__b5851183103011">Basic Information</strong> area.</p>
<ul id="en-us_topic_0018127975__ul654511504309"><li id="en-us_topic_0018127975__li1044984322517"><span id="en-us_topic_0018127975__ph525424317296">Shared</span> load balancers<p id="en-us_topic_0018127975__p3414151710266">On the <strong id="en-us_topic_0018127975__b88486316308">Load Balancers</strong> page, click the name of the load balancer to view its details. Click <strong id="en-us_topic_0018127975__b198501831308">Backend Server Groups</strong> and locate the server group. You can view the health check results for backend servers in the <strong id="en-us_topic_0018127975__b5851183103011">Basic Information</strong> area.</p>
</li></ul>
</div>
<div class="section" id="en-us_topic_0018127975__section3890132962817"><h4 class="sectiontitle">Background</h4><p id="en-us_topic_0018127975__p182515566522">To check the health of backend servers, dedicated load balancers use the IP addresses from the backend subnet where they work to send heartbeat requests to the backend servers, while shared load balancers use IP addresses in 100.125.0.0/16.</p>
<div class="section" id="en-us_topic_0018127975__section3890132962817"><h4 class="sectiontitle">Background</h4><p id="en-us_topic_0018127975__p182515566522">To check the health of backend servers, dedicated load balancers use the IP addresses in the backend subnet where they work to send heartbeat requests to the backend servers, while shared load balancers use IP addresses in 100.125.0.0/16.</p>
<p id="en-us_topic_0018127975__p8157622125518">Dedicated load balancers: To ensure that health checks can be performed as expected, ensure that traffic is allowed from the backend subnet where the load balancer is working to the backend servers.</p>
<p id="en-us_topic_0018127975__p41561225516">Shared load balancers: To ensure that health checks can be performed as expected, ensure that traffic is allowed from 100.125.0.0/16 to the backend servers.</p>
<div class="caution" id="en-us_topic_0018127975__note16898920154013"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="en-us_topic_0018127975__ul11410203114221"><li id="en-us_topic_0018127975__li19796144622215">Security group rules configured for backend servers associated with dedicated load balancers are different from those configured for backend servers associated with shared load balancers.<ul id="en-us_topic_0018127975__ul19784134692216"><li id="en-us_topic_0018127975__li1087114163232">Dedicated load balancers: Ensure that security group rules allow access from IP addresses in the VPC where the backend server resides. For details, see <a href="elb_ug_hd_0007.html">Configuring Security Group and Firewall Rules</a>.</li><li id="en-us_topic_0018127975__li378416465221">Shared load balancers: Ensure that security group rules allow access from IP addresses in 100.125.0.0/16. For details, see <a href="elb_ug_hd_0002.html">Configuring a Security Group for Backend Servers (Shared Load Balancers)</a>.</li></ul>
@ -106,7 +106,7 @@
</li></ul>
</div></div>
</div>
<div class="section" id="en-us_topic_0018127975__section2948957185917"><a name="en-us_topic_0018127975__section2948957185917"></a><a name="section2948957185917"></a><h4 class="sectiontitle">Checking Security Group Rules</h4><ul id="en-us_topic_0018127975__ul3162105921417"><li id="en-us_topic_0018127975__li111621159191410"><strong id="en-us_topic_0018127975__b20573121772519">Dedicated Load balancers</strong><ul id="en-us_topic_0018127975__ul20283154485015"><li id="en-us_topic_0018127975__li1743125315011"><strong id="en-us_topic_0018127975__b149481127111">TCP, HTTP, or HTTPS listeners</strong>: Verify that the inbound security group rule allows TCP traffic from the VPC where the dedicated load balancer resides to the backend server over the health check port.<ul id="en-us_topic_0018127975__ul98748772214"><li id="en-us_topic_0018127975__li787415702212">If the health check port is the same as the backend port, the inbound rule must allow traffic over the backend port, for example, port 80.</li><li id="en-us_topic_0018127975__li587457152210">If the port (port 80 as an example) for health check is different from that used by the backend server (port 443 as an example), inbound security group rules must allow traffic over both ports.<div class="note" id="en-us_topic_0018127975__note1387412711224"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0018127975__p187415715228">You can check the protocol and port in the <strong id="en-us_topic_0018127975__b1451995311">Basic Information</strong> area of the backend server group.</p>
<div class="section" id="en-us_topic_0018127975__section2948957185917"><a name="en-us_topic_0018127975__section2948957185917"></a><a name="section2948957185917"></a><h4 class="sectiontitle">Checking Security Group Rules</h4><ul id="en-us_topic_0018127975__ul3162105921417"><li id="en-us_topic_0018127975__li111621159191410"><strong id="en-us_topic_0018127975__b20573121772519">Dedicated Load balancers</strong><ul id="en-us_topic_0018127975__ul20283154485015"><li id="en-us_topic_0018127975__li1743125315011"><strong id="en-us_topic_0018127975__b149481127111">TCP, HTTP, or HTTPS listeners</strong>: Verify that the inbound security group rule allows TCP traffic from the VPC where the dedicated load balancer resides to the backend server over the health check port.<ul id="en-us_topic_0018127975__ul98748772214"><li id="en-us_topic_0018127975__li787415702212">If the health check port is the same as the backend port, the inbound rule must allow traffic over the backend port, for example, port 80.</li><li id="en-us_topic_0018127975__li587457152210">If the port (port 80 as an example) for health check is different from that used by the backend server (port 443 as an example), inbound security group rules must allow traffic over both ports.<div class="note" id="en-us_topic_0018127975__note1387412711224"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0018127975__p187415715228">You can check the protocol and port in the <strong id="en-us_topic_0018127975__b1521927726">Basic Information</strong> area of the backend server group.</p>
</div></div>
</li></ul>
<div class="fignone" id="en-us_topic_0018127975__fig128747713229"><span class="figcap"><b>Figure 2 </b>Example inbound rule</span><br><span><img id="en-us_topic_0018127975__image188744720224" src="en-us_image_0000001747381004.png"></span></div>

6
docs/elb/umn/en-us_topic_0150301848.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Access Logging</h1>
<div id="body8662426"><div class="section" id="en-us_topic_0150301848__en-us_topic_0000001819164194_section175377416919"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p1220239164010">ELB logs HTTP and HTTPS requests received by load balancers, including the time when the request was sent, client IP address, request path, and server response.</p>
<p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p1517249102112">With Log Tank Service (LTS), you can view logs of requests to load balancers at Layer 7 and analyze response status codes to quickly locate unhealthy backend servers.</p>
<div class="note" id="en-us_topic_0150301848__en-us_topic_0000001819164194_note18898177181519"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="en-us_topic_0150301848__ul8764172213270"><li id="en-us_topic_0150301848__li07641228274">ELB displays operations data, such as access logs, on the LTS console. Do not transmit private or sensitive data through fields in access logs. Encrypt your sensitive data if necessary.</li><li id="en-us_topic_0150301848__en-us_topic_0242751126_li0284142520492">Currently, access logging is not supported in the <strong id="en-us_topic_0150301848__b194981840183213">eu-nl</strong> region.</li></ul>
<div class="note" id="en-us_topic_0150301848__en-us_topic_0000001819164194_note18898177181519"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0150301848__p07761818124913">ELB displays operations data, such as access logs, on the LTS console. Do not transmit private or sensitive data through fields in access logs. Encrypt your sensitive data if necessary.</p>
</div></div>
</div>
<div class="section" id="en-us_topic_0150301848__en-us_topic_0000001819164194_section97361345495"><h4 class="sectiontitle">Constraints</h4><ul id="en-us_topic_0150301848__en-us_topic_0000001819164194_ul1713832394517"><li id="en-us_topic_0150301848__en-us_topic_0000001819164194_li6245142420456">Access logging can be configured only for load balancers that have HTTP or HTTPS listeners.</li><li id="en-us_topic_0150301848__en-us_topic_0000001819164194_li101384231457">The access logs do not contain requests whose return code is <strong id="en-us_topic_0150301848__b1019594117114">400 Bad Request</strong>. This is because such requests do not comply with HTTP specification and cannot be processed properly.</li></ul>
@ -300,7 +300,7 @@ $pool_name "$member_name" $tenant_id $eip_address:$eip_port "$upstream_addr_priv
</td>
<td class="cellrowborder" valign="top" width="24.960447852014116%" headers="mcps1.3.8.9.2.5.1.3 "><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p207531189913">String</p>
</td>
<td class="cellrowborder" valign="top" width="23.09845442375563%" headers="mcps1.3.8.9.2.5.1.4 "><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p15384142875618">-</p>
<td class="cellrowborder" valign="top" width="23.09845442375563%" headers="mcps1.3.8.9.2.5.1.4 "><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p15384142875618">N/A</p>
</td>
</tr>
<tr id="en-us_topic_0150301848__en-us_topic_0000001819164194_row125011836141511"><td class="cellrowborder" valign="top" width="25.045637093829864%" headers="mcps1.3.8.9.2.5.1.1 "><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p35761328219">ssl_protocol</p>
@ -345,7 +345,7 @@ $pool_name "$member_name" $tenant_id $eip_address:$eip_port "$upstream_addr_priv
</td>
<td class="cellrowborder" valign="top" width="24.960447852014116%" headers="mcps1.3.8.9.2.5.1.3 "><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p2053113516271">String</p>
</td>
<td class="cellrowborder" valign="top" width="23.09845442375563%" headers="mcps1.3.8.9.2.5.1.4 "><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p10384628155611">-</p>
<td class="cellrowborder" valign="top" width="23.09845442375563%" headers="mcps1.3.8.9.2.5.1.4 "><p id="en-us_topic_0150301848__en-us_topic_0000001819164194_p10384628155611">N/A</p>
</td>
</tr>
</tbody>

6
docs/elb/umn/en-us_topic_0287737145.html
View File

@ -48,7 +48,7 @@
</tbody>
</table>
</div>
<div class="section" id="en-us_topic_0287737145__en-us_topic_0000001819323754_section1629617145820"><h4 class="sectiontitle">Elastic Specifications</h4><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p13684131425815">If your service traffic fluctuates greatly, you can choose elastic specifications and select network load balancing (TCP/UDP/TLS) or application load balancing (HTTP/HTTPS), or both that best meet your service needs.</p>
<div class="section" id="en-us_topic_0287737145__en-us_topic_0000001819323754_section1629617145820"><h4 class="sectiontitle">Elastic Specifications</h4><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p13684131425815">If your service traffic fluctuates greatly, you can choose elastic specifications and select network load balancing (TCP/UDP) or application load balancing (HTTP/HTTPS), or both that best meet your service needs.</p>
<div class="note" id="en-us_topic_0287737145__en-us_topic_0000001819323754_note93031250192012"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p330315011209">The listener protocol must match the load balancing type. For example, if you select application load balancing (HTTP/HTTPS), you can only add an HTTP or HTTPS listener to this load balancer.</p>
</div></div>
<p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p37871619132110"><a href="#en-us_topic_0287737145__en-us_topic_0000001819323754_table12368131594417">Table 2</a> describes the dimensions about elastic specifications. When your traffic exceeds the specifications defined in <a href="#en-us_topic_0287737145__en-us_topic_0000001819323754_table52091547185916">Table 3</a>, new requests will be discarded.</p>
@ -58,12 +58,12 @@
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.5.2.3.1.1 "><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p18368131564411">Indicates the maximum number of concurrent connections that a load balancer can handle per minute. If the number reaches the maximum connections that is defined in the elastic specifications, new requests will be discarded to ensure the performance of established connections.</p>
</td>
</tr>
<tr id="en-us_topic_0287737145__en-us_topic_0000001819323754_row193681915174411"><th class="firstcol" valign="top" width="30%" id="mcps1.3.4.5.2.3.2.1"><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p94620546443">Connection Per Second (CPS)</p>
<tr id="en-us_topic_0287737145__en-us_topic_0000001819323754_row193681915174411"><th class="firstcol" valign="top" width="30%" id="mcps1.3.4.5.2.3.2.1"><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p94620546443">Connections Per Second (CPS)</p>
</th>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.5.2.3.2.1 "><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p190565914443">Indicates the number of new connections that a load balancer can establish per second. If the number reaches the CPS that is defined in the elastic specifications, new requests will be discarded to ensure the performance of established connections.</p>
</td>
</tr>
<tr id="en-us_topic_0287737145__en-us_topic_0000001819323754_row2368101519442"><th class="firstcol" valign="top" width="30%" id="mcps1.3.4.5.2.3.3.1"><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p667126204510">Query Per Second (QPS)</p>
<tr id="en-us_topic_0287737145__en-us_topic_0000001819323754_row2368101519442"><th class="firstcol" valign="top" width="30%" id="mcps1.3.4.5.2.3.3.1"><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p667126204510">Queries Per Second (QPS)</p>
</th>
<td class="cellrowborder" valign="top" width="70%" headers="mcps1.3.4.5.2.3.3.1 "><p id="en-us_topic_0287737145__en-us_topic_0000001819323754_p4368111514447">Indicates the number of HTTP or HTTPS requests sent to a backend server per second. If the QPS reaches that is defined in the elastic specifications, new requests will be discarded to ensure the performance of established connections.</p>
</td>