Region-level bandwidth sharing and multiplexing simplify O&M statistics, management, and operations cost settlement.
You can add EIPs (except for 5_gray EIPs of dedicated load balancers) to or remove them from a shared bandwidth regardless of the type of instances that they are bound to.
-
- Do not add EIPs of the dedicated load balancer type (5_gray) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
- Do not add EIPs of the dedicated load balancer type (5_gray) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
Assigning a Shared Bandwidth
Scenarios
Assign a shared bandwidth for use with EIPs.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click
in the upper left corner, and choose Network > Elastic IP. - In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the upper right corner, click Assign Shared Bandwidth. On the displayed page, configure parameters as prompted.Figure 1 Assigning Shared Bandwidth+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Internet Access > Shared Bandwidths.
- In the upper right corner, click Assign Shared Bandwidth. On the displayed page, configure parameters as prompted.Figure 1 Assigning a shared bandwidth-
Table 1 Parameter descriptions Parameter
Bandwidth
The bandwidth size in Mbit/s. The minimum value is 5 Mbit/s. The maximum bandwidth can be 1000 Mbit/s.
+The shared bandwidth size in Mbit/s. It starts with 5 Mbit/s. The maximum value is 2,000 Mbit/s.
10
Enterprise Project
The enterprise project that the EIP belongs to.
-An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.
+An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.
default
- Click Assign Now.
- Click Assign Now.
Notes and Constraints
- The type of EIPs must be the same as that of the shared bandwidth the EIPs to be added to.
- Do not add EIPs of the dedicated load balancer type (5_gray) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the target shared bandwidth that you want to add EIPs to. In the Operation column, choose Add Public IP Address, and select the EIPs or IPv6 addresses to be added.Figure 1 Adding an EIP+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Internet Access > Shared Bandwidths.
- In the shared bandwidth list, locate the target shared bandwidth that you want to add EIPs to. In the Operation column, choose Add Public IP Address, and select the EIPs or IPv6 addresses to be added.Figure 1 Adding an EIPFigure 2 Adding an IPv6 address
diff --git a/docs/eip/umn/bandwidth_0005.html b/docs/eip/umn/bandwidth_0005.html index c0772d433..7b1de89e8 100644 --- a/docs/eip/umn/bandwidth_0005.html +++ b/docs/eip/umn/bandwidth_0005.html @@ -3,7 +3,7 @@ - After an EIP is added to a shared bandwidth, the dedicated bandwidth used by the EIP will become invalid and the EIP will start to use the shared bandwidth. The EIP will be removed from the original dedicated bandwidth.
Removing EIPs from a Shared Bandwidth
-Scenarios
Remove EIPs that are no longer required from a shared bandwidth if needed.
diff --git a/docs/eip/umn/bandwidth_0006.html b/docs/eip/umn/bandwidth_0006.html index eb15cbaad..799cf5e04 100644 --- a/docs/eip/umn/bandwidth_0006.html +++ b/docs/eip/umn/bandwidth_0006.html @@ -3,7 +3,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner, and choose Network > Elastic IP. - In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the target bandwidth from which you want to remove EIPs, choose More > Remove Public IP Address in the Operation column, and select the EIPs or IPv6 addresses to be removed in the displayed dialog box.Figure 1 Removing EIPs or IPv6 addresses+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Internet Access > Shared Bandwidths.
- In the shared bandwidth list, locate the target bandwidth from which you want to remove EIPs, choose More > Remove Public IP Address in the Operation column, and select the EIPs or IPv6 addresses to be removed in the displayed dialog box.Figure 1 Removing EIPs or IPv6 addresses
- Click OK.
Modifying a Shared Bandwidth
-Scenarios
You can modify the name and size of a shared bandwidth as required.
diff --git a/docs/eip/umn/bandwidth_0007.html b/docs/eip/umn/bandwidth_0007.html index 708ef4402..99f9322cf 100644 --- a/docs/eip/umn/bandwidth_0007.html +++ b/docs/eip/umn/bandwidth_0007.html @@ -5,7 +5,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the row that contains the shared bandwidth you want to modify, click Modify Bandwidth in the Operation column, and modify the bandwidth settings.Figure 1 Modify Bandwidth+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Internet Access > Shared Bandwidths.
- In the shared bandwidth list, locate the row that contains the shared bandwidth you want to modify, click Modify Bandwidth in the Operation column, and modify the bandwidth settings.Figure 1 Modify Bandwidth
- Click Next.
- Click Submit.
-Prerequisites
Before deleting a shared bandwidth, remove all the EIPs associated with it. For details, see Removing EIPs from a Shared Bandwidth.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the row that contains the shared bandwidth you want to delete, click More in the Operation column, and then click Delete.
- Enter DELETE as prompted and click OK.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Internet Access > Shared Bandwidths.
- In the shared bandwidth list, locate the row that contains the shared bandwidth you want to delete, click More in the Operation column, and then click Delete.
- Enter DELETE as prompted and click OK.
diff --git a/docs/eip/umn/bandwidth_0009.html b/docs/eip/umn/bandwidth_0009.html index 45242b2bf..d296b7510 100644 --- a/docs/eip/umn/bandwidth_0009.html +++ b/docs/eip/umn/bandwidth_0009.html @@ -1,9 +1,14 @@-Exporting Shared Bandwidths
-- Log in to the management console.
- Click
in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- On the shared bandwidth list page, select one or more shared bandwidths and click Export in the upper left corner.
The system will automatically export information about all your shared bandwidths in the selected region of your account to a local directory.
++Scenarios
You can export the information about the shared bandwidths as an Excel file to a local directory.
+The file records the shared bandwidth name, status, shared bandwidth ID, bandwidth (Mbit/s), and EIPs.
++Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Internet Access > Shared Bandwidths.
- In the upper left corner above the shared bandwidth list, click Export.
- Export selected data to an XLSX file: Select one or more shared bandwidths and export information about the selected shared bandwidths.
- Export all data to an XLSX file: Export information about all the shared bandwidths in the current region.
The system will automatically export information about the shared bandwidths as an Excel file to a local directory.
Parent topic: Shared Bandwidthdiff --git a/docs/eip/umn/eip_0001.html b/docs/eip/umn/eip_0001.html index 8007a8c3d..7a0ac7036 100644 --- a/docs/eip/umn/eip_0001.html +++ b/docs/eip/umn/eip_0001.html @@ -12,7 +12,7 @@- Modifying an EIP Bandwidth
-
- Exporting EIP Information
+- Exporting EIPs
- Adding EIPs to a Shared Bandwidth
diff --git a/docs/eip/umn/eip_0002.html b/docs/eip/umn/eip_0002.html index a1a5b2026..fbff9e6e3 100644 --- a/docs/eip/umn/eip_0002.html +++ b/docs/eip/umn/eip_0002.html @@ -7,7 +7,7 @@
Assigning an EIP
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Elastic IP.
- On the displayed page, click Assign EIP.
- Set the parameters as prompted.Figure 1 Assign EIP+
Assigning an EIP
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Elastic IP.
- On the displayed page, click Assign EIP.
- Set the parameters as prompted.Figure 1 Assign EIP
-Table 1 Parameter descriptions Parameter
EIP Type
- Dynamic BGP: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.
- Mail BGP: EIPs with port 25, 465, or 587 enabled are used for email services.
- Dynamic BGP: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.
- Mail BGP: EIPs with port 25, 465, or 587 enabled are used for email services.
The selected EIP type cannot be changed after the EIP is assigned.
Dynamic BGP
@@ -35,7 +35,7 @@Billed By
Two options are available:
-- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
Dedicated
100
Bandwidth Name
+The name of the bandwidth.
+bandwidth
+EIP Name
The EIP name.
@@ -62,13 +69,6 @@default
Bandwidth Name
-The name of the bandwidth.
-bandwidth
-Tag
The EIP tags. Each tag contains a key and value pair.
@@ -88,28 +88,26 @@Table 2 EIP tag requirements Parameter
+Table 2 EIP tag requirements Parameter
Requirement
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- The key value must be unique for the same EIP.
- Can contain up to 36 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only hyphens (-), underscores (_), and at signs (@) are allowed.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
- Cannot be left blank.
- Can contain a maximum of 128 characters.
- Cannot start or end with a space.
Ipv4_key1
+Ipv4_key1
Value
+Value
- Can contain up to 43 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only underscores (_), hyphens (-), and at signs (@) are allowed.
- Can be left blank.
- Can contain a maximum of 255 characters.
- Cannot start or end with a space.
3005eip
+3005eip
- Click Create Now.
- Click Submit.
-Binding an EIP
- On the EIPs page, locate the row that contains the target EIP, and click Bind.
- Select the instance that you want to bind the EIP to.
-Figure 2 Bind EIP+
Figure 2 Bind EIP
- Click OK.
An IPv6 client on the internet can access the ECS that has an EIP bound in a VPC. For details, see How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
Follow-Up Procedure
After an ECS with an EIP bound is created, the system generates a domain name in the format of ecs-xx-xx-xx-xx.compute.xxx.com for the EIP by default. xx-xx-xx-xx indicates the EIP, and xxx indicates the domain name of the cloud service provider. You can use the domain name to access the ECS.
-You can use any of the following commands to obtain the domain name of an EIP:diff --git a/docs/eip/umn/eip_0003.html b/docs/eip/umn/eip_0003.html index e012c144f..6ff0ae72b 100644 --- a/docs/eip/umn/eip_0003.html +++ b/docs/eip/umn/eip_0003.html @@ -7,13 +7,13 @@- ping -an EIP
- nslookup [-qt=ptr] EIP
- dig -x EIP
Follow-Up Procedure
After an ECS with an EIP bound is created, the system generates a reverse domain name in the format of ecs-xx-xx-xx-xx.compute.xxx.com for the EIP by default. xx-xx-xx-xx indicates the EIP, and xxx indicates the domain name of the cloud service provider. You can use the reverse domain name to access the ECS.
+You can use any of the following commands to obtain the reverse domain name of an EIP:- nslookup -query=ptr EIP
- dig -x EIP
- EIP assigned together with your load balancers will also be displayed in the EIP list.
- Only EIPs with no instance bound can be released. If you want to release an EIP with an instance bound, you need to unbind EIP from the instance first.
Procedure
Unbinding a single EIP
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the EIP, and click Unbind.
- Click OK.
Releasing a single EIP- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the target EIP, click More and then Release in the Operation column.
- Click OK.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the EIP, and click Unbind.
- Click OK.
Releasing a single EIP- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the target EIP, click More and then Release in the Operation column.
- Click OK.
Unbinding multiple EIPs at once
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be unbound.
- Click the Unbind button located above the EIP list.
- Click OK.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be unbound.
- Click the Unbind button located above the EIP list.
- Click OK.
Releasing multiple EIPs at once
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be released.
- Click the Release button located above the EIP list.
- Click OK.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be released.
- Click the Release button located above the EIP list.
- Click OK.
diff --git a/docs/eip/umn/eip_0004.html b/docs/eip/umn/eip_0004.html index 30a8c1b72..e86fa8ec2 100644 --- a/docs/eip/umn/eip_0004.html +++ b/docs/eip/umn/eip_0004.html @@ -5,42 +5,37 @@A tag consists of a key and value pair. Table 1 lists the tag key and value requirements.
-Table 1 EIP tag requirements Parameter
+-Table 1 EIP tag requirements Parameter
Requirement
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each EIP.
- Can contain a maximum of 36 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only hyphens (-), underscores (_), and at signs (@) are allowed.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
- Cannot be left blank.
- Can contain a maximum of 128 characters.
- Cannot start or end with a space.
Ipv4_key1
+Ipv4_key1
Value
+Value
- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only underscores (_), hyphens (-), and at signs (@) are allowed.
- Can be left blank.
- Can contain a maximum of 255 characters.
- Cannot start or end with a space.
3005eip
+3005eip
Procedure
Searching for EIPs by tag key and value on the page showing the EIP list- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the search box above the EIP list, click anywhere in the box to set filters.
- Click the tag key and then the value as required. The system filters resources based on the tag you select.
- Click anywhere in the search box to add the next tag key and value.
You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for EIPs, the system will display only the EIPs that match all of the tags you specified.
+-Procedure
Searching for EIPs by tag key and value on the page showing the EIP list-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the search box above the EIP list, click anywhere in the box to set filters.
- Click the tag key and then the value as required. The system filters resources based on the tag you select.
- Click anywhere in the search box to add the next tag key and value.
You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for EIPs, the system will display only the EIPs that match all of the tags you specified.
Adding, deleting, editing, and viewing tags on the Tags tab of an EIPdiff --git a/docs/eip/umn/eip_0005.html b/docs/eip/umn/eip_0005.html index f7e6447a7..7a346de49 100644 --- a/docs/eip/umn/eip_0005.html +++ b/docs/eip/umn/eip_0005.html @@ -5,8 +5,9 @@- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the EIP whose tags you want to manage, and click the EIP name.
- On the page showing EIP details, click the Tags tab and perform desired operations on tags.
- View tags.
On the Tags tab, you can view details about tags added to the current EIP, including the number of tags and the key and value of each tag.
- - Add a tag.
Click Add Tag in the upper left corner. In the displayed Add Tag dialog box, enter the tag key and value, and click OK.
- - Edit a tag.
Locate the row that contains the tag you want to edit, and click Edit in the Operation column. Enter the new tag value, and click OK.
-The tag key cannot be modified.
- - Delete a tag.
Locate the row that contains the tag you want to delete, and click Delete in the Operation column. In the displayed dialog box, click OK.
-
Adding, deleting, editing, and viewing tags on the Tags tab of an EIP- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the EIP whose tags you want to manage, and click the EIP name. +
- Click the Tags tab and then click Edit Tag in the upper left corner above the tag list.
The Edit Tag page is displayed.
+ - Perform the following operations on the tags as required:
- Adding a tag: Click
, enter a tag key and value, and click OK. - Modifying a tag: Click
next to the target tag key or value to delete the original value, enter a new value, and click OK. - Deleting a tag: Click Delete next to the target tag and click OK.
- Adding a tag: Click
- View tags.
This section describes how to modify the dedicated bandwidth or shared bandwidth of an EIP. For details about how to modify a shared bandwidth, see Modifying a Shared Bandwidth.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- Locate the row that contains the target EIP in the EIP list, click More in the Operation column, and select Modify Bandwidth.
- Modify the bandwidth parameters as prompted. -
- Click Next.
- Click Submit.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- Locate the row that contains the target EIP in the EIP list, click More in the Operation column, and select Modify Bandwidth.
- Modify the bandwidth parameters as prompted.Figure 1 Modifying bandwidth of a pay-per-use EIP+ +
- Click Submit.
diff --git a/docs/eip/umn/eip_0015.html b/docs/eip/umn/eip_0015.html index 4bdf9b966..c537f010e 100644 --- a/docs/eip/umn/eip_0015.html +++ b/docs/eip/umn/eip_0015.html @@ -1,9 +1,11 @@ -Exporting EIP Information
-Scenarios
The information of all EIPs under your account can be exported in an Excel file to a local directory. The file records the ID, status, type, bandwidth name, and bandwidth size of EIPs.
+Exporting EIPs
+-Scenarios
The information of all EIPs under your account can be exported in an Excel file to a local directory.
+The file records the EIP, EIP ID, status, type, bandwidth name, bandwidth size, bandwidth ID, Instance Type, Instance Name, Instance ID, Tags ,and Created.
diff --git a/docs/eip/umn/eip_0019.html b/docs/eip/umn/eip_0019.html index 14bee749a..4bbfe203d 100644 --- a/docs/eip/umn/eip_0019.html +++ b/docs/eip/umn/eip_0019.html @@ -3,7 +3,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Elastic IP.
- On the EIP list page, select one or more EIPs and click Export in the upper left corner.
The system automatically exports all the selected EIP information to an Excel file and downloads the file to a local directory.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the EIP list page, click Export in the upper left corner.
- Export selected data to an XLSX file: Select one or more EIPs and export the information about all the selected EIPs.
- Export all data to an XLSX file: Export information about all the EIPs in the current region.
The system automatically exports the information about the EIPs as an Excel file to a specified directory.
Removing EIPs from a Shared Bandwidth
-Scenarios
You can remove EIPs from a shared bandwidth as needed.
diff --git a/docs/eip/umn/eip_his_0003.html b/docs/eip/umn/eip_his_0003.html index 9230ee328..f714476d3 100644 --- a/docs/eip/umn/eip_his_0003.html +++ b/docs/eip/umn/eip_his_0003.html @@ -8,7 +8,20 @@Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click
in the upper left corner, and choose Network > Elastic IP. - In the navigation pane on the left, choose Elastic IP and Bandwidth > EIPs.
- In the EIP list, locate the target EIP. In the Operation column, choose More > Remove from Shared Bandwidth.
- Set the EIP bandwidth after the EIP is removed. The bandwidth (Mbit/s) of an EIP can be changed.Figure 1 Removing an EIP from a shared bandwidth+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > EIPs.
- In the EIP list, locate the target EIP. In the Operation column, choose More > Remove from Shared Bandwidth.
- Set the EIP bandwidth after the EIP is removed. The bandwidth (Mbit/s) of an EIP can be changed.Figure 1 Removing an EIP from a shared bandwidth
- Click OK.
2024-10-23
+2026-03-20
+This release incorporates the following changes:
+- Changed Name to Subnet Name in the table in Step 1: Create a VPC.
- Modified steps in Step 2: Create a Subnet for the VPC and Step 4: Create a Security Group.
- Changed the description to export EIPs to a specified directory in Exporting EIPs.
- Modified figures in Removing EIPs from a Shared Bandwidth.
- Modified steps in Shared Bandwidth.
- Changed the description in How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?.
- Added What Are the Priorities of the Custom Route and EIP If Both Are Configured for an ECS to Enable the ECS to Access the Internet?.
2026-03-04
+This release incorporates the following changes:
+- Modified figures and tag rules in Assigning an EIP and Binding It to an ECS.
- Modified figures and steps in Modifying an EIP Bandwidth.
- Modified tag rules and steps in Managing EIP Tags.
2024-10-23
This release incorporates the following change:
Added outbound and inbound bandwidth usage in Supported Metrics.
@@ -23,7 +36,7 @@2024-05-13
This release incorporates the following change:
-- Added section Adding EIPs to a Shared Bandwidth.
- Added section Removing EIPs from a Shared Bandwidth.
- Modified the procedure for exporting the EIP list in Exporting EIP Information.
- Added step numbers in Managing EIP Tags.
- Added the description indicating that after an EIP is added to a shared bandwidth, the dedicated bandwidth used by the EIP will become invalid and the EIP will start to use the shared bandwidth in Adding EIPs to a Shared Bandwidth.
- Changed EIP ReadOnlyAccess to VPC ReadOnlyAccess in Creating a User and Granting EIP Permissions and EIP Custom Policies.
- Added the description indicating that one EIP can be bound to only one ECS in What Are the Differences Between EIP, Private IP Address, and Virtual IP Address?
- Modified the section title in What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth?
- Added section Adding EIPs to a Shared Bandwidth.
- Added section Removing EIPs from a Shared Bandwidth.
- Modified the procedure for exporting EIPs in Exporting EIPs.
- Added step numbers in Managing EIP Tags.
- Added the description indicating that after an EIP is added to a shared bandwidth, the dedicated bandwidth used by the EIP will become invalid and the EIP will start to use the shared bandwidth in Adding EIPs to a Shared Bandwidth.
- Changed EIP ReadOnlyAccess to VPC ReadOnlyAccess in Creating a User and Granting EIP Permissions and EIP Custom Policies.
- Added the description indicating that one EIP can be bound to only one ECS in What Are the Differences Between EIP, Private IP Address, and Virtual IP Address?
- Modified the section title in What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth?
2024-03-28
@@ -35,7 +48,7 @@2024-03-04
This release incorporates the following changes:
-- Modified the procedure for exporting EIPs in Exporting EIP Information.
- Added the procedure for exporting the list of shared bandwidths in Exporting Shared Bandwidths.
- Modified the procedure for exporting EIPs in Exporting EIPs.
- Added the procedure for exporting the shared bandwidths in Exporting Shared Bandwidths.
2023-08-01
@@ -83,7 +96,7 @@Updated the following content:
- Modified links of related services in EIP and Other Services.
- Modified steps in Can Multiple EIPs Be Bound to an ECS?
Added the following content:
- +2023-01-12
@@ -110,7 +123,7 @@2022-10-30
Added the following content:
-- Advantages
- Application Scenarios
- Functions
- Notes and Constraints
- EIP and Other Services
- EIP Overview
- How Do I Assign or Retrieve a Specific EIP?
- Why Is an EIP Newly Assigned the Same as the One I Released?
- What Is the EIP Assignment Policy?
- Can I Assign a Specific EIP?
- Can a Bandwidth Be Used by Multiple Accounts?
- How Do I Unbind an EIP from an Instance and Bind a New EIP to the Instance?
- Why Can't I Find My Assigned EIP on the Management Console?
- How Do I Access the Internet Using an EIP Bound to an Extension NIC?
- Can I Bind an EIP of an ECS to Another ECS?
- Can I Bind an EIP to a Cloud Resource in Another Region?
- What Are Inbound Bandwidth and Outbound Bandwidth?
- What Are the Differences Between Public Bandwidth and Private Bandwidth?
- What Is the Relationship Between Bandwidth and Upload/Download Rate?
- What Should I Do If an EIP Cannot Be Pinged?
- Why Does the Download Speed of My ECS Is Slow?
- Advantages
- Application Scenarios
- Functions
- Notes and Constraints
- EIP and Other Services
- EIP Overview
- How Do I Assign or Retrieve a Specific EIP?
- Why Is an EIP Newly Assigned the Same as the One I Released?
- What Is the EIP Assignment Policy?
- Can I Assign a Specific EIP?
- Can a Bandwidth Be Used by Multiple Accounts?
- How Do I Unbind an EIP from an Instance and Bind a New EIP to the Instance?
- Why Can't I Find My Assigned EIP on the Management Console?
- How Do I Access the Internet Using an EIP Bound to an Extended Network Interface?
- Can I Bind an EIP of an ECS to Another ECS?
- Can I Bind an EIP to a Cloud Resource in Another Region?
- What Are Inbound Bandwidth and Outbound Bandwidth?
- What Are the Differences Between Public Bandwidth and Private Bandwidth?
- What Is the Relationship Between Bandwidth and Upload/Download Rate?
- What Should I Do If an EIP Cannot Be Pinged?
- Why Does the Download Speed of My ECS Is Slow?
2022-10-18
diff --git a/docs/eip/umn/en-us_image_0000001675418673.png b/docs/eip/umn/en-us_image_0000001675418673.png deleted file mode 100644 index d8f9804a8..000000000 Binary files a/docs/eip/umn/en-us_image_0000001675418673.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000001818823034.png b/docs/eip/umn/en-us_image_0000001818823034.png deleted file mode 100644 index 135693afc..000000000 Binary files a/docs/eip/umn/en-us_image_0000001818823034.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000001818983386.png b/docs/eip/umn/en-us_image_0000001818983386.png new file mode 100644 index 000000000..fc924be04 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001818983386.png differ diff --git a/docs/eip/umn/en-us_image_0000001454059512.png b/docs/eip/umn/en-us_image_0000001865663457.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001454059512.png rename to docs/eip/umn/en-us_image_0000001865663457.png diff --git a/docs/eip/umn/en-us_image_0000001572300492.png b/docs/eip/umn/en-us_image_0000001865663461.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001572300492.png rename to docs/eip/umn/en-us_image_0000001865663461.png diff --git a/docs/eip/umn/en-us_image_0000001865837676.png b/docs/eip/umn/en-us_image_0000001865837676.png deleted file mode 100644 index 267f2deec..000000000 Binary files a/docs/eip/umn/en-us_image_0000001865837676.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000001925615569.png b/docs/eip/umn/en-us_image_0000001925615569.png deleted file mode 100644 index 1c2c2ef63..000000000 Binary files a/docs/eip/umn/en-us_image_0000001925615569.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000002029182980.png b/docs/eip/umn/en-us_image_0000002029182980.png deleted file mode 100644 index c5495044f..000000000 Binary files a/docs/eip/umn/en-us_image_0000002029182980.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000002065116093.png b/docs/eip/umn/en-us_image_0000002065116093.png deleted file mode 100644 index a8574fa81..000000000 Binary files a/docs/eip/umn/en-us_image_0000002065116093.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000002065205609.png b/docs/eip/umn/en-us_image_0000002065205609.png deleted file mode 100644 index 64ad10b4a..000000000 Binary files a/docs/eip/umn/en-us_image_0000002065205609.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000002065206257.png b/docs/eip/umn/en-us_image_0000002065206257.png deleted file mode 100644 index 20d580e33..000000000 Binary files a/docs/eip/umn/en-us_image_0000002065206257.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000002065211017.png b/docs/eip/umn/en-us_image_0000002065211017.png deleted file mode 100644 index 80591145d..000000000 Binary files a/docs/eip/umn/en-us_image_0000002065211017.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0210779229.png b/docs/eip/umn/en-us_image_0000002188678994.png similarity index 100% rename from docs/eip/umn/en-us_image_0210779229.png rename to docs/eip/umn/en-us_image_0000002188678994.png diff --git a/docs/eip/umn/en-us_image_0000002355688332.png b/docs/eip/umn/en-us_image_0000002355688332.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002355688332.png differ diff --git a/docs/eip/umn/en-us_image_0000002389328437.png b/docs/eip/umn/en-us_image_0000002389328437.png new file mode 100644 index 000000000..5aa7f83fa Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002389328437.png differ diff --git a/docs/eip/umn/en-us_image_0000001649841616.png b/docs/eip/umn/en-us_image_0000002389448333.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001649841616.png rename to docs/eip/umn/en-us_image_0000002389448333.png diff --git a/docs/eip/umn/en-us_image_0000002524247358.png b/docs/eip/umn/en-us_image_0000002524247358.png new file mode 100644 index 000000000..a84822096 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002524247358.png differ diff --git a/docs/eip/umn/en-us_image_0000002524270832.png b/docs/eip/umn/en-us_image_0000002524270832.png new file mode 100644 index 000000000..c2c95514b Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002524270832.png differ diff --git a/docs/eip/umn/en-us_image_0000002525194920.png b/docs/eip/umn/en-us_image_0000002525194920.png new file mode 100644 index 000000000..0bb49364e Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002525194920.png differ diff --git a/docs/eip/umn/en-us_image_0000002531823460.png b/docs/eip/umn/en-us_image_0000002531823460.png new file mode 100644 index 000000000..11c30eb21 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002531823460.png differ diff --git a/docs/eip/umn/en-us_image_0000002555242197.png b/docs/eip/umn/en-us_image_0000002555242197.png new file mode 100644 index 000000000..18cfc3eeb Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555242197.png differ diff --git a/docs/eip/umn/en-us_image_0000002555247269.png b/docs/eip/umn/en-us_image_0000002555247269.png new file mode 100644 index 000000000..a84822096 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555247269.png differ diff --git a/docs/eip/umn/en-us_image_0000002555271913.png b/docs/eip/umn/en-us_image_0000002555271913.png new file mode 100644 index 000000000..a593f53f3 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555271913.png differ diff --git a/docs/eip/umn/en-us_image_0000002555360481.png b/docs/eip/umn/en-us_image_0000002555360481.png new file mode 100644 index 000000000..c0e86b753 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555360481.png differ diff --git a/docs/eip/umn/en-us_image_0000002555369043.png b/docs/eip/umn/en-us_image_0000002555369043.png new file mode 100644 index 000000000..b8e21c87d Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555369043.png differ diff --git a/docs/eip/umn/en-us_image_0000002555381165.png b/docs/eip/umn/en-us_image_0000002555381165.png new file mode 100644 index 000000000..8599148ed Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555381165.png differ diff --git a/docs/eip/umn/en-us_image_0000002555531839.png b/docs/eip/umn/en-us_image_0000002555531839.png new file mode 100644 index 000000000..ab1accfa6 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555531839.png differ diff --git a/docs/eip/umn/en-us_image_0000002555651817.png b/docs/eip/umn/en-us_image_0000002555651817.png new file mode 100644 index 000000000..a649f9b7b Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002555651817.png differ diff --git a/docs/eip/umn/en-us_image_0000002556232513.png b/docs/eip/umn/en-us_image_0000002556232513.png new file mode 100644 index 000000000..f286e6db6 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000002556232513.png differ diff --git a/docs/eip/umn/en-us_image_0000001675258889.png b/docs/eip/umn/en-us_image_0000002556425923.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001675258889.png rename to docs/eip/umn/en-us_image_0000002556425923.png diff --git a/docs/eip/umn/faq_bandwidth_0007.html b/docs/eip/umn/faq_bandwidth_0007.html index 69c4b90af..646fdae51 100644 --- a/docs/eip/umn/faq_bandwidth_0007.html +++ b/docs/eip/umn/faq_bandwidth_0007.html @@ -2,7 +2,8 @@What Are Inbound Bandwidth and Outbound Bandwidth?
Bandwidth refers to the maximum amount of data that can be transmitted in a given amount of time (generally one second). A larger bandwidth value indicates a stronger transmission capability. Bandwidth is classified into public bandwidth and private bandwidth.
-Public bandwidth is the bandwidth consumed when data is transferred between cloud instances and the Internet. Public bandwidth is classified into inbound bandwidth and outbound bandwidth. For details the outbound bandwidth and inbound bandwidth, see Table 1.
+Public bandwidth is the bandwidth consumed when data is transferred between cloud instances and the Internet. Public bandwidth is classified into inbound bandwidth and outbound bandwidth. For details about the outbound bandwidth and inbound bandwidth, see Table 1.- Outbound Bandwidth means the same thing as Upstream Bandwidth or Upstream Traffic on the Cloud Eye console.
- Inbound Bandwidth means the same thing as Downstream Bandwidth and Downstream Traffic on the Cloud Eye console.
Figure 1 Inbound bandwidth and outbound bandwidth
Table 1 Inbound bandwidth and outbound bandwidth Type
diff --git a/docs/eip/umn/faq_connect_0001.html b/docs/eip/umn/faq_connect_0001.html index 20a25b6d9..b14a06bb8 100644 --- a/docs/eip/umn/faq_connect_0001.html +++ b/docs/eip/umn/faq_connect_0001.html @@ -1,9 +1,9 @@What Are the Priorities of the Custom Route and EIP If Both Are Configured for an ECS to Enable the ECS to Access the Internet?
-The priority of an EIP is higher than that of a custom route in a VPC route table. For example:
-The VPC route table of an ECS has a custom route with 0.0.0.0/0 as the destination and NAT gateway as the next hop.
-If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than its custom route. In this case, traffic is forwarded to the EIP and cannot reach the NAT gateway.
+In a VPC route table, routes are matched by priority in the following order: Local route > specific route > EIP route > default route.+- If the destination of a custom route is a specific IP address (not 0.0.0.0/0), it takes priority over the EIP route.
- If the destination of a custom route is 0.0.0.0/0, it can match any traffic. In this case, the EIP route has a higher priority.
For more information about route priorities, see Route Tables and Routes.
diff --git a/docs/eip/umn/faq_connect_0002.html b/docs/eip/umn/faq_connect_0002.html index 7acb031ad..f87cfd426 100644 --- a/docs/eip/umn/faq_connect_0002.html +++ b/docs/eip/umn/faq_connect_0002.html @@ -2,11 +2,11 @@How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
Users with IPv6 clients can call APIs to assign IPv6 EIPs and bind the EIPs to ECSs. Then, the users can use the EIP to access the ECSs in the VPC over the Internet.
-For details, see Floating IP Address (IPv6) > Creating a Floating IP Address in the Virtual Private Cloud API Reference. The NAT64 gateway in the data center will convert the IPv6 EIP to the IPv4 address. (The last 32 bits of the obtained IPv6 EIP is the IPv4 EIP.)
+For details, see Floating IP Address (IPv6) > Creating a Floating IP Address in the Virtual Private Cloud API Reference. The NAT64 gateway in the data center will translate the IPv6 EIP to the IPv4 address. (The last 32 bits of the obtained IPv6 EIP is the IPv4 EIP.)
After users who use IPv6 clients bind an IPv6 EIP to an ECS, the data flow is shown in Figure 1.
The IPv6 service has the following restrictions:
-- ECSs use IPv4 addresses and cannot directly access public IPv6 addresses. Therefore, only public IPv6 addresses can access ECSs. That means ECSs cannot use IPv4 EIPs that are converted from IPv6 address to access the Internet. To enable the ECSs to access the Internet, you must bind IPv4 EIPs to them.
- Data packets from an IPv6 network on the Internet are converted to IPv4 packets on the NAT64 gateway. Both the source IP address and port number will be converted. (The source IP address is invisible.)
- The IPv6 client can access only the EIP and the ELB service.
- Only one EIP (IPv6 or IPv4) can be bound to each NIC.
- You can only make API calls to use an EIP to obtain the IPv6 address. The management console displays only IPv4 addresses.
- The security group function does not apply to IPv6 clients.
- Resources in internal networks on the cloud can access IPv4 addresses converted by NAT64 gateway.
- The public cloud does not provide IP spoofing protection for IPv6 traffic from the Internet.
- Currently, the Anti-DDoS service does not protect IPv6 addresses.
- ECSs use IPv4 addresses and cannot directly access public IPv6 addresses. Therefore, only public IPv6 addresses can access ECSs. That means ECSs cannot use IPv4 EIPs that are translated from IPv6 address to access the Internet. To enable the ECSs to access the Internet, you must bind IPv4 EIPs to them.
- Data packets from an IPv6 network on the Internet are translated to IPv4 packets on the NAT64 gateway. Both the source IP address and port number will be translated. (The source IP address is invisible.)
- The IPv6 client can access only the EIP and the ELB service.
- Only one EIP (IPv6 or IPv4) can be bound to each network interface.
- You can only make API calls to use an EIP to obtain the IPv6 address. The management console displays only IPv4 addresses.
- The security group function does not apply to IPv6 clients.
- Resources in internal networks on the cloud can access IPv4 addresses translated by NAT64 gateways.
- IP spoofing protection is not provided for IPv6 traffic from the Internet.
- Anti-DDoS does not protect IPv6 addresses.
diff --git a/docs/eip/umn/faq_connect_0004.html b/docs/eip/umn/faq_connect_0004.html index 685c1f8aa..adcbc0140 100644 --- a/docs/eip/umn/faq_connect_0004.html +++ b/docs/eip/umn/faq_connect_0004.html @@ -30,12 +30,12 @@Network ACL is associated.
If the VPC is associated with a network ACL, check the network ACL rules. For details, see Checking ACL Rules.
+If the VPC is associated with a network ACL, check the network ACL rules. For details, see Checking Network ACL Rules.
A network exception occurred.
Use another ECS in the same region to check whether the local network is functional. For details, see Checking Whether the Network Is Functional.
+Use another ECS in the same region to check whether the local network is functional. For details, see Checking Whether the Network Is Normal.
Routes are incorrectly configured if multiple NICs are used.
@@ -48,7 +48,7 @@Checking Security Group Rules
ICMP is used for the ping command. Check whether the security group accommodating the ECS allows ICMP traffic.
-- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, choose Elastic Cloud Server.
- On the Elastic Cloud Server page, click the name of the target ECS.
The page providing details about the ECS is displayed.
+- Log in to the management console.
- Click
in the upper left corner and select a region and project. - Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, click the name of the target ECS.
The ECS details page is displayed.
- Click the Security Groups tab, expand the information of the security group, and view security group rules.
- Click the security group ID.
The system automatically switches to the Security Group page.
- On the Outbound Rules page, click Add Rule. In the displayed dialog box, set required parameters to add an outbound rule.
Table 2 Security group rules Transfer Direction
@@ -112,7 +112,7 @@Windows-- Log in to the Windows ECS, click the Windows icon in the lower left corner of the desktop, and choose Control Panel > Windows Firewall.
- Click Turn Windows Firewall on or off.
View and set the firewall status.
- - If the firewall is On, go to 4.
- Check the ICMP rule statuses in the firewall.
- In the navigation pane on the Windows Firewall page, click Advanced settings.
- Enable the following rules:
Inbound Rules: File and Printer Sharing (Echo Request - ICMPv4-In)
+ - If the firewall is On, go to step 4.
- Check the ICMP rule statuses in the firewall.
- In the navigation pane on the Windows Firewall page, click Advanced settings.
- Enable the following rules:
Inbound Rules: File and Printer Sharing (Echo Request - ICMPv4-In)
Outbound Rules: File and Printer Sharing (Echo Request - ICMPv4-Out)
If IPv6 is enabled, enable the following rules:
Inbound Rules: File and Printer Sharing (Echo Request - ICMPv6-In)
@@ -134,13 +134,13 @@
Checking ACL Rules
By default, no ACL is configured for a VPC. If a network ACL is associated with a VPC, check the ACL rules.
+-Checking Network ACL Rules
By default, no ACL is configured for a VPC. If a network ACL is associated with a VPC, check the ACL rules.
- Check whether the subnet of the ECS has been associated with a network ACL.
If an ACL name is displayed, the network ACL has been associated with the ECS.
- Click the ACL name to view its status.
- If the network ACL is enabled, add an ICMP rule to allow traffic.
The default network ACL rule denies all incoming and outgoing packets. If a network ACL is disabled, the default rule is still effective.
Checking Whether the Network Is Functional
- Use another ECS in the same region to check whether the local network is functional.
Use another ECS in the same region to ping the affected EIP. If the EIP can be pinged, the VPC is functional. In such a case, rectify the local network fault and ping the affected EIP again.
+diff --git a/docs/eip/umn/faq_connect_180507.html b/docs/eip/umn/faq_connect_180507.html index e51c0d653..59049016d 100644 --- a/docs/eip/umn/faq_connect_180507.html +++ b/docs/eip/umn/faq_connect_180507.html @@ -4,7 +4,7 @@Checking Whether the Network Is Normal
- Use another ECS in the same region to check whether the local network is functional.
Use another ECS in the same region to ping the affected EIP. If the EIP can be pinged, the VPC is functional. In such a case, rectify the local network fault and ping the affected EIP again.
- Check whether the link is accessible.
A ping failure is caused by packet loss or long delay, which may be caused by link congestion, link node faults, or heavy load on the ECS.
If the download speed of an ECS is slow, check the following:
- Bandwidth limit exceeded: Your used bandwidth exceeds its limit and the limiting policy of the bandwidth takes effect, causing packet loss and slowing down the access. You can check the bandwidth usage or increase the bandwidth.
If your service traffic continues to be high, you can increase the bandwidth by referring to Modifying a Shared Bandwidth.
- - The memory usage of the ECS is higher than 80%.
For details, see section "Why Is My Linux ECS Running Slowly?" or "Why Is My Windows ECS Running Slowly?" in the Elastic Cloud Server User Guide.Why Is My Linux ECS Running Slowly? or Why Is My Windows ECS Running Slowly?
+ - The memory usage of the ECS is higher than 80%.
For details, see Why Is My Linux ECS Running Slowly? or Why Is My Windows ECS Running Slowly?
- Unstable carrier lines: The network between the local server and the cloud is unstable. Contact the carrier to check the network status.
diff --git a/docs/eip/umn/faq_eip.html b/docs/eip/umn/faq_eip.html index 1541058fa..e9631de95 100644 --- a/docs/eip/umn/faq_eip.html +++ b/docs/eip/umn/faq_eip.html @@ -6,7 +6,7 @@- How Do I Access an ECS with an EIP Bound from the Internet?
- - How Do I Access the Internet Using an EIP Bound to an Extension NIC?
+ - How Do I Access the Internet Using an EIP Bound to an Extended Network Interface?
- Can I Bind an EIP of an ECS to Another ECS?
diff --git a/docs/eip/umn/faq_eip_0009.html b/docs/eip/umn/faq_eip_0009.html
index 437b36c15..2418ebfea 100644
--- a/docs/eip/umn/faq_eip_0009.html
+++ b/docs/eip/umn/faq_eip_0009.html
@@ -1,16 +1,16 @@
- - After an EIP is bound to an extension NIC, log in to the ECS and use the route command to query the routes.
You can run route --help to learn more about the route command.
+How Do I Access the Internet Using an EIP Bound to an Extended Network Interface?
+- After an EIP is bound to an extended network interface, log in to the ECS and use the route command to query the routes.
You can run route --help to learn more about the route command.
Figure 1 Viewing route information-
- Run the ifconfig command to view NIC information.Figure 2 Viewing NIC information-
- Enable access to the Internet through the extension NIC by default.
- Run the following command to delete the default route of the primary NIC:
route del -net 0.0.0.0 gw 192.168.11.1 dev eth0
-192.168.11.1 is the gateway of the subnet that the NIC works. You can view the gateway on the Summary tab page of the subnet on the management console. This operation will interrupt ECS communication. It is recommended that you perform the configuration by following step 4.
+- Run the ifconfig command to view the information about the network interface.
Figure 2 Viewing the information about the network interface+- Enable access to the Internet through the extended network interface by default.
- Run the following command to delete the default route of the primary network interface:
route del -net 0.0.0.0 gw 192.168.11.1 dev eth0
+192.168.11.1 is the gateway of the subnet that the network interface works. You can view the gateway on the Summary tab page of the subnet on the management console.- This operation will interrupt ECS communication. It is recommended that you perform the configuration by following step 4.
- Run the following command to configure the default route for the extension NIC: +
- Run the following command to configure the default route for the extended network interface:
- Configure Internet access from the extension NIC based on your destination address.
Run the following command to configure access to a specified CIDR block (for example, xx.xx.0.0/16) through the extension NIC:
+- Configure Internet access from the extended network interface based on your destination address.
diff --git a/docs/eip/umn/faq_eip_0022.html b/docs/eip/umn/faq_eip_0022.html index 01ddea92b..80203c5f8 100644 --- a/docs/eip/umn/faq_eip_0022.html +++ b/docs/eip/umn/faq_eip_0022.html @@ -2,7 +2,7 @@Run the following command to configure access to a specified CIDR block (for example, xx.xx.0.0/16) through the extended network interface:
You can configure the CIDR block as required.
route add -net xx.xx.0.0 netmask 255.255.0.0 gw 192.168.17.1
Can Multiple EIPs Be Bound to an ECS?
diff --git a/docs/eip/umn/faq_eip_0025.html b/docs/eip/umn/faq_eip_0025.html index 6fc798d28..a4bdf1ff3 100644 --- a/docs/eip/umn/faq_eip_0025.html +++ b/docs/eip/umn/faq_eip_0025.html @@ -5,7 +5,7 @@Scenarios
Multiple EIPs can be bound to an ECS, but this operation is not recommended.
-If an ECS has multiple NICs attached and you want to bind multiple EIPs to this ECS, you need to configure policy-based routes for these NICs so that these extension NICs can communicate with external works. For details, see Configuration Example.
+If an ECS has multiple network interfaces attached and you want to bind multiple EIPs to this ECS, you need to configure policy-based routes for these network interfaces so that these extension network interfaces can communicate with external networks. For details, see Configuration Example.
Configuration Example
Table 1 lists ECS configurations.
@@ -51,7 +51,7 @@
Exercise caution when deleting the default route because this operation will interrupt the network and result in SSH login failures.
- Run the following command to configure a new default route:
ip route add 0.0.0.0/0 dev eth1 via 192.168.2.1
-In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.
+In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.
-Possible Cause
Your EIP is not in the current region. For details, see EIP Not in the Current Region.
diff --git a/docs/eip/umn/monitor_0001.html b/docs/eip/umn/monitor_0001.html index 748e00ac3..9f454711d 100644 --- a/docs/eip/umn/monitor_0001.html +++ b/docs/eip/umn/monitor_0001.html @@ -1,7 +1,7 @@ -EIP Not in the Current Region
- Log in to the management console.
- Locate the EIP.
- In the upper left corner of the console, select the region to which the EIP to be queried belongs.
- Click in the upper left corner and choose Network > Elastic IP.
- In the EIP list, view the assigned EIP.
EIP Not in the Current Region
- Log in to the management console.
- Locate the EIP.
- In the upper left corner of the console, select the region to which the EIP to be queried belongs.
- Click
in the upper left corner of the page to expand the service list. Choose Network > Elastic IP. - In the EIP list, view the assigned EIP.
Cloud Eye Monitoring
- +Cloud Eye
+- Supported Metrics
diff --git a/docs/eip/umn/monitor_0002.html b/docs/eip/umn/monitor_0002.html index 88666987e..27192678d 100644 --- a/docs/eip/umn/monitor_0002.html +++ b/docs/eip/umn/monitor_0002.html @@ -148,7 +148,7 @@
diff --git a/docs/eip/umn/monitor_0003.html b/docs/eip/umn/monitor_0003.html index 177433ada..8def5a5d8 100644 --- a/docs/eip/umn/monitor_0003.html +++ b/docs/eip/umn/monitor_0003.html @@ -1,17 +1,17 @@-Parent topic: Cloud Eye Monitoring+Parent topic: Cloud EyeViewing Metrics
-Scenarios
You can view the bandwidth and EIP usage on the Elastic IP and Bandwidth or Cloud Eye console.
-You can view the inbound bandwidth, outbound bandwidth, inbound bandwidth usage, outbound bandwidth usage, inbound traffic, and outbound traffic in a specified period.
+-Scenarios
You can view the bandwidth and EIP usage on the Elastic IP and Bandwidth or Cloud Eye console.
+You can view the inbound bandwidth, outbound bandwidth, inbound bandwidth usage, outbound bandwidth usage, inbound traffic, and outbound traffic in a specified period.
Procedure (Elastic IP and Bandwidth Console)
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Elastic IP. - On the EIPs page, locate the target EIP and click View Metric in the Monitoring column to view the monitoring metrics.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- On the Shared Bandwidths page, locate the shared bandwidth, click More in the Operation column, and click View Metric to view the monitoring metric details.
-Procedure (Elastic IP and Bandwidth Console)
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Elastic IP. - On the EIPs page, locate the target EIP and click View Metric in the Monitoring column to view the monitoring metrics.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- On the Shared Bandwidths page, locate the shared bandwidth, click More in the Operation column, and click View Metric to view the monitoring metric details.
Procedure (Cloud Eye Console)
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- In the upper left corner of the page, click
to open the service list and choose Management & Deployment > Cloud Eye. - Click Cloud Service Monitoring on the left of the page, and choose Elastic IP and Bandwidth.
- Locate the target bandwidth or EIP and click View Metric in the Operation column to check the bandwidth or EIP monitoring information.
Procedure (Cloud Eye Console)
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- In the upper left corner of the page, click
to open the service list and choose Management & Deployment > Cloud Eye. - Click Cloud Service Monitoring on the left of the page, and choose Elastic IP and Bandwidth.
- Locate the row that contains the target bandwidth or EIP and click View Metric in the Operation column to check the bandwidth or EIP monitoring information.
diff --git a/docs/eip/umn/monitor_0004.html b/docs/eip/umn/monitor_0004.html index e48b6a719..4e7a8dd2a 100644 --- a/docs/eip/umn/monitor_0004.html +++ b/docs/eip/umn/monitor_0004.html @@ -1,17 +1,18 @@-Parent topic: Cloud Eye Monitoring+Parent topic: Cloud EyeCreating an Alarm Rule
-Scenarios
You can configure alarm rules to customize the monitored objects and notification policies. You can learn your resource statuses at any time.
+-Scenarios
You can configure alarm rules to customize the resources to be monitored and notification policies. The rules can keep you informed of your EIP status.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- In the upper left corner of the page, click
to open the service list and choose Management & Deployment > Cloud Eye. - In the left navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the Alarm Rules page, click Create Alarm Rule and set required parameters, or modify an existing alarm rule.
- After the parameters are set, click Create.
After the alarm rule is created, the system automatically notifies you if an alarm is triggered for the VPC service.
- For more information about alarm rules, see Cloud Eye User Guide.
+Procedure
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the upper left corner of the page, click
to open the service list and choose Management & Deployment > Cloud Eye. - In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the Alarm Rules page, click Create Alarm Rule to add an alarm rule, or select an existing alarm rule and modify it.Figure 1 Creating an alarm rule+
- Configure the parameters and click Create.
After the alarm rule is configured, the system notifies you when an alarm is triggered.
+
diff --git a/docs/eip/umn/monitor_0005.html b/docs/eip/umn/monitor_0005.html index 58b7c5918..288fbb29b 100644 --- a/docs/eip/umn/monitor_0005.html +++ b/docs/eip/umn/monitor_0005.html @@ -3,7 +3,7 @@-Parent topic: Cloud Eye Monitoring+Parent topic: Cloud EyeExporting Monitoring Data
-Scenarios
If you want to analyze the bandwidth or traffic usage of EIPs to locate faults, you can export EIP monitoring data.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Hover on the upper left corner to display Service List and choose Management & Deployment > Cloud Eye.
- In the navigation pane on the left, choose Cloud Service Monitoring > Elastic IP and Bandwidth.
- On the Cloud Service Monitoring page, click Export Data.
- Configure the time range, resource type, dimension, monitored object, and metric.
- Click Export.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Hover on the upper left corner to display Service List and choose Management & Deployment > Cloud Eye.
- In the navigation pane on the left, choose Cloud Service Monitoring > Elastic IP and Bandwidth.
- On the Cloud Service Monitoring page, click Export Data.
- Configure Time Range, Resource Type, Dimension, Monitored Object, and Metrics as needed.
- Click Export.
- The first row in the exported CSV file displays the username, region, service, instance name, instance ID, metric name, metric data, time, and timestamp. You can view historical monitoring data.
- To convert the time using a Unix timestamp to the time of the target time zone, perform the following steps:
diff --git a/docs/eip/umn/overview_permission.html b/docs/eip/umn/overview_permission.html index ad7cffca0..8fc90959e 100644 --- a/docs/eip/umn/overview_permission.html +++ b/docs/eip/umn/overview_permission.html @@ -43,7 +43,7 @@-Parent topic: Cloud Eye Monitoring+Parent topic: Cloud EyeVPC Administrator
Most permissions on VPC, excluding creating, modifying, deleting, and viewing security groups and security group rules.
-To be granted this permission, users must also have the Tenant Guest and Server Administrator permission.
+To be granted this permission, users must also have the Tenant Guest and Server Administrator permissions.
System-defined role
Figure 1 shows the relationship between regions and AZs.
-Selecting a Region
Select a region closest to your target users for lower network latency and quick access.
+Selecting a Region
You are advised to select a region close to you or your target users. This helps ensure low access latency.
Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
This task is optional.
If the default subnet cannot meet your requirements, you can create one.
-The new subnet is used to assign IP addresses to NICs added to the ECS.
+The new subnet is used to assign IP addresses to network interfaces attached to the ECS.
Assign an EIP and bind it to an ECS.
diff --git a/docs/eip/umn/qsg_0003.html b/docs/eip/umn/qsg_0003.html index ef0cb857d..3579ae813 100644 --- a/docs/eip/umn/qsg_0003.html +++ b/docs/eip/umn/qsg_0003.html @@ -6,221 +6,220 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- Click Create VPC.
- On the Create VPC page, set parameters as prompted.
A default subnet will be created together with a VPC and you can also click Add Subnet to create more subnets for the VPC.
-Figure 1 Creating a VPC and subnet+
Figure 1 Creating a VPC with a subnet (VPC information)+
Figure 2 Creating a VPC with a subnet (subnet information)-
Table 1 VPC parameter descriptions Category
+-Table 1 VPC parameter descriptions Category
Parameter
+Parameter
Description
+Description
Example Value
+Example Value
Basic Information
+Basic Configuration
Region
+Region
Select the region nearest to you to ensure the lowest latency possible.
+Select the region nearest to you to ensure the lowest latency possible.
eu-de
+eu-de
Basic Information
+Virtual Private Cloud
Name
+Name
The VPC name.
-The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
+The VPC name.
+The name can contain a maximum of 64 characters, which can consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
VPC-001
+VPC-001
Basic Information
+Virtual Private Cloud
IPv4 CIDR Block
+IPv4 CIDR Block
The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC).
+The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC).
The following CIDR blocks are supported:
10.0.0.0/8-24
172.16.0.0/12-24
192.168.0.0/16-24
192.168.0.0/16
+192.168.0.0/16
Basic Information
+Virtual Private Cloud
Enterprise Project
+Enterprise Project
The enterprise project to which the VPC belongs.
+The enterprise project to which the VPC belongs.
An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.
default
+default
Basic Information/Advanced Settings
+More (Optional)
Tag
+Tag
The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC.
+Click
+
to expand the configuration area and configure this parameter.The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC.
The tag key and value must meet the requirements listed in Table 2.
- Key: vpc_key1
- Value: vpc-01
- Key: vpc_key1
- Value: vpc-01
Basic Information/Advanced Settings
+More (Optional)
Description
+Description
Supplementary information about the VPC. This parameter is optional.
-The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
+Click
+
to expand the configuration area and configure this parameter.Supplementary information about the VPC. This parameter is optional.
+The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
N/A
+N/A
Default Subnet
+Subnet 1
Name
+Subnet Name
The subnet name.
-The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
+The subnet name.
+The name can contain a maximum of 64 characters, which can consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
Subnet
+Subnet
Default Subnet
+Subnet 1
IPv4 CIDR Block
+IPv4 CIDR Block
The CIDR block for the subnet. This value must be within the VPC CIDR block.
+The CIDR block for the subnet. This value must be within the VPC CIDR block.
192.168.0.0/24
+192.168.0.0/24
Default Subnet
+Subnet 1
IPv6 CIDR Block
+IPv6 CIDR Block (Optional)
Specifies whether to set IPv6 CIDR Block to Enable.
+Specifies whether to set IPv6 CIDR Block to Enable.
After the IPv6 function is enabled, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created.
-
+-
Default Subnet
+Subnet 1
Associated Route Table
+Associated Route Table
The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
+The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
Default
+Default
Default Subnet/Advanced Settings
+Advanced Settings (Optional)
Gateway
+Gateway
The gateway address of the subnet.
+The gateway address of the subnet.
192.168.0.1
+192.168.0.1
Default Subnet/Advanced Settings
+Advanced Settings (Optional)
DNS Server Address
+DNS Server Address
By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).
+By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).
100.125.x.x
+100.125.x.x
Default Subnet/Advanced Settings
+Advanced Settings (Optional)
NTP Server Address
+NTP Server Address
The IP address of the NTP server. This parameter is optional.
+The IP address of the NTP server. This parameter is optional.
You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added.
A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).
192.168.2.1
+192.168.2.1
Default Subnet/Advanced Settings
+Advanced Settings (Optional)
Tag
+Tag
The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.
+The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.
The tag key and value must meet the requirements listed in Table 3.
- Key: subnet_key1
- Value: subnet-01
- Key: subnet_key1
- Value: subnet-01
Default Subnet/Advanced Settings
+Advanced Settings (Optional)
Description
+Description
Supplementary information about the subnet. This parameter is optional.
-The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
+Supplementary information about the subnet. This parameter is optional.
+The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
N/A
+N/A
Table 2 VPC tag key and value requirements Parameter
+-Table 2 VPC tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each VPC and can be the same for different VPCs.
- Can contain a maximum of 36 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only hyphens (-), underscores (_), and at signs (@) are allowed.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
- Cannot be left blank.
- Can contain a maximum of 128 characters.
- Cannot start or end with a space.
vpc_key1
+vpc_key1
Value
+Value
- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only underscores (_), hyphens (-), and at signs (@) are allowed.
- Can be left blank.
- Can contain a maximum of 255 characters.
- Cannot start or end with a space.
vpc-01
+vpc-01
Table 3 Subnet tag key and value requirements Parameter
+Table 3 Subnet tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each subnet.
- Can contain a maximum of 36 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only hyphens (-), underscores (_), and at signs (@) are allowed.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
- Cannot be left blank.
- Can contain a maximum of 128 characters.
- Cannot start or end with a space.
subnet_key1
+subnet_key1
Value
+Value
- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only underscores (_), hyphens (-), and at signs (@) are allowed.
- Can be left blank.
- Can contain a maximum of 255 characters.
- Cannot start or end with a space.
subnet-01
+subnet-01
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
- Click Create Subnet.
The Create Subnet page is displayed.
- - Set the parameters as prompted.Figure 1 Creating a subnet+
- Set the parameters as prompted.Figure 1 Creating a subnet-
Table 1 Parameter descriptions Parameter
+-Table 1 Parameter descriptions Category
Description
+Parameter
Example Value
+Description
+Example Value
Region
+Select VPC
The region where the VPC is located.
+Region
-
+The region where the VPC is located.
+-
VPC
+Select VPC
The VPC for which you want to create a subnet.
+VPC
-
+The VPC for which you want to create a subnet.
+-
Subnet Name
+Subnet 1
The subnet name.
-The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
+Subnet Name
Subnet
+The subnet name.
+The name can contain a maximum of 64 characters, which can consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
+Subnet
IPv4 CIDR Block
+Subnet 1
The CIDR block for the subnet. This value must be within the VPC CIDR block.
+IPv4 CIDR Block
+The CIDR block for the subnet. This value must be within the VPC CIDR block.
If the VPC has a secondary CIDR block, you can select the primary or the secondary CIDR block that the subnet will belong to based on service requirements.
192.168.0.0/24
+192.168.0.0/24
IPv6 CIDR Block
+Subnet 1
Specifies whether to set IPv6 CIDR Block to Enable.
+IPv6 CIDR Block (Optional)
+Specifies whether to set IPv6 CIDR Block to Enable.
If you select this option, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created.
-
+-
Associated Route Table
+Subnet 1
The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
+Associated Route Table
Default
+The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
+Default
Advanced Settings/Gateway
+Advanced Settings (Optional)
+Gateway
The gateway address of the subnet.
+The gateway address of the subnet.
192.168.0.1
+192.168.0.1
Advanced Settings/DNS Server Address
+Advanced Settings (Optional)
By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).
+DNS Server Address
100.125.x.x
+By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).
+100.125.x.x
Advanced Settings/NTP Server Address
+Advanced Settings (Optional)
The IP address of the NTP server. This parameter is optional.
+NTP Server Address
+The IP address of the NTP server. This parameter is optional.
You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added.
A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).
192.168.2.1
+192.168.2.1
Advanced Settings/Tag
+Advanced Settings (Optional)
The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.
+Tag
+The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.
The tag key and value must meet the requirements listed in Table 2.
- Key: subnet_key1
- Value: subnet-01
- Key: subnet_key1
- Value: subnet-01
Advanced Settings/Description
+Advanced Settings (Optional)
Supplementary information about the subnet. This parameter is optional.
-The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
+Description
-
+Supplementary information about the subnet. This parameter is optional.
+The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
+-
Table 2 Subnet tag key and value requirements Parameter
+-Table 2 Subnet tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each subnet.
- Can contain a maximum of 36 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only hyphens (-), underscores (_), and at signs (@) are allowed.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
- Cannot be left blank.
- Can contain a maximum of 128 characters.
- Cannot start or end with a space.
subnet_key1
+subnet_key1
Value
+Value
- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only underscores (_), hyphens (-), and at signs (@) are allowed.
- Can be left blank.
- Can contain a maximum of 255 characters.
- Cannot start or end with a space.
subnet-01
+subnet-01
- Click OK.
+- Click Create Now.
-Precautions
When a subnet is created, there are five reserved IP addresses, which cannot be used. For example, in a subnet with CIDR block 192.168.0.0/24, the following IP addresses are reserved:
- 192.168.0.0: Network ID. This address is the beginning of the private IP address range and will not be assigned to any instance.
- 192.168.0.1: Gateway address.
- 192.168.0.253: Reserved for the system interface. This IP address is used by the VPC for external communication.
- 192.168.0.254: DHCP service address.
- 192.168.0.255: Network broadcast address.
Assigning an EIP
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Elastic IP.
- On the displayed page, click Assign EIP.
- Set the parameters as prompted.Figure 1 Assign EIP+
Assigning an EIP
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Elastic IP.
- On the displayed page, click Assign EIP.
- Set the parameters as prompted.Figure 1 Assign EIP-
Table 1 Parameter descriptions Parameter
EIP Type
- Dynamic BGP: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.
- Mail BGP: EIPs with port 25, 465, or 587 enabled are used for email services.
- Dynamic BGP: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.
- Mail BGP: EIPs with port 25, 465, or 587 enabled are used for email services.
The selected EIP type cannot be changed after the EIP is assigned.
Dynamic BGP
@@ -35,7 +35,7 @@Billed By
Two options are available:
-- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
Dedicated
100
Bandwidth Name
+The name of the bandwidth.
+bandwidth
+EIP Name
The EIP name.
@@ -62,13 +69,6 @@default
Bandwidth Name
-The name of the bandwidth.
-bandwidth
-Tag
The EIP tags. Each tag contains a key and value pair.
@@ -88,28 +88,26 @@Table 2 EIP tag requirements Parameter
+Table 2 EIP tag requirements Parameter
Requirement
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- The key value must be unique for the same EIP.
- Can contain up to 36 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only hyphens (-), underscores (_), and at signs (@) are allowed.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
- Cannot be left blank.
- Can contain a maximum of 128 characters.
- Cannot start or end with a space.
Ipv4_key1
+Ipv4_key1
Value
+Value
- Can contain up to 43 characters.
- Can contain only the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Only underscores (_), hyphens (-), and at signs (@) are allowed.
- Can be left blank.
- Can contain a maximum of 255 characters.
- Cannot start or end with a space.
3005eip
+3005eip
- Click Create Now.
- Click Submit.
-Binding an EIP
- On the EIPs page, locate the row that contains the target EIP, and click Bind.
- Select the instance that you want to bind the EIP to.
-Figure 2 Bind EIP+Figure 2 Bind EIP
- Click OK.
An IPv6 client on the internet can access the ECS that has an EIP bound in a VPC. For details, see How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
-Follow-Up Procedure
After an ECS with an EIP bound is created, the system generates a domain name in the format of ecs-xx-xx-xx-xx.compute.xxx.com for the EIP by default. xx-xx-xx-xx indicates the EIP, and xxx indicates the domain name of the cloud service provider. You can use the domain name to access the ECS.
-You can use any of the following commands to obtain the domain name of an EIP:diff --git a/docs/eip/umn/qsg_0006.html b/docs/eip/umn/qsg_0006.html index 32c79f1e3..a58365abe 100644 --- a/docs/eip/umn/qsg_0006.html +++ b/docs/eip/umn/qsg_0006.html @@ -5,154 +5,154 @@- ping -an EIP
- nslookup [-qt=ptr] EIP
- dig -x EIP
Follow-Up Procedure
After an ECS with an EIP bound is created, the system generates a reverse domain name in the format of ecs-xx-xx-xx-xx.compute.xxx.com for the EIP by default. xx-xx-xx-xx indicates the EIP, and xxx indicates the domain name of the cloud service provider. You can use the reverse domain name to access the ECS.
+You can use any of the following commands to obtain the reverse domain name of an EIP:- nslookup -query=ptr EIP
- dig -x EIP
If your instances have different Internet access requirements, you can allocate them to different security groups when creating them.
Each ECS must be associated with at least one security group. If you do not have a security group when creating an ECS, the system provides a default security group.
Security Group Templates
The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. Table 1 describes the security group templates. -Table 1 Security group templates Template
++Preset Security Group Rules
The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. Table 1 describes the security group templates.
+ +-Table 1 Security group template description Template
Direction
+Direction
Protocol/Port/Type
+Protocol & Port & Type
Source/Destination
+Source or Destination
Description
+Description
Application Scenario
+Scenario
General-purpose web server
+General-purpose web server
Inbound
+Inbound
TCP: 22 (IPv4)
+TCP: 22 (IPv4)
0.0.0.0/0
+0.0.0.0/0
Allows all IPv4 addresses to access ECSs in the security group over port 22 (SSH) for remotely logging in to Linux ECSs.
+Allows all IPv4 addresses to access instances in the security group over port 22 (SSH) for remotely logging in to Linux instances.
- Remotely log in to ECSs.
- Use the ping command to test ECS connectivity.
- ECSs functioning as web servers provide website access services.
- Remotely logging in to an instance (such as an ECS) in the security group from an external network
- Enabling external servers to ping the instances in the security group to verify network connectivity
- Using instances in the security group as web servers to provide website services accessible from an external network
TCP: 3389 (IPv4)
+TCP: 3389 (IPv4)
0.0.0.0/0
+0.0.0.0/0
Allows all IPv4 addresses to access ECSs in the security group over port 3389 (RDP) for remotely logging in to Windows ECSs.
+Allows all IPv4 addresses to access instances in the security group over port 3389 (RDP) for remotely logging in to Windows instances.
TCP: 80 (IPv4)
+TCP: 80 (IPv4)
0.0.0.0/0
+0.0.0.0/0
Allows all IPv4 addresses to access ECSs in the security group over port 80 (HTTP) for visiting websites.
+Allows all IPv4 addresses to access instances in the security group over port 80 (HTTP) for visiting websites.
TCP: 443 (IPv4)
+TCP: 443 (IPv4)
0.0.0.0/0
+0.0.0.0/0
Allows all IPv4 addresses to access ECSs in the security group over port 443 (HTTPS) for visiting websites.
+Allows all IPv4 addresses to access instances in the security group over port 443 (HTTPS) for visiting websites.
ICMP: All (IPv4)
+ICMP: All (IPv4)
0.0.0.0/0
+0.0.0.0/0
Allows all IPv4 addresses to access ECSs in the security group over any port for using the ping command to test ECS connectivity.
+Allows all IPv4 addresses to access instances in the security group over any port for using the ping command to test connectivity.
All (IPv4)
-All (IPv6)
+All (IPv4)
+All (IPv6)
sg-xxx
+Current security group
Allows ECSs in the security group to communicate with each other.
+Allows the instances in the security group to communicate with each other over an internal network over any protocol.
Outbound
+Outbound
All (IPv4)
-All (IPv6)
+All (IPv4)
+All (IPv6)
0.0.0.0/0
+0.0.0.0/0
Allows access from ECSs in the security group to any IP address over any port.
+Allows all traffic from the instances in the security group to external resources over any protocol.
All ports open
+All ports open
Inbound
+Inbound
All (IPv4)
-All (IPv6)
+All (IPv4)
+All (IPv6)
sg-xxx
+Current security group
Allows ECSs in the security group to communicate with each other.
+Allows the instances in the security group to communicate with each other over an internal network over any protocol.
Opening all ECS ports in a security group poses security risks.
+This template allows any traffic to enter and leave the instances in the security group, which has security risks.
All (IPv4)
-All (IPv6)
+All (IPv4)
+All (IPv6)
0.0.0.0/0
+0.0.0.0/0
Allows all IP addresses to access ECSs in the security group over any port.
+Allows any IP address to access the instances in the security group over any protocol.
Outbound
+Outbound
All (IPv4)
-All (IPv6)
+All (IPv4)
+All (IPv6)
0.0.0.0/0
+0.0.0.0/0
Allows access from ECSs in the security group to any IP address over any port.
+Allows all traffic from the instances in the security group to external resources over any protocol.
Fast-add rule
+Common ports open
Inbound
+Inbound
All (IPv4)
-All (IPv6)
+All (IPv4)
+All (IPv6)
sg-xxx
+Current security group
Allows ECSs in the security group to communicate with each other.
+Allows the instances in the security group to communicate with each other over an internal network over any protocol.
You can select protocols and ports that the inbound rule will apply to.
-If you do not select any protocols and ports, no protocols and ports will be opened. After the security group is created, add required rules by referring to Step 5: Add a Security Group Rule.
+You can select protocols and ports that the inbound rule will apply to.
Custom port and protocol
+Custom port and protocol
0.0.0.0/0
+0.0.0.0/0
Allows all IP addresses to access ECSs in a security group over specified ports (TCP or ICMP) for different purposes.
+Allows all IP addresses to access instances in the security group over specified ports (TCP or ICMP) for different purposes.
Outbound
+Outbound
All (IPv4)
-All (IPv6)
+All (IPv4)
+All (IPv6)
0.0.0.0/0
-::/0
+0.0.0.0/0
+::/0
Allows access from ECSs in the security group to any IP address over any port.
+Allows all traffic from the instances in the security group to external resources over any protocol.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- In the upper right corner, click Create Security Group.
The Create Security Group page is displayed.
- - Configure the parameters as prompted.Figure 1 Create Security Group+
- Configure the parameters as prompted.Figure 1 Create Security Group
-Table 2 Parameter description Parameter
Mandatory
Enter the security group name.
-The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
+The security group name can contain a maximum of 64 characters, which can consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
NOTE:You can change the security group name after a security group is created. It is recommended that you give each security group a different name.
default
Template
-Mandatory
-The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements.
-Table 1 describes the security group templates.
-General-purpose web server
-Description
Optional
Supplementary information about the security group. This parameter is optional.
-The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
+The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
N/A
Template
+Mandatory
+The templates have preset inbound and outbound rules. You can select one as needed to quickly create a security group.
+General-purpose web server
+ - Confirm the inbound and outbound rules of the template and click OK.
- Click OK.
diff --git a/docs/eip/umn/qsg_0007.html b/docs/eip/umn/qsg_0007.html index 5913be0f4..695ab2410 100644 --- a/docs/eip/umn/qsg_0007.html +++ b/docs/eip/umn/qsg_0007.html @@ -12,77 +12,80 @@If the rules of the security group associated with your instance cannot meet your requirements, for example, you need to allow inbound traffic on a specific TCP port, you can add an inbound rule to allow traffic on the TCP port.
-Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
+Adding Rules to a Security Group
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Virtual Private Cloud.
The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- Locate the row that contains the target security group and click Manage Rules in the Operation column.
The page for configuring security group rules is displayed.
- On the Inbound Rules tab, click Add Rule.
The Add Inbound Rule dialog box is displayed.
- Configure required parameters.
You can click + to add more inbound rules.
-Figure 1 Add Inbound Rule+
Figure 1 Add Inbound Rule+ -
- Run the ifconfig command to view the information about the network interface.
- Run the following command to delete the default route of the primary NIC:
- After an EIP is bound to an extended network interface, log in to the ECS and use the route command to query the routes.
How Do I Access the Internet Using an EIP Bound to an Extension NIC?
- - Use another ECS in the same region to check whether the local network is functional.
