diff --git a/umn/source/_static/images/en-us_image_0000001294957952.png b/umn/source/_static/images/en-us_image_0000001294957952.png new file mode 100644 index 0000000..cf85379 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001294957952.png differ diff --git a/umn/source/_static/images/en-us_image_0000001347633729.png b/umn/source/_static/images/en-us_image_0000001347633729.png new file mode 100644 index 0000000..543204c Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001347633729.png differ diff --git a/umn/source/_static/images/en-us_image_0000001347641769.png b/umn/source/_static/images/en-us_image_0000001347641769.png new file mode 100644 index 0000000..fb46bd7 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001347641769.png differ diff --git a/umn/source/_static/images/en-us_image_0000001347809009.png b/umn/source/_static/images/en-us_image_0000001347809009.png new file mode 100644 index 0000000..3002d87 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001347809009.png differ diff --git a/umn/source/_static/images/en-us_image_0000001427131632.png b/umn/source/_static/images/en-us_image_0000001427131632.png deleted file mode 100644 index 14b93c8..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001427131632.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001427301842.png b/umn/source/_static/images/en-us_image_0000001427301842.png deleted file mode 100644 index c98f936..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001427301842.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001432667421.png b/umn/source/_static/images/en-us_image_0000001432667421.png deleted file mode 100644 index 0c55e3f..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001432667421.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001477172813.png b/umn/source/_static/images/en-us_image_0000001477172813.png deleted file mode 100644 index 4c1b38b..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001477172813.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001477452077.png b/umn/source/_static/images/en-us_image_0000001477452077.png deleted file mode 100644 index a4a7050..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001477452077.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001529830673.png b/umn/source/_static/images/en-us_image_0000001529830673.png new file mode 100644 index 0000000..fa5230e Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001529830673.png differ diff --git a/umn/source/_static/images/en-us_image_0000001529948913.png b/umn/source/_static/images/en-us_image_0000001529948913.png deleted file mode 100644 index 9c35502..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001529948913.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001529950265.png b/umn/source/_static/images/en-us_image_0000001529950265.png deleted file mode 100644 index fb489ba..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001529950265.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001530148853.png b/umn/source/_static/images/en-us_image_0000001530148853.png new file mode 100644 index 0000000..404d3e4 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001530148853.png differ diff --git a/umn/source/_static/images/en-us_image_0000001559118632.png b/umn/source/_static/images/en-us_image_0000001559118632.png deleted file mode 100644 index bd6f1f2..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001559118632.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001609438833.png b/umn/source/_static/images/en-us_image_0000001609438833.png new file mode 100644 index 0000000..69b3768 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001609438833.png differ diff --git a/umn/source/_static/images/en-us_image_0000001656353678.png b/umn/source/_static/images/en-us_image_0000001656353678.png new file mode 100644 index 0000000..d20226b Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001656353678.png differ diff --git a/umn/source/_static/images/en-us_image_0000001656513070.png b/umn/source/_static/images/en-us_image_0000001656513070.png new file mode 100644 index 0000000..022a859 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001656513070.png differ diff --git a/umn/source/associations/association_overview.rst b/umn/source/associations/association_overview.rst index 69e8fe0..bb4673a 100644 --- a/umn/source/associations/association_overview.rst +++ b/umn/source/associations/association_overview.rst @@ -10,26 +10,23 @@ Each attachment can be associated with one route table for: - Packet forwarding: Packets from the attachment are forwarded through the routes specified in the associated route table. - Route propagation: The routes in the associated route tables are automatically propagated to the route table of the attachment. -.. _er_01_0030__fig13563243183610: -.. figure:: /_static/images/en-us_image_0000001477452077.png +.. figure:: /_static/images/en-us_image_0000001347641769.png :alt: **Figure 1** Associations **Figure 1** Associations .. table:: **Table 1** Association description - +-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Attachment Type | Route Propagation | Way to Create Association | Description | - +=================+===================+==============================================================================================================================================================================================================+=======================================================================================================================================================================================+ - | VPC | Not supported | - Auto creation: If **Default Route Table Association** is enabled and the default association route table is specified, attachments are automatically associated with the default association route table. | Each attachment can only be associated with one route table. Associations between attachments in :ref:`Figure 1 ` are described as follows: | - | | | | | - | | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router `. | - Auto creation: The system automatically associates attachments, such as virtual gateway 1, VPC 1, and VPN gateway 1, with the default route table of the enterprise router. | - | | | - If you want to enable this function after an enterprise router is created, refer to :ref:`Modifying Settings of an Enterprise Router `. | - Manual creation: You need to manually create associations in the custom route table of the enterprise router for attachments, such as VPC 2, VPN gateway 2, and virtual gateway 2. | - | | | | | - | | | - Manual creation: You can select a route table and create an association in it to associate an attachment with the route table. For details, see :ref:`Creating an Association `. | | - +-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Virtual gateway | Supported | | | - +-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | VPN gateway | Supported | | | - +-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-----------------+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Attachment Type | Route Learning | Way to Create Association | Description | + +=================+=================+====================================================================================================================================================================================================================================+===========================================================================================================================================================================================+ + | VPC | Not supported | - Auto creation: If **Default Route Table Association** is enabled and the default association route table is specified, attachments are automatically associated with the default association route table. | Each attachment can only be associated with one route table. Associations between attachments in :ref:`Association Overview ` are described as follows: | + | | | | | + | | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router `. | - Auto creation: The system automatically associates attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments, with the default route table of the enterprise router. | + | | | - If you want to enable this function after an enterprise router is created, refer to :ref:`Modifying an Enterprise Router `. | - Manual creation: You need to manually create associations in the custom route table of the enterprise router for attachments, such as VPC 3, VPC 4, and virtual gateway 2 attachments. | + | | | | | + | | | - Manual creation: You can select a route table and create an association in it to associate an attachment with the route table. For details, see :ref:`Creating an Association for an Attachment in a Route Table `. | | + +-----------------+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Virtual gateway | Supported | | | + +-----------------+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/associations/creating_an_association.rst b/umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst similarity index 95% rename from umn/source/associations/creating_an_association.rst rename to umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst index e6a7dc1..677e0a0 100644 --- a/umn/source/associations/creating_an_association.rst +++ b/umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst @@ -2,8 +2,8 @@ .. _er_01_0031: -Creating an Association -======================= +Creating an Association for an Attachment in a Route Table +========================================================== Scenarios --------- @@ -52,7 +52,6 @@ Procedure | | | | | | - **VPC** | | | | - **Virtual gateway** | | - | | - **VPN gateway** | | | | | | | | For more information, see :ref:`Attachment Overview `. | | +-----------------------+-------------------------------------------------------------------------------------+-----------------------+ diff --git a/umn/source/associations/deleting_an_association.rst b/umn/source/associations/deleting_an_association_from_a_route_table.rst similarity index 92% rename from umn/source/associations/deleting_an_association.rst rename to umn/source/associations/deleting_an_association_from_a_route_table.rst index b87ffb3..941a6ec 100644 --- a/umn/source/associations/deleting_an_association.rst +++ b/umn/source/associations/deleting_an_association_from_a_route_table.rst @@ -2,8 +2,8 @@ .. _er_01_0033: -Deleting an Association -======================= +Deleting an Association from a Route Table +========================================== Scenarios --------- diff --git a/umn/source/associations/index.rst b/umn/source/associations/index.rst index 1bc3e07..06128a6 100644 --- a/umn/source/associations/index.rst +++ b/umn/source/associations/index.rst @@ -6,15 +6,15 @@ Associations ============ - :ref:`Association Overview ` -- :ref:`Creating an Association ` -- :ref:`Viewing an Association ` -- :ref:`Deleting an Association ` +- :ref:`Creating an Association for an Attachment in a Route Table ` +- :ref:`Viewing Associations in a Route Table ` +- :ref:`Deleting an Association from a Route Table ` .. toctree:: :maxdepth: 1 :hidden: association_overview - creating_an_association - viewing_an_association - deleting_an_association + creating_an_association_for_an_attachment_in_a_route_table + viewing_associations_in_a_route_table + deleting_an_association_from_a_route_table diff --git a/umn/source/associations/viewing_an_association.rst b/umn/source/associations/viewing_associations_in_a_route_table.rst similarity index 71% rename from umn/source/associations/viewing_an_association.rst rename to umn/source/associations/viewing_associations_in_a_route_table.rst index 066b63e..e3b6f9f 100644 --- a/umn/source/associations/viewing_an_association.rst +++ b/umn/source/associations/viewing_associations_in_a_route_table.rst @@ -2,8 +2,8 @@ .. _er_01_0032: -Viewing an Association -====================== +Viewing Associations in a Route Table +===================================== Scenarios --------- @@ -28,8 +28,14 @@ Procedure - In the upper right corner of the enterprise router, click **Manage Route Table**. - Click the enterprise router name and click **Route Tables**. + + .. figure:: /_static/images/en-us_image_0000001656513070.png + :alt: **Figure 1** Viewing associations + + **Figure 1** Viewing associations + #. Click the route table where you want to view its associations. On the **Associations** tab page, view the associations. - All attachments associated with the route table are also displayed. + All attachments associated with the route table are displayed in the list. You can view their settings such as the ID, status, and name of each attachment. .. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/attachments/adding_vpc_attachments_to_an_enterprise_router.rst b/umn/source/attachments/adding_vpc_attachments_to_an_enterprise_router.rst index fb07e58..4fe8cb3 100644 --- a/umn/source/attachments/adding_vpc_attachments_to_an_enterprise_router.rst +++ b/umn/source/attachments/adding_vpc_attachments_to_an_enterprise_router.rst @@ -42,7 +42,7 @@ Procedure .. _er_01_0070__table7204821194013: - .. table:: **Table 1** Parameters for creating an attachment + .. table:: **Table 1** Parameters for adding a VPC attachment +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ | Parameter | Setting | Example Value | @@ -56,9 +56,9 @@ Procedure +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ | Attachment Type | Mandatory | - Attachment Type: VPC | | | | - VPC: vpc-demo-01 | - | | a. **VPC** is selected by default, indicating that the instance to be attached to the enterprise router is a VPC. | - Subnet: subnet-demo-01 | + | | a. Select the attachment type. Select **VPC**, indicating that the instance to be attached to the enterprise router is a VPC. | - Subnet: subnet-demo-01 | | | | | - | | The methods for creating attachments vary by attachment type. For details, see :ref:`Attachment Overview `. | | + | | The methods for creating attachments vary depending on the attachment type. For details, see :ref:`Attachment Overview `. | | | | | | | | b. Select the VPC to be attached to the enterprise router. You can enter a VPC name to quickly find the target VPC. | | | | | | @@ -96,16 +96,16 @@ Procedure Follow-up Procedure ------------------- -- If **Default Route Table Association** and **Default Route Table Propagation** are not enabled for an enterprise router, you need to: +If **Default Route Table Association** and **Default Route Table Propagation** are not enabled for an enterprise router, you need to: - #. Create a custom route table for the enterprise router. For details, see :ref:`Creating a Route Table `. - #. Create associations for the attachments of the enterprise router. For details, see :ref:`Creating an Association `. - #. Use either of the following methods to add routes for the attachment to the route table: +#. Create a custom route table for the enterprise router. For details, see :ref:`Creating a Route Table `. +#. Create associations for the attachments of the enterprise router. For details, see :ref:`Creating an Association for an Attachment in a Route Table `. +#. Use either of the following methods to add routes for the attachment to the route table: - - Create a propagation in the route table. For details, see :ref:`Creating a Propagation `. + - Create a propagation in the route table. For details, see :ref:`Creating a Propagation for an Attachment in the Route Table `. - After the propagation is created, routes of the attachments to the enterprise router will be automatically propagated to the route table of the enterprise router. + After the propagation is created, routes of the attachments to the enterprise router will be automatically propagated to the route table of the enterprise router. - - Add static routes to the route table. For details, see :ref:`Creating a Static Route `. + - Add static routes to the route table. For details, see :ref:`Creating a Static Route `. .. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/attachments/attachment_overview.rst b/umn/source/attachments/attachment_overview.rst index a6ae83e..c201ece 100644 --- a/umn/source/attachments/attachment_overview.rst +++ b/umn/source/attachments/attachment_overview.rst @@ -8,19 +8,17 @@ Attachment Overview You can create an attachment to attach a network instance to an enterprise router. The attachment type varies according to the network instance. -.. figure:: /_static/images/en-us_image_0000001427131632.png +.. figure:: /_static/images/en-us_image_0000001294957952.png :alt: **Figure 1** Attachments **Figure 1** Attachments .. table:: **Table 1** Attachments - +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ - | Attachment Type | Network Instance | Create Attachment | View Attachment | Delete Attachment | - +============================+===================================+========================================================================================================================================================================+=========================================================+===========================================================+ - | VPC attachment | VPC | :ref:`Adding VPC Attachments to an Enterprise Router ` | :ref:`Viewing Details About an Attachment ` | :ref:`Deleting a VPC Attachment ` | - +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ - | Virtual gateway attachment | Virtual gateway of Direct Connect | Add virtual gateway attachments to an enterprise router. To create a virtual gateway, refer to "Establishing Network Connectivity" in the *Direct Connect User Guide*. | | :ref:`Deleting a Virtual Gateway Attachment ` | - +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ - | VPN gateway attachment | VPN gateway | Add VPN gateway attachments to an enterprise router. To create a VPN gateway, refer to "Creating a VPN Gateway" in the *Virtual Private Network User Guide*. | | :ref:`Deleting a VPN Gateway Attachment ` | - +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ + +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ + | Attachment Type | Network Instance | Create Attachment | View Attachment | Delete Attachment | + +============================+===================================+====================================================================================================================================================================================================================================================================================+=========================================================+===========================================================+ + | VPC attachment | VPC | :ref:`Adding VPC Attachments to an Enterprise Router ` | :ref:`Viewing Details About an Attachment ` | :ref:`Deleting a VPC Attachment ` | + +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ + | Virtual gateway attachment | Virtual gateway of Direct Connect | Attach a virtual gateway to an enterprise router. For details, see `Connecting Your On-Premises Data Center to the Cloud `__. | | :ref:`Deleting a Virtual Gateway Attachment ` | + +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ diff --git a/umn/source/attachments/deleting_an_attachment/deleting_a_vpc_attachment.rst b/umn/source/attachments/deleting_an_attachment/deleting_a_vpc_attachment.rst index 4aa24c2..6d4ab15 100644 --- a/umn/source/attachments/deleting_an_attachment/deleting_a_vpc_attachment.rst +++ b/umn/source/attachments/deleting_an_attachment/deleting_a_vpc_attachment.rst @@ -39,7 +39,7 @@ Procedure A confirmation dialog box is displayed. -#. Click **Yes**. +#. Confirm the information and click **Yes**. A deleted attachment cannot be recovered. diff --git a/umn/source/attachments/deleting_an_attachment/deleting_a_vpn_gateway_attachment.rst b/umn/source/attachments/deleting_an_attachment/deleting_a_vpn_gateway_attachment.rst deleted file mode 100644 index 478da68..0000000 --- a/umn/source/attachments/deleting_an_attachment/deleting_a_vpn_gateway_attachment.rst +++ /dev/null @@ -1,63 +0,0 @@ -:original_name: er_01_0114.html - -.. _er_01_0114: - -Deleting a VPN Gateway Attachment -================================= - -Scenarios ---------- - -This section describes how to delete a VPN gateway attachment from an enterprise router. - -Notes and Constraints ---------------------- - -- Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table. - -- Deleting an attachment will also delete its flow logs. - -Procedure ---------- - -#. Log in to the management console. - -#. Click |image1| in the upper left corner and select the desired region and project. - -#. Click **Service List** and choose **Networking** > **Enterprise Router**. - - The **Enterprise Router** homepage is displayed. - -#. Search for the target enterprise router by name. - -#. Go to the **Attachments** tab page using either of the following methods: - - - In the upper right corner of the enterprise router, click **Manage Attachment**. - - Click the enterprise router name and click **Attachments**. - - .. important:: - - A VPN gateway attachment cannot be directly deleted on the **Attachments** page of the enterprise router. - - A VPN gateway attachment will be automatically deleted after you perform the following operations to delete its VPN connections, unbind the EIP from the VPN gateway, and delete the VPN gateway. - -#. Locate the row that contains the target VPN gateway attachment and click the attached resource. - - Example: vpngw-demo - - The VPN gateway attachment details page is displayed. - -#. On the attachment details page, click |image2| in the upper left corner. - - The VPN gateway list is displayed. - -#. In the VPN gateway list, locate the row that contains the target VPN gateway, click **More** in the **Operation** column, and click **Delete**. - - A confirmation dialog box is displayed. - -#. Click **Yes**. - - A deleted VPN gateway cannot be recovered. - -.. |image1| image:: /_static/images/en-us_image_0000001190483836.png -.. |image2| image:: /_static/images/en-us_image_0000001432667421.png diff --git a/umn/source/attachments/deleting_an_attachment/index.rst b/umn/source/attachments/deleting_an_attachment/index.rst index e92e3ed..c2b3a2c 100644 --- a/umn/source/attachments/deleting_an_attachment/index.rst +++ b/umn/source/attachments/deleting_an_attachment/index.rst @@ -7,7 +7,6 @@ Deleting an Attachment - :ref:`Deleting a VPC Attachment ` - :ref:`Deleting a Virtual Gateway Attachment ` -- :ref:`Deleting a VPN Gateway Attachment ` .. toctree:: :maxdepth: 1 @@ -15,4 +14,3 @@ Deleting an Attachment deleting_a_vpc_attachment deleting_a_virtual_gateway_attachment - deleting_a_vpn_gateway_attachment diff --git a/umn/source/attachments/viewing_details_about_an_attachment.rst b/umn/source/attachments/viewing_details_about_an_attachment.rst index 9cbc5a0..8bfc808 100644 --- a/umn/source/attachments/viewing_details_about_an_attachment.rst +++ b/umn/source/attachments/viewing_details_about_an_attachment.rst @@ -32,7 +32,7 @@ Procedure #. On the **Attachments** tab page, you can view: - - In the attachment list, you can view the attachment status, attachment type, and attached resource. + - In the attachment list, you can view information such as the name, status, type, and attached resource. - If you click the attachment name, you can view more information about the attachment on the displayed page, including the attachment ID, creation time, and tags. - If you click the attached resource, you will go to the details page of the attached resource. diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index 5c8418a..27d1d83 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -5,12 +5,19 @@ Change History ============== -+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| Released On | Description | -+===================================+==========================================================================================================================================================================================================================================================================================================================+ -| 2023-05-30 | Updated the following content: | -| | | -| | Added descriptions of flow logs in :ref:`Functions `, :ref:`Deleting an Enterprise Router `, :ref:`Deleting a VPC Attachment `, :ref:`Deleting a Virtual Gateway Attachment `, :ref:`Deleting a VPN Gateway Attachment `, and :ref:`Flow Logs `. | -+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-03-24 | This issue is the first official release. | -+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Released On | Description | ++===================================+==================================================================================================================================================================================================================================================================+ +| 2023-09-22 | Modified the following content: | +| | | +| | - Added the link to the Direct Connect operation guide in :ref:`Attachment Overview `. | +| | - Modified the maximum number of tags that can be added in :ref:`Overview `. | +| | - Added detailed descriptions and screenshots in :ref:`Viewing Associations in a Route Table ` and :ref:`Viewing a Propagation in a Route Table `. | +| | - Added the link to the *Cloud Trace Service User Guide* in :ref:`Viewing Traces `. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-05-30 | Modified the following content: | +| | | +| | Added descriptions of flow logs in :ref:`Functions `, :ref:`Deleting an Enterprise Router `, :ref:`Deleting a VPC Attachment `, :ref:`Deleting a Virtual Gateway Attachment ` and :ref:`Flow Logs `. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-03-24 | This issue is the first official release. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/conf.py b/umn/source/conf.py index e151cc1..8e777c4 100644 --- a/umn/source/conf.py +++ b/umn/source/conf.py @@ -18,7 +18,7 @@ import os import sys extensions = [ - 'otcdocstheme' + 'otcdocstheme', ] otcdocs_auto_name = False diff --git a/umn/source/enterprise_routers/changing_the_azs_of_an_enterprise_router.rst b/umn/source/enterprise_routers/changing_the_azs_of_an_enterprise_router.rst deleted file mode 100644 index 3984a8b..0000000 --- a/umn/source/enterprise_routers/changing_the_azs_of_an_enterprise_router.rst +++ /dev/null @@ -1,58 +0,0 @@ -:original_name: er_01_0015.html - -.. _er_01_0015: - -Changing the AZs of an Enterprise Router -======================================== - -Scenarios ---------- - -This section describes how to change the AZs of an enterprise router, which will not interrupt network communication. - -Procedure ---------- - -#. Log in to the management console. - -#. Click |image1| in the upper left corner and select the desired region and project. - -#. Click **Service List** and choose **Networking** > **Enterprise Router**. - - The **Enterprise Router** homepage is displayed. - -#. Search for the target enterprise router by name. - -#. In the upper right corner of the target enterprise router, choose **More** > **Change AZ**. - - The **Change AZ** page is displayed. - -#. Change AZs according to :ref:`Table 1 `. - - .. _er_01_0015__table7204821194013: - - .. table:: **Table 1** Parameter description - - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Setting | Example Value | - +=======================+=================================================================================================================================================================================================================================================================================================+=======================+ - | AZ | Mandatory | AZ1 | - | | | | - | | An AZ is a physical location where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. Each region contains multiple AZs. If one AZ is unavailable, the other AZs in the same region continue to provide services. | | - | | | | - | | Traffic in an AZ is preferentially transmitted to the enterprise router in the same AZ to reduce latency. | | - | | | | - | | Changing the AZs of an enterprise router does not interrupt network communication. | | - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - -#. Click **Next**. - -#. Confirm the AZs and click **Submit**. - - The enterprise router list is displayed. - -#. Check the enterprise router status. - - If the status changes from **Modifying** to **Normal**, the AZs of the enterprise router are successfully changed. - -.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/enterprise_routers/creating_an_enterprise_router.rst b/umn/source/enterprise_routers/creating_an_enterprise_router.rst index fdd4486..77cdf14 100644 --- a/umn/source/enterprise_routers/creating_an_enterprise_router.rst +++ b/umn/source/enterprise_routers/creating_an_enterprise_router.rst @@ -31,87 +31,87 @@ Procedure .. table:: **Table 1** Parameters for creating an enterprise router - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Setting | Example Value | - +=================================+=================================================================================================================================================================================================================================================================================================+=======================+ - | Region | Mandatory | ``-`` | - | | | | - | | Select the region nearest to you to ensure the lowest latency possible. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | AZ | Mandatory | AZ1 | - | | | | - | | An AZ is a physical location where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. Each region contains multiple AZs. If one AZ is unavailable, the other AZs in the same region continue to provide services. | AZ2 | - | | | | - | | We recommend you to select two AZs. The enterprise router will be deployed in both AZs that work in active-active mode, ensuring reliability for disaster recovery. | | - | | | | - | | Traffic in an AZ is preferentially transmitted to the enterprise router in the same AZ to reduce latency. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Name | Mandatory | er-test-01 | - | | | | - | | Enter a name for the enterprise router. The name: | | - | | | | - | | - Must contain 1 to 64 characters. | | - | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | ASN | Mandatory | 64512 | - | | | | - | | An autonomous system is an IP network that is managed by an entity and has the same routing policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them. | | - | | | | - | | You can use the default ASN, or specify one from 64512 to 65534 or from 4200000000 to 4294967294. | | - | | | | - | | Networks in the same region can be considered as an AS. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Default Route Table Association | Optional | Enable | - | | | | - | | Enabled by default | | - | | | | - | | Enabling **Default Route Table Association** can simplify network configurations. After this function is enabled: | | - | | | | - | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default association route table. | | - | | | | - | | After the enterprise router is created, you can create a custom route table and set it as the default association route table to replace the original one if needed. For details, see :ref:`Modifying Settings of an Enterprise Router `. | | - | | | | - | | b. If you create an attachment to this enterprise router, the attachment will be automatically associated with the default association route table. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Default Route Table Propagation | Optional | Enable | - | | | | - | | Enabled by default | | - | | | | - | | Enabling **Default Route Table Propagation** can simplify network configurations. After this function is enabled: | | - | | | | - | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default propagation route table. | | - | | | | - | | If both **Default Route Table Association** and **Default Route Table Propagation** are enabled, **defaultRouteTable** is not only the default association route table but also the default propagation route table. | | - | | | | - | | After the enterprise router is created, you can create a custom route table and set it as the default propagation route table to replace the original one if needed. For details, see :ref:`Modifying Settings of an Enterprise Router `. | | - | | | | - | | b. If you create an attachment to this enterprise router, the attachment will be automatically propagated to the default propagation route table. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Auto Accept Shared Attachments | Optional | Disable | - | | | | - | | As the owner, you can share your enterprise router with other users. These other users can create attachments for your enterprise router. | | - | | | | - | | - If you do not select this option, you must manually accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | - | | - If you select this option, the system will automatically accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | - | | | | - | | For details, see :ref:`Sharing Overview `. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Enterprise Project | Mandatory | default | - | | | | - | | Select an enterprise project that the enterprise router will be added to. | | - | | | | - | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The default project is **default**. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Tag | Optional | **Tag key**: test | - | | | | - | | Add tags to help you quickly find your enterprise router. | **Tag value**: 01 | - | | | | - | | For details, see :ref:`Overview `. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Description | Optional | ``-`` | - | | | | - | | Describe the enterprise router for easy identification. | | - +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=================================+===================================================================================================================================================================================================================================================================================================+=======================+ + | Region | Mandatory | ``-`` | + | | | | + | | Select the region nearest to you to ensure the lowest latency possible. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | AZ | Mandatory | AZ1 | + | | | | + | | An AZ is a physical location where resources use independent power supplies and networks. AZs are physically isolated but interconnected through an internal network. Each region contains multiple AZs. If one AZ is unavailable, the other AZs in the same region continue to provide services. | AZ2 | + | | | | + | | We recommend you to select two AZs. The enterprise router will be deployed in both AZs that work in active-active mode, ensuring reliability and disaster recovery. | | + | | | | + | | Traffic in an AZ is preferentially transmitted to the enterprise router in the same AZ to reduce latency. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Name | Mandatory | er-test-01 | + | | | | + | | Enter a name for the enterprise router. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | ASN | Mandatory | 64512 | + | | | | + | | An autonomous system is an IP network that is managed by an entity and has the same routing policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them. | | + | | | | + | | You can use the default ASN, or specify one from 64512 to 65534 or from 4200000000 to 4294967294. | | + | | | | + | | Networks in the same region can be considered as an AS. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Default Route Table Association | Optional | Enable | + | | | | + | | Enabled by default | | + | | | | + | | Enabling **Default Route Table Association** can simplify network configurations. After this function is enabled: | | + | | | | + | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default association route table. | | + | | | | + | | After the enterprise router is created, you can create a custom route table and set it as the default association route table to replace the original one if needed. For details, see :ref:`Modifying an Enterprise Router `. | | + | | | | + | | b. If you create an attachment to this enterprise router, the attachment will be automatically associated with the default association route table. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Default Route Table Propagation | Optional | Enable | + | | | | + | | Enabled by default | | + | | | | + | | Enabling **Default Route Table Propagation** can simplify network configurations. After this function is enabled: | | + | | | | + | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default propagation route table. | | + | | | | + | | If both **Default Route Table Association** and **Default Route Table Propagation** are enabled, **defaultRouteTable** is not only the default association route table but also the default propagation route table. | | + | | | | + | | After the enterprise router is created, you can create a custom route table and set it as the default propagation route table to replace the original one if needed. For details, see :ref:`Modifying an Enterprise Router `. | | + | | | | + | | b. If you create an attachment to this enterprise router, the attachment will be automatically propagated to the default propagation route table. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Auto Accept Shared Attachments | Optional | Disable | + | | | | + | | As the owner, you can share your enterprise router with other users. These other users can create attachments for your enterprise router. | | + | | | | + | | - If you do not select this option, you must manually accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | + | | - If you select this option, the system will automatically accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | + | | | | + | | For details, see :ref:`Sharing Overview `. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Enterprise Project | Mandatory | default | + | | | | + | | Select an enterprise project that the enterprise router will be added to. | | + | | | | + | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The default project is **default**. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Tag | Optional | **Tag key**: test | + | | | | + | | Add tags to help you quickly find your enterprise router. | **Tag value**: 01 | + | | | | + | | For details, see :ref:`Overview `. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | Optional | ``-`` | + | | | | + | | Describe the enterprise router for easy identification. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ #. Click **Create Now**. @@ -131,10 +131,10 @@ Follow-Up Operations - If **Default Route Table Association** and **Default Route Table Propagation** are not enabled for an enterprise router, you need to: #. Create a custom route table for the enterprise router. For details, see :ref:`Creating a Route Table `. - #. Create associations for the attachments of the enterprise router. For details, see :ref:`Creating an Association `. + #. Create associations for the attachments of the enterprise router. For details, see :ref:`Creating an Association for an Attachment in a Route Table `. #. Use either of the following methods to add routes for the attachment to the route table: - - Create a propagation in the route table. For details, see :ref:`Creating a Propagation `. + - Create a propagation in the route table. For details, see :ref:`Creating a Propagation for an Attachment in the Route Table `. After the propagation is created, routes of the attachments to the enterprise router will be automatically propagated to the route table of the enterprise router. diff --git a/umn/source/enterprise_routers/deleting_an_enterprise_router.rst b/umn/source/enterprise_routers/deleting_an_enterprise_router.rst index 21022c7..655299a 100644 --- a/umn/source/enterprise_routers/deleting_an_enterprise_router.rst +++ b/umn/source/enterprise_routers/deleting_an_enterprise_router.rst @@ -15,7 +15,7 @@ Notes and Constraints - An enterprise router that has attachments cannot be deleted. To delete such an enterprise router, delete its attachments first. For details, see :ref:`Deleting an Attachment `. - An enterprise router that has route tables can be deleted directly. -- An enterprise router that has sharings can be deleted directly. +- An enterprise router that is shared with other accounts can be deleted directly. - Deleting an enterprise router will also delete all of its flow logs. Procedure diff --git a/umn/source/enterprise_routers/index.rst b/umn/source/enterprise_routers/index.rst index 62dd8bb..88372c0 100644 --- a/umn/source/enterprise_routers/index.rst +++ b/umn/source/enterprise_routers/index.rst @@ -6,8 +6,7 @@ Enterprise Routers ================== - :ref:`Creating an Enterprise Router ` -- :ref:`Modifying Settings of an Enterprise Router ` -- :ref:`Changing the AZs of an Enterprise Router ` +- :ref:`Modifying an Enterprise Router ` - :ref:`Viewing an Enterprise Router ` - :ref:`Deleting an Enterprise Router ` @@ -16,7 +15,6 @@ Enterprise Routers :hidden: creating_an_enterprise_router - modifying_settings_of_an_enterprise_router - changing_the_azs_of_an_enterprise_router + modifying_an_enterprise_router viewing_an_enterprise_router deleting_an_enterprise_router diff --git a/umn/source/enterprise_routers/modifying_settings_of_an_enterprise_router.rst b/umn/source/enterprise_routers/modifying_an_enterprise_router.rst similarity index 99% rename from umn/source/enterprise_routers/modifying_settings_of_an_enterprise_router.rst rename to umn/source/enterprise_routers/modifying_an_enterprise_router.rst index bb1f10c..3edb3b4 100644 --- a/umn/source/enterprise_routers/modifying_settings_of_an_enterprise_router.rst +++ b/umn/source/enterprise_routers/modifying_an_enterprise_router.rst @@ -2,8 +2,8 @@ .. _er_01_0013: -Modifying Settings of an Enterprise Router -========================================== +Modifying an Enterprise Router +============================== Scenarios --------- diff --git a/umn/source/faq/how_do_i_enable_two_attachments_of_an_enterprise_router_to_learn_routes_from_each_other.rst b/umn/source/faq/how_do_i_enable_two_attachments_of_an_enterprise_router_to_learn_routes_from_each_other.rst index 53f7c6f..2aea7ce 100644 --- a/umn/source/faq/how_do_i_enable_two_attachments_of_an_enterprise_router_to_learn_routes_from_each_other.rst +++ b/umn/source/faq/how_do_i_enable_two_attachments_of_an_enterprise_router_to_learn_routes_from_each_other.rst @@ -7,11 +7,11 @@ How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Eac If you want two attachments of an enterprise router to learn routes from each other, the router and each attachment must have a unique ASN. In this way, the enterprise router advertises the learned route information between the attachments. -If you want a virtual gateway and a VPN gateway attached to an enterprise router to learn routes from each other, their ASNs can be as follows: +If you want two virtual gateways attached to the same enterprise router to learn routes from each other, their ASNs can be as follows: - Enterprise router: 64512 -- Virtual gateway attachment: 64513 (BGP ASN of the virtual gateway) -- VPN gateway attachment: 64515 (BGP ASN of the VPN gateway) +- Virtual gateway attachment A: 64513 (BGP ASN of virtual gateway A) +- Virtual gateway attachment B: 64515 (BGP ASN of virtual gateway B) .. note:: diff --git a/umn/source/faq/how_do_i_route_traffic_to_100.64.x.x_through_an_enterprise_router.rst b/umn/source/faq/how_do_i_route_traffic_to_100.64.x.x_through_an_enterprise_router.rst index 375c10c..74eb50e 100644 --- a/umn/source/faq/how_do_i_route_traffic_to_100.64.x.x_through_an_enterprise_router.rst +++ b/umn/source/faq/how_do_i_route_traffic_to_100.64.x.x_through_an_enterprise_router.rst @@ -102,15 +102,13 @@ The required resources and routes are as follows: | | 100.64.x.x | Virtual gateway attachment | Propagated route | +-------------------+-----------------------------------------------+----------------------------+-----------------------+ -#. to request 100.64.x.x as the destination for :ref:`4 `. - #. Create a transit VPC, attach it to the enterprise router, and associate the transit VPC with the default route table of the enterprise router. - - The subnet of the transit VPC cannot overlap with that of the service VPC. Otherwise, the VPC peering connection to be created in :ref:`3 ` cannot take effect. - - The transit VPC cannot have the following situations. Otherwise, the default route (0.0.0.0/0) to be configured in :ref:`4 ` cannot forward traffic. + - The subnet of the transit VPC cannot overlap with that of the service VPC. Otherwise, the VPC peering connection to be created in :ref:`2 ` cannot take effect. + - The transit VPC cannot have the following situations. Otherwise, the default route (0.0.0.0/0) to be configured in :ref:`3 ` cannot forward traffic. - An ECS in the VPC has an EIP bound. - - The VPC is being used by ELB, NAT Gateway, or VPC Endpoint. + - The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS. #. .. _er_01_0122__li14564823993: @@ -118,7 +116,7 @@ The required resources and routes are as follows: .. important:: - You do not need to add routes for the VPC peering connection. For details about the routes to be added, see :ref:`4 `. + You do not need to add routes for the VPC peering connection. For details about the routes to be added, see :ref:`3 `. #. .. _er_01_0122__li92642018194217: diff --git a/umn/source/faq/why_traffic_cant_be_forwarded_from_a_vpc_with_a_route_destination_of_0.0.0.0_0_to_its_enterprise_router.rst b/umn/source/faq/why_traffic_cant_be_forwarded_from_a_vpc_with_a_route_destination_of_0.0.0.0_0_to_its_enterprise_router.rst index f9f8a44..2464eae 100644 --- a/umn/source/faq/why_traffic_cant_be_forwarded_from_a_vpc_with_a_route_destination_of_0.0.0.0_0_to_its_enterprise_router.rst +++ b/umn/source/faq/why_traffic_cant_be_forwarded_from_a_vpc_with_a_route_destination_of_0.0.0.0_0_to_its_enterprise_router.rst @@ -8,7 +8,7 @@ Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0 Scenarios --------- -Traffic cannot be forwarded from a VPC to the enterprise router that the VPC is attached if you set the destination of a route in the VPC route table to 0.0.0.0/0 and: +Traffic cannot be forwarded from a VPC to the enterprise router that it is attached to if you set the destination of a route in the VPC route table to 0.0.0.0/0 and: - An ECS in the VPC has an EIP bound. @@ -16,7 +16,7 @@ Traffic cannot be forwarded from a VPC to the enterprise router that the VPC is Refer to solution 1. -- The VPC is being used by ELB, NAT Gateway, or VPC Endpoint. +- The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS. .. note:: diff --git a/umn/source/flow_logs/creating_a_flow_log.rst b/umn/source/flow_logs/creating_a_flow_log.rst index 7c4a809..9d43679 100644 --- a/umn/source/flow_logs/creating_a_flow_log.rst +++ b/umn/source/flow_logs/creating_a_flow_log.rst @@ -30,9 +30,9 @@ Procedure #. Click the enterprise router name and click **Flow Logs**. -#. On the **Flow Logs** tab, click **Create Flow Log**. +#. On the **Flow Logs** tab page, click **Create Flow Log**. - The **Create Flow Log** page is displayed. + The **Create Flow Log** dialog box is displayed. Configure the parameters based on :ref:`Table 1 `. @@ -56,7 +56,6 @@ Procedure | | | | | | - VPC | | | | - Virtual gateway: Virtual gateway of Direct Connect | | - | | - VPN gateway | | +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Resource | Mandatory | vgw-ab | | | | | diff --git a/umn/source/flow_logs/flow_log_overview.rst b/umn/source/flow_logs/flow_log_overview.rst index a203b84..6e6f72f 100644 --- a/umn/source/flow_logs/flow_log_overview.rst +++ b/umn/source/flow_logs/flow_log_overview.rst @@ -14,7 +14,6 @@ Flow logs can capture traffic of the following types of attachments: - VPC - Virtual gateway -- VPN gateway Creation Process ---------------- diff --git a/umn/source/flow_logs/viewing_details_about_a_flow_log.rst b/umn/source/flow_logs/viewing_details_about_a_flow_log.rst index 519c90c..b069fd3 100644 --- a/umn/source/flow_logs/viewing_details_about_a_flow_log.rst +++ b/umn/source/flow_logs/viewing_details_about_a_flow_log.rst @@ -10,6 +10,11 @@ Scenarios This section describes how to view details about a flow log, including the attachment ID, source/destination address, source/destination port, data packet size, and packet quantity. +Constraints +----------- + +Flow logs are generated every 10 minutes. After creating a VPC flow log, you need to wait about 10 minutes before you can view the flow log record. + Procedure --------- diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_2_create_an_enterprise_router.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_2_create_an_enterprise_router.rst index 21f9fa6..b1e898a 100644 --- a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_2_create_an_enterprise_router.rst +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_2_create_an_enterprise_router.rst @@ -42,13 +42,13 @@ Procedure +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Name | Specify the enterprise router name. You can change it after the enterprise router is created. | er-test-01 | +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | ASN | Set the Autonomous System Number for the cloud side of a Border Gateway Protocol (BGP) session. You can change it after the enterprise router is created. | 64512 | + | ASN | Set the Autonomous System Number (ASN) for the cloud side of a Border Gateway Protocol (BGP) session. You cannot change it after the enterprise router is created. | 64512 | +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Default Route Table Association | If you select this option, you do not need to create route tables or associations. You can change your option after the enterprise router is created. | Enable | +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Default Route Table Propagation | If you select this option, you do not need to create route tables, propagations, or routes. You can change your option after the enterprise router is created. | Enable | +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Auto Accept Shared Attachments | If you do not select this option, you must accept the requests for creating attachments to this enterprise router from other users that this enterprise router is shared with. | Disable | + | Auto Accept Shared Attachments | If you do not select this option, you must accept the requests for creating attachments to this enterprise router from other users with whom this enterprise router is shared. | Disable | +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Enterprise Project | Select an enterprise project for the enterprise router. You can change it after the enterprise router is created. | default | +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_4_create_vpc_attachments_to_the_enterprise_router.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_4_create_vpc_attachments_to_the_enterprise_router.rst index ce3d8b5..b1ca2fd 100644 --- a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_4_create_vpc_attachments_to_the_enterprise_router.rst +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_4_create_vpc_attachments_to_the_enterprise_router.rst @@ -77,7 +77,7 @@ Procedure .. important:: - In the example given, **Default Route Table Association** and **Default Route Table Propagation** are enabled when you create the enterprise router. Therefore, after the VPCs are attached to the enterprise router, the system will automatically: + In the example given, **Default Route Table Association** and **Default Route Table Propagation** are enabled when you create the enterprise router. After the VPCs are attached to the enterprise router, the system will automatically: - Associate VPC attachments with the route table of the enterprise router. - Propagate VPC attachments to the route table of the enterprise router. The CIDR blocks of the VPCs are propagated to the route table. diff --git a/umn/source/interconnecting_with_cts/key_operations_recorded_by_cts.rst b/umn/source/interconnecting_with_cts/key_operations_recorded_by_cts.rst index 75d895e..bb08d2d 100644 --- a/umn/source/interconnecting_with_cts/key_operations_recorded_by_cts.rst +++ b/umn/source/interconnecting_with_cts/key_operations_recorded_by_cts.rst @@ -16,12 +16,10 @@ With CTS, you can record operations associated with your enterprise routers for +============================================+===============+========================+ | Creating an Enterprise Router | erInstance | createInstance | +--------------------------------------------+---------------+------------------------+ - | Modifying Settings of an Enterprise Router | erInstance | updateInstance | + | Modifying an Enterprise Router | erInstance | updateInstance | +--------------------------------------------+---------------+------------------------+ | Deleting an Enterprise Router | erInstance | deleteInstance | +--------------------------------------------+---------------+------------------------+ - | Changing AZs of an Enterprise Router | erInstance | changeAvailableZone | - +--------------------------------------------+---------------+------------------------+ | Adding Attachments to an Enterprise Router | erAttachment | createAttachment | +--------------------------------------------+---------------+------------------------+ | Modifying an Attachment | erAttachment | updateAttachment | @@ -56,3 +54,11 @@ With CTS, you can record operations associated with your enterprise routers for +--------------------------------------------+---------------+------------------------+ | Deleting a Propagation | erPropagation | deletePropagation | +--------------------------------------------+---------------+------------------------+ + | Creating a Flow Log | erFlowLog | createFlowLog | + +--------------------------------------------+---------------+------------------------+ + | Disabling a Flow Log | erFlowLog | updateFlowLog | + +--------------------------------------------+---------------+------------------------+ + | Enabling a Flow Log | erFlowLog | updateFlowLog | + +--------------------------------------------+---------------+------------------------+ + | Deleting a Flow Log | erFlowLog | deleteFlowLog | + +--------------------------------------------+---------------+------------------------+ diff --git a/umn/source/interconnecting_with_cts/viewing_traces.rst b/umn/source/interconnecting_with_cts/viewing_traces.rst index 9234ad8..469a0d6 100644 --- a/umn/source/interconnecting_with_cts/viewing_traces.rst +++ b/umn/source/interconnecting_with_cts/viewing_traces.rst @@ -45,6 +45,6 @@ Procedure #. Click **View Trace**. A dialog box is displayed, in which the trace details are displayed. - For more information about CTS, see *Cloud Trace Service User Guide*. + For more information about CTS, see `Cloud Trace Service User Guide `__. .. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/monitoring/supported_metrics.rst b/umn/source/monitoring/supported_metrics.rst index 472f7c2..f2f26e0 100644 --- a/umn/source/monitoring/supported_metrics.rst +++ b/umn/source/monitoring/supported_metrics.rst @@ -137,4 +137,4 @@ er_attachment_id Attachment ================ ================= - The monitoring metric measurement dimension of an enterprise router is **er_instance_id**. -- The monitoring metric measurement dimension of an attachment is **er_instance_id,er_attachment_id**. +- The monitoring metric measurement dimensions of an attachment are **er_instance_id** and **er_attachment_id**. diff --git a/umn/source/propagations/creating_a_propagation.rst b/umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst similarity index 93% rename from umn/source/propagations/creating_a_propagation.rst rename to umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst index f23a298..b0c0ac9 100644 --- a/umn/source/propagations/creating_a_propagation.rst +++ b/umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst @@ -2,16 +2,16 @@ .. _er_01_0036: -Creating a Propagation -====================== +Creating a Propagation for an Attachment in the Route Table +=========================================================== Scenarios --------- This section describes how to create a propagation in the route table of an enterprise router. -Notes and Constraints ---------------------- +Notes +----- You can create propagations for the same attachment in different route tables. @@ -52,7 +52,6 @@ Procedure | | | | | | - **VPC** | | | | - **Virtual gateway** | | - | | - **VPN gateway** | | | | | | | | For more information, see :ref:`Attachment Overview `. | | +-----------------------+--------------------------------------------------------------------------------------------+-----------------------+ diff --git a/umn/source/propagations/deleting_a_propagation.rst b/umn/source/propagations/deleting_a_propagation_from_a_route_table.rst similarity index 93% rename from umn/source/propagations/deleting_a_propagation.rst rename to umn/source/propagations/deleting_a_propagation_from_a_route_table.rst index 871fc4d..96fd666 100644 --- a/umn/source/propagations/deleting_a_propagation.rst +++ b/umn/source/propagations/deleting_a_propagation_from_a_route_table.rst @@ -2,8 +2,8 @@ .. _er_01_0038: -Deleting a Propagation -====================== +Deleting a Propagation from a Route Table +========================================= Scenarios --------- diff --git a/umn/source/propagations/index.rst b/umn/source/propagations/index.rst index 2afed12..775f57e 100644 --- a/umn/source/propagations/index.rst +++ b/umn/source/propagations/index.rst @@ -6,15 +6,15 @@ Propagations ============ - :ref:`Propagation Overview ` -- :ref:`Creating a Propagation ` -- :ref:`Viewing a Propagation ` -- :ref:`Deleting a Propagation ` +- :ref:`Creating a Propagation for an Attachment in the Route Table ` +- :ref:`Viewing a Propagation in a Route Table ` +- :ref:`Deleting a Propagation from a Route Table ` .. toctree:: :maxdepth: 1 :hidden: propagation_overview - creating_a_propagation - viewing_a_propagation - deleting_a_propagation + creating_a_propagation_for_an_attachment_in_the_route_table + viewing_a_propagation_in_a_route_table + deleting_a_propagation_from_a_route_table diff --git a/umn/source/propagations/propagation_overview.rst b/umn/source/propagations/propagation_overview.rst index f2f3090..53fb4be 100644 --- a/umn/source/propagations/propagation_overview.rst +++ b/umn/source/propagations/propagation_overview.rst @@ -9,26 +9,24 @@ You can create a propagation for each attachment to propagate routes to one or m If you do not want to create a propagation, you can manually add static routes for attachments to the route tables. -.. _er_01_0035__fig421415328433: +.. _er_01_0035__fig16423163124017: -.. figure:: /_static/images/en-us_image_0000001477172813.png +.. figure:: /_static/images/en-us_image_0000001347809009.png :alt: **Figure 1** Propagated routes and static routes **Figure 1** Propagated routes and static routes .. table:: **Table 1** Propagation description - +-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Attachment Type | Propagated Info | Way to Create Propagation | Description | - +=================+=================+==============================================================================================================================================================================================================+======================================================================================================================================================================================================================+ - | VPC | VPC CIDR blocks | - Auto creation: If **Default Route Table Propagation** is enabled and the default propagation route table is specified, attachments automatically propagate routes to the default propagation route table. | An attachment can be propagated to different route tables. You can create propagations for attachments in :ref:`Figure 1 ` as follows: | - | | | | | - | | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router `. | - Auto creation: Propagations are automatically created for the attachments, such as virtual gateway 1, VPN gateway 1, and VPC 1 attachments, in the default propagation route table of the enterprise router. | - | | | - If you want to enable this function after an enterprise router is created, refer to :ref:`Modifying Settings of an Enterprise Router `. | - Manual creation: You need to manually create propagations in the custom route table of the enterprise router for attachments, such as virtual gateway 1, VPC 1, VPN gateway 2, and virtual gateway 2 attachments. | - | | | | - No propagation: If you do not want to use propagated routes, you need to manually add static routes to the custom route table of the enterprise router for attachments, such as VPC 2. | - | | | - Manual creation: You can select a route table and create a propagation for an attachment in the route table. For details, see :ref:`Creating a Propagation `. | | - +-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Virtual gateway | All routes | | | - +-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | VPN gateway | All routes | | | - +-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-----------------+-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Attachment Type | Propagated Info | Way to Create Propagation | Description | + +=================+=================+===================================================================================================================================================================================================================+=================================================================================================================================================================================================================+ + | VPC | VPC CIDR blocks | - Auto creation: If **Default Route Table Propagation** is enabled and the default propagation route table is specified, attachments automatically propagate routes to the default propagation route table. | An attachment can be propagated to different route tables. You can create propagations for attachments in :ref:`Figure 1 ` as follows: | + | | | | | + | | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router `. | - Auto creation: Propagations are automatically created for the attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments, in the default propagation route table of the enterprise router. | + | | | - If you want to enable this function after an enterprise router is created, refer to :ref:`Modifying an Enterprise Router `. | - Manual creation: You need to manually create propagations in the custom route table of the enterprise router for attachments, such as VPC 1, virtual gateway 1, and virtual gateway 2 attachments. | + | | | | - No propagation: If you do not want to use propagated routes, you need to manually add static routes to the custom route table of the enterprise router for attachments, such as VPC 3 and VPC 4 attachments. | + | | | - Manual creation: You can select a route table and create a propagation for an attachment in the route table. For details, see :ref:`Creating a Propagation for an Attachment in the Route Table `. | | + +-----------------+-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Virtual gateway | All routes | | | + +-----------------+-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/propagations/viewing_a_propagation.rst b/umn/source/propagations/viewing_a_propagation_in_a_route_table.rst similarity index 70% rename from umn/source/propagations/viewing_a_propagation.rst rename to umn/source/propagations/viewing_a_propagation_in_a_route_table.rst index fb0ccf7..77e7087 100644 --- a/umn/source/propagations/viewing_a_propagation.rst +++ b/umn/source/propagations/viewing_a_propagation_in_a_route_table.rst @@ -2,8 +2,8 @@ .. _er_01_0037: -Viewing a Propagation -===================== +Viewing a Propagation in a Route Table +====================================== Scenarios --------- @@ -28,8 +28,14 @@ Procedure - In the upper right corner of the enterprise router, click **Manage Route Table**. - Click the enterprise router name and click **Route Tables**. + + .. figure:: /_static/images/en-us_image_0000001656353678.png + :alt: **Figure 1** Viewing a propagation + + **Figure 1** Viewing a propagation + #. Click the route table where you want to view a propagation. On the **Propagations** tab page, view your propagation. - You can view the status, attachment type, and attachment name of the propagation. + All propagations associated with the route table are displayed in the list. You can view their settings such as the ID, status, and name of each propagation. .. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/route_tables/deleting_a_route_table.rst b/umn/source/route_tables/deleting_a_route_table.rst index 77f9e60..80e0c25 100644 --- a/umn/source/route_tables/deleting_a_route_table.rst +++ b/umn/source/route_tables/deleting_a_route_table.rst @@ -18,12 +18,12 @@ Notes and Constraints - If **Default Route Association** is set to **Yes** on the basic information page of the route table, the route table is used as the default association route table. - Also, if **Default Route Propagation** is set to **Yes** on the basic information of the route table, the route table is used as the default propagation route table. - To delete such a route table, disable **Default Route Association** and **Default Route Propagation** first. For details, see :ref:`Modifying Settings of an Enterprise Router `. + To delete such a route table, disable **Default Route Association** and **Default Route Propagation** first. For details, see :ref:`Modifying an Enterprise Router `. - A route table cannot be deleted if it contains an association or a propagation. You need to delete the association and propagation before deleting this route table. - - For details about how to delete an association, see :ref:`Deleting an Association `. - - For details about how to delete a propagation, see :ref:`Deleting a Propagation `. + - For details about how to delete an association, see :ref:`Deleting an Association from a Route Table `. + - For details about how to delete a propagation, see :ref:`Deleting a Propagation from a Route Table `. - A route table can be deleted if it contains only static routes. Ensure that the routes are no longer required before deleting their route table. diff --git a/umn/source/route_tables/index.rst b/umn/source/route_tables/index.rst index d7f27eb..0b1301f 100644 --- a/umn/source/route_tables/index.rst +++ b/umn/source/route_tables/index.rst @@ -7,7 +7,7 @@ Route Tables - :ref:`Route Table Overview ` - :ref:`Creating a Route Table ` -- :ref:`Changing the Name and Description of a Route Table ` +- :ref:`Modifying a Route Table ` - :ref:`Viewing Route Tables ` - :ref:`Deleting a Route Table ` @@ -17,6 +17,6 @@ Route Tables route_table_overview creating_a_route_table - changing_the_name_and_description_of_a_route_table + modifying_a_route_table viewing_route_tables deleting_a_route_table diff --git a/umn/source/route_tables/changing_the_name_and_description_of_a_route_table.rst b/umn/source/route_tables/modifying_a_route_table.rst similarity index 94% rename from umn/source/route_tables/changing_the_name_and_description_of_a_route_table.rst rename to umn/source/route_tables/modifying_a_route_table.rst index 13749d6..d74a89b 100644 --- a/umn/source/route_tables/changing_the_name_and_description_of_a_route_table.rst +++ b/umn/source/route_tables/modifying_a_route_table.rst @@ -2,13 +2,13 @@ .. _er_01_0026: -Changing the Name and Description of a Route Table -================================================== +Modifying a Route Table +======================= Scenarios --------- -This section describes how to change the name and description of a route table. +This section describes how to modify the name and description of a route table. Notes and Constraints --------------------- diff --git a/umn/source/routes/deleting_a_static_route.rst b/umn/source/routes/deleting_a_static_route.rst index c37b969..3a60a96 100644 --- a/umn/source/routes/deleting_a_static_route.rst +++ b/umn/source/routes/deleting_a_static_route.rst @@ -10,7 +10,7 @@ Scenarios Delete a static route from a route table of an enterprise router. -Only static routes can be deleted. To delete a propagated route, you need to delete its propagation. The route will be deleted together with the propagation. For details, see :ref:`Deleting a Propagation `. +Only static routes can be deleted. To delete a propagated route, you need to delete its propagation. The route will be deleted together with the propagation. For details, see :ref:`Deleting a Propagation from a Route Table `. Procedure --------- diff --git a/umn/source/routes/route_overview.rst b/umn/source/routes/route_overview.rst index 07cfc92..fa76e76 100644 --- a/umn/source/routes/route_overview.rst +++ b/umn/source/routes/route_overview.rst @@ -12,36 +12,36 @@ Routes are used to forward packets. A route contains information such as the des You can create a propagation for attachments to automatically propagate routes to route tables or manually add static routes to route tables. -.. _er_01_0040__fig8141193684720: +.. _er_01_0040__fig2088721517588: -.. figure:: /_static/images/en-us_image_0000001477172813.png +.. figure:: /_static/images/en-us_image_0000001347809009.png :alt: **Figure 1** Propagated routes and static routes **Figure 1** Propagated routes and static routes .. table:: **Table 1** Route types - +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Route Type | Description | How to Create | Description | - +===================+===========================================================================================================================================+==========================================================================+=================================================================================================================================================================================+ - | Propagated routes | Propagated routes are routes that attachments propagate to the route tables of the enterprise router. They cannot be modified or deleted. | To create a propagation, see :ref:`Creating a Propagation `. | Routes are classified into propagated routes and static routes. The routes shown in :ref:`Figure 1 ` are described as follows: | - | | | | | - | | | | - Propagated routes are from: | - | | | | | - | | | | - Propagations automatically created in the default route table of the enterprise router for attachments, such as virtual gateway 1, VPN gateway 1 and VPC 1. | - | | | | - Propagations manually created in the custom route table of the enterprise router for attachments, such as virtual gateway 1, VPC 1, VPN gateway 2, and virtual gateway 2. | - | | | | | - | | | | - Static routes are manually added to the custom route table of the enterprise router for attachments, such as VPC 2. | - +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Static routes | Static routes are manually created and can be modified or deleted. | To create a route, see :ref:`Creating a Static Route `. | | - +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Route Type | Description | How to Create | Description | + +===================+===========================================================================================================================================+===============================================================================================================+==============================================================================================================================================================================+ + | Propagated routes | Propagated routes are routes that attachments propagate to the route tables of the enterprise router. They cannot be modified or deleted. | To create a propagation, see :ref:`Creating a Propagation for an Attachment in the Route Table `. | Routes are classified into propagated routes and static routes. The routes shown in :ref:`Figure 1 ` are described as follows: | + | | | | | + | | | | - Propagated routes are from: | + | | | | | + | | | | - Propagations automatically created in the default route table of the enterprise router for attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments. | + | | | | - Propagations manually created in the custom route table of the enterprise router for attachments, such as VPC 1, virtual gateway 1, and virtual gateway 2 attachments. | + | | | | | + | | | | - Static routes are manually added to the custom route table of the enterprise router for attachments, such as VPC 3 and VPC 4 attachments. | + +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Static routes | Static routes are manually created and can be modified or deleted. | To create a route, see :ref:`Creating a Static Route `. | | + +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Route Priority -------------- If there are multiple routes with the same destination but different targets in a route table, the route priority is as follows: -Static routes > propagated routes for attachments > propagated routes for virtual gateway attachments > propagated routes for VPN gateway attachments +Static route > propagated route for VPC attachment > propagated route for virtual gateway attachment route .. note:: diff --git a/umn/source/service_overview/enterprise_router_and_other_services.rst b/umn/source/service_overview/enterprise_router_and_other_services.rst index dad1160..d301494 100644 --- a/umn/source/service_overview/enterprise_router_and_other_services.rst +++ b/umn/source/service_overview/enterprise_router_and_other_services.rst @@ -14,8 +14,6 @@ Enterprise Router and Other Services +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Direct Connect | You can attach a Direct Connect virtual gateway to an enterprise router to connect VPCs to an on-premises data center through a shared Direct Connect connection. | +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Virtual Private Network (VPN) | You can attach a VPN gateway to an enterprise router to connect VPCs to an on-premises data center through a shared VPN connection. | - +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Identity and Access Management (IAM) | You can use IAM to assign different permissions to different users to control their access to enterprise router resources. | +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Cloud Eye | You can use Cloud Eye to monitor the network status of enterprise routers and their attachments, and report alarms when exceptions occur, ensuring smooth service running. | diff --git a/umn/source/service_overview/functions.rst b/umn/source/service_overview/functions.rst index 9b68460..03e8c43 100644 --- a/umn/source/service_overview/functions.rst +++ b/umn/source/service_overview/functions.rst @@ -14,57 +14,57 @@ An enterprise router provides the functions listed in :ref:`Table 1 ` | - | | | | - | | After an enterprise router is created, you can still change its parameters based on service requirements. | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Attachments | You can add attachments to attach network instances to the enterprise router. Different network instances are attached through different consoles. | :ref:`Attachment Overview ` | - | | | | - | | - Virtual Private Clouds (VPCs) are attached through the enterprise router console. | | - | | - Virtual gateways are attached through the Direct Connect console. | | - | | - VPN gateways are attached through the VPN console. | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Route tables | Route tables are used by enterprise routers to forward packets. Route tables contain associations, propagations, and routes. | :ref:`Route Table Overview ` | - | | | | - | | An enterprise router can have multiple route tables. You can associate attachments with different route tables to enable communication or isolation between network instances. | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Associations | Associations are created manually or automatically to associate attachments with enterprise router route tables. | :ref:`Association Overview ` | - | | | | - | | - Manually: Select a route table and create an association for an attachment in the route table. | | - | | - Automatically: You just need to enable **Default Route Table Association** and specify the default route table. The system automatically creates an association for an attachment in the default route table. | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Propagations | A propagation is created manually or automatically to enable an enterprise router to learn the routes to an associated attachment. | :ref:`Propagation Overview ` | - | | | | - | | - Manually: Select a route table and create a propagation for an attachment in the route table. | | - | | - Automatically: You just need to enable **Default Route Table Propagation** and specify the default route table. A propagation is automatically created for an attachment in the default propagation route table. | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Routes | A route consists of information such as the destination address, next hop, and route type. There are two types of routes: | :ref:`Route Overview ` | - | | | | - | | - Propagated routes | | - | | - Static routes | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Sharing | You are the owner of the enterprise router, and other accounts are the users of your enterprise router. | :ref:`Sharing Overview ` | - | | | | - | | After you share your enterprise router with other accounts, these other users can attach their network instances to your enterprise router, so that their network instances can access your enterprise router. | | - | | | | - | | This allows VPCs in the same region but different accounts to be attached to the same enterprise router. | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Flow logs | The flow log function records traffic logs of attachments on enterprise routers in real time. The logs allow you to monitor the network traffic of attachment and analyze network attacks, helping you achieve efficient O&M. | :ref:`Flow Log Overview ` | - | | | | - | | Flow logs can capture traffic of the following types of attachments: | | - | | | | - | | - VPC | | - | | - Virtual gateway | | - | | - VPN gateway | | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Monitoring | You can use Cloud Eye to monitor the network status of enterprise routes and their attachments. | :ref:`Supported Metrics ` | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Auditing | You can use Cloud Trace Service (CTS) to record operations associated with your enterprise routers for future query, audit, and backtracking. | :ref:`Key Operations Recorded by CTS ` | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Tags | Tags are used to identify the cloud resources. You can add tags to enterprise routers and route tables. | :ref:`Overview ` | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ - | Quotas | Quotas can limit the number or amount of resources available to users, for example, how many enterprise routers can be created, how many attachments can be created on each enterprise router, and how many routes can be added to each route table. | :ref:`Overview ` | - +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Function | Description | Reference | + +=======================+=======================================================================================================================================================================================================================================================+====================================================+ + | Enterprise routers | An enterprise router is a high-performance centralized router that supports route learning. When creating an enterprise router, you can set parameters such as its region, AZ, and name. | :ref:`Creating an Enterprise Router ` | + | | | | + | | After an enterprise router is created, you can still change its parameters based on service requirements. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Attachments | You can add attachments to attach network instances to the enterprise router. | :ref:`Attachment Overview ` | + | | | | + | | Different network instances are attached through different consoles. | | + | | | | + | | - VPCs are attached through the Enterprise Router console. | | + | | - Virtual gateways are attached through the Direct Connect console. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Route tables | Route tables are used by enterprise routers to forward packets. Route tables contain associations, propagations, and routes. | :ref:`Route Table Overview ` | + | | | | + | | An enterprise router can have multiple route tables. You can associate attachments with different route tables to enable communication or isolation between network instances. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Associations | Associations are created manually or automatically to associate attachments with enterprise router route tables. | :ref:`Association Overview ` | + | | | | + | | - Manually: Select a route table and create an association for an attachment in the route table. | | + | | - Automatically: You just need to enable **Default Route Table Association** and specify the default route table. The system automatically creates an association for an attachment in the default route table. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Propagations | A propagation is created manually or automatically to enable an enterprise router to learn the routes to an associated attachment. | :ref:`Propagation Overview ` | + | | | | + | | - Manually: Select a route table and create a propagation for an attachment in the route table. | | + | | - Automatically: You just need to enable **Default Route Table Propagation** and specify the default route table. A propagation is automatically created for an attachment in the default propagation route table. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Routes | A route consists of information such as the destination address, next hop, and route type. There are two types of routes: | :ref:`Route Overview ` | + | | | | + | | - Propagated routes | | + | | - Static routes | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Sharing | You are the owner of the enterprise router, and other accounts are the users of your enterprise router. | :ref:`Sharing Overview ` | + | | | | + | | After you share your enterprise router with other accounts, these other users can attach their network instances to your enterprise router, so that their network instances can access your enterprise router. | | + | | | | + | | This allows VPCs in the same region but different accounts to be attached to the same enterprise router. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Flow logs | The flow log function records traffic logs of attachments on enterprise routers in real time. The logs allow you to monitor the network traffic of attachments and analyze network attacks, helping you achieve efficient O&M. | :ref:`Flow Log Overview ` | + | | | | + | | Flow logs can capture traffic of the following types of attachments: | | + | | | | + | | - VPC | | + | | - Virtual gateway | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Monitoring | You can use Cloud Eye to monitor the network status of enterprise routers and their attachments. | :ref:`Supported Metrics ` | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Auditing | You can use Cloud Trace Service (CTS) to record operations associated with your enterprise routers for future query, audit, and backtracking. | :ref:`Key Operations Recorded by CTS ` | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Tags | Tags are used to identify cloud resources. You can add tags to enterprise routers and route tables. | :ref:`Overview ` | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Quotas | Quotas can limit the number or amount of resources available to users, for example, how many enterprise routers can be created, how many attachments can be created for each enterprise router, and how many routes can be added to each route table. | :ref:`Overview ` | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ diff --git a/umn/source/service_overview/how_enterprise_routers_work.rst b/umn/source/service_overview/how_enterprise_routers_work.rst index bf1a47c..09e7cf8 100644 --- a/umn/source/service_overview/how_enterprise_routers_work.rst +++ b/umn/source/service_overview/how_enterprise_routers_work.rst @@ -5,17 +5,16 @@ How Enterprise Routers Work =========================== -You can attach your network connections to an enterprise router to quickly construct diversified networks and meet various service requirements. :ref:`Figure 1 ` shows the process of using an enterprise router, including creating an enterprise router, adding attachments to the enterprise router, and configure routes. +You can attach your network connections to an enterprise router to quickly construct diversified networks and meet various service requirements. :ref:`Figure 1 ` shows the process of using an enterprise router, including creating an enterprise router, adding attachments to the enterprise router, and configure routes. Currently, enterprise routers support the following attachments: - **VPC attachment**: Attach VPCs from the same region as that of an enterprise router to the router. - **Virtual gateway attachment**: Attach Direct Connect virtual gateways from the same region as that of an enterprise router to the router. -- **VPN gateway attachment**: Attach VPN gateways from the same region as that of an enterprise router to the router. -.. _er_01_0011__fig1863072118237: +.. _er_01_0011__fig9264191913235: -.. figure:: /_static/images/en-us_image_0000001529948913.png +.. figure:: /_static/images/en-us_image_0000001530148853.png :alt: **Figure 1** Processing of using an enterprise router **Figure 1** Processing of using an enterprise router @@ -23,7 +22,7 @@ Currently, enterprise routers support the following attachments: The following describes how an enterprise router works. -.. figure:: /_static/images/en-us_image_0000001529950265.png +.. figure:: /_static/images/en-us_image_0000001529830673.png :alt: **Figure 2** How an enterprise router works **Figure 2** How an enterprise router works @@ -51,13 +50,11 @@ The following describes how an enterprise router works. | | | | | | | - **VPC attachments**: VPC 1, VPC 2, and VPC 3 | | | | - **Virtual gateway attachment**: Virtual gateway | - | | | - **VPN gateway attachment**: VPN gateway | +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2 | Associate the :ref:`attachments ` with the :ref:`route tables ` of the enterprise router. | - Associate VPC 1 with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from VPC 1 attachment to the default route table and custom route table of enterprise router 1. | | | | - Associate VPC 2 with the custom route table of enterprise router 1 and create a propagation to propagate the routes learned from VPC 2 to the custom route table. | | | Each attachment can only be associated with one route table. | - Associate VPC 3 with the custom route table of enterprise router 1, and add static routes for VPC 3 to this custom route table. | | | | - Associate the Direct Connect virtual gateway with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from the virtual gateway attachment to the default route table. | - | | | - Associate the VPN gateway with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from the VPN gateway attachment to the default route table. | +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 3 | Create :ref:`propagation ` for the attachments to propagate the :ref:`routes ` to the enterprise router's :ref:`route tables `. | | | | | | @@ -76,11 +73,10 @@ If you want to attach a network instance to an enterprise router, you need to ad .. table:: **Table 3** Attachments ========================== ================================= - Attachment Network Instance + Attachment Type Network Instance ========================== ================================= VPC attachment VPC Virtual gateway attachment Virtual gateway of Direct Connect - VPN gateway attachment VPN gateway ========================== ================================= .. _er_01_0011__section14844328152418: @@ -120,13 +116,12 @@ Not all attachments can propagate routes. For details, see :ref:`Table 5 ` - The VPC route table does not allow you to add a route whose destination address is 100.64.x.x and next hop is an enterprise router. - To solve this problem, refer to :ref:`How Do I Route Traffic to 100.64.x.x Through an Enterprise Router? `. + To solve this problem, refer to :ref:`How Do I Route Traffic to 100.64.x.x Through an Enterprise Router? ` diff --git a/umn/source/service_overview/whats_an_enterprise_router.rst b/umn/source/service_overview/whats_an_enterprise_router.rst index 3c28f2c..9207167 100644 --- a/umn/source/service_overview/whats_an_enterprise_router.rst +++ b/umn/source/service_overview/whats_an_enterprise_router.rst @@ -7,33 +7,33 @@ What's an Enterprise Router? An enterprise router connects virtual private clouds (VPCs) and on-premises networks to build a central hub network. It has high specifications, provides high bandwidth, and delivers high performance. Enterprise routers use the Border Gateway Protocol (BGP) to learn, dynamically select, or switch between routes, thereby ensuring the service continuity and significantly improving network scalability and O&M efficiency. -:ref:`Figure 1 ` and :ref:`Figure 2 ` show the networks with and without enterprise routers, respectively. :ref:`Table 1 ` compares the two networks. +:ref:`Figure 1 ` and :ref:`Figure 2 ` show the networks with and without enterprise routers, respectively. :ref:`Table 1 ` compares the two networks. -.. _er_01_0002__fig1160410331975: +.. _er_01_0002__fig8654112125420: -.. figure:: /_static/images/en-us_image_0000001427301842.png +.. figure:: /_static/images/en-us_image_0000001347633729.png :alt: **Figure 1** A network without enterprise routers **Figure 1** A network without enterprise routers -.. _er_01_0002__fig12604833873: +.. _er_01_0002__fig1865418216549: -.. figure:: /_static/images/en-us_image_0000001559118632.png +.. figure:: /_static/images/en-us_image_0000001609438833.png :alt: **Figure 2** A network with enterprise routers **Figure 2** A network with enterprise routers -.. _er_01_0002__table126045339718: +.. _er_01_0002__table14654162155418: .. table:: **Table 1** Comparison between the networks with and without enterprise routers +------------------------------------------------------------+--------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------+ | Item | Without Enterprise Routers | With Enterprise Routers | Benefits of Using Enterprise Routers | +============================================================+============================================================================================+============================================================================================================================================================================================================+===============================================================================================+ - | Communications among VPCs in the same region | - Create six VPC peering connections between these four VPCs in the same region. | - Attach these four VPCs to one enterprise router. This router can then handle the traffic from and to all the connected VPCs. | - There is no need to configure a large number of VPC peering connections. | + | Communications among VPCs in the same region | - Create six VPC peering connections between these four VPCs in the same region. | - Attach the four VPCs to one enterprise router. This router can then handle the traffic from and to all the connected VPCs. | - There is no need to configure a large number of VPC peering connections. | | | - Add 12 routes, with three routes for each VPC to communicate with the other three VPCs. | - Add routes to the route tables of these four VPCs for routing traffic through the enterprise router. The enterprise router can automatically learn the VPC CIDR blocks and add them to its route table. | - Fewer routes need to be added, simplifying the maintenance. | +------------------------------------------------------------+--------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------+ - | Communications between an on-premises data center and VPCs | Establish Direct Connect or VPN connections between each VPC and the data center. | Attach the Direct Connect or VPN connection to the enterprise router. These VPCs can then share the connection. | - Route propagation simplifies the route configuration and the O&M. | + | Communications between an on-premises data center and VPCs | Establish Direct Connect connections between each VPC and the data center. | Attach the Direct Connect connection to the enterprise router. These VPCs can then share the connection. | - Route propagation simplifies the route configuration and the O&M. | | | | | - Multiple lines work in load-sharing or active/standby mode to achieve higher availability. | +------------------------------------------------------------+--------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------+ diff --git a/umn/source/service_overview/why_using_enterprise_routers.rst b/umn/source/service_overview/why_using_enterprise_routers.rst index 66b1767..d3fc5a9 100644 --- a/umn/source/service_overview/why_using_enterprise_routers.rst +++ b/umn/source/service_overview/why_using_enterprise_routers.rst @@ -23,7 +23,7 @@ Simplified Management Enterprise routers can connect to multiple VPCs, Direct Connect connections, or enterprise routers in different regions and route traffic among them. The network topology is simpler and the network is easier to manage and maintain. - For cross-VPC communications, you only need to maintain the route tables on the VPCs without requiring so many VPC peering connections. -- For communications between VPCs and an on-premises data center, multiple VPCs can connect to an enterprise router and then communicate with the data center over a shared Direct Connect or VPN connection. You do not need to establish Direct Connect or VPN connections between the data center and each of the VPCs. +- For communications between VPCs and an on-premises data center, multiple VPCs can connect to an enterprise router and then communicate with the data center over a shared Direct Connect connection. You do not need to establish Direct Connect connections between the data center and each of the VPCs. - Enterprise routers can automatically learn, update, and synchronize routes, eliminating the need to manually configure or update routes whenever the network topology changes. Seamless Failover Between Lines diff --git a/umn/source/sharing/accepting_an_attachment_request.rst b/umn/source/sharing/accepting_an_attachment_request.rst index c43a89b..16584f5 100644 --- a/umn/source/sharing/accepting_an_attachment_request.rst +++ b/umn/source/sharing/accepting_an_attachment_request.rst @@ -12,7 +12,8 @@ This section describes how to accept a request from another user for creating an .. note:: - If **Auto Accept Shared Attachments** is disabled on your enterprise router, you can choose to accept the attachment request or not. + - If **Auto Accept Shared Attachments** is disabled on your enterprise router, you can choose to accept the attachment request or not. + - If **Auto Accept Shared Attachments** is enabled on your enterprise router, the attachment will be automatically accepted without your approval. Procedure --------- @@ -27,12 +28,12 @@ Procedure #. Search for the target enterprise router by name. -#. Go to the **Sharing** tab page using either of the following methods: +#. Go to the **Attachments** tab page using either of the following methods: - - In the upper right corner of the enterprise router, click **Manage Sharing**. - - Click the enterprise router name and click **Sharing**. + - In the upper right corner of the enterprise router, click **Manage Attachment**. + - Click the enterprise router name and click **Attachments**. -#. In the sharing list, locate the row that contains the attachment you want to accept and click **Accept** in the **Operation** column. +#. In the attachment list, locate the row that contains the attachment you want to accept and click **Accept** in the **Operation** column. The owner accepts the attachment request. The attachment status changes from **Pending acceptance** to **Creating**. diff --git a/umn/source/sharing/changing_the_name_of_a_sharing.rst b/umn/source/sharing/changing_the_name_of_a_sharing.rst index cdf16c2..369adf2 100644 --- a/umn/source/sharing/changing_the_name_of_a_sharing.rst +++ b/umn/source/sharing/changing_the_name_of_a_sharing.rst @@ -8,7 +8,7 @@ Changing the Name of a Sharing Scenarios --------- -This section describes how to change the name of a sharing. +This section describes how you can change the name of a sharing. Procedure --------- diff --git a/umn/source/sharing/index.rst b/umn/source/sharing/index.rst index f97198b..b86a3f5 100644 --- a/umn/source/sharing/index.rst +++ b/umn/source/sharing/index.rst @@ -8,7 +8,7 @@ Sharing - :ref:`Sharing Overview ` - :ref:`Creating a Sharing ` - :ref:`Changing the Name of a Sharing ` -- :ref:`Viewing a Sharing ` +- :ref:`Viewing Sharing Details ` - :ref:`Accepting an Attachment Request ` - :ref:`Rejecting an Attachment Request ` - :ref:`Deleting a Sharing ` @@ -20,7 +20,7 @@ Sharing sharing_overview creating_a_sharing changing_the_name_of_a_sharing - viewing_a_sharing + viewing_sharing_details accepting_an_attachment_request rejecting_an_attachment_request deleting_a_sharing diff --git a/umn/source/sharing/rejecting_an_attachment_request.rst b/umn/source/sharing/rejecting_an_attachment_request.rst index 0c886b4..f024f32 100644 --- a/umn/source/sharing/rejecting_an_attachment_request.rst +++ b/umn/source/sharing/rejecting_an_attachment_request.rst @@ -12,7 +12,8 @@ This section describes how to reject a request from another user for creating an .. note:: - If **Auto Accept Shared Attachments** is disabled on your enterprise router, you can choose to accept the attachment request or not. + - If **Auto Accept Shared Attachments** is disabled on your enterprise router, you can choose to accept the attachment request or not. + - If **Auto Accept Shared Attachments** is enabled on your enterprise router, the attachment will be automatically accepted without your approval. Procedure --------- @@ -27,12 +28,12 @@ Procedure #. Search for the target enterprise router by name. -#. Go to the **Sharing** tab page using either of the following methods: +#. Go to the **Attachments** tab page using either of the following methods: - - In the upper right corner of the enterprise router, click **Manage Sharing**. - - Click the enterprise router name and click **Sharing**. + - In the upper right corner of the enterprise router, click **Manage Attachment**. + - Click the enterprise router name and click **Attachments**. -#. In the sharing list, locate the row that contains the attachment you want to reject and click **Reject** in the **Operation** column. +#. In the attachment list, locate the row that contains the attachment you want to reject and click **Reject** in the **Operation** column. The owner can also reject the attachment request. If the owner rejects the request, the attachment status changes from **Pending acceptance** to **Rejected**, and the attachment fails to be created. If this happens, contact the owner. diff --git a/umn/source/sharing/sharing_overview.rst b/umn/source/sharing/sharing_overview.rst index 391c0aa..e1cbbbd 100644 --- a/umn/source/sharing/sharing_overview.rst +++ b/umn/source/sharing/sharing_overview.rst @@ -33,12 +33,8 @@ If account A shares enterprise router (ER-A) with account B and account C, the V | | | VPC-A-02 | +-----------------------+-----------------------+-----------------------+ | B | ER-B | VPC-B-01 | - | | | | - | | | VPC-B-02 | +-----------------------+-----------------------+-----------------------+ | C | ER-C | VPC-C-01 | - | | | | - | | | VPC-C-02 | +-----------------------+-----------------------+-----------------------+ .. _er_01_0095__fig16662957112716: @@ -62,7 +58,7 @@ The owner can perform all operations but these other users can perform only some +=============================+====================================================================+===================================================================================================================================================================================================+ | Other users (user accounts) | :ref:`Viewing an Enterprise Router ` | Other users can view: | | | | | - | | | - The name of the shared enterprise router followed by **Shared with me**. | + | | | The name of the shared enterprise router followed by **Shared with me**. | +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | Adding attachments to an enterprise router | Other users: | | | | | @@ -85,6 +81,10 @@ The owner can perform all operations but these other users can perform only some | | :ref:`Deleting a VPC Attachment ` | Other users can delete their attachments created for the shared enterprise router without the approval of the owner account. | +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +.. note:: + + Other users cannot view the **Route tables**, **Sharing**, **Flow logs**, and **Tags** tabs of the enterprise router. + .. _er_01_0095__section169164232367: Sharing an Enterprise Router with Other Users diff --git a/umn/source/sharing/viewing_a_sharing.rst b/umn/source/sharing/viewing_sharing_details.rst similarity index 95% rename from umn/source/sharing/viewing_a_sharing.rst rename to umn/source/sharing/viewing_sharing_details.rst index 659ef5b..a0dd3e6 100644 --- a/umn/source/sharing/viewing_a_sharing.rst +++ b/umn/source/sharing/viewing_sharing_details.rst @@ -2,8 +2,8 @@ .. _er_01_0098: -Viewing a Sharing -================= +Viewing Sharing Details +======================= Scenarios --------- diff --git a/umn/source/tags/overview.rst b/umn/source/tags/overview.rst index ef27cce..9e03695 100644 --- a/umn/source/tags/overview.rst +++ b/umn/source/tags/overview.rst @@ -29,8 +29,8 @@ You can quickly search for specific cloud resources based on the tags added to t **Figure 1** Example tags added for Enterprise Router -Restrictions on Using Tags --------------------------- +Constraints on Using Tags +------------------------- - Each tag consists of a tag key and a tag value. The rules for naming a tag key and a tag value are as follows: @@ -38,14 +38,14 @@ Restrictions on Using Tags - Cannot be left blank. - Can contain a maximum of 36 characters. - - Can consist of only letters, digits, underscores (_), hyphens (-), and Unicode characters (\\u4E00-\\u9FFF). + - Can consist of letters, digits, underscores (_), and hyphens (-). Tag value - Can be left blank. - Can contain a maximum of 43 characters. - - Can consist of letters, digits, underscores (_), periods (.), hyphens (-), and Unicode characters (\\u4E00-\\u9FFF). + - Can consist of letters, digits, underscores (_), periods (.), and hyphens (-). -- Up to 10 tags can be added to each cloud resource. +- Up to 20 tags can be added to each cloud resource. - For each resource, each tag key must be unique, and each tag key can only have one tag value. diff --git a/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_attachment_by_tag.rst b/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_attachment_by_tag.rst index b8dbdbf..2f93795 100644 --- a/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_attachment_by_tag.rst +++ b/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_attachment_by_tag.rst @@ -27,17 +27,8 @@ Procedure The attachment list is displayed. -#. Click **Search by Tag**. +#. Click the search box, select **Tag** for **Property**, select the tag to be searched for, and click **OK**. -#. Enter or select a tag key and a tag value. - - - If you need to query a resource with multiple tags, click |image2| to add multiple tags. A maximum of 10 tags can be added at a time. - - You can click |image3| to delete the added tags one by one or click **Reset** to clear all of them. - -#. Click **Search**. - - The resource with the tags is displayed in the list. + The resource with the tag is displayed in the list. .. |image1| image:: /_static/images/en-us_image_0000001190483836.png -.. |image2| image:: /_static/images/en-us_image_0000001213604225.png -.. |image3| image:: /_static/images/en-us_image_0000001435362757.png