forked from docs/virtual-private-cloud
Update content
This commit is contained in:
parent
96f5f86566
commit
a2d343d0cf
BIN
umn/source/_static/images/en-us_image_0000001209321492.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001209321492.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
BIN
umn/source/_static/images/en-us_image_0000001209777270.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001209777270.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
BIN
umn/source/_static/images/en-us_image_0000001221790501.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001221790501.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1004 B |
BIN
umn/source/_static/images/en-us_image_0000001337710801.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001337710801.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 388 B |
BIN
umn/source/_static/images/en-us_image_0000001461263993.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001461263993.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 357 B |
|
Before Width: | Height: | Size: 128 B After Width: | Height: | Size: 128 B |
|
Before Width: | Height: | Size: 128 B After Width: | Height: | Size: 128 B |
|
Before Width: | Height: | Size: 128 B After Width: | Height: | Size: 128 B |
|
Before Width: | Height: | Size: 128 B After Width: | Height: | Size: 128 B |
|
Before Width: | Height: | Size: 128 B After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503170970.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503170970.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503170974.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503170974.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503318922.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503318922.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503330854.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503330854.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503330858.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503330858.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503478818.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503478818.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503490746.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503490746.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001503490750.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001503490750.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
BIN
umn/source/_static/images/en-us_image_0000001553650753.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001553650753.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001553650757.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001553650757.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001553770733.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001553770733.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001553770737.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001553770737.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001553930581.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001553930581.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001554010645.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001554010645.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001554010649.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001554010649.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 B |
BIN
umn/source/_static/images/en-us_image_0000001570070841.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001570070841.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB |
BIN
umn/source/_static/images/en-us_image_0171311823.png
Normal file
BIN
umn/source/_static/images/en-us_image_0171311823.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 26 KiB |
BIN
umn/source/_static/images/en-us_image_0209577986.png
Normal file
BIN
umn/source/_static/images/en-us_image_0209577986.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 31 KiB |
BIN
umn/source/_static/images/en-us_image_0214585306.png
Normal file
BIN
umn/source/_static/images/en-us_image_0214585306.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
|
Before Width: | Height: | Size: 377 B After Width: | Height: | Size: 377 B |
|
Before Width: | Height: | Size: 5.9 KiB After Width: | Height: | Size: 5.9 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 4.5 KiB After Width: | Height: | Size: 4.5 KiB |
@ -32,8 +32,7 @@ Change History
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2022-10-20 | Modified the following content: |
|
||||
| | |
|
||||
| | - Added user-defined networks in :ref:`Route Table Overview <route_0001>`. |
|
||||
| | - Modified the bandwidth range in :ref:`What Is the Bandwidth Size Range? <vpc_faq_0011>` |
|
||||
| | Modified the bandwidth range in :ref:`What Is the Bandwidth Size Range? <vpc_faq_0011>` |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2022-09-07 | Added the following content: |
|
||||
| | |
|
||||
@ -92,7 +91,7 @@ Change History
|
||||
| | |
|
||||
| | - Added rules in :ref:`Firewall Configuration Examples <acl_0002>`. |
|
||||
| | - Modified :ref:`Does a Security Group Rule or a Firewall Rule Immediately Take Effect for Existing Connections After It Is Modified? <vpc_faq_0074>` |
|
||||
| | - Modified :ref:`How Can I Delete a Subnet That Is Being Used by Other Resources? <vpc_faq_0075>` |
|
||||
| | - Modified :ref:`Why Can't I Delete My VPCs and Subnets? <vpc_faq_0075>` |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2020-02-25 | Added the following content: |
|
||||
| | |
|
||||
@ -132,10 +131,9 @@ Change History
|
||||
| | - Modified the steps in :ref:`Assigning an EIP and Binding It to an ECS <en-us_topic_0013748738>`, :ref:`Elastic IP <vpc_eip_0000>`, and :ref:`Shared Bandwidth <vpc010003>`. |
|
||||
| | - Updated screenshots in :ref:`Modifying a Shared Bandwidth <vpc010008>`. |
|
||||
| | - Updated screenshots and parameter description in :ref:`Creating a Subnet for the VPC <en-us_topic_0013748726>`. |
|
||||
| | - Updated screenshots in :ref:`Creating a Custom Route Table <vpc_route_0005>`, :ref:`Adding a Custom Route <vpc_route_0006>`, and :ref:`Associating a Subnet with a Route Table <vpc_route_0007>`. |
|
||||
| | - Modified steps in :ref:`Assigning a Virtual IP Address <vpc_vip_0002>`, :ref:`Binding a Virtual IP Address to an EIP or ECS <en-us_topic_0067802474>`, and :ref:`Releasing a Virtual IP Address <vpc_vip_0009>`. |
|
||||
| | - Updated screenshots in :ref:`VPC Peering Connection <vpc_peering_0000>`. |
|
||||
| | - Modified description in :ref:`How Many Routes Can a Route Table Contain? <vpc_faq_0063>` and :ref:`How Many Route Tables Can Be Created for a VPC? <vpc_faq_0071>` |
|
||||
| | - Modified description in :ref:`How Many Routes Can a Route Table Contain? <vpc_faq_0063>` |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2019-12-13 | Added the following content: |
|
||||
| | |
|
||||
@ -186,43 +184,36 @@ Change History
|
||||
| | |
|
||||
| | Added the following content: |
|
||||
| | |
|
||||
| | Added descriptions about route types in :ref:`Route Table <en-us_topic_0038263963>` and :ref:`Route Table Overview <route_0001>`. |
|
||||
| | Added descriptions about route types in :ref:`Route Table <en-us_topic_0038263963>`. |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2019-08-16 | Added the following content: |
|
||||
| | |
|
||||
| | Added :ref:`Exporting Route Table Information <vpc_route_0014>`. |
|
||||
| | Added :ref:`Exporting Route Table Information <vpc_route01_0014>`. |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2019-08-09 | Added the following content: |
|
||||
| | |
|
||||
| | - Added parameters **Type** and **Bandwidth Type** to :ref:`Step 3: Assign an EIP and Bind It to an ECS <vpc_qs_0011>` and :ref:`Assigning an EIP and Binding It to an ECS <en-us_topic_0013748738>`. |
|
||||
| | - Added description about how to replicate multiple routes in :ref:`Replicating a Route <vpc_route_0013>`. |
|
||||
| | - Added the description about **Next Hop Type** in :ref:`Adding a Custom Route <vpc_route_0006>`. |
|
||||
| | - Added description about how to replicate multiple routes in :ref:`Replicating a Route <vpc_route01_0013>`. |
|
||||
| | - Added the description about **Next Hop Type** in :ref:`Adding a Custom Route <vpc_route01_0006>`. |
|
||||
| | |
|
||||
| | Modified the following content: |
|
||||
| | |
|
||||
| | - Modified description about **NTP Server Address** in :ref:`Modifying a Subnet <vpc_vpc_0001>`. |
|
||||
| | - Modified description about replication in the "Default Route Table and Custom Route Table" part in :ref:`Route Table Overview <route_0001>`. |
|
||||
| | - Modified descriptions about system routes and custom routes in :ref:`Route Table Overview <route_0001>`. |
|
||||
| | - Modified description about usage restrictions in :ref:`Route Table Overview <route_0001>`. |
|
||||
| | - Modified steps in :ref:`Creating a Custom Route Table <vpc_route_0005>`. |
|
||||
| | - Modified description about the scenario in :ref:`Modifying a Route <vpc_route_0011>` and :ref:`Deleting a Route <vpc_route_0012>`. |
|
||||
| | - Modified description about replication in the "Default Route Table and Custom Route Table" part in :ref:`Route Table Overview <vpc_route01_0001>`. |
|
||||
| | - Modified descriptions about system routes and custom routes in :ref:`Route Table Overview <vpc_route01_0001>`. |
|
||||
| | - Modified description about usage restrictions in :ref:`Route Table Overview <vpc_route01_0001>`. |
|
||||
| | |
|
||||
| | Deleted the following content: |
|
||||
| | |
|
||||
| | - Deleted parameter **Enterprise Project** from the document. |
|
||||
| | - Deleted the Cloud Connect service from the "Default Route Table and Custom Route Table" part in :ref:`Route Table Overview <route_0001>`. |
|
||||
| | - Deleted the Cloud Connect service from the "Default Route Table and Custom Route Table" part in :ref:`Route Table Overview <vpc_route01_0001>`. |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2019-08-02 | Added the following content based on the RM-584 requirements: |
|
||||
| | |
|
||||
| | - Added subnet parameter description in :ref:`Modifying a Subnet <vpc_vpc_0001>`. |
|
||||
| | - Added **Route Settings** to the parameter description in :ref:`Creating a Custom Route Table <vpc_route_0005>`. |
|
||||
| | - Added description about route parameters in :ref:`Modifying a Route <vpc_route_0011>`. |
|
||||
| | |
|
||||
| | Modified the following content based on the RM-584 requirements: |
|
||||
| | |
|
||||
| | - Optimized description about **Next Hop** in :ref:`Adding a Custom Route <vpc_route_0006>`. |
|
||||
| | - Optimized description about the scenario in :ref:`Associating a Subnet with a Route Table <vpc_route_0007>`. |
|
||||
| | - Modified steps in :ref:`Changing the Route Table Associated with a Subnet <vpc_route_0008>`. |
|
||||
| | - Added prerequisites in :ref:`Releasing a Virtual IP Address <vpc_vip_0009>`. |
|
||||
| | - Optimized description about scenarios and prerequisites in :ref:`Deleting a Subnet <vpc_vpc_0002>`. |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
@ -405,7 +396,6 @@ Change History
|
||||
| | Added the following content: |
|
||||
| | |
|
||||
| | - Added :ref:`Security Group Configuration Examples <en-us_topic_0081124350>`. |
|
||||
| | - Added :ref:`Route Table Overview <route_0001>`. |
|
||||
| | - Added :ref:`Modifying an EIP Bandwidth <en-us_topic_0013748743>`. |
|
||||
| | - Added description about disassociating and releasing multiple EIPs at a time in :ref:`Unbinding an EIP from an ECS and Releasing the EIP <vpc_eip_0001>`. |
|
||||
| | |
|
||||
|
||||
@ -44,39 +44,39 @@ Assigning an EIP
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| Parameter | Description | Example Value |
|
||||
+=======================+=======================================================================================================================================================================================================================================================================================================================================================================+=========================+
|
||||
| Region | Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. The region selected for the EIP is its geographical location. | eu-de |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| EIP Type | - **Dynamic BGP**: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails. | Dynamic BGP |
|
||||
| | - **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. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| Billed By | Two options are available: | Dedicated |
|
||||
| | | |
|
||||
| | - **Dedicated**: The bandwidth can be used by only one EIP. | |
|
||||
| | - **Shared**: The bandwidth can be shared by multiple EIPs. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| Bandwidth | The bandwidth size in Mbit/s. | 100 |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| EIP Name | The EIP name. | eip-test |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| Enterprise Project | The enterprise project that the EIP belongs to. | default |
|
||||
| | | |
|
||||
| | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | |
|
||||
| | | |
|
||||
| | For details about creating and managing enterprise projects, see the *Enterprise Management User Guide*. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| Bandwidth Name | The name of the bandwidth. | bandwidth |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| Tag | The EIP tags. Each tag contains a key and value pair. | - Key: Ipv4_key1 |
|
||||
| | | - Value: 192.168.12.10 |
|
||||
| | The tag key and value must meet the requirements listed in :ref:`Table 2 <en-us_topic_0013748738__table36606052153313>`. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
| Quantity | The number of EIPs you want to assign. | 1 |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------+
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Parameter | Description | Example Value |
|
||||
+=======================+=======================================================================================================================================================================================================================================================================================================================================================================+=======================+
|
||||
| Region | Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. The region selected for the EIP is its geographical location. | eu-de |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| EIP Type | - **Dynamic BGP**: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails. | Dynamic BGP |
|
||||
| | - **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. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Billed By | Two options are available: | Dedicated |
|
||||
| | | |
|
||||
| | - **Dedicated**: The bandwidth can be used by only one EIP. | |
|
||||
| | - **Shared**: The bandwidth can be shared by multiple EIPs. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Bandwidth | The bandwidth size in Mbit/s. | 100 |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| EIP Name | The EIP name. | eip-test |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Enterprise Project | The enterprise project that the EIP belongs to. | default |
|
||||
| | | |
|
||||
| | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | |
|
||||
| | | |
|
||||
| | For details about creating and managing enterprise projects, see the *Enterprise Management User Guide*. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Bandwidth Name | The name of the bandwidth. | bandwidth |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Tag | The EIP tags. Each tag contains a key and value pair. | - Key: Ipv4_key1 |
|
||||
| | | - Value: 3005eip |
|
||||
| | The tag key and value must meet the requirements listed in :ref:`Table 2 <en-us_topic_0013748738__table36606052153313>`. | |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
| Quantity | The number of EIPs you want to assign. | 1 |
|
||||
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
|
||||
|
||||
.. _en-us_topic_0013748738__table36606052153313:
|
||||
|
||||
@ -95,7 +95,7 @@ Assigning an EIP
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | 192.168.12.10 |
|
||||
| Value | - Can contain a maximum of 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
|
||||
@ -29,7 +29,7 @@ A tag consists of a key and value pair. :ref:`Table 1 <en-us_topic_0068145818__t
|
||||
| | - Digits | |
|
||||
| | - Special characters, including hyphens (-) and underscores (_) | |
|
||||
+-----------------------+---------------------------------------------------------------------+-----------------------+
|
||||
| Value | - Can contain a maximum of 43 characters. | 192.168.12.10 |
|
||||
| Value | - Can contain a maximum of 43 characters. | 3005eip |
|
||||
| | - Can contain only the following character types: | |
|
||||
| | | |
|
||||
| | - Uppercase letters | |
|
||||
@ -49,17 +49,13 @@ Procedure
|
||||
|
||||
#. Click |image2| in the upper left corner and choose **Network** > **Elastic IP**.
|
||||
|
||||
#. In the upper right corner of the EIP list, click **Search by Tag**.
|
||||
#. Click the search box and then click **Tag** in the drop-down list.
|
||||
|
||||
#. 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.
|
||||
#. 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 **Search**.
|
||||
#. Click **OK**.
|
||||
|
||||
The system displays the EIPs you are looking for based on the entered tag keys and values.
|
||||
|
||||
|
||||
@ -1,15 +0,0 @@
|
||||
:original_name: vpc_faq_0035.html
|
||||
|
||||
.. _vpc_faq_0035:
|
||||
|
||||
How Do I Buy a Shared Bandwidth?
|
||||
================================
|
||||
|
||||
#. Log in to the management console.
|
||||
#. Click |image1| in the upper left corner and select the desired region and project.
|
||||
#. Click |image2| 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.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0141273034.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001454059512.png
|
||||
@ -8,7 +8,6 @@ Bandwidth
|
||||
- :ref:`What Is the Bandwidth Size Range? <vpc_faq_0011>`
|
||||
- :ref:`What Bandwidth Types Are Available? <vpc_faq_0012>`
|
||||
- :ref:`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? <faq_bandwidth_0003>`
|
||||
- :ref:`How Do I Buy a Shared Bandwidth? <vpc_faq_0035>`
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
@ -17,4 +16,3 @@ Bandwidth
|
||||
what_is_the_bandwidth_size_range
|
||||
what_bandwidth_types_are_available
|
||||
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
|
||||
how_do_i_buy_a_shared_bandwidth
|
||||
|
||||
@ -1,8 +0,0 @@
|
||||
:original_name: faq_eip_0010.html
|
||||
|
||||
.. _faq_eip_0010:
|
||||
|
||||
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.
|
||||
10
umn/source/faqs/eips/can_i_change_the_region_of_my_eip.rst
Normal file
10
umn/source/faqs/eips/can_i_change_the_region_of_my_eip.rst
Normal file
@ -0,0 +1,10 @@
|
||||
:original_name: faq_eip_0014.html
|
||||
|
||||
.. _faq_eip_0014:
|
||||
|
||||
Can I Change the Region of My EIP?
|
||||
==================================
|
||||
|
||||
The region of an EIP cannot be changed.
|
||||
|
||||
If you assigned an EIP in region A but need an EIP in region B, you cannot directly change the region of the assigned EIP from A to B. Instead, you have to assign an EIP in region B.
|
||||
@ -8,8 +8,8 @@ EIPs
|
||||
- :ref:`What Is an EIP? <vpc_faq_0013>`
|
||||
- :ref:`Can I Bind an EIP to Multiple ECSs? <vpc_faq_0019>`
|
||||
- :ref:`How Do I Access an ECS with an EIP Bound from the Internet? <vpc_faq_0020>`
|
||||
- :ref:`Can a Bandwidth Be Used by Multiple Accounts? <faq_eip_0010>`
|
||||
- :ref:`Can I Bind an EIP to a Cloud Resource in Another Region? <faq_eip_0012>`
|
||||
- :ref:`Can I Change the Region of My EIP? <faq_eip_0014>`
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
@ -18,5 +18,5 @@ EIPs
|
||||
what_is_an_eip
|
||||
can_i_bind_an_eip_to_multiple_ecss
|
||||
how_do_i_access_an_ecs_with_an_eip_bound_from_the_internet
|
||||
can_a_bandwidth_be_used_by_multiple_accounts
|
||||
can_i_bind_an_eip_to_a_cloud_resource_in_another_region
|
||||
can_i_change_the_region_of_my_eip
|
||||
|
||||
@ -45,5 +45,7 @@ Before dialing the hotline number or sending an email, make sure that the follow
|
||||
- Quota type
|
||||
- Required quota
|
||||
|
||||
`Learn how to obtain the service hotline and email address. <https://open-telekom-cloud.com/en/contact>`__
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0275513364.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0152727234.png
|
||||
|
||||
@ -1,8 +0,0 @@
|
||||
:original_name: vpc_faq_0071.html
|
||||
|
||||
.. _vpc_faq_0071:
|
||||
|
||||
How Many Route Tables Can Be Created for a VPC?
|
||||
===============================================
|
||||
|
||||
Currently, a VPC can have a maximum of 10 route tables by default.
|
||||
@ -7,10 +7,8 @@ Routing
|
||||
|
||||
- :ref:`How Many Routes Can a Route Table Contain? <vpc_faq_0063>`
|
||||
- :ref:`Are There Any Restrictions on Using a Route Table? <vpc_faq_0064>`
|
||||
- :ref:`Will a Route Table Be Billed? <vpc_faq_0065>`
|
||||
- :ref:`Do the Same Routing Priorities Apply to Direct Connect Connections and Custom Routes in the Same VPC? <vpc_faq_0066>`
|
||||
- :ref:`Are There Different Routing Priorities of the VPN and Custom Routes in the Same VPC? <vpc_faq_00001>`
|
||||
- :ref:`How Many Route Tables Can Be Created for a VPC? <vpc_faq_0071>`
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
@ -18,7 +16,5 @@ Routing
|
||||
|
||||
how_many_routes_can_a_route_table_contain
|
||||
are_there_any_restrictions_on_using_a_route_table
|
||||
will_a_route_table_be_billed
|
||||
do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc
|
||||
are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc
|
||||
how_many_route_tables_can_be_created_for_a_vpc
|
||||
|
||||
@ -1,8 +0,0 @@
|
||||
:original_name: vpc_faq_0065.html
|
||||
|
||||
.. _vpc_faq_0065:
|
||||
|
||||
Will a Route Table Be Billed?
|
||||
=============================
|
||||
|
||||
The route table function itself is free, but you are charged for the ECSs and bandwidth that you use together with the route table function.
|
||||
@ -0,0 +1,22 @@
|
||||
:original_name: faq_connection_0001.html
|
||||
|
||||
.. _faq_connection_0001:
|
||||
|
||||
Can a VPC Peering Connection Connect VPCs in Different Regions?
|
||||
===============================================================
|
||||
|
||||
A VPC peering connection only can connect VPCs in the same region.
|
||||
|
||||
:ref:`Figure 1 <faq_connection_0001__en-us_topic_0046655036_fig4721642193711>` shows an application scenario of VPC peering connections.
|
||||
|
||||
- There are two VPCs (VPC-A and VPC-B) in region A that are not connected.
|
||||
- Service servers (ECS-A01 and ECS-A02) are in VPC-A, and database servers (RDS-B01 and RDS-B02) are in VPC-B. The service servers and database servers cannot communicate with each other.
|
||||
|
||||
- You need to create a VPC peering connection (peering-AB) between VPC-A and VPC-B so the service servers and database servers can communicate with each other.
|
||||
|
||||
.. _faq_connection_0001__en-us_topic_0046655036_fig4721642193711:
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0000001512591549.png
|
||||
:alt: **Figure 1** VPC peering connection network diagram
|
||||
|
||||
**Figure 1** VPC peering connection network diagram
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user