A shared bandwidth can be shared by multiple EIPs and controls the data transfer rate on these EIPs in a centralized manner. All ECSs, BMSs, and load balancers that have EIPs bound in the same region can share a bandwidth.
-When you host a large number of applications on the cloud, if each EIP uses a bandwidth, a lot of bandwidths are required, increasing O&M workload. If all EIPs share the same bandwidth, VPCs and the region-level bandwidth can be managed in a unified manner, simplifying O&M statistics and network operations cost settlement.
-- Easy to Manage
Region-level bandwidth sharing and multiplexing simplify O&M statistics, management, and operations cost settlement.
- - Flexible Operations
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.
diff --git a/docs/eip/umn/bandwidth_0003.html b/docs/eip/umn/bandwidth_0003.html index 325209e1..1a68c90a 100644 --- a/docs/eip/umn/bandwidth_0003.html +++ b/docs/eip/umn/bandwidth_0003.html @@ -1,53 +1,53 @@A shared bandwidth can be shared by multiple EIPs and controls the data transfer rate on these EIPs in a centralized manner. All ECSs, BMSs, and load balancers that have EIPs bound in the same region can share a bandwidth.
++ - A shared bandwidth cannot control how much data can be transferred using a single EIP. Data transfer rate on EIPs cannot be customized.
When you host a large number of applications on the cloud, if each EIP uses a bandwidth, a lot of bandwidths are required, increasing O&M workload. If all EIPs share the same bandwidth, VPCs and the region-level bandwidth can be managed in a unified manner, simplifying O&M statistics and network operations cost settlement.
+- Easy to Manage
Region-level bandwidth sharing and multiplexing simplify O&M statistics, management, and operations cost settlement.
+ - Flexible Operations
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.
Assigning a Shared Bandwidth
-Scenarios
Assign a shared bandwidth for use with EIPs.
+-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-
-Table 1 Parameter descriptions Parameter
+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+
+-Table 1 Parameter descriptions Parameter
Description
+Description
Example Value
+Example Value
Region
+Region
Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you.
+Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you.
eu-de
+eu-de
Bandwidth
+Bandwidth
The bandwidth size in Mbit/s. The minimum value is 5 Mbit/s. The maximum bandwidth can be 1000 Mbit/s.
+The bandwidth size in Mbit/s. The minimum value is 5 Mbit/s. The maximum bandwidth can be 1000 Mbit/s.
10
+10
Name
+Name
The name of the shared bandwidth.
+The name of the shared bandwidth.
Bandwidth-001
+Bandwidth-001
Enterprise Project
+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.
+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.
default
+default
- Click Assign Now.
- Click Assign Now.
diff --git a/docs/eip/umn/bandwidth_0004.html b/docs/eip/umn/bandwidth_0004.html index 78be6d65..07afaaad 100644 --- a/docs/eip/umn/bandwidth_0004.html +++ b/docs/eip/umn/bandwidth_0004.html @@ -1,14 +1,16 @@Adding EIPs to a Shared Bandwidth
-Scenarios
Add EIPs to a shared bandwidth and the EIPs can then share that bandwidth. You can add multiple EIPs to a shared bandwidth at the same time.
+-Scenarios
Add EIPs to a shared bandwidth and the EIPs can then share that bandwidth. You can add multiple EIPs to a shared bandwidth at the same time.
Notes and Constraints
- After an EIP is added to a shared bandwidth, the original bandwidth used by the EIP will become invalid and the EIP will start to use the shared bandwidth.
- The EIP's original dedicated bandwidth will be deleted.
- 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.
-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 row that contains the shared bandwidth that you want to add EIPs to. In the Operation column, choose More > Add EIP, and select the EIPs to be added.
- 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's dedicated bandwidth will be deleted and will no longer be billed.
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+
Figure 2 Adding an IPv6 address+
+- - 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.
Figure 1 Add EIP-
- Click OK.
+ - Click OK.
diff --git a/docs/eip/umn/bandwidth_0005.html b/docs/eip/umn/bandwidth_0005.html index 5c73d2fd..6bc2263b 100644 --- a/docs/eip/umn/bandwidth_0005.html +++ b/docs/eip/umn/bandwidth_0005.html @@ -1,10 +1,10 @@Removing EIPs from a Shared Bandwidth
-Scenarios
Remove EIPs that are no longer required from a shared bandwidth if needed.
+-Scenarios
Remove EIPs that are no longer required from a shared bandwidth if needed.
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 bandwidth from which EIPs are to be removed, choose More > Remove EIP in the Operation column, and select the EIPs to be removed in the displayed dialog box.Figure 1 Remove EIP-
- 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 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+
- Click OK.
diff --git a/docs/eip/umn/bandwidth_0006.html b/docs/eip/umn/bandwidth_0006.html index 66048403..eb15cbaa 100644 --- a/docs/eip/umn/bandwidth_0006.html +++ b/docs/eip/umn/bandwidth_0006.html @@ -1,10 +1,10 @@Modifying a Shared Bandwidth
-Scenarios
You can modify the name and size of a shared bandwidth as required.
+-Scenarios
You can modify the name and size of a shared bandwidth as required.
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-
- 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.
- 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+
- Click Next.
- Click Submit.
diff --git a/docs/eip/umn/bandwidth_0007.html b/docs/eip/umn/bandwidth_0007.html index 6460eec8..e7aa6075 100644 --- a/docs/eip/umn/bandwidth_0007.html +++ b/docs/eip/umn/bandwidth_0007.html @@ -1,11 +1,11 @@Deleting a Shared Bandwidth
-Scenarios
Delete a shared bandwidth when it is no longer required.
+-Scenarios
Delete a shared bandwidth when it is no longer required.
Prerequisites
Before deleting a shared bandwidth, remove all the EIPs associated with it. For details, see Removing EIPs from a Shared Bandwidth.
+-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.
- In the displayed dialog box, click Yes.
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.
- In the displayed dialog box, click OK.
diff --git a/docs/eip/umn/bandwidth_0009.html b/docs/eip/umn/bandwidth_0009.html new file mode 100644 index 00000000..45242b2b --- /dev/null +++ b/docs/eip/umn/bandwidth_0009.html @@ -0,0 +1,12 @@ + + +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.
+
++ diff --git a/docs/eip/umn/eip_0001.html b/docs/eip/umn/eip_0001.html index c226b800..8007a8c3 100644 --- a/docs/eip/umn/eip_0001.html +++ b/docs/eip/umn/eip_0001.html @@ -14,6 +14,10 @@++Parent topic: Shared Bandwidth+- Exporting EIP Information
+
- Adding EIPs to a Shared Bandwidth
+
+- Removing EIPs from a Shared Bandwidth
+- Managing EIP Tags
diff --git a/docs/eip/umn/eip_0002.html b/docs/eip/umn/eip_0002.html index 81b882c2..623be141 100644 --- a/docs/eip/umn/eip_0002.html +++ b/docs/eip/umn/eip_0002.html @@ -1,128 +1,129 @@
Assigning an EIP and Binding It to an ECS
-Scenarios
You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.
- Note the following when you use EIPs of the Dedicated Load Balancer (5_gray) type:- In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
- Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- 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.
-Scenarios
You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.
+ Note the following when you use EIPs of the Dedicated Load Balancer (5_gray) type:- In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
- Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- 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 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
+-Table 1 Parameter descriptions Parameter
Description
+Description
Example Value
+Example Value
Region
+Region
Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. The region selected for the EIP is its geographical location.
+Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. The region selected for the EIP is its geographical location.
eu-de
+eu-de
EIP Type
+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.
The selected EIP type cannot be changed after the EIP is assigned.
+- 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
+Dynamic BGP
Billed By
+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.
Two options are available:
+- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
Dedicated
+Dedicated
Bandwidth
+Bandwidth
The bandwidth size in Mbit/s.
+The bandwidth size in Mbit/s.
100
+100
EIP Name
+EIP Name
The EIP name.
+The EIP name.
eip-test
+eip-test
Enterprise Project
+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.
+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.
default
+default
Bandwidth Name
+Bandwidth Name
The name of the bandwidth.
+The name of the bandwidth.
bandwidth
+bandwidth
Tag
+Tag
The EIP tags. Each tag contains a key and value pair.
-The tag key and value must meet the requirements listed in Table 2.
+The EIP tags. Each tag contains a key and value pair.
+The tag key and value must meet the requirements listed in Table 2.
- Key: Ipv4_key1
- Value: 3005eip
- Key: Ipv4_key1
- Value: 3005eip
Quantity
+Quantity
The number of EIPs you want to assign.
+The number of EIPs you want to assign.
1
+1
Table 2 EIP tag requirements Parameter
+-Table 2 EIP tag requirements Parameter
Requirement
+Requirement
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
3005eip
+3005eip
- Click Create Now.
- Click Submit.
+- 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-
- 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?
+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.
-diff --git a/docs/eip/umn/eip_0003.html b/docs/eip/umn/eip_0003.html index e1e23b80..b06d9f10 100644 --- a/docs/eip/umn/eip_0003.html +++ b/docs/eip/umn/eip_0003.html @@ -1,19 +1,19 @@
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:+- ping -a EIP
- nslookup [-qt=ptr] EIP
- dig -x 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:- ping -an EIP
- nslookup [-qt=ptr] EIP
- dig -x EIP
Unbinding an EIP from an ECS and Releasing the EIP
-Scenarios
If you no longer need an EIP, unbind it from the ECS and release the EIP to avoid wasting network resources.
+-Scenarios
If you no longer need an EIP, unbind it from the ECS and release the EIP to avoid wasting network resources.
Notes and Constraints
- In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
- Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- EIP assigned together with your load balancers will also be displayed in the EIP list.
- You can only release EIPs that are not bound to any resources.
-Notes and Constraints
- In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
- Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- 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 target EIP, and click Unbind.
- Click Yes in the displayed dialog box.
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 Yes in the displayed dialog box.
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 Yes in the displayed dialog box.
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 Yes in the displayed dialog box.
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 Yes in the displayed dialog box.
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 Yes in the displayed dialog box.
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 Yes in the displayed dialog box.
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 Yes in the displayed dialog box.
diff --git a/docs/eip/umn/eip_0004.html b/docs/eip/umn/eip_0004.html index 95370023..51204560 100644 --- a/docs/eip/umn/eip_0004.html +++ b/docs/eip/umn/eip_0004.html @@ -1,46 +1,45 @@Managing EIP Tags
-Scenarios
Tags can be added to EIPs to facilitate EIP identification and administration. You can add a tag to an EIP when assigning the EIP. Alternatively, you can add a tag to an assigned EIP on the EIP details page. A maximum of 20 tags can be added to each EIP.
+-Scenarios
Tags can be added to EIPs to facilitate EIP identification and administration. You can add a tag to an EIP when assigning the EIP. Alternatively, you can add a tag to an assigned EIP on the EIP details page. A maximum of 20 tags can be added to each EIP.
A tag consists of a key and value pair. Table 1 lists the tag key and value requirements.
+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
+Requirement
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
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.
- Click the search box and then click Tag in the drop-down list.
- Select the tag key and value of the EIP.
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 contain all of the tags you specified.
- - Click OK.
The system displays the EIPs you are looking for based on the entered tag keys and values.
+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 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.
- 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 Yes.
+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 5bade26c..f7e6447a 100644 --- a/docs/eip/umn/eip_0005.html +++ b/docs/eip/umn/eip_0005.html @@ -1,12 +1,12 @@- 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 Yes.
- View tags.
Modifying an EIP Bandwidth
-Scenarios
Modify the EIP bandwidth name or size.
- 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.
+-Scenarios
Modify the EIP bandwidth name or size.
+ 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. +
- Click Next.
- Click Submit.
diff --git a/docs/eip/umn/eip_0007.html b/docs/eip/umn/eip_0007.html index 34f0d2a5..0597c8bf 100644 --- a/docs/eip/umn/eip_0007.html +++ b/docs/eip/umn/eip_0007.html @@ -3,7 +3,7 @@EIP Overview
EIP
The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. If a resource has an EIP bound, it can directly access the Internet. If a resource only has a private IP address, it cannot directly access the Internet. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.
Each EIP can be bound to only one cloud resource and they must be in the same region.
-Figure 1 Connecting to the Internet using an EIP+
Figure 1 Connecting to the Internet using an EIP
diff --git a/docs/eip/umn/eip_0015.html b/docs/eip/umn/eip_0015.html index 840d491f..4bdf9b96 100644 --- a/docs/eip/umn/eip_0015.html +++ b/docs/eip/umn/eip_0015.html @@ -3,7 +3,7 @@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.
diff --git a/docs/eip/umn/eip_0018.html b/docs/eip/umn/eip_0018.html new file mode 100644 index 00000000..1ee4aa7d --- /dev/null +++ b/docs/eip/umn/eip_0018.html @@ -0,0 +1,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.
- On the displayed page, click
in the upper right corner of the EIP list.The system will automatically export all EIPs in the current region of your account to an Excel file and download 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, 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.
Adding EIPs to a Shared Bandwidth
+++Scenarios
You can add multiple EIPs to a shared bandwidth to save costs.
++Notes and Constraints
- The type of EIPs must be the same as that of the shared bandwidth the EIPs to be added to.
- 5_gray EIPs cannot be added to the same bandwidth as EIPs of other types. If they are in the same shared bandwidth, the bandwidth limit settings 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 > EIPs.
- In the EIP list, locate the target EIP. In the Operation column, choose More > Add to Shared Bandwidth.Figure 1 Adding an EIP to a shared bandwidth+
++ - 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.
- Click OK.
++ diff --git a/docs/eip/umn/eip_0019.html b/docs/eip/umn/eip_0019.html new file mode 100644 index 00000000..14bee749 --- /dev/null +++ b/docs/eip/umn/eip_0019.html @@ -0,0 +1,15 @@ + + +++Parent topic: Elastic IP+Removing EIPs from a Shared Bandwidth
+++Scenarios
You can remove EIPs from a shared bandwidth as needed.
++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.
++ diff --git a/docs/eip/umn/eip_feature.html b/docs/eip/umn/eip_feature.html index 970a6fcd..dd4027aa 100644 --- a/docs/eip/umn/eip_feature.html +++ b/docs/eip/umn/eip_feature.html @@ -25,7 +25,7 @@++Parent topic: Elastic IP+
- View tags.
Shared Bandwidth
All ECSs, BMSs, and load balancers can share the same bandwidth if they reside in the same region and have EIPs bound.
+All ECSs, BMSs, and load balancers can share the same bandwidth if they reside in the same region and have EIPs bound.
You can assign, modify, delete a shared bandwidth, add EIPs to a shared bandwidth, and remove EIPs from a shared bandwidth.
For details, see Shared Bandwidth Overview.
Change History
-Released On
+Released On
Description
2023-08-01
+2024-05-17
+This release incorporates the following change:
+- Modified the figure for adding an EIP to a shared bandwidth in Adding EIPs to a Shared Bandwidth.
- Modified the figure for removing an EIP from a shared bandwidth in Removing EIPs from a Shared Bandwidth.
- Modified Buy EIP to Assign EIP in Creating a User and Granting EIP Permissions.
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?
2024-03-28
+This release incorporates the following changes:
+- Changed VPCReadOnlyAccess and VPCFullAccess into VPC ReadOnlyAccess and VPC FullAccess.
- The "at" signs (@) are allowed for tag keys and values.
- Added bandwidth constraints in Notes and Constraints.
- Deleted the content related to the IP address group in Step 5: Add a Security Group Rule.
- Modified the operation procedure and figures in Adding EIPs to a Shared Bandwidth and Removing EIPs from a Shared Bandwidth.
- Updated the link directing to the Cloud Eye User Guide in Creating an Alarm Rule.
- Modified the link of "Creating a Custom Policy" in EIP Custom Policies.
- Modified the procedure for unbinding an existing EIP from a load balancer and binding a new EIP to a load balancer in How Do I Unbind an EIP from an Instance and Bind a New EIP to the Instance?
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.
2023-08-01
This release incorporates the following changes:
Updated the following content:
@@ -26,16 +50,18 @@This release incorporates the following changes:
Updated the following content:
-Modified links in How Do I Assign or Retrieve a Specific EIP?, What Are the Differences Between EIP Bandwidth and Private Network Bandwidth?, and Why Does the Download Speed of My ECS Is Slow?.
-Modified the description of modifying an EIP for an ECS in How Do I Change an EIP for an Instance?.
+- + + + +
- Modified the description of modifying an EIP for an ECS in How Do I Unbind an EIP from an Instance and Bind a New EIP to the Instance?
2023-05-15
This release incorporates the following changes:
Updated the following content:
-Modified the links to "Unbinding an EIP from an Instance" and "Binding an EIP to an Instance" in Can I Bind an EIP of an ECS to Another ECS?.
-Modified the link to "Virtual IP Address Overview" in What Are the Differences Between EIP, Private IP Address, and Virtual IP Address?.
+- Modified the links to "Unbinding an EIP from an Instance" and "Binding an EIP to an Instance" in Can I Bind an EIP of an ECS to Another ECS?
- Modified the link to "Virtual IP Address Overview" in What Are the Differences Between EIP, Private IP Address, and Virtual IP Address?
2023-03-28
@@ -49,8 +75,7 @@This release incorporates the following changes:
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?
+- 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:
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 Change an EIP for an 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?
- How Do I Buy a Shared Bandwidth?
- What Are Inbound Bandwidth and Outbound Bandwidth?
- What Are the Differences Between EIP Bandwidth and Private Network Bandwidth?
- What Is the Relationship Between Bandwidth and Upload/Download Rate?
- Why Can't an EIP 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 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?
2022-10-18
Updated the following content:
-- Modified the bandwidth range in What Is the Bandwidth Size Range?.
- Modified the description of dynamic BGP and email BGP in Assigning an EIP and Binding It to an ECS.
- Modified the bandwidth range in What Is the Bandwidth Size Range?
- Modified the description of dynamic BGP and email BGP in Assigning an EIP and Binding It to an ECS.
2022-06-25
@@ -115,7 +140,7 @@2021-03-16
Added the following FAQs:
- +2020-12-16
@@ -143,7 +168,7 @@Added the following content:
Modified the following content:
-- Optimized What Is Elastic IP?.
- Added function and namespace description and optimized information in tables in Supported Metrics.
- Optimized What Is Elastic IP?
- Added function and namespace description and optimized information in tables in Supported Metrics.
2018-09-14
diff --git a/docs/eip/umn/en-us_image_0000001197228903.png b/docs/eip/umn/en-us_image_0000001197228903.png deleted file mode 100644 index 6ef66ec6..00000000 Binary files a/docs/eip/umn/en-us_image_0000001197228903.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000001211006359.png b/docs/eip/umn/en-us_image_0000001211006359.png deleted file mode 100644 index 66686f7e..00000000 Binary files a/docs/eip/umn/en-us_image_0000001211006359.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000001211445065.png b/docs/eip/umn/en-us_image_0000001211445065.png deleted file mode 100644 index a86f5c5d..00000000 Binary files a/docs/eip/umn/en-us_image_0000001211445065.png and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0000001500905066.png b/docs/eip/umn/en-us_image_0000001649841616.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001500905066.png rename to docs/eip/umn/en-us_image_0000001649841616.png diff --git a/docs/eip/umn/en-us_image_0000001520717193.png b/docs/eip/umn/en-us_image_0000001675258889.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001520717193.png rename to docs/eip/umn/en-us_image_0000001675258889.png diff --git a/docs/eip/umn/en-us_image_0000001520959725.png b/docs/eip/umn/en-us_image_0000001675418673.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001520959725.png rename to docs/eip/umn/en-us_image_0000001675418673.png diff --git a/docs/eip/umn/en-us_image_0000001785700150.png b/docs/eip/umn/en-us_image_0000001785700150.png new file mode 100644 index 00000000..a9273b27 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001785700150.png differ diff --git a/docs/eip/umn/en-us_image_0162332046.png b/docs/eip/umn/en-us_image_0000001818823006.png similarity index 100% rename from docs/eip/umn/en-us_image_0162332046.png rename to docs/eip/umn/en-us_image_0000001818823006.png diff --git a/docs/eip/umn/en-us_image_0000001117669274.png b/docs/eip/umn/en-us_image_0000001818823034.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001117669274.png rename to docs/eip/umn/en-us_image_0000001818823034.png diff --git a/docs/eip/umn/en-us_image_0000001595877226.png b/docs/eip/umn/en-us_image_0000001818823082.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001595877226.png rename to docs/eip/umn/en-us_image_0000001818823082.png diff --git a/docs/eip/umn/en-us_image_0000001818823514.png b/docs/eip/umn/en-us_image_0000001818823514.png new file mode 100644 index 00000000..a5876445 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001818823514.png differ diff --git a/docs/eip/umn/en-us_image_0000001117669524.png b/docs/eip/umn/en-us_image_0000001818823830.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001117669524.png rename to docs/eip/umn/en-us_image_0000001818823830.png diff --git a/docs/eip/umn/en-us_image_0000001338408584.png b/docs/eip/umn/en-us_image_0000001818982734.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001338408584.png rename to docs/eip/umn/en-us_image_0000001818982734.png diff --git a/docs/eip/umn/en-us_image_0000001596195138.png b/docs/eip/umn/en-us_image_0000001818982822.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001596195138.png rename to docs/eip/umn/en-us_image_0000001818982822.png diff --git a/docs/eip/umn/en-us_image_0000001818983298.png b/docs/eip/umn/en-us_image_0000001818983298.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001818983298.png differ diff --git a/docs/eip/umn/en-us_image_0000001832343237.png b/docs/eip/umn/en-us_image_0000001832343237.png new file mode 100644 index 00000000..743f2b18 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001832343237.png differ diff --git a/docs/eip/umn/en-us_image_0000001832479012.png b/docs/eip/umn/en-us_image_0000001832479012.png new file mode 100644 index 00000000..2fb3fb2d Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001832479012.png differ diff --git a/docs/eip/umn/en-us_image_0000001388688657.png b/docs/eip/umn/en-us_image_0000001844205350.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001388688657.png rename to docs/eip/umn/en-us_image_0000001844205350.png diff --git a/docs/eip/umn/en-us_image_0204809678.png b/docs/eip/umn/en-us_image_0000001844205418.png similarity index 100% rename from docs/eip/umn/en-us_image_0204809678.png rename to docs/eip/umn/en-us_image_0000001844205418.png diff --git a/docs/eip/umn/en-us_image_0000001844364098.png b/docs/eip/umn/en-us_image_0000001844364098.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001844364098.png differ diff --git a/docs/eip/umn/en-us_image_0204809728.png b/docs/eip/umn/en-us_image_0000001844364134.png similarity index 100% rename from docs/eip/umn/en-us_image_0204809728.png rename to docs/eip/umn/en-us_image_0000001844364134.png diff --git a/docs/eip/umn/en-us_image_0204809524.png b/docs/eip/umn/en-us_image_0000001844364142.png similarity index 100% rename from docs/eip/umn/en-us_image_0204809524.png rename to docs/eip/umn/en-us_image_0000001844364142.png diff --git a/docs/eip/umn/en-us_image_0210188011.png b/docs/eip/umn/en-us_image_0000001844364154.png similarity index 100% rename from docs/eip/umn/en-us_image_0210188011.png rename to docs/eip/umn/en-us_image_0000001844364154.png diff --git a/docs/eip/umn/en-us_image_0000001163949251.png b/docs/eip/umn/en-us_image_0000001865582577.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001163949251.png rename to docs/eip/umn/en-us_image_0000001865582577.png diff --git a/docs/eip/umn/en-us_image_0000001865582629.png b/docs/eip/umn/en-us_image_0000001865582629.png new file mode 100644 index 00000000..58647558 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001865582629.png differ diff --git a/docs/eip/umn/en-us_image_0000001865582681.png b/docs/eip/umn/en-us_image_0000001865582681.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001865582681.png differ diff --git a/docs/eip/umn/en-us_image_0000001166028070.png b/docs/eip/umn/en-us_image_0000001865662761.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001166028070.png rename to docs/eip/umn/en-us_image_0000001865662761.png diff --git a/docs/eip/umn/en-us_image_0000001865662817.png b/docs/eip/umn/en-us_image_0000001865662817.png new file mode 100644 index 00000000..d46c18d8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001865662817.png differ diff --git a/docs/eip/umn/en-us_image_0000001401506644.png b/docs/eip/umn/en-us_image_0000001865662865.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001401506644.png rename to docs/eip/umn/en-us_image_0000001865662865.png diff --git a/docs/eip/umn/en-us_image_0000001197426329.png b/docs/eip/umn/en-us_image_0000001865662885.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001197426329.png rename to docs/eip/umn/en-us_image_0000001865662885.png diff --git a/docs/eip/umn/en-us_image_0000001865663089.png b/docs/eip/umn/en-us_image_0000001865663089.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001865663089.png differ diff --git a/docs/eip/umn/en-us_image_0000001865837676.png b/docs/eip/umn/en-us_image_0000001865837676.png new file mode 100644 index 00000000..267f2dee Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001865837676.png differ diff --git a/docs/eip/umn/en-us_image_0000001871372156.png b/docs/eip/umn/en-us_image_0000001871372156.png new file mode 100644 index 00000000..c4f51c3f Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001871372156.png differ diff --git a/docs/eip/umn/en-us_image_0000001879005797.png b/docs/eip/umn/en-us_image_0000001879005797.png new file mode 100644 index 00000000..f6203273 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001879005797.png differ diff --git a/docs/eip/umn/en-us_image_0000001879491934.png b/docs/eip/umn/en-us_image_0000001879491934.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001879491934.png differ diff --git a/docs/eip/umn/en-us_image_0000001567669964.png b/docs/eip/umn/en-us_image_0000001879576152.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001567669964.png rename to docs/eip/umn/en-us_image_0000001879576152.png diff --git a/docs/eip/umn/en-us_image_0000001618428593.png b/docs/eip/umn/en-us_image_0000001890444945.png similarity index 100% rename from docs/eip/umn/en-us_image_0000001618428593.png rename to docs/eip/umn/en-us_image_0000001890444945.png diff --git a/docs/eip/umn/en-us_image_0204809685.png b/docs/eip/umn/en-us_image_0000001890445013.png similarity index 100% rename from docs/eip/umn/en-us_image_0204809685.png rename to docs/eip/umn/en-us_image_0000001890445013.png diff --git a/docs/eip/umn/en-us_image_0000001890564513.png b/docs/eip/umn/en-us_image_0000001890564513.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001890564513.png differ diff --git a/docs/eip/umn/en-us_image_0000001890564517.png b/docs/eip/umn/en-us_image_0000001890564517.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001890564517.png differ diff --git a/docs/eip/umn/en-us_image_0000001890564529.png b/docs/eip/umn/en-us_image_0000001890564529.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001890564529.png differ diff --git a/docs/eip/umn/en-us_image_0000001925251293.png b/docs/eip/umn/en-us_image_0000001925251293.png new file mode 100644 index 00000000..8c885190 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001925251293.png differ diff --git a/docs/eip/umn/en-us_image_0000001925410917.png b/docs/eip/umn/en-us_image_0000001925410917.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001925410917.png differ diff --git a/docs/eip/umn/en-us_image_0000001925495185.png b/docs/eip/umn/en-us_image_0000001925495185.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001925495185.png differ diff --git a/docs/eip/umn/en-us_image_0000001925615569.png b/docs/eip/umn/en-us_image_0000001925615569.png new file mode 100644 index 00000000..1c2c2ef6 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001925615569.png differ diff --git a/docs/eip/umn/en-us_image_0118498829.gif b/docs/eip/umn/en-us_image_0118498829.gif deleted file mode 100644 index ee7d27d1..00000000 Binary files a/docs/eip/umn/en-us_image_0118498829.gif and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0118499137.gif b/docs/eip/umn/en-us_image_0118499137.gif deleted file mode 100644 index 24491f9d..00000000 Binary files a/docs/eip/umn/en-us_image_0118499137.gif and /dev/null differ diff --git a/docs/eip/umn/en-us_image_0233469196.png b/docs/eip/umn/en-us_image_0233469196.png deleted file mode 100644 index a844ced3..00000000 Binary files a/docs/eip/umn/en-us_image_0233469196.png and /dev/null differ diff --git a/docs/eip/umn/en-us_topic_0000001890444789.html b/docs/eip/umn/en-us_topic_0000001890444789.html new file mode 100644 index 00000000..330210ac --- /dev/null +++ b/docs/eip/umn/en-us_topic_0000001890444789.html @@ -0,0 +1,53 @@ + + +What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?
++Table 1 lists the differences between 5_bgp, 5_mailbgp, and 5_gray EIPs.
+ ++
+Table 1 Differences between 5_bgp, 5_mailbgp, and 5_gray EIPs Dimension
+5_bgp EIP
+5_gray EIP
+5_mailbgp EIP
+Application scenario
+Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.
+5_bgp EIPs can be bound to cloud resources except dedicated load balancers.
+5_gray EIPs are no longer supported.
+5_mailbgp EIPs are used together with port 25, 465, or 587 for email services.
+Differences
+- Cannot be used for email services.
- Can be bound to dedicated and shared load balancers.
- Not suggested to be bound to dedicated or shared load balancers by default.
- Cannot be used for email services.
- Cannot be bound to dedicated load balancers.
- Can be used for email services.
Constraints
+The selected EIP type cannot be changed after the EIP is assigned.
+- In eu-de, existing 5_gray EIPs cannot be bound to dedicated or shared load balancers. You can use 5_bgp EIPs instead.
- In eu-de, no more new EIPs of this type can be assigned. You can assign EIPs of the BGP (5_bgp) type.
If you need an EIP of this type, contact the account administrator to grant the required permissions.
+++ diff --git a/docs/eip/umn/faq_bandwidth.html b/docs/eip/umn/faq_bandwidth.html index 87b27222..99ec14c6 100644 --- a/docs/eip/umn/faq_bandwidth.html +++ b/docs/eip/umn/faq_bandwidth.html @@ -8,13 +8,11 @@++Parent topic: Product Consultation+- What Bandwidth Types Are Available?
-
- How Do I Buy a Shared Bandwidth?
-
-- What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth or the Other Way Around?
+- What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth?
- What Are Inbound Bandwidth and Outbound Bandwidth?
-
- What Are the Differences Between EIP Bandwidth and Private Network Bandwidth?
+- What Are the Differences Between Public Bandwidth and Private Bandwidth?
- What Is the Relationship Between Bandwidth and Upload/Download Rate?
diff --git a/docs/eip/umn/faq_bandwidth_0002.html b/docs/eip/umn/faq_bandwidth_0002.html index 7957f5fa..631fc578 100644 --- a/docs/eip/umn/faq_bandwidth_0002.html +++ b/docs/eip/umn/faq_bandwidth_0002.html @@ -1,7 +1,7 @@
What Bandwidth Types Are Available?
-There are dedicated bandwidth and shared bandwidth. A dedicated bandwidth can only be used by one EIP, but a shared bandwidth can be used by multiple EIPs.
+There are dedicated bandwidths and shared bandwidths. A dedicated bandwidth can only be used by one EIP, but a shared bandwidth can be used by multiple EIPs.
diff --git a/docs/eip/umn/faq_bandwidth_0003.html b/docs/eip/umn/faq_bandwidth_0003.html deleted file mode 100644 index c1d2aea5..00000000 --- a/docs/eip/umn/faq_bandwidth_0003.html +++ /dev/null @@ -1,11 +0,0 @@ - - -How Do I Buy a Shared Bandwidth?
--- 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 Shared Bandwidths.
- In the upper right corner, click Assign Shared Bandwidth. On the displayed page, configure parameters as prompted to assign a shared bandwidth.
-- diff --git a/docs/eip/umn/faq_bandwidth_0006.html b/docs/eip/umn/faq_bandwidth_0006.html index a209ecd1..77635f94 100644 --- a/docs/eip/umn/faq_bandwidth_0006.html +++ b/docs/eip/umn/faq_bandwidth_0006.html @@ -1,10 +1,10 @@ ---Parent topic: Bandwidth-What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth or the Other Way Around?
-A dedicated bandwidth can only be used by one EIP. An EIP can only be used by one cloud resource, such as an ECS, a NAT gateway, or a load balancer.
-A shared bandwidth can be shared by multiple EIPs. Adding an EIP to or removing an EIP from a shared bandwidth does not affect your workloads.
-A dedicated bandwidth cannot be changed to a shared bandwidth or the other way around. You can purchase a shared bandwidth for your EIPs.
-- After you add an EIP to a shared bandwidth, the EIP will use the shared bandwidth.
- After you remove an EIP from a shared bandwidth, the EIP will use the dedicated bandwidth.
What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth?
+A dedicated bandwidth can only be used by one EIP that is bound to one cloud resource, such as an ECS, a NAT gateway, or a load balancer.
+A shared bandwidth can be shared by multiple EIPs. Adding an EIP to or removing an EIP from a shared bandwidth does not affect your services.
+A dedicated bandwidth cannot be changed to a shared bandwidth or the other way around. You can purchase a shared bandwidth for your EIPs.
+- After you add an EIP to a shared bandwidth, the EIP will use the shared bandwidth.
- After you remove an EIP from a shared bandwidth, the EIP will use the dedicated bandwidth.
diff --git a/docs/eip/umn/faq_bandwidth_0007.html b/docs/eip/umn/faq_bandwidth_0007.html index 9ebf4ac4..a826ba5b 100644 --- a/docs/eip/umn/faq_bandwidth_0007.html +++ b/docs/eip/umn/faq_bandwidth_0007.html @@ -1,9 +1,30 @@What Are Inbound Bandwidth and Outbound Bandwidth?
-Inbound bandwidth is the bandwidth consumed when data is transferred from the Internet to the cloud. For example, when resources are downloaded from the Internet to ECSs, that consumes inbound bandwidth.
-Outbound bandwidth is the bandwidth consumed when data is transferred from the cloud to the Internet. For example, when ECSs provide services accessible from the Internet and external users download resources from the ECSs, that consumes 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.
Figure 1 Inbound bandwidth and outbound bandwidth+ +
+Table 1 Inbound bandwidth and outbound bandwidth Type
+Description
+Outbound bandwidth
+Bandwidth consumed when data is transferred from cloud to the Internet. For example, the outbound bandwidth is used when ECSs provide services accessible from the Internet and FTP clients download resources from the ECSs.
+ +Inbound bandwidth
+Bandwidth consumed when data is transferred from the Internet to cloud. For example, the inbound bandwidth is used when resources are downloaded from the Internet to ECSs and FTP clients upload resources to the ECSs.
+diff --git a/docs/eip/umn/faq_bandwidth_0009.html b/docs/eip/umn/faq_bandwidth_0009.html index 6d1147bc..cefa0cbb 100644 --- a/docs/eip/umn/faq_bandwidth_0009.html +++ b/docs/eip/umn/faq_bandwidth_0009.html @@ -1,8 +1,13 @@ -What Are the Differences Between EIP Bandwidth and Private Network Bandwidth?
-EIP bandwidths are used by ECSs to access the Internet through EIPs.
-Private bandwidth refers to the bandwidth used by ECSs in VPCs. The private bandwidth and maximum data transfer speed (in PPS) allowed for an ECS are determined based on ECS specifications.
+What Are the Differences Between Public Bandwidth and Private Bandwidth?
+diff --git a/docs/eip/umn/faq_bandwidth_0012.html b/docs/eip/umn/faq_bandwidth_0012.html index f9909d1d..28b6fffd 100644 --- a/docs/eip/umn/faq_bandwidth_0012.html +++ b/docs/eip/umn/faq_bandwidth_0012.html @@ -1,9 +1,9 @@+Public Bandwidth
Public bandwidth is the bandwidth consumed when data is transferred between cloud instances and the Internet. You can configure the public bandwidth when creating an ECS or bind an EIP to an ECS after the ECS is created.
+Public bandwidth is classified into inbound bandwidth and outbound bandwidth.
+Inbound bandwidth is the bandwidth consumed when data is transferred from the Internet to the cloud. For example, when resources are downloaded from the Internet to ECSs, that consumes inbound bandwidth.
+Outbound bandwidth is the bandwidth consumed when data is transferred from the cloud to the Internet. For example, when ECSs provide services accessible from the Internet and external users download resources from the ECSs, that consumes outbound bandwidth.
+Private Bandwidth
Private bandwidth is the bandwidth consumed when data is transferred between ECSs in the same region and on the same private network. ECSs can also be connected to cloud databases, load balancers, and OBS through private bandwidth. The private bandwidth size depends on the instance specifications.
+For details, see ECS Types.
What Is the Relationship Between Bandwidth and Upload/Download Rate?
-The bandwidth is measured in bit/s, but the download rate is measured in byte/s.
+The bandwidth is measured in bit/s, indicating the number of binary bits transmitted per second. The download rate is measured in byte/s, indicating the number of bytes transmitted per second.
1 byte = 8 bits, that is, download rate = bandwidth/8
-Due to various issues such as computer performance, network device quality, resource usage, and network peak hours, if the bandwidth is 1 Mbit/s, the actual upload or download rate is generally lower than 125 kByte/s (1 Mbit/s = 1,000 Kbit/s, upload or download rate = 1,000/8 = 125 kByte/s).
+Due to various issues such as computer performance, network device quality, resource usage, and network peak hours, if the bandwidth is 1 Mbit/s, the actual upload or download rate is generally lower than 125 kByte/s (1 Mbit/s = 1,000 Kbit/s, upload or download rate = 1,000/8 = 125 kByte/s).
diff --git a/docs/eip/umn/faq_common.html b/docs/eip/umn/faq_common.html index 8edbf2be..79c3521c 100644 --- a/docs/eip/umn/faq_common.html +++ b/docs/eip/umn/faq_common.html @@ -20,10 +20,12 @@- Can a Bandwidth Be Used by Multiple Accounts?
-
- How Do I Change an EIP for an Instance?
+- 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?
+
- What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?
+diff --git a/docs/eip/umn/faq_common_0001.html b/docs/eip/umn/faq_common_0001.html index cddd586d..c0d3f8e9 100644 --- a/docs/eip/umn/faq_common_0001.html +++ b/docs/eip/umn/faq_common_0001.html @@ -10,7 +10,7 @@How Do I Apply for a Higher Quota?
The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.
Before dialing the hotline number or sending an email, make sure that the following information has been obtained:
-- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
+- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
- Quota information, which includes:
- Service name
- Quota type
- Required quota
- Domain name, project name, and project ID, which can be obtained by performing the following operations:
- How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
- - Why Can't an EIP Be Pinged?
+ - What Should I Do If an EIP Cannot Be Pinged?
- Why Does the Download Speed of My ECS Is Slow?
diff --git a/docs/eip/umn/faq_connect_0004.html b/docs/eip/umn/faq_connect_0004.html
index dc3ef178..32d53166 100644
--- a/docs/eip/umn/faq_connect_0004.html
+++ b/docs/eip/umn/faq_connect_0004.html
@@ -1,7 +1,7 @@
- - 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.
+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)
Outbound Rules: File and Printer Sharing (Echo Request - ICMPv4-Out)
If IPv6 is enabled, enable the following rules:
@@ -140,7 +140,7 @@
- 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 8137c8f3..e51c0d65 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 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.
- 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 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?
- 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_0009.html b/docs/eip/umn/faq_eip_0009.html index a104bcda..0720a006 100644 --- a/docs/eip/umn/faq_eip_0009.html +++ b/docs/eip/umn/faq_eip_0009.html @@ -1,9 +1,9 @@How Do I Access the Internet Using an EIP Bound to an Extension NIC?
-- After an EIP is bound to an extension NIC, log in to the ECS and use the route command to query the route.
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+
- 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.
+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.diff --git a/docs/eip/umn/faq_eip_0013.html b/docs/eip/umn/faq_eip_0013.html index f463cde2..99cc069c 100644 --- a/docs/eip/umn/faq_eip_0013.html +++ b/docs/eip/umn/faq_eip_0013.html @@ -1,40 +1,40 @@ This operation will interrupt ECS communication. It is recommended that you perform the configuration by following step 4.
What Are the Differences Between EIP, Private IP Address, and Virtual IP Address?
-Different types of IP addresses have different functions.
-Figure 1 IP address architecture+
Different types of IP addresses have different functions.
+Figure 1 IP address architecture-
Table 1 Functions of different IP address types IP Address Type
+Table 1 Functions of different IP address types IP Address Type
Description
+Description
Example Value
+Example Value
Private IP address
+Private IP address
Private IP addresses come with your ECSs and belong to the VPC subnets of the ECSs. They are used for private communication on the cloud.
+Private IP addresses come with your ECSs and belong to the VPC subnets of the ECSs. They are used for private communication on the cloud.
- Private IP address of ECS-A-01: 172.16.0.84
- Private IP address of ECS-B-01: 172.16.1.12
- Private IP address of ECS-A-01: 172.16.0.84
- Private IP address of ECS-B-01: 172.16.1.12
Virtual IP address
+Virtual IP address
A virtual IP address can be shared among multiple ECSs. Two ECSs can work as an active and standby pair to achieve high availability by using a virtual IP address and Keepalived. If the active ECS is faulty, the virtual IP address can be dynamically switched to the standby ECS to continue providing services.
- - -For more information about virtual IP addresses, see Virtual IP Address Overview.
+A virtual IP address can be shared among multiple ECSs. Two ECSs can work as an active and standby pair to achieve high availability by using a virtual IP address and Keepalived. If the active ECS is faulty, the virtual IP address can be dynamically switched to the standby ECS to continue providing services.
+ + +For more information about virtual IP addresses, see Virtual IP Address Overview.
Bind virtual IP address (172.16.0.2) both ECS-A-01 and ECS-A-02. The active/standby switchover of ECS-A-01 and ECS-A-02 can be implemented by using Keepalived.
+Bind virtual IP address (172.16.0.2) both ECS-A-01 and ECS-A-02. The active/standby switchover of ECS-A-01 and ECS-A-02 can be implemented by using Keepalived.
EIP
+EIP
EIPs can be used by cloud resources for Internet access.
-- You can bind an EIP to a virtual IP address to enable the ECSs with the virtual IP address bound to access the Internet.
- You can bind an EIP to an ECS to enable the ECS to access the Internet. Each EIP can be bound to only one ECS at a time.
EIPs can be used by cloud resources for Internet access.
+- You can bind an EIP to a virtual IP address to enable the ECSs with the virtual IP address bound to access the Internet.
- You can bind an EIP to the ECSs to enable them to access the Internet. Each EIP can be bound to only one ECS.
- Bind EIP (122.9.9.85) to virtual IP address (172.16.0.2) to enable ECS-A-01 and ECS-A-02 to access the Internet.
- Bind EIP (122.9.9.87) to ECS-B-01 to enable ECS-B-01 to access the Internet.
- Bind EIP (122.9.9.85) to virtual IP address (172.16.0.2) to enable ECS-A-01 and ECS-A-02 to access the Internet.
- Bind EIP (122.9.9.87) to ECS-B-01 to enable ECS-B-01 to access the Internet.
What Is the EIP Assignment Policy?
+What Is the EIP Assignment Policy?
By default, EIPs are assigned randomly.
If an EIP is released by mistake, the system will preferentially assign you an EIP that you have released in the last 24 hours.
If you want a specific EIP that you released more than 24 hours ago, see How Do I Assign or Retrieve a Specific EIP?
diff --git a/docs/eip/umn/faq_eip_0020.html b/docs/eip/umn/faq_eip_0020.html index f27a0a1a..551ac2f6 100644 --- a/docs/eip/umn/faq_eip_0020.html +++ b/docs/eip/umn/faq_eip_0020.html @@ -1,12 +1,16 @@ -How Do I Change an EIP for an Instance?
-diff --git a/docs/eip/umn/monitor_0003.html b/docs/eip/umn/monitor_0003.html index e83e178f..6467f9f0 100644 --- a/docs/eip/umn/monitor_0003.html +++ b/docs/eip/umn/monitor_0003.html @@ -4,9 +4,9 @@Scenario 1: Changing an EIP for an ECS
Refer to Assigning an EIP and Binding It to an ECS and Unbinding an EIP from an ECS and Releasing the EIP.
+How Do I Unbind an EIP from an Instance and Bind a New EIP to the Instance?
+-Scenario 1: Unbinding an EIP from an ECS and Binding a New EIP to the ECS
For details, see Assigning an EIP and Binding It to an ECS and Unbinding an EIP from an ECS and Releasing the EIP.
diff --git a/docs/eip/umn/faq_eip_0022.html b/docs/eip/umn/faq_eip_0022.html index 3323b8a1..01ddea92 100644 --- a/docs/eip/umn/faq_eip_0022.html +++ b/docs/eip/umn/faq_eip_0022.html @@ -51,7 +51,7 @@Scenario 2: Changing an EIP for a Load Balancer
- Unbind an EIP.
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click Service List. Under Networking, click Elastic Load Balance.
- In the load balancer list, locate the target load balancer and choose More > Unbind EIP in the Operation column.
- Click Yes.
- Assign 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.
- Click Create Now.
- Bind the new EIP to the load balancer.
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click Service List. Under Networking, click Elastic Load Balance.
- In the load balancer list, locate the target load balancer and choose More > Bind EIP in the Operation column.
- In the Bind EIP dialog box, select the EIP to be bound and click OK.
- Release the EIP that has been replaced.
- 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 EIP list, locate the row that contains the target EIP, and click Release.
- Click Yes.
Scenario 2: Unbinding an EIP from a Load Balancer and Binding a New EIP to the Load Balancer
- Unbind an EIP.
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click Service List. Under Network, click Elastic Load Balancing.
- In the load balancer list, locate the target load balancer and choose More > Unbind IPv4 EIP in the Operation column.
- Click Yes.
- Assign an EIP.+
If you already have an EIP that you require, skip this step.
+- 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.
- Click Create Now.
- Bind the new EIP to the load balancer.
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click Service List. Under Network, click Elastic Load Balancing.
- In the load balancer list, locate the target load balancer and choose More > Bind IPv4 EIP in the Operation column.
- In the Bind IPv4 EIP dialog box, select the EIP to be bound and click OK.
- Release the EIP that is unbound.+
If an unbound EIP is no longer required, you can release it.
+- 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 EIP list, locate the target EIP and click Release.
- Click Yes.
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.
-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, search for the EIP, click More in the Operation column, and click View Metric to view the monitoring metric details.
- 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.
- Hover on the upper left corner to display 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.
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.
diff --git a/docs/eip/umn/monitor_0004.html b/docs/eip/umn/monitor_0004.html index 8289a711..495a62a0 100644 --- a/docs/eip/umn/monitor_0004.html +++ b/docs/eip/umn/monitor_0004.html @@ -3,8 +3,8 @@Creating 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.
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 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 the Cloud Eye User Guide.
+diff --git a/docs/eip/umn/monitor_0005.html b/docs/eip/umn/monitor_0005.html index 7bd5c705..d434f628 100644 --- a/docs/eip/umn/monitor_0005.html +++ b/docs/eip/umn/monitor_0005.html @@ -4,8 +4,8 @@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.
+
diff --git a/docs/eip/umn/overview_0001.html b/docs/eip/umn/overview_0001.html index 368d0c56..817660bc 100644 --- a/docs/eip/umn/overview_0001.html +++ b/docs/eip/umn/overview_0001.html @@ -3,7 +3,7 @@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.
- The first row in the exported monitoring report 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:
- Use Excel to open a .csv file.
- Use the following formula to convert the time:
Target time = [Unix timestamp/1000 + (Target time zone) x 3600]/86400 + 70 x 365 + 19
- - Set cell format to Date.
- 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:
What Is Elastic IP?
The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. If a resource has an EIP bound, it can directly access the Internet. If a resource only has a private IP address, it cannot directly access the Internet. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.
Each EIP can be bound to only one cloud resource and they must be in the same region.
-Figure 1 Connecting to the Internet using an EIP+Figure 1 Connecting to the Internet using an EIPdiff --git a/docs/eip/umn/overview_0003.html b/docs/eip/umn/overview_0003.html index 0a44f86d..2beb8ca3 100644 --- a/docs/eip/umn/overview_0003.html +++ b/docs/eip/umn/overview_0003.html @@ -1,11 +1,11 @@Notes and Constraints
-EIP
-- Each EIP can only be bound to one cloud resource.
- An EIP that has already been bound to a cloud resource cannot be bound to another resource without first being unbound from the current resource.
- You can only release unbound EIPs.
- The system preferentially assigns EIPs to you from the ones you released, if any. However, if any of these EIPs is already assigned to another user, it cannot be re-assigned to you.
- EIPs cannot be transferred across accounts.
-EIP
Note the following when using EIPs:
+- Each EIP can only be bound to one cloud resource.
- An EIP that has already been bound to a cloud resource cannot be bound to another resource without first being unbound from the current resource.
- EIPs cannot be transferred across accounts.
- You can only release unbound EIPs.
- The system preferentially assigns EIPs to you from the ones you released, if any. However, if any of these EIPs is already assigned to another user, it cannot be re-assigned to you.
Bandwidth
-- A dedicated bandwidth can control how much data can be transferred using a single EIP.
- A shared bandwidth cannot control how much data can be transferred using a single EIP. Data transfer rate on EIPs cannot be customized.
- A shared bandwidth or dedicated bandwidth can only be used by resources owned by the same account.
diff --git a/docs/eip/umn/overview_0004.html b/docs/eip/umn/overview_0004.html index 10ee4f29..8d7b0ced 100644 --- a/docs/eip/umn/overview_0004.html +++ b/docs/eip/umn/overview_0004.html @@ -13,20 +13,20 @@Bandwidth
- A dedicated bandwidth can control how much data can be transferred using a single EIP.
- A shared bandwidth cannot control how much data can be transferred using a single EIP. Data transfer rate on EIPs cannot be customized.
- A shared bandwidth or dedicated bandwidth can only be used by resources owned by the same account.
- Inbound bandwidth is the bandwidth consumed when data is transferred from the Internet to the cloud. Outbound bandwidth is the bandwidth consumed when data is transferred from the cloud to the Internet.
Bind an EIP to a server to allow the server to access the Internet.
Elastic Cloud Server (ECS)
-BMS
+Bare Metal Server (BMS)
Bind a virtual IP address to an EIP so that you can access the ECSs deployed in active/standby mode through the virtual IP address.
+Bind a virtual IP address to an EIP so that you can access the ECSs deployed in active/standby mode through the virtual IP address.
Virtual Private Cloud (VPC)
Configure ECSs to share one or more EIPs through a NAT gateway to access the Internet.
+Configure ECSs to share one or more EIPs through a NAT gateway to access the Internet.
NAT Gateway
diff --git a/docs/eip/umn/overview_0006.html b/docs/eip/umn/overview_0006.html index 2509d66d..90b958c1 100644 --- a/docs/eip/umn/overview_0006.html +++ b/docs/eip/umn/overview_0006.html @@ -4,7 +4,7 @@Binding an EIP to an ECS
Scenario
You can bind an EIP to an ECS to enable the ECS to access the Internet.
Related Services
-ECS, BMS, or VPCFigure 1 Binding an EIP to a server+
ECS, BMS, or VPCFigure 1 Binding an EIP to a server
Binding an EIP to a NAT Gateway
Scenario
@@ -12,14 +12,14 @@An SNAT rule allows servers in a specific VPC subnet to use the same EIP to access the Internet.
A DNAT rule enables servers in a VPC to provide services accessible from the Internet.
Related Services
-NAT Gateway, Cloud server (ECS and BMS), and VPC
-Figure 2 EIP used by a NAT gateway+
NAT Gateway, cloud server (ECS and BMSs), and VPC
+Figure 2 EIP used by a NAT gateway
Binding an EIP to a Load Balancer
Scenario
After you attach an EIP to a load balancer, the load balancer can distribute requests from the Internet to backend servers.
Related Services
ELB, ECS, and VPC
-Figure 3 EIP used by a load balancer+
Figure 3 EIP used by a load balancer
diff --git a/docs/eip/umn/overview_permission.html b/docs/eip/umn/overview_permission.html index 21c4d410..4ea733c7 100644 --- a/docs/eip/umn/overview_permission.html +++ b/docs/eip/umn/overview_permission.html @@ -1,13 +1,13 @@Permissions
-If you need to assign different permissions to employees in your enterprise to access your EIP resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you securely manage access to your resources.
-With IAM, you can use your to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use EIP resources but should not be allowed to delete them or perform any high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using EIP resources.
-If your does not need individual IAM users for permissions management, you may skip over this section.
+If you need to assign different permissions to employees in your enterprise to access your EIP resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you securely manage access to your cloud resources.
+With IAM, you can use your cloud account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use EIP resources but should not be allowed to delete them or perform any high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using EIP resources.
+If your cloud account does not need individual IAM users for permissions management, you may skip over this section.
IAM can be used free of charge. You pay only for the resources in your account. For more information, see IAM Service Overview.
EIP Permissions
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
Currently, EIP permissions are included in VPC permissions.
-VPC is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions , the users only have permissions for VPCs in the selected projects. If you set Scope to All resources, users have permissions for VPCs in all region-specific projects. When accessing VPCs, the users need to switch to the authorized region.
+VPC is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for VPCs in the selected projects. If you set Scope to All resources, users have permissions for VPCs in all region-specific projects. When accessing VPCs, the users need to switch to the authorized region.
You can grant permissions by using roles and policies.
- Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. When you grant permissions using roles, you also need to attach dependent roles. Roles are not ideal for fine-grained authorization and least privilege access.
- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant VPC users only the permissions for managing a certain type of resources. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by VPC, see Permissions Policies and Supported Actions.
Table 1 lists all the system-defined roles and policies supported by VPC.
diff --git a/docs/eip/umn/permission_0003.html b/docs/eip/umn/permission_0003.html index 3d3b7283..0478ccf7 100644 --- a/docs/eip/umn/permission_0003.html +++ b/docs/eip/umn/permission_0003.html @@ -2,19 +2,19 @@Creating a User and Granting EIP Permissions
Currently, the EIP service permissions are included in the VPC permissions. For details, see Permissions Management.
-This section describes how to use IAM to implement fine-grained permissions control for your VPC resources. With IAM, you can:- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing VPC resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Entrust a cloud account or cloud service to perform efficient O&M on your VPC resources.
This section describes how to use IAM to implement fine-grained permissions control for your VPC resources. With IAM, you can:- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing VPC resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Entrust a cloud account or cloud service to perform efficient O&M on your VPC resources.
If your cloud account meets your permissions requirements, you can skip this section.
Figure 1 shows the process flow for granting permissions.
-Prerequisites
Before granting permissions to user groups, learn about EIP Permissions for EIP.
+-Prerequisites
Before granting permissions to user groups, learn about EIP Permissions.
To grant permissions for other services, learn about all permissions supported by IAM.
Process Flow
+Process Flow
-On the IAM console, create a user group and grant it permissions (EIP ReadOnlyAccess as an example).
+On the IAM console, create a user group and grant it permissions (VPC ReadOnlyAccess as an example).
- Log in as the IAM user and verify permissions.
In the authorized region, perform the following operations:
-- Choose Service List > Elastic IP. Then click Buy EIP on the EIP console. If a message appears indicating that you have insufficient permissions to perform the operation, the EIPReadOnlyAccess policy is in effect.
- Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the EIPReadOnlyAccess policy is in effect.
- Choose Service List > Elastic IP and click Assign EIP in the upper right corner. If a message appears indicating that you have insufficient permissions to perform the operation, the VPC ReadOnlyAccess policy is in effect.
- Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the VPC ReadOnlyAccess policy is in effect.
Example Custom Policies
- Example 1: Grant permissions to assign and view EIPs
{ @@ -24,7 +24,7 @@ "Effect": "Allow", "Action": [ " - vpc:publicIps:create + vpc:publicIps:create, vpc:publicIps:list " ] @@ -32,7 +32,7 @@ ] } - Example 2: Grant permission to deny EIP deletion.
A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
-Assume that you want to grant the permissions of the VPC FullAccess policy to a user but want to prevent them from releasing EIPs. You can create a custom policy for denying EIP release, and attach both policies to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on EIPs except releasing them. Example policy denying EIP release:
+Assume that you want to grant the permissions of the VPC FullAccess policy to a user but want to prevent them from releasing EIPs. You can create a custom policy for denying EIP release, and attach both policies to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on EIPs except releasing them. Example policy denying EIP release:
{ "Version": "1.1", "Statement": [ @@ -53,7 +53,6 @@ { "Effect": "Allow", "Action": [ - "ecs:servers:delete", "vpc:publicIps:update", "vpc:publicIps:create" ] diff --git a/docs/eip/umn/permission_0004.html b/docs/eip/umn/permission_0004.html index c4bd1790..44a2ee1e 100644 --- a/docs/eip/umn/permission_0004.html +++ b/docs/eip/umn/permission_0004.html @@ -1,9 +1,9 @@EIP Custom Policies
-Custom policies can be created as a supplement to the system policies of EIP. For the actions supported for custom policies, see Permissions Policies and Supported Actions.
+Custom policies can be created as a supplement to the system policies of EIP. For the actions supported for custom policies, see Permissions Policies and Supported Actions.
You can create custom policies in either of the following ways:
-- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
For details, see Creating a Custom Policy. The following section contains examples of common EIP custom policies.
+- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
For details, see Creating a Custom Policy. The following section contains examples of common EIP custom policies.
Example Custom Policies
- Example 1: Grant permissions to assign and view EIPs
{ "Version": "1.1", @@ -12,7 +12,7 @@ "Effect": "Allow", "Action": [ " - vpc:publicIps:create + vpc:publicIps:create, vpc:publicIps:list " ] @@ -20,7 +20,7 @@ ] } - Example 2: Grant permission to deny EIP deletion.
A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
-Assume that you want to grant the permissions of the VPC FullAccess policy to a user but want to prevent them from releasing EIPs. You can create a custom policy for denying EIP release, and attach both policies to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on EIPs except releasing them. Example policy denying EIP release:
+Assume that you want to grant the permissions of the VPC FullAccess policy to a user but want to prevent them from releasing EIPs. You can create a custom policy for denying EIP release, and attach both policies to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on EIPs except releasing them. Example policy denying EIP release:
{ "Version": "1.1", "Statement": [ @@ -41,7 +41,6 @@ { "Effect": "Allow", "Action": [ - "ecs:servers:delete", "vpc:publicIps:update", "vpc:publicIps:create" ] diff --git a/docs/eip/umn/qsg_0002.html b/docs/eip/umn/qsg_0002.html index f8f5c403..985523fa 100644 --- a/docs/eip/umn/qsg_0002.html +++ b/docs/eip/umn/qsg_0002.html @@ -1,46 +1,46 @@Overview
-If your ECSs need to access the Internet (for example, the ECSs functioning as the service nodes for deploying a website), you can follow the procedure shown in Figure 1 to bind EIPs to the ECSs.
- -Table 1 describes the different tasks in the procedure for configuring the network.
+If your ECSs need to access the Internet (for example, the ECSs functioning as the service nodes for deploying a website), you can follow the procedure shown in Figure 1 to bind EIPs to the ECSs.
+ +Table 1 describes the different tasks in the procedure for configuring the network.
-Table 1 Configuration process description Task
+Table 1 Configuration process description Task
Description
+Description
Create a VPC.
+Create a VPC.
This task is mandatory.
-A created VPC comes with a default subnet you specified.
-After the VPC is created, you can create other required network resources in the VPC based on your service requirements.
+This task is mandatory.
+A created VPC comes with a default subnet you specified.
+After the VPC is created, you can create other required network resources in the VPC based on your service requirements.
Create another subnet for the VPC.
+Create another subnet for the VPC.
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.
+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.
Assign an EIP and bind it to an ECS.
+Assign an EIP and bind it to an ECS.
This task is mandatory.
-You can assign an EIP and bind it to an ECS for Internet access.
+This task is mandatory.
+You can assign an EIP and bind it to an ECS for Internet access.
Create a security group.
+Create a security group.
This task is mandatory.
-You can create a security group and add ECSs in the VPC to the security group to improve ECS access security. After a security group is created, it has default rules, which allow all outgoing data packets. ECSs in a security group can access each other without the need to add rules.
+This task is mandatory.
+You can create a security group and add ECSs in the VPC to the security group to improve ECS access security. After a security group is created, it has default rules, which allow all outgoing data packets. ECSs in a security group can access each other without the need to add rules.
Add a security group rule.
+Add a security group rule.
This task is optional.
-If the default rule does not meet your service requirements, you can add security group rules.
+This task is optional.
+If the default rule does not meet your service requirements, you can add security group rules.
Step 1: Create a VPC
-Scenarios
A VPC provides an isolated virtual network for ECSs. You can configure and manage the network as required.
-You can create a VPC by following the procedure provided in this section. Then, create subnets, security groups, and assign EIPs by following the procedure provided in subsequent sections based on your actual network requirements.
+-Scenarios
A VPC provides an isolated virtual network for ECSs. You can configure and manage the network as required.
+You can create a VPC by following the procedure provided in this section. Then, create subnets, security groups, and assign EIPs by following the procedure provided in subsequent sections based on your actual network requirements.
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. - 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.
+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-
Table 1 VPC parameter descriptions Category
+-Table 1 VPC parameter descriptions Category
Parameter
+Parameter
Description
+Description
Example Value
+Example Value
Basic Information
+Basic Information
Region
+Region
Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you.
+Select the region nearest to you to ensure the lowest latency possible.
eu-de
+eu-de
Basic Information
+Basic Information
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 may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
VPC-001
+VPC-001
Basic Information
+Basic Information
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 following CIDR blocks are supported:
-10.0.0.0/8-24
-172.16.0.0/12-24
-192.168.0.0/16-24
+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
+Basic Information
Enterprise Project
+Enterprise Project
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.
+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
+Basic Information/Advanced Settings
Tag
+Tag
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.
+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
+Basic Information/Advanced Settings
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 >).
+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 >).
N/A
+N/A
Default Subnet
+Default Subnet
Name
+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 may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
Subnet
+Subnet
Default Subnet
+Default Subnet
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
+Default Subnet
Associated Route Table
+IPv6 CIDR Block
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.
+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
+-
Default Subnet/Advanced Settings
+Default Subnet
Gateway
+Associated Route Table
The gateway address of the subnet.
+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.
192.168.0.1
+Default
Default Subnet/Advanced Settings
+Default Subnet/Advanced Settings
DNS Server Address
+Gateway
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 (,).
+The gateway address of the subnet.
100.125.x.x
+192.168.0.1
Default Subnet/Advanced Settings
+Default Subnet/Advanced Settings
NTP Server Address
+DNS 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 this parameter is left empty, no IP address of the NTP server is added.
-A maximum of four IP 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 (,).
192.168.2.1
+100.125.x.x
Default Subnet/Advanced Settings
+Default Subnet/Advanced Settings
Tag
+NTP Server Address
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.
+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 (,).
- Key: subnet_key1
- Value: subnet-01
192.168.2.1
Default Subnet/Advanced Settings
+Default Subnet/Advanced Settings
Description
+Tag
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 >).
+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.
N/A
+- Key: subnet_key1
- Value: subnet-01
Default Subnet/Advanced Settings
+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 >).
+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
- Special characters, including hyphens (-) and underscores (_)
- 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.
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
subnet-01
+subnet-01
- Click Create Now.
+- Click Create Now.
diff --git a/docs/eip/umn/qsg_0004.html b/docs/eip/umn/qsg_0004.html index 8ecaa815..6338e77e 100644 --- a/docs/eip/umn/qsg_0004.html +++ b/docs/eip/umn/qsg_0004.html @@ -1,126 +1,136 @@Step 2: Create a Subnet for the VPC
-Scenarios
A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.
-A subnet is configured with DHCP by default. When an ECS in this subnet starts, the ECS automatically obtains an IP address using DHCP.
+-Scenarios
A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.
+A subnet is configured with DHCP by default. When an ECS in this subnet starts, the ECS automatically obtains an IP address using DHCP.
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. - 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 Create Subnet- +
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-
Table 1 Parameter descriptions Parameter
+-Table 1 Parameter descriptions Parameter
Description
+Description
Example Value
+Example Value
VPC
+VPC
The VPC for which you want to create a subnet.
+The VPC for which you want to create a subnet.
-
+-
Name
+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 may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
Subnet
+Subnet
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.
+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
Associated Route Table
+IPv6 CIDR Block
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.
+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.
Default
+-
Advanced Settings/Gateway
- +Associated Route Table
The gateway address of the subnet.
+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.
192.168.0.1
+Default
Advanced Settings/DNS Server Address
+Advanced Settings/Gateway
+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 (,).
+The gateway address of the subnet.
100.125.x.x
+192.168.0.1
Advanced Settings/NTP Server Address
+Advanced Settings/DNS 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 this parameter is left empty, no IP address of the NTP server is added.
-A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).
+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 (,).
192.168.2.1
+100.125.x.x
Advanced Settings/Tag
+Advanced Settings/NTP Server Address
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.
+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 (,).
- Key: subnet_key1
- Value: subnet-01
192.168.2.1
Advanced Settings/Description
+Advanced Settings/Tag
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 >).
+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
Advanced Settings/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 >).
+-
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
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
- Special characters, including hyphens (-) and underscores (_)
- 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.
subnet-01
+subnet-01
- Click OK.
+- Click OK.
-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.
If you configured the default settings under Advanced Settings during subnet creation, the reserved IP addresses may be different from the default ones, but there will still be five of them. The specific addresses depend on your subnet settings.
+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.
If you configured the default settings under Advanced Settings during subnet creation, the reserved IP addresses may be different from the default ones, but there will still be five of them. The specific addresses depend on your subnet settings.
diff --git a/docs/eip/umn/qsg_0005.html b/docs/eip/umn/qsg_0005.html index f0e7b34e..d95c4d71 100644 --- a/docs/eip/umn/qsg_0005.html +++ b/docs/eip/umn/qsg_0005.html @@ -1,128 +1,129 @@Step 3: Assign an EIP and Bind It to an ECS
-Scenarios
You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.
- Note the following when you use EIPs of the Dedicated Load Balancer (5_gray) type:- In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
- Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- 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.
-Scenarios
You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.
+ Note the following when you use EIPs of the Dedicated Load Balancer (5_gray) type:- In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
- Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
- The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
- You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
- EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
- You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
- 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 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
+-Table 1 Parameter descriptions Parameter
Description
+Description
Example Value
+Example Value
Region
+Region
Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. The region selected for the EIP is its geographical location.
+Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. The region selected for the EIP is its geographical location.
eu-de
+eu-de
EIP Type
+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.
The selected EIP type cannot be changed after the EIP is assigned.
+- 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
+Dynamic BGP
Billed By
+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.
Two options are available:
+- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
Dedicated
+Dedicated
Bandwidth
+Bandwidth
The bandwidth size in Mbit/s.
+The bandwidth size in Mbit/s.
100
+100
EIP Name
+EIP Name
The EIP name.
+The EIP name.
eip-test
+eip-test
Enterprise Project
+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.
+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.
default
+default
Bandwidth Name
+Bandwidth Name
The name of the bandwidth.
+The name of the bandwidth.
bandwidth
+bandwidth
Tag
+Tag
The EIP tags. Each tag contains a key and value pair.
-The tag key and value must meet the requirements listed in Table 2.
+The EIP tags. Each tag contains a key and value pair.
+The tag key and value must meet the requirements listed in Table 2.
- Key: Ipv4_key1
- Value: 3005eip
- Key: Ipv4_key1
- Value: 3005eip
Quantity
+Quantity
The number of EIPs you want to assign.
+The number of EIPs you want to assign.
1
+1
- Run the following command to delete the default route of the primary NIC:
- After an EIP is bound to an extension NIC, log in to the ECS and use the route command to query the routes.
- Use another ECS in the same region to check whether the local network is functional.
Why Can't an EIP Be Pinged?
-Symptom
After you purchase an EIP and bind it to an ECS, the EIP cannot be pinged on a local server or other cloud servers.
+What Should I Do If an EIP Cannot Be Pinged?
+-Symptom
After you purchase an EIP and bind it to an ECS, the local host or other cloud servers cannot ping the EIP of the ECS.
-Fault Locating
The following fault causes are sequenced based on their occurrence probability.
If the fault persists after you have ruled out a cause, check other causes.
@@ -111,7 +111,7 @@iptables -A OUTPUT -p icmp --icmp-type echo-reply -j ACCEPT
WindowsChecking Whether the Network Is Functional
