Shared bandwidth allows multiple EIPs to share the same bandwidth. 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 an independent 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.
+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 to a shared bandwidth or remove them from a shared bandwidth regardless of the instances to which they are bound.
+ - 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.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, under Network, click 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.
+
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
@@ -23,23 +23,31 @@Bandwidth
The bandwidth size in Mbit/s. The value ranges from starting with 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
Bandwidth Name
+Name
The name of the shared bandwidth.
Bandwidth-001
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.
+default
+ - Click Create Now.
- Click Assign Now.
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.
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 and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
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.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- On the console homepage, under Network, click 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 to which you want to add EIPs. In the Operation column, choose More > Add EIP, and select the EIPs to be added.Figure 1 Add 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 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.
Figure 1 Add EIP+ - Click OK.
Removing EIPs from a Shared Bandwidth
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.
- On the console homepage, under Network, click 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+
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.
Modifying a Shared Bandwidth
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.
- On the console homepage, under Network, click Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the row that contains the shared bandwidth you want to modify, click Modify Bandwidth in the Operation column, and modify the bandwidth settings.Figure 1 Modify Bandwidth+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Elastic IP.
- In the navigation pane on the left, choose 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.
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.
- On the console homepage, under Network, click 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 Yes.
EIP
+Elastic IP
-
+
- EIP Overview
+ - Assigning an EIP and Binding It to an ECS
- Unbinding an EIP from an ECS and Releasing the EIP
- Modifying an EIP Bandwidth
+ - Exporting EIP Information
+ - Managing EIP Tags
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.
- - In the eu-de region, if you choose to assign an EIP when you create a dedicated load balancer on the management console or using APIs, EIPs for dedicated load balancers (5_gray) will be assigned.
- Do not bind EIPs of this type to non-dedicated load balancers.
- Do not add EIPs of the dedicated load balancer type and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
- 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.
- On the console homepage, under Network, click 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.
+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.
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
Bandwidth
+Billed By
The bandwidth size in Mbit/s.
+Two options are available:
+- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
100
+Dedicated
Bandwidth Name
+Bandwidth
The name of the bandwidth.
+The bandwidth size in Mbit/s.
bandwidth
+100
Tag
+EIP Name
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 name.
- Key: Ipv4_key1
- Value: 192.168.12.10
eip-test
Quantity
+Enterprise Project
The number of EIPs you want to purchase.
+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.
1
+default
+Bandwidth Name
+The name of the bandwidth.
+bandwidth
+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.
+- Key: Ipv4_key1
- Value: 3005eip
Quantity
+The number of EIPs you want to assign.
+1
- 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 (_)
192.168.12.10
+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 to which you want to bind the EIP.Figure 2 Bind EIP+
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 about the implementation and constraints, see How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
+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 -a EIP
- nslookup [-qt=ptr] EIP
- dig -x EIP
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
diff --git a/docs/eip/umn/eip_0003.html b/docs/eip/umn/eip_0003.html index 84afad453..e1e23b800 100644 --- a/docs/eip/umn/eip_0003.html +++ b/docs/eip/umn/eip_0003.html @@ -3,21 +3,22 @@-Parent topic: EIP+Parent topic: Elastic IPUnbinding 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.
Notes and Constraints
- EIP assigned together with your load balancers will also be displayed in the EIP list on the VPC console. On the EIP console or using EIP APIs, you cannot bind EIPs to or unbind them from dedicated load balancers, but you can bind EIPs to or unbind them from shared load balancers.
- 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.
- You can only release EIPs that are not bound to any resources.
Procedure
Unbinding a single EIP
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- On the console homepage, under Network, click 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.
- On the console homepage, under Network, click 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.
- 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.
Unbinding multiple EIPs at once
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- On the console homepage, under Network, click 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.
- 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.
- On the console homepage, under Network, click 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.
- 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 aa07c5aab..953700237 100644 --- a/docs/eip/umn/eip_0004.html +++ b/docs/eip/umn/eip_0004.html @@ -26,18 +26,17 @@-Parent topic: EIP+Parent topic: Elastic IP- 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 (_)
192.168.12.10
+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.
- On the console homepage, under Network, click Elastic IP.
- In the upper right corner of the EIP list, click Search by Tag.
- In the displayed area, enter the tag key and value of the EIP you are looking for.
You must specify both the tag key and value. The system will display the EIPs that contain the tag you specified.
- - Click + to add another 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 contain all of the tags you specified.
- - Click Search.
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.
- 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.
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.
- On the console homepage, under Network, click 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.
+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.
@@ -49,7 +48,7 @@
- View tags.
diff --git a/docs/eip/umn/eip_0005.html b/docs/eip/umn/eip_0005.html index bccc8f2e6..5bade26ce 100644 --- a/docs/eip/umn/eip_0005.html +++ b/docs/eip/umn/eip_0005.html @@ -5,13 +5,13 @@-Parent topic: EIP+Parent topic: Elastic IP 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.
- View tags.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- On the console homepage, under Network, click 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.
+
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 new file mode 100644 index 000000000..34f0d2a57 --- /dev/null +++ b/docs/eip/umn/eip_0007.html @@ -0,0 +1,14 @@ + + +-Parent topic: EIP+Parent topic: Elastic IPEIP 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+
++ diff --git a/docs/eip/umn/eip_0015.html b/docs/eip/umn/eip_0015.html new file mode 100644 index 000000000..840d491f8 --- /dev/null +++ b/docs/eip/umn/eip_0015.html @@ -0,0 +1,15 @@ + + +++Parent topic: Elastic IP+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.
++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.
+
++ diff --git a/docs/eip/umn/eip_feature.html b/docs/eip/umn/eip_feature.html new file mode 100644 index 000000000..970a6fcdf --- /dev/null +++ b/docs/eip/umn/eip_feature.html @@ -0,0 +1,50 @@ + + +++Parent topic: Elastic IP+Functions
++Table 1 lists the common functions of EIP.
+ ++
+Table 1 Common EIP functions Category
+Function
+Description
+EIP and Bandwidth
+ + + +EIP
+The EIP service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths.
+You can assign EIPs, bind them to or unbind them from cloud resources, release EIPs, and modify EIP bandwidth.
+For details, see EIP Overview.
+Shared Bandwidth
+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.
+Monitoring
+Viewing Metrics
+If you have subscribed to the VPC service, you can view bandwidth and EIP usage through Cloud Eye without adding plug-ins. On Cloud Eye, you can also create alarm rules, and customize monitored resources and notification policies.
+For details, see Supported Metrics.
+++ diff --git a/docs/eip/umn/eip_his_0003.html b/docs/eip/umn/eip_his_0003.html index d486bc277..22e7ad02b 100644 --- a/docs/eip/umn/eip_his_0003.html +++ b/docs/eip/umn/eip_his_0003.html @@ -8,7 +8,87 @@ -++Parent topic: Service Overview+2022-06-25
+2023-08-01
+This release incorporates the following changes:
+Updated the following content:
+Modified notes and constraints in Adding EIPs to a Shared Bandwidth.
+2023-06-12
+This release incorporates the following changes:
+Updated the following content:
+Added description about viewing monitoring metrics in Viewing Metrics.
+2023-06-06
+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?.
+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?.
+2023-03-28
+This release incorporates the following changes:
+Added the following sections:
+ +2023-02-09
+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?
+Added the following content:
+ +2023-01-12
+This release incorporates the following change:
+Updated the following content:
+Modified steps in Elastic IP.
+2022-12-12
+This release incorporates the following changes:
+Updated the following content:
+Added description that EIPs of the Dedicated Load Balancer (5_gray) type cannot be created in Step 3: Assign an EIP and Bind It to an ECS, Assigning an EIP and Binding It to an ECS, and Unbinding an EIP from an ECS and Releasing the EIP.
+2022-11-15
+This release incorporates the following changes:
+Modified the following content:
+Added support for binding and unbinding EIPs of the Dedicated Load Balancer (5_gray) type using APIs in Step 3: Assign an EIP and Bind It to an ECS, Assigning an EIP and Binding It to an ECS, and Unbinding an EIP from an ECS and Releasing the EIP.
+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?
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.
2022-06-25
Added the following content:
- Modified constraints on EIPs dedicated for dedicated load balancers in Assigning an EIP and Binding It to an ECS.
- Modified constraints on EIP binding to or unbinding from different types of load balancers in Unbinding an EIP from an ECS and Releasing the EIP.
2020-12-16
This release incorporates the following changes:
-- Added description about enabling ports 465 and 587 for Mail BGP EIPs in section Assigning an EIP and Binding It to an ECS.
- Added FAQ Can I Bind Multiple EIPs to an ECS?
- Deleted FAQ "What Are EIPs?"
- Changed the structure of "FAQs".
- Updated the screenshots in sections Step 3: Assign an EIP and Bind It to an ECS, Assigning an EIP and Binding It to an ECS, and Assigning a Shared Bandwidth.
- Modified phrases to or added phrase Notes and Constraints.
- Changed the maximum number of tags that can be added to 20 in section Managing EIP Tags.
- Added description about enabling ports 465 and 587 for Mail BGP EIPs in section Assigning an EIP and Binding It to an ECS.
- Added Can Multiple EIPs Be Bound to an ECS?
- Deleted FAQ "What Are EIPs?"
- Changed the structure of "FAQs".
- Updated the screenshots in sections Step 3: Assign an EIP and Bind It to an ECS, Assigning an EIP and Binding It to an ECS, and Assigning a Shared Bandwidth.
- Modified phrases to or added phrase Notes and Constraints.
- Changed the maximum number of tags that can be added to 20 in section Managing EIP Tags.
2020-03-20
@@ -55,7 +135,7 @@Added the following content:
- Added section Shared Bandwidth.
Modified the following content:
-- Modified the steps in EIP.
- Modified steps in Elastic IP.
2020-01-08
diff --git a/docs/eip/umn/en-us_image_0000001117669274.png b/docs/eip/umn/en-us_image_0000001117669274.png index 76633c84b..135693afc 100644 Binary files a/docs/eip/umn/en-us_image_0000001117669274.png and b/docs/eip/umn/en-us_image_0000001117669274.png differ diff --git a/docs/eip/umn/en-us_image_0000001117669524.png b/docs/eip/umn/en-us_image_0000001117669524.png index 7a8a4aeb6..d6b756a93 100644 Binary files a/docs/eip/umn/en-us_image_0000001117669524.png and b/docs/eip/umn/en-us_image_0000001117669524.png differ diff --git a/docs/eip/umn/en-us_image_0000001163949251.png b/docs/eip/umn/en-us_image_0000001163949251.png index c3db78d86..fea06056a 100644 Binary files a/docs/eip/umn/en-us_image_0000001163949251.png and b/docs/eip/umn/en-us_image_0000001163949251.png differ diff --git a/docs/eip/umn/en-us_image_0000001197426329.png b/docs/eip/umn/en-us_image_0000001197426329.png index eacf18140..986344163 100644 Binary files a/docs/eip/umn/en-us_image_0000001197426329.png and b/docs/eip/umn/en-us_image_0000001197426329.png differ diff --git a/docs/eip/umn/en-us_image_0000001211006359.png b/docs/eip/umn/en-us_image_0000001211006359.png index ff5a995a9..66686f7e6 100644 Binary files a/docs/eip/umn/en-us_image_0000001211006359.png and b/docs/eip/umn/en-us_image_0000001211006359.png differ diff --git a/docs/eip/umn/en-us_image_0000001211445065.png b/docs/eip/umn/en-us_image_0000001211445065.png index 9d7396e24..a86f5c5dd 100644 Binary files a/docs/eip/umn/en-us_image_0000001211445065.png and b/docs/eip/umn/en-us_image_0000001211445065.png differ diff --git a/docs/eip/umn/en-us_image_0000001223659800.png b/docs/eip/umn/en-us_image_0000001223659800.png new file mode 100644 index 000000000..cc760e244 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001223659800.png differ diff --git a/docs/eip/umn/en-us_image_0000001338408584.png b/docs/eip/umn/en-us_image_0000001338408584.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001338408584.png differ diff --git a/docs/eip/umn/en-us_image_0000001388688657.png b/docs/eip/umn/en-us_image_0000001388688657.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001388688657.png differ diff --git a/docs/eip/umn/en-us_image_0000001401506644.png b/docs/eip/umn/en-us_image_0000001401506644.png new file mode 100644 index 000000000..83ed9f387 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001401506644.png differ diff --git a/docs/eip/umn/en-us_image_0000001454059512.png b/docs/eip/umn/en-us_image_0000001454059512.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001454059512.png differ diff --git a/docs/eip/umn/en-us_image_0000001486922646.png b/docs/eip/umn/en-us_image_0000001486922646.png new file mode 100644 index 000000000..5d14a41b1 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001486922646.png differ diff --git a/docs/eip/umn/en-us_image_0000001500905066.png b/docs/eip/umn/en-us_image_0000001500905066.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001500905066.png differ diff --git a/docs/eip/umn/en-us_image_0000001520717193.png b/docs/eip/umn/en-us_image_0000001520717193.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001520717193.png differ diff --git a/docs/eip/umn/en-us_image_0000001520959725.png b/docs/eip/umn/en-us_image_0000001520959725.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001520959725.png differ diff --git a/docs/eip/umn/en-us_image_0000001567669964.png b/docs/eip/umn/en-us_image_0000001567669964.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001567669964.png differ diff --git a/docs/eip/umn/en-us_image_0000001572300492.png b/docs/eip/umn/en-us_image_0000001572300492.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001572300492.png differ diff --git a/docs/eip/umn/en-us_image_0000001595877226.png b/docs/eip/umn/en-us_image_0000001595877226.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001595877226.png differ diff --git a/docs/eip/umn/en-us_image_0000001596195138.png b/docs/eip/umn/en-us_image_0000001596195138.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001596195138.png differ diff --git a/docs/eip/umn/en-us_image_0000001618428593.png b/docs/eip/umn/en-us_image_0000001618428593.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/eip/umn/en-us_image_0000001618428593.png differ diff --git a/docs/eip/umn/en-us_image_0118498829.gif b/docs/eip/umn/en-us_image_0118498829.gif new file mode 100644 index 000000000..ee7d27d16 Binary files /dev/null and b/docs/eip/umn/en-us_image_0118498829.gif differ diff --git a/docs/eip/umn/en-us_image_0118499137.gif b/docs/eip/umn/en-us_image_0118499137.gif new file mode 100644 index 000000000..24491f9d5 Binary files /dev/null and b/docs/eip/umn/en-us_image_0118499137.gif differ diff --git a/docs/eip/umn/en-us_image_0204809524.png b/docs/eip/umn/en-us_image_0204809524.png new file mode 100644 index 000000000..36e76bba9 Binary files /dev/null and b/docs/eip/umn/en-us_image_0204809524.png differ diff --git a/docs/eip/umn/en-us_image_0204809678.png b/docs/eip/umn/en-us_image_0204809678.png new file mode 100644 index 000000000..a74474ad0 Binary files /dev/null and b/docs/eip/umn/en-us_image_0204809678.png differ diff --git a/docs/eip/umn/en-us_image_0204809685.png b/docs/eip/umn/en-us_image_0204809685.png new file mode 100644 index 000000000..2deaba1cc Binary files /dev/null and b/docs/eip/umn/en-us_image_0204809685.png differ diff --git a/docs/eip/umn/en-us_image_0204809728.png b/docs/eip/umn/en-us_image_0204809728.png new file mode 100644 index 000000000..0d3411a22 Binary files /dev/null and b/docs/eip/umn/en-us_image_0204809728.png differ diff --git a/docs/eip/umn/en-us_image_0210779229.png b/docs/eip/umn/en-us_image_0210779229.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/eip/umn/en-us_image_0210779229.png differ diff --git a/docs/eip/umn/en-us_image_0233469196.png b/docs/eip/umn/en-us_image_0233469196.png new file mode 100644 index 000000000..a844ced30 Binary files /dev/null and b/docs/eip/umn/en-us_image_0233469196.png differ diff --git a/docs/eip/umn/en-us_image_0250105611.png b/docs/eip/umn/en-us_image_0250105611.png new file mode 100644 index 000000000..64dc28e84 Binary files /dev/null and b/docs/eip/umn/en-us_image_0250105611.png differ diff --git a/docs/eip/umn/en-us_image_0250117342.png b/docs/eip/umn/en-us_image_0250117342.png new file mode 100644 index 000000000..f075e8f15 Binary files /dev/null and b/docs/eip/umn/en-us_image_0250117342.png differ diff --git a/docs/eip/umn/en-us_image_0250182352.png b/docs/eip/umn/en-us_image_0250182352.png new file mode 100644 index 000000000..41f5da3fc Binary files /dev/null and b/docs/eip/umn/en-us_image_0250182352.png differ diff --git a/docs/eip/umn/en-us_image_0250182717.png b/docs/eip/umn/en-us_image_0250182717.png new file mode 100644 index 000000000..40a9d0d16 Binary files /dev/null and b/docs/eip/umn/en-us_image_0250182717.png differ diff --git a/docs/eip/umn/faq_bandwidth.html b/docs/eip/umn/faq_bandwidth.html index f35caa103..87b27222b 100644 --- a/docs/eip/umn/faq_bandwidth.html +++ b/docs/eip/umn/faq_bandwidth.html @@ -1,16 +1,23 @@Bandwidth
--+- What Is the Bandwidth Size Range?
- 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 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?
+
diff --git a/docs/eip/umn/faq_bandwidth_0001.html b/docs/eip/umn/faq_bandwidth_0001.html index 9d58a824a..e98acdc19 100644 --- a/docs/eip/umn/faq_bandwidth_0001.html +++ b/docs/eip/umn/faq_bandwidth_0001.html @@ -1,7 +1,7 @@What Is the Bandwidth Size Range?
-The bandwidth range is from 1 Mbit/s to 1,000 Mbit/s.
+The bandwidth range is from 5 Mbit/s to 1000 Mbit/s.
diff --git a/docs/eip/umn/faq_bandwidth_0003.html b/docs/eip/umn/faq_bandwidth_0003.html new file mode 100644 index 000000000..c1d2aea52 --- /dev/null +++ b/docs/eip/umn/faq_bandwidth_0003.html @@ -0,0 +1,11 @@ + + +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 58a621e16..a209ecd13 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?
-Dedicated bandwidth: The bandwidth can only be used by one EIP and the EIP can only be used by one cloud resource, such as an ECS, a NAT gateway, or a load balancer.
-Shared bandwidth: The 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.
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.
diff --git a/docs/eip/umn/faq_bandwidth_0007.html b/docs/eip/umn/faq_bandwidth_0007.html new file mode 100644 index 000000000..9ebf4ac44 --- /dev/null +++ b/docs/eip/umn/faq_bandwidth_0007.html @@ -0,0 +1,13 @@ + + +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.
+Figure 1 Inbound bandwidth and outbound bandwidth+
++ diff --git a/docs/eip/umn/faq_bandwidth_0009.html b/docs/eip/umn/faq_bandwidth_0009.html new file mode 100644 index 000000000..6d1147bcb --- /dev/null +++ b/docs/eip/umn/faq_bandwidth_0009.html @@ -0,0 +1,14 @@ + + +++Parent topic: Bandwidth+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.
+ +For details, see ECS Types.
+++ diff --git a/docs/eip/umn/faq_bandwidth_0012.html b/docs/eip/umn/faq_bandwidth_0012.html new file mode 100644 index 000000000..f9909d1df --- /dev/null +++ b/docs/eip/umn/faq_bandwidth_0012.html @@ -0,0 +1,13 @@ + + +++Parent topic: Bandwidth+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.
+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).
+++ diff --git a/docs/eip/umn/faq_common.html b/docs/eip/umn/faq_common.html index bff62ed05..8edbf2bec 100644 --- a/docs/eip/umn/faq_common.html +++ b/docs/eip/umn/faq_common.html @@ -1,17 +1,29 @@ - -++Parent topic: Bandwidth+Product Consultation
- --- +Product Consultation
+- What Is a Quota?
+ - How Do I Assign or Retrieve a Specific EIP?
+
+ - Why Is an EIP Newly Assigned the Same as the One I Released?
+
+ - What Are the Differences Between EIP, Private IP Address, and Virtual IP Address?
+ - Can I Bind an EIP to Multiple ECSs?
+ - 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?
+
diff --git a/docs/eip/umn/faq_common_0001.html b/docs/eip/umn/faq_common_0001.html index 4bae7bccf..cddd586d1 100644 --- a/docs/eip/umn/faq_common_0001.html +++ b/docs/eip/umn/faq_common_0001.html @@ -13,7 +13,7 @@- 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
diff --git a/docs/eip/umn/faq_connect.html b/docs/eip/umn/faq_connect.html index 0a7915891..5a5661fa1 100644 --- a/docs/eip/umn/faq_connect.html +++ b/docs/eip/umn/faq_connect.html @@ -8,6 +8,10 @@- 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?
+
+- Why Does the Download Speed of My ECS Is Slow?
+diff --git a/docs/eip/umn/faq_connect_0002.html b/docs/eip/umn/faq_connect_0002.html index b40708cd6..7acb031ad 100644 --- a/docs/eip/umn/faq_connect_0002.html +++ b/docs/eip/umn/faq_connect_0002.html @@ -1,12 +1,12 @@How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
-Users with IPv6 clients can call APIs to assign IPv6 EIPs and bind the EIPs to ECSs. Then, the users can use the EIP to access the ECSs in the VPC over the Internet.
-For details, see Floating IP Address (IPv6) > Creating a Floating IP Address in the Virtual Private Cloud API Reference. The NAT64 gateway in the data center will convert the IPv6 EIP to the IPv4 address. (The last 32 bits of the obtained IPv6 EIP is the IPv4 EIP.)
+Users with IPv6 clients can call APIs to assign IPv6 EIPs and bind the EIPs to ECSs. Then, the users can use the EIP to access the ECSs in the VPC over the Internet.
+For details, see Floating IP Address (IPv6) > Creating a Floating IP Address in the Virtual Private Cloud API Reference. The NAT64 gateway in the data center will convert the IPv6 EIP to the IPv4 address. (The last 32 bits of the obtained IPv6 EIP is the IPv4 EIP.)
After users who use IPv6 clients bind an IPv6 EIP to an ECS, the data flow is shown in Figure 1.
The IPv6 service has the following restrictions:
-- ECSs use IPv4 addresses and cannot directly access public IPv6 addresses. Therefore, only public IPv6 addresses can access ECSs. That means ECSs cannot use IPv4 EIPs that are converted from IPv6 address to access the Internet. To enable the ECSs to access the Internet, you must bind IPv4 EIPs to them.
- Data packets from an IPv6 network on the Internet are converted to IPv4 packets on the NAT64 gateway. Both the source IP address and port number will be converted. (The source IP address is invisible.)
- The IPv6 client can access only the EIP and the ELB service.
- Only one EIP (IPv6 or IPv4) can be bound to each NIC.
- You can only make API calls to use an EIP to obtain the IPv6 address. The management console displays only IPv4 addresses.
- The security group function does not apply to IPv6 clients.
- Resources in internal networks on the cloud can access IPv4 addresses converted by NAT64 gateway.
- The public cloud does not provide IP spoofing protection for IPv6 traffic from the Internet.
- Currently, the Anti-DDoS service does not protect IPv6 addresses.
- ECSs use IPv4 addresses and cannot directly access public IPv6 addresses. Therefore, only public IPv6 addresses can access ECSs. That means ECSs cannot use IPv4 EIPs that are converted from IPv6 address to access the Internet. To enable the ECSs to access the Internet, you must bind IPv4 EIPs to them.
- Data packets from an IPv6 network on the Internet are converted to IPv4 packets on the NAT64 gateway. Both the source IP address and port number will be converted. (The source IP address is invisible.)
- The IPv6 client can access only the EIP and the ELB service.
- Only one EIP (IPv6 or IPv4) can be bound to each NIC.
- You can only make API calls to use an EIP to obtain the IPv6 address. The management console displays only IPv4 addresses.
- The security group function does not apply to IPv6 clients.
- Resources in internal networks on the cloud can access IPv4 addresses converted by NAT64 gateway.
- The public cloud does not provide IP spoofing protection for IPv6 traffic from the Internet.
- Currently, the Anti-DDoS service does not protect IPv6 addresses.
diff --git a/docs/eip/umn/faq_connect_0004.html b/docs/eip/umn/faq_connect_0004.html new file mode 100644 index 000000000..dc3ef1783 --- /dev/null +++ b/docs/eip/umn/faq_connect_0004.html @@ -0,0 +1,163 @@ + + +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.
++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.
+Figure 1 Method of locating the failure to ping an EIP+ +
+
+Table 1 Method of locating the failure to ping an EIP Possible Cause
+Solution
+ICMP access rules are not added to the security group.
+Add ICMP access rules to the security group. For details, see Checking Security Group Rules.
+Ping operations are prohibited on the firewall.
+Allow ping operations on the firewall. For details, see Checking Firewall Settings.
+Ping operations are prohibited on the ECS.
+Allow ping operations on the ECS. For details, see Checking Whether Ping Operations Have Been Disabled on the ECS.
+Network ACL is associated.
+If the VPC is associated with a network ACL, check the network ACL rules. For details, see Checking ACL Rules.
+A network exception occurred.
+Use another ECS in the same region to check whether the local network is functional. For details, see Checking Whether the Network Is Functional.
+Routes are incorrectly configured if multiple NICs are used.
+If the network is inaccessible due to an extension NIC, the fault is generally caused by incorrect route configurations. To resolve this issue, see Checking the ECS Route Configuration If Multiple NICs Are Used.
++Checking Security Group Rules
ICMP is used for the ping command. Check whether the security group accommodating the ECS allows ICMP traffic.
+- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, click the name of the target ECS.
The page providing details about the ECS is displayed.
+ - Click the Security Groups tab, expand the information of the security group, and view security group rules.
- Click the security group ID.
The system automatically switches to the Security Group page.
+ - On the Outbound Rules page, click Add Rule. In the displayed dialog box, set required parameters to add an outbound rule.
++
+Table 2 Security group rules Transfer Direction
+Type
+Protocol/Port Range
+Source
+Outbound
+IPv4
+ICMP/Any
+0.0.0.0/0
+0.0.0.0/0 indicates all IP addresses.
+ - On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters to add an inbound rule.
++
+Table 3 Security group rules Transfer Direction
+Type
+Protocol/Port Range
+Source
+Inbound
+IPv4
+ICMP/Any
+0.0.0.0/0
+0.0.0.0/0 indicates all IP addresses.
+ - Click OK to complete the security rule configuration.
+Checking Firewall Settings
If a firewall is enabled on the ECS, check whether the firewall blocks the ping operations.
+Linux+- Consider CentOS 7 as an example. Run the following command to check the firewall status:
+
If running is displayed in the command output, the firewall has been enabled.
+
- Check whether there is any ICMP rule blocking the ping operations.
+
If the command output shown in Figure 2 is displayed, there is no ICMP rule blocking the ping operations.
+ +If the ping operations are blocked by an ICMP rule, run the following commands to modify the rule for unblocking:
+iptables -A INPUT -p icmp --icmp-type echo-request -j ACCEPT
+iptables -A OUTPUT -p icmp --icmp-type echo-reply -j ACCEPT
+
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:
+Inbound Rules: File and Printer Sharing (Echo Request - ICMPv6-In)
+Outbound Rules: File and Printer Sharing (Echo Request - ICMPv6-Out)
+Figure 3 Inbound Rules+
Figure 4 Outbound Rules+
+Checking Whether Ping Operations Have Been Disabled on the ECS
Windows
+Enable ping operations using the CLI.
+- Start the Run dialog box. Enter cmd and press Enter.
- Run the following command to enable ping operations: +
Linux
+Check the ECS kernel parameters.+- Check the net.ipv4.icmp_echo_ignore_all value in the /etc/sysctl.conf file. Value 0 indicates that ping operations are allowed, and value 1 indicates that ping operations are prohibited.
- Allow ping operations. +
+Checking ACL Rules
By default, no ACL is configured for a VPC. If a network ACL is associated with a VPC, check the ACL rules.
+- Check whether the subnet of the ECS has been associated with a network ACL.
If an ACL name is displayed, the network ACL has been associated with the ECS.
+ - Click the ACL name to view its status.
- If the network ACL is enabled, add an ICMP rule to allow traffic.+
The default network ACL rule denies all incoming and outgoing packets. If a network ACL is disabled, the default rule is still effective.
+
+Checking Whether the Network Is Functional
- Use another ECS in the same region to check whether the local network is functional.
Use another ECS in the same region to ping the affected EIP. If the EIP can be pinged, the VPC is functional. In such a case, rectify the local network fault and ping the affected EIP again.
+ - 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.
+
+Checking the ECS Route Configuration If Multiple NICs Are Used
Generally, the default route of an OS will preferentially select the primary NIC. If an extension NIC is selected in a route and the network malfunctions, this issue is typically caused by incorrect route configuration.
+- If the ECS has multiple NICs, check whether the default route is available.
- Log in to the ECS and run the following command to check whether the default route is available:
ip route
+Figure 5 Default route+
- If the route is unavailable, run the following command to add it:
ip route add default via XXXX dev eth0
++ In the preceding command, XXXX specifies a gateway IP address.
+
- Log in to the ECS and run the following command to check whether the default route is available:
- If the ECS has multiple NICs and the EIP is bound to an extension NIC, configure policy routing on the ECS for network communication with the extension NIC.
++ diff --git a/docs/eip/umn/faq_connect_180507.html b/docs/eip/umn/faq_connect_180507.html new file mode 100644 index 000000000..8137c8f30 --- /dev/null +++ b/docs/eip/umn/faq_connect_180507.html @@ -0,0 +1,15 @@ + + +++Parent topic: Connectivity+Why Does the Download Speed of My ECS Is Slow?
++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?
+ - Unstable carrier lines: The network between the local server and the cloud is unstable. Contact the carrier to check the network status.
++ diff --git a/docs/eip/umn/faq_eip.html b/docs/eip/umn/faq_eip.html index 81a51b234..1541058fa 100644 --- a/docs/eip/umn/faq_eip.html +++ b/docs/eip/umn/faq_eip.html @@ -6,7 +6,13 @@++Parent topic: Connectivity+- How Do I Access an ECS with an EIP Bound from the Internet?
- - Can I Bind Multiple EIPs to an ECS?
+ - 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 Multiple EIPs Be Bound to an ECS?
+
+ - Can I Bind an EIP to a Cloud Resource in Another Region?
Can I Bind an EIP to Multiple ECSs?
Each EIP can be bound to only one ECS at a time.
+Multiple ECSs cannot share the same EIP. An ECS and its bound EIP must be in the same region. If you want multiple ECSs in the same VPC to share an EIP, you have to use a NAT gateway. For more information, see NAT Gateway User Guide.
diff --git a/docs/eip/umn/faq_eip_0007.html b/docs/eip/umn/faq_eip_0007.html index 715047d6c..3fa94a57d 100644 --- a/docs/eip/umn/faq_eip_0007.html +++ b/docs/eip/umn/faq_eip_0007.html @@ -2,10 +2,9 @@How Do I Access an ECS with an EIP Bound from the Internet?
Each ECS is automatically added to a security group after being created to ensure its security. The security group denies access traffic from the Internet by default. To allow external access to ECSs in the security group, add an inbound rule to the security group.
-You can set Protocol to TCP, UDP, ICMP, or All as required on the page for creating a security group rule.
-- If the ECS needs to be accessible over the Internet and the IP address used to access the ECS over the Internet has been configured on the ECS, or the ECS does not need to be accessible over the Internet, set Source to the IP address range containing the IP address that is allowed to access the ECS over the Internet.
- If the ECS needs to be accessible over the Internet and the IP address used to access the ECS over the Internet has not been configured on the ECS, it is recommended that you retain the default setting 0.0.0.0/0 for Source, and then set allowed ports to improve network security.
- Allocate ECSs that have different Internet access policies to different security groups.-
The default source IP address 0.0.0.0/0 indicates that all IP addresses can access ECSs in the security group.
-
You can set Protocol to TCP, UDP, ICMP, GRE, or All as required on the page for creating a security group rule.
+- If your ECS needs to be accessible over the Internet and you know the IP address used to access the ECS, set Source to the IP address range containing the IP address.
- If your ECS needs to be accessible over the Internet but you do not know the IP address used to access the ECS, retain the default setting 0.0.0.0/0 for Source, and then set allowed ports to improve network security.
The default source 0.0.0.0/0 indicates that all IP addresses can access ECSs in the security group.
+ - Allocate ECSs that have different Internet access requirements to different security groups.
diff --git a/docs/eip/umn/faq_eip_0009.html b/docs/eip/umn/faq_eip_0009.html new file mode 100644 index 000000000..a104bcda5 --- /dev/null +++ b/docs/eip/umn/faq_eip_0009.html @@ -0,0 +1,23 @@ + + +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+
- Enable access to the Internet through the extension NIC by default.
- Run the following command to delete the default route of the primary NIC:
route del -net 0.0.0.0 gw 192.168.11.1 dev eth0
+192.168.11.1 is the gateway of the subnet that the NIC works. You can view the gateway on the Summary tab page of the subnet on the management console.++ This operation will interrupt ECS communication. It is recommended that you perform the configuration by following step 4.
+ - Run the following command to configure the default route for the extension NIC: +
- Run the following command to delete the default route of the primary NIC:
- Configure Internet access from the extension NIC based on your destination address.
Run the following command to configure access to a specified CIDR block (for example, xx.xx.0.0/16) through the extension NIC:
+You can configure the CIDR block as required.
+route add -net xx.xx.0.0 netmask 255.255.0.0 gw 192.168.17.1
+
++ diff --git a/docs/eip/umn/faq_eip_0010.html b/docs/eip/umn/faq_eip_0010.html new file mode 100644 index 000000000..c1fd2367a --- /dev/null +++ b/docs/eip/umn/faq_eip_0010.html @@ -0,0 +1,13 @@ + + +++Parent topic: EIP Binding and Unbinding+Can I Bind an EIP of an ECS to Another ECS?
++Yes.
+You can unbind the EIP from the original ECS. For details, see Unbinding an EIP from an ECS and Releasing the EIP.
+Then, bind the EIP to the target ECS. For details, see Assigning an EIP and Binding It to an ECS.
+++ diff --git a/docs/eip/umn/faq_eip_0012.html b/docs/eip/umn/faq_eip_0012.html new file mode 100644 index 000000000..e14526fcb --- /dev/null +++ b/docs/eip/umn/faq_eip_0012.html @@ -0,0 +1,13 @@ + + +++Parent topic: EIP Binding and Unbinding+How Do I Assign or Retrieve a Specific EIP?
++If you want to retrieve an EIP that you have released or assign a specific EIP, you can use APIs by setting the value of ip_address to the one that you want to assign. For details, see Elastic IP API Reference.
++ - If the EIP has been assigned to another user, you will fail to assign your required EIP.
- You cannot use the management console to assign a specific EIP.
++ diff --git a/docs/eip/umn/faq_eip_0013.html b/docs/eip/umn/faq_eip_0013.html new file mode 100644 index 000000000..f463cde2d --- /dev/null +++ b/docs/eip/umn/faq_eip_0013.html @@ -0,0 +1,49 @@ + + +++Parent topic: Product Consultation+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+ +
+
+Table 1 Functions of different IP address types IP Address Type
+Description
+Example Value
+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 address of ECS-A-01: 172.16.0.84
- Private IP address of ECS-B-01: 172.16.1.12
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.
+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
+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.
- 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.
++ diff --git a/docs/eip/umn/faq_eip_0014.html b/docs/eip/umn/faq_eip_0014.html new file mode 100644 index 000000000..f2b39e510 --- /dev/null +++ b/docs/eip/umn/faq_eip_0014.html @@ -0,0 +1,12 @@ + + +++Parent topic: Product Consultation+Can I Assign a Specific EIP?
++By default, EIPs are assigned randomly. If you have released EIPs, the system preferentially assigns EIPs from the ones you released.
+You can assign a specific EIP only by calling an API. For details, see section "Assigning an EIP" in the Elastic IP API Reference.
+++ diff --git a/docs/eip/umn/faq_eip_0016.html b/docs/eip/umn/faq_eip_0016.html new file mode 100644 index 000000000..0dad87da4 --- /dev/null +++ b/docs/eip/umn/faq_eip_0016.html @@ -0,0 +1,14 @@ + + +++Parent topic: Product Consultation+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?
+If you do not want an EIP that you have released, it is recommended that you buy another EIP first and then release the one that you do not need.
+++ diff --git a/docs/eip/umn/faq_eip_0019.html b/docs/eip/umn/faq_eip_0019.html new file mode 100644 index 000000000..ed76b024b --- /dev/null +++ b/docs/eip/umn/faq_eip_0019.html @@ -0,0 +1,11 @@ + + +++Parent topic: Product Consultation+Can a Bandwidth Be Used by Multiple Accounts?
++A bandwidth cannot be shared between different accounts. Each account can use and manage only its own EIP bandwidths.
+++ diff --git a/docs/eip/umn/faq_eip_0020.html b/docs/eip/umn/faq_eip_0020.html new file mode 100644 index 000000000..f27a0a1a3 --- /dev/null +++ b/docs/eip/umn/faq_eip_0020.html @@ -0,0 +1,18 @@ + + +++Parent topic: Product Consultation+How Do I Change an EIP for an Instance?
+++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.
++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.
++ diff --git a/docs/eip/umn/faq_eip_0021.html b/docs/eip/umn/faq_eip_0021.html new file mode 100644 index 000000000..30d274a64 --- /dev/null +++ b/docs/eip/umn/faq_eip_0021.html @@ -0,0 +1,11 @@ + + +++Parent topic: Product Consultation+Can I Bind an EIP to a Cloud Resource in Another Region?
++No. EIPs and their associated cloud resources must be in the same region.
+++ diff --git a/docs/eip/umn/faq_eip_0022.html b/docs/eip/umn/faq_eip_0022.html index 4cfcb8af2..3323b8a1c 100644 --- a/docs/eip/umn/faq_eip_0022.html +++ b/docs/eip/umn/faq_eip_0022.html @@ -1,10 +1,10 @@ -++Parent topic: EIP Binding and Unbinding+Can I Bind Multiple EIPs to an ECS?
-Scenarios
You can bind multiple EIPs to an ECS. However, this configuration is not recommended.
-To bind multiple EIPs to an ECS, you must manually configure routes.
+Can Multiple EIPs Be Bound to an ECS?
+-Scenarios
Multiple EIPs can be bound to an ECS, but this operation is not recommended.
+If an ECS has multiple NICs attached and you want to bind multiple EIPs to this ECS, you need to configure policy-based routes for these NICs so that these extension NICs can communicate with external works. For details, see Configuration Example.
diff --git a/docs/eip/umn/monitor_0002.html b/docs/eip/umn/monitor_0002.html index 452e03b4b..915bf21dd 100644 --- a/docs/eip/umn/monitor_0002.html +++ b/docs/eip/umn/monitor_0002.html @@ -1,12 +1,12 @@Configuration Example
Table 1 lists ECS configurations.
+diff --git a/docs/eip/umn/faq_eip_0025.html b/docs/eip/umn/faq_eip_0025.html new file mode 100644 index 000000000..6fc798d28 --- /dev/null +++ b/docs/eip/umn/faq_eip_0025.html @@ -0,0 +1,17 @@ + + +Configuration Example
Table 1 lists ECS configurations.
Table 1 ECS configurations Parameter
CentOS 6.5 64bit
EIP
+EIP
2
Example 1:
-If you are required to access public network 11.11.11.0/24 through standby NIC eth1, perform the following operations to configure a route:- Log in to the ECS.
- Run the following command to configure a route:
ip route add 11.11.11.0/24 dev eth1 via 192.168.2.1
+If you intend to access public network 11.11.11.0/24 through standby NIC eth1, perform the following operations to configure a route:Example 2:
-Based on example 1, if you are required to enable routing for default public network traffic through standby NIC eth1, perform the following operations to configure a route:
+Based on example 1, if you intend to enable routing for default public network traffic through standby NIC eth1, perform the following operations to configure a route:
- Log in to the ECS.
- Run the following command to delete the default route:
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.
Why Can't I Find My Assigned EIP on the Management Console?
+++Symptom
After I logged in to the management console, I could not find my assigned EIP.
++ +Possible Cause
Your EIP is not in the current region. For details, see EIP Not in the Current Region.
+++ diff --git a/docs/eip/umn/faq_eip_0028.html b/docs/eip/umn/faq_eip_0028.html new file mode 100644 index 000000000..a64ff0ea4 --- /dev/null +++ b/docs/eip/umn/faq_eip_0028.html @@ -0,0 +1,13 @@ + + +++Parent topic: Product Consultation+Why Is an EIP Newly Assigned the Same as the One I Released?
++If you have released EIPs in a region, the system preferentially assigns EIPs from the ones you released in the last 24 hours.
+If you do not want an EIP that you have released, assign an EIP first and then release the one that you do not want.
+You can assign a specific EIP by calling APIs. For details, see Elastic IP API Reference.
+++ diff --git a/docs/eip/umn/monitor_0001.html b/docs/eip/umn/monitor_0001.html index ca062a3f0..512c29bd0 100644 --- a/docs/eip/umn/monitor_0001.html +++ b/docs/eip/umn/monitor_0001.html @@ -10,6 +10,8 @@++Parent topic: Product Consultation+- Creating an Alarm Rule
+
- Exporting Monitoring Data
+Supported Metrics
-Description
This section describes the namespace, list, and measurement dimensions of EIP and bandwidth metrics that you can check on Cloud Eye. You can use APIs or the Cloud Eye console to query the metrics of the monitored metrics and alarms generated for EIPs and bandwidths.
+-Description
This section describes the namespace, list, and measurement dimensions of metrics of EIPs and bandwidths that you can check on Cloud Eye. You can use APIs or the Cloud Eye console to query the metrics of the monitored metrics and generated alarms.
Namespace
SYS.VPC
+Namespace
Namespace of EIPs and bandwidths: SYS.VPC
Monitoring Metrics
-Table 1 EIP and bandwidth metrics ID
++Table 1 Metrics of EIPs and bandwidths ID
Name
If a bandwidth is increased or decreased, there is a delay of 5 to 10 minutes for the monitoring metrics to update for the new bandwidth.
+Dimensions
Key
diff --git a/docs/eip/umn/monitor_0003.html b/docs/eip/umn/monitor_0003.html index 6eef983af..e83e178f0 100644 --- a/docs/eip/umn/monitor_0003.html +++ b/docs/eip/umn/monitor_0003.html @@ -1,9 +1,12 @@Viewing Metrics
-Scenarios
View related metrics to see bandwidth and EIP usage information.
+-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
- 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 & Governance > 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 (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 (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.
diff --git a/docs/eip/umn/monitor_0004.html b/docs/eip/umn/monitor_0004.html index 69744c076..8289a7112 100644 --- a/docs/eip/umn/monitor_0004.html +++ b/docs/eip/umn/monitor_0004.html @@ -3,7 +3,7 @@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 & Governance > 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.
+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.
Exporting Monitoring Data
+++Scenarios
If you want to analyze the bandwidth or traffic usage of EIPs to locate faults, you can export EIP monitoring data.
++Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Hover on the upper left corner to display Service List and choose Management & Deployment > Cloud Eye.
- In the navigation pane on the left, choose Cloud Service Monitoring > Elastic IP and Bandwidth.
- On the Cloud Service Monitoring page, click Export Data.
- Configure the time range, resource type, dimension, monitored object, and metric.
- Click Export.
- 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: +
++ diff --git a/docs/eip/umn/overview.html b/docs/eip/umn/overview.html index 6af8ba836..ba3b13bb3 100644 --- a/docs/eip/umn/overview.html +++ b/docs/eip/umn/overview.html @@ -6,8 +6,20 @@++Parent topic: Monitoring+- What Is Elastic IP?
+ - Advantages
+
+ - Application Scenarios
+
+ - Functions
+
+ - Notes and Constraints
+ - User Permissions
+ - Permissions
+
+ - EIP and Other Services
+ - Region and AZ
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. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.
-Each EIP can be used by only one cloud resource at a time.
+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 EIPdiff --git a/docs/eip/umn/overview_0002.html b/docs/eip/umn/overview_0002.html new file mode 100644 index 000000000..2ad4708fa --- /dev/null +++ b/docs/eip/umn/overview_0002.html @@ -0,0 +1,14 @@ + + +Advantages
++An EIP has the following advantages: ++++ diff --git a/docs/eip/umn/overview_0003.html b/docs/eip/umn/overview_0003.html new file mode 100644 index 000000000..0a44f86dd --- /dev/null +++ b/docs/eip/umn/overview_0003.html @@ -0,0 +1,18 @@ + + +++Parent topic: Service Overview+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.
+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.
++ diff --git a/docs/eip/umn/overview_0004.html b/docs/eip/umn/overview_0004.html new file mode 100644 index 000000000..10ee4f29b --- /dev/null +++ b/docs/eip/umn/overview_0004.html @@ -0,0 +1,67 @@ + + +++Parent topic: Service Overview+EIP and Other Services
++++
+Table 1 Related services Interactive Function
+Service
+Reference
+Bind an EIP to a server to allow the server to access the Internet.
+Elastic Cloud Server (ECS)
+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.
+Virtual Private Cloud (VPC)
++ +Configure ECSs to share one or more EIPs through a NAT gateway to access the Internet.
+NAT Gateway
+ ++ +Distribute incoming traffic to multiple ECSs in a VPC.
+ELB
++ +Check the bandwidth and traffic usage.
+Cloud Eye
++ +Add tags to EIPs so that you can quickly identify EIPs and manage them.
+Tag Management Service (TMS)
++ +++ diff --git a/docs/eip/umn/overview_0006.html b/docs/eip/umn/overview_0006.html new file mode 100644 index 000000000..2509d66dd --- /dev/null +++ b/docs/eip/umn/overview_0006.html @@ -0,0 +1,30 @@ + + +++Parent topic: Service Overview+Application Scenarios
+++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 VPC+Figure 1 Binding an EIP to a server+
+Binding an EIP to a NAT Gateway
Scenario
+After an EIP is bound to a NAT gateway and SNAT and DNAT rules are added, multiple servers (such as ECSs and BMSs) can use the same EIP to access the Internet and provide services accessible from the Internet.
+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+
+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+
++ diff --git a/docs/eip/umn/overview_permission.html b/docs/eip/umn/overview_permission.html new file mode 100644 index 000000000..21c4d4103 --- /dev/null +++ b/docs/eip/umn/overview_permission.html @@ -0,0 +1,161 @@ + + +++Parent topic: Service Overview+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.
+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.
+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.
+ ++
+Table 1 System-defined permissions for VPC Policy Name
+Description
+Policy Type
+Dependencies
+VPC FullAccess
+Full permissions for VPC
+System-defined policy
+To use the VPC flow log function, users must also have the LTS ReadOnlyAccess permission.
+VPC ReadOnlyAccess
+Read-only permissions on VPC.
+System-defined policy
+None
+VPC Administrator
+Most permissions on VPC, excluding creating, modifying, deleting, and viewing security groups and security group rules.
+To be granted this permission, users must also have the Tenant Guest and Server Administrator permission.
+System-defined role
+Tenant Guest and Server Administrator policies, which must be attached in the same project as VPC Administrator.
+Table 2 lists the common operations supported by each system policy of VPC. Please choose proper system policies according to this table.
+ ++
+Table 2 Common operations supported by system-defined permissions Operation
+VPC ReadOnlyAccess
+VPC Administrator
+VPC FullAccess
+Assigning an EIP
+x
+x
+√
+Viewing an EIP
+√
+x
+√
+Releasing an EIP
+x
+x
+√
+Binding or unbinding an EIP
+x
+x
+√
+Adding an EIP to or removing an EIP from a shared bandwidth
+x
+x
+√
+Assigning a bandwidth
+x
+x
+√
+Viewing a bandwidth
+√
+x
+√
+Modifying a bandwidth
+x
+x
+√
+Deleting a bandwidth
+x
+x
+√
++Helpful Links
+++ diff --git a/docs/eip/umn/overview_region.html b/docs/eip/umn/overview_region.html index 6962bb0a7..5ba08ecef 100644 --- a/docs/eip/umn/overview_region.html +++ b/docs/eip/umn/overview_region.html @@ -11,7 +11,7 @@++Parent topic: Service Overview+-Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
diff --git a/docs/eip/umn/permission_0001.html b/docs/eip/umn/permission_0001.html new file mode 100644 index 000000000..b99287f05 --- /dev/null +++ b/docs/eip/umn/permission_0001.html @@ -0,0 +1,13 @@ + + +Permissions Management
+ + + diff --git a/docs/eip/umn/permission_0003.html b/docs/eip/umn/permission_0003.html new file mode 100644 index 000000000..3d3b72837 --- /dev/null +++ b/docs/eip/umn/permission_0003.html @@ -0,0 +1,76 @@ + + +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.
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.
+To grant permissions for other services, learn about all permissions supported by IAM.
++Process Flow
+ +On the IAM console, create a user group and grant it permissions (EIP 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.
+Example Custom Policies
- Example 1: Grant permissions to assign and view EIPs
{ + "Version": "1.1", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + " + vpc:publicIps:create + vpc:publicIps:list + " + ] + } + ] +}+ - 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:
+{ + "Version": "1.1", + "Statement": [ + { + "Effect": "Deny", + "Action": [ + "vpc:publicIps:delete" + ] + } + ] +}+
- Example 3: Create a custom policy containing multiple actions.
A custom policy can contain the actions of one or multiple services that are of the same type (global or project-level). Example policy containing multiple actions:
+{ + "Version": "1.1", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "ecs:servers:delete", + "vpc:publicIps:update", + "vpc:publicIps:create" + ] + }, + { + "Effect": "Deny", + "Action": [ + "vpc:publicIps:delete" + ] + } + ] +}+
++ diff --git a/docs/eip/umn/permission_0004.html b/docs/eip/umn/permission_0004.html new file mode 100644 index 000000000..c4bd17907 --- /dev/null +++ b/docs/eip/umn/permission_0004.html @@ -0,0 +1,64 @@ + + +++Parent topic: Permissions Management+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.
+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.
+
+Example Custom Policies
- Example 1: Grant permissions to assign and view EIPs
{ + "Version": "1.1", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + " + vpc:publicIps:create + vpc:publicIps:list + " + ] + } + ] +}+ - 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:
+{ + "Version": "1.1", + "Statement": [ + { + "Effect": "Deny", + "Action": [ + "vpc:publicIps:delete" + ] + } + ] +}+
- Example 3: Create a custom policy containing multiple actions.
A custom policy can contain the actions of one or multiple services that are of the same type (global or project-level). Example policy containing multiple actions:
+{ + "Version": "1.1", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "ecs:servers:delete", + "vpc:publicIps:update", + "vpc:publicIps:create" + ] + }, + { + "Effect": "Deny", + "Action": [ + "vpc:publicIps:delete" + ] + } + ] +}+
++ diff --git a/docs/eip/umn/public_sys-resources/icon-arrowdn.gif b/docs/eip/umn/public_sys-resources/icon-arrowdn.gif index 84eec9be2..379428032 100644 Binary files a/docs/eip/umn/public_sys-resources/icon-arrowdn.gif and b/docs/eip/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/eip/umn/public_sys-resources/icon-arrowrt.gif b/docs/eip/umn/public_sys-resources/icon-arrowrt.gif index 39583d168..6aaaa11c2 100644 Binary files a/docs/eip/umn/public_sys-resources/icon-arrowrt.gif and b/docs/eip/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/eip/umn/qsg_0002.html b/docs/eip/umn/qsg_0002.html index 3a992c6de..f8f5c4030 100644 --- a/docs/eip/umn/qsg_0002.html +++ b/docs/eip/umn/qsg_0002.html @@ -28,13 +28,13 @@++Parent topic: Permissions Management+Assign an EIP and bind it to an ECS.
This task is mandatory.
-You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.
+You can assign an EIP and bind it to an ECS for Internet access.
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 a default rule, which allows all outgoing data packets. ECSs in a security group can access each other without the need to add rules.
+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.
diff --git a/docs/eip/umn/qsg_0003.html b/docs/eip/umn/qsg_0003.html index 03c55cef5..e51d1ccef 100644 --- a/docs/eip/umn/qsg_0003.html +++ b/docs/eip/umn/qsg_0003.html @@ -4,15 +4,15 @@-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.
- On the console homepage, under Network, click 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. - 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.
-Table 1 VPC parameter descriptions Category
Parameter
+Parameter
Description
+Description
Example Value
+Example Value
Basic Information
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:
@@ -48,6 +48,36 @@192.168.0.0/16
Basic Information
+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.
+default
+Basic Information/Advanced Settings
+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.
+- Key: vpc_key1
- Value: vpc-01
Basic Information/Advanced Settings
+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 >).
+N/A
+Default Subnet
Name
@@ -71,7 +101,7 @@Associated Route Table
The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
+The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
Default
-Table 2 VPC tag key and value requirements Parameter
+@@ -115,7 +116,7 @@Table 2 VPC tag key and value requirements Parameter
Requirements
Key
- Cannot be left blank.
- Must be unique for the same 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
- Special characters, including hyphens (-) and underscores (_)
vpc_key1
diff --git a/docs/eip/umn/qsg_0004.html b/docs/eip/umn/qsg_0004.html index cef0b8e63..8ecaa815b 100644 --- a/docs/eip/umn/qsg_0004.html +++ b/docs/eip/umn/qsg_0004.html @@ -2,9 +2,9 @@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.
-The subnet is configured with DHCP by default. When an ECS in this subnet starts, the ECS automatically obtains an IP address using DHCP.
+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.
- On the console homepage, under Network, click Virtual Private Cloud.
- In the navigation pane on the left, click Subnets.
- Click Create Subnet.
The Create Subnet page is displayed.
+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@@ -16,11 +16,11 @@
VPC
+VPC
The VPC for which you want to create a subnet.
+The VPC for which you want to create a subnet.
-
+-
Name
@@ -45,14 +45,7 @@Default
Advanced Settings
-Two options are available, Default and Custom. You can set Advanced Settings to Custom to configure advanced subnet parameters.
--
-Gateway
+Advanced Settings/Gateway
The gateway address of the subnet.
@@ -60,14 +53,14 @@192.168.0.1
DNS Server Address
+Advanced Settings/DNS Server Address
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 (,).
100.125.x.x
NTP Server Address
+Advanced Settings/NTP Server Address
The IP address of the NTP server. This parameter is optional.
You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added.
@@ -76,7 +69,7 @@192.168.2.1
Tag
+Advanced Settings/Tag
The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.
The tag key and value must meet the requirements listed in Table 2.
@@ -84,6 +77,14 @@- 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 >).
+-
+ - 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.
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.
- EIPs for dedicated load balancers:-- In the eu-de region, if you choose to assign an EIP when you create a dedicated load balancer on the management console or using APIs, EIPs for dedicated load balancers (5_gray) will be assigned.
- Do not bind EIPs of this type to non-dedicated load balancers.
- Do not add EIPs of the dedicated load balancer type and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
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.
- On the console homepage, under Network, click 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.
+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.
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
Bandwidth
+Billed By
The bandwidth size in Mbit/s.
+Two options are available:
+- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
100
+Dedicated
Bandwidth Name
+Bandwidth
The name of the bandwidth.
+The bandwidth size in Mbit/s.
bandwidth
+100
Tag
+EIP Name
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 name.
- Key: Ipv4_key1
- Value: 192.168.12.10
eip-test
Quantity
+Enterprise Project
The number of EIPs you want to purchase.
+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.
1
+default
+Bandwidth Name
+The name of the bandwidth.
+bandwidth
+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.
+- Key: Ipv4_key1
- Value: 3005eip
Quantity
+The number of EIPs you want to assign.
+1
- 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 (_)
192.168.12.10
+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 to which you want to bind the EIP.Figure 2 Bind EIP+
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 about the implementation and constraints, see How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
+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?
diff --git a/docs/eip/umn/qsg_0006.html b/docs/eip/umn/qsg_0006.html index d7d99dd45..33f569830 100644 --- a/docs/eip/umn/qsg_0006.html +++ b/docs/eip/umn/qsg_0006.html @@ -1,41 +1,63 @@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
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
Step 4: Create a Security Group
-Scenarios
To improve ECS access security, you can create security groups, define security group rules, and add ECSs in a VPC to different security groups. We recommend that you allocate ECSs that have different Internet access policies to different security groups.
+-Scenarios
A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. A security group consists of inbound and outbound rules.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- On the console homepage, under Network, click Virtual Private Cloud.
- In the navigation pane on the left, choose Access Control > Security Groups.
- On the Security Groups page, click Create Security Group.
- In the Create Security Group area, set the parameters as prompted. Table 1 lists the parameters to be configured.Figure 1 Create Security Group- +
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 Access Control > Security Groups.
The security group list is displayed.
+ - In the upper right corner, click Create Security Group.
The Create Security Group page is displayed.
+ - Configure the parameters as prompted.Figure 1 Create Security Group+ -
Table 1 Parameter description Parameter
+-Table 1 Parameter description Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
The security group name. This parameter is mandatory.
+Mandatory
+Enter the security group name.
The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
NOTE:You can change the security group name after a security group is created. It is recommended that you give each security group a different name.
sg-318b
+sg-AB
Description
+Enterprise Project
Supplementary information about the security group. This parameter is optional.
+Mandatory
+When creating a security group, you can add the security group to an enabled enterprise project.
+An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.
+default
+Template
+Mandatory
+A template comes with default security group rules, helping you quickly create security groups. The following templates are provided:
+- Custom: This template allows you to create security groups with custom security group rules.
- General-purpose web server: The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389.
- All ports open: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks.
General-purpose web server
+Description
+Optional
+Supplementary information about the security group. This parameter is optional.
The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
N/A
+N/A
- Click OK.
+- Confirm the inbound and outbound rules of the template and click OK.
diff --git a/docs/eip/umn/qsg_0007.html b/docs/eip/umn/qsg_0007.html index 855eb1179..1007acec2 100644 --- a/docs/eip/umn/qsg_0007.html +++ b/docs/eip/umn/qsg_0007.html @@ -2,9 +2,10 @@Step 5: Add a Security Group Rule
-Scenarios
After you create a security group, you can add rules to the security group. A rule applies either to inbound traffic or outbound traffic. After you add cloud resources to the security group, they are protected by the rules of the group.
-- Inbound rules control incoming traffic to cloud resources in the security group.
- Outbound rules control outgoing traffic from cloud resources in the security group.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- On the console homepage, under Network, click Virtual Private Cloud.
- In the navigation pane on the left, choose Access Control > Security Groups.
- On the Security Groups page, locate the target security group and click Manage Rule in the Operation column to switch to the page for managing inbound and outbound rules.
- On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters.
You can click + to add more inbound rules.
+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 Access Control > Security Groups.
The security group list is displayed.
+ - Locate the row that contains the target security group, click Manage Rule in the Operation column.
The page for configuring security group rules is displayed.
+ - On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters.
You can click + to add more inbound rules.
Table 1 Inbound rule parameter description Parameter
Protocol & Port
Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
+Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
Custom TC
+Protocols/TCP (Custom ports)
Port: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535.
+Port: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535.
22, or 22-30
Type
+The IP address type can be IPv4.
+IPv4
+Source
The source of the security group rule. The value can be a single IP address or a security group to allow access from the IP address or instances in the security group. For example:- xxx.xxx.xxx.xxx/32 (IPv4 address)
- xxx.xxx.xxx.0/24 (IPv4 address range)
- 0.0.0.0/0 (all IPv4 addresses)
- sg-abc (security group)
Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example:- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: sg-A
0.0.0.0/0
@@ -59,20 +68,26 @@Protocol & Port
Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
+Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
Custom TCP
Port: The port or port range over which the traffic can leave your ECS. The value ranges from 1 to 65535.
+Port: The port or port range over which the traffic can leave your ECS. The value ranges from 1 to 65535.
22, or 22-30
Type
+The IP address type can be IPv4.
+IPv4
+Destination
The destination of the security group rule. The value can be a single IP address or a security group to allow access to the IP address or instances in the security group. For example:+- xxx.xxx.xxx.xxx/32 (IPv4 address)
- xxx.xxx.xxx.0/24 (IPv4 address range)
- 0.0.0.0/0 (all IPv4 addresses)
- sg-abc (security group)
Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:
For more information, see Virtual Private Cloud User Guide.
0.0.0.0/0
