diff --git a/umn/source/_static/images/en-us_image_0000001142144144.png b/umn/source/_static/images/en-us_image_0000001142144144.png new file mode 100644 index 0000000..1011f4d Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001142144144.png differ diff --git a/umn/source/_static/images/en-us_image_0000001144919892.png b/umn/source/_static/images/en-us_image_0000001144919892.png new file mode 100644 index 0000000..d957d3a Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001144919892.png differ diff --git a/umn/source/_static/images/en-us_image_0000001147413690.png b/umn/source/_static/images/en-us_image_0000001147413690.png new file mode 100644 index 0000000..c3d75fe Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001147413690.png differ diff --git a/umn/source/_static/images/en-us_image_0000001160921916.png b/umn/source/_static/images/en-us_image_0000001160921916.png new file mode 100644 index 0000000..140f57f Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001160921916.png differ diff --git a/umn/source/_static/images/en-us_image_0000001188217841.png b/umn/source/_static/images/en-us_image_0000001188217841.png new file mode 100644 index 0000000..775bc36 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001188217841.png differ diff --git a/umn/source/_static/images/en-us_image_0000001190483836.png b/umn/source/_static/images/en-us_image_0000001190483836.png new file mode 100644 index 0000000..1909444 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001190483836.png differ diff --git a/umn/source/_static/images/en-us_image_0000001190538519.png b/umn/source/_static/images/en-us_image_0000001190538519.png new file mode 100644 index 0000000..75311cf Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001190538519.png differ diff --git a/umn/source/_static/images/en-us_image_0000001193598903.png b/umn/source/_static/images/en-us_image_0000001193598903.png new file mode 100644 index 0000000..6d5ecbf Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001193598903.png differ diff --git a/umn/source/_static/images/en-us_image_0000001195294363.png b/umn/source/_static/images/en-us_image_0000001195294363.png new file mode 100644 index 0000000..27948c8 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001195294363.png differ diff --git a/umn/source/_static/images/en-us_image_0000001213604225.png b/umn/source/_static/images/en-us_image_0000001213604225.png new file mode 100644 index 0000000..08a3ca8 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001213604225.png differ diff --git a/umn/source/_static/images/en-us_image_0000001213710098.png b/umn/source/_static/images/en-us_image_0000001213710098.png new file mode 100644 index 0000000..91b44eb Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001213710098.png differ diff --git a/umn/source/_static/images/en-us_image_0000001213710140.png b/umn/source/_static/images/en-us_image_0000001213710140.png new file mode 100644 index 0000000..3516a0a Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001213710140.png differ diff --git a/umn/source/_static/images/en-us_image_0000001214183634.png b/umn/source/_static/images/en-us_image_0000001214183634.png new file mode 100644 index 0000000..a3296c2 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001214183634.png differ diff --git a/umn/source/_static/images/en-us_image_0000001243603657.png b/umn/source/_static/images/en-us_image_0000001243603657.png new file mode 100644 index 0000000..775bc36 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001243603657.png differ diff --git a/umn/source/_static/images/en-us_image_0000001243682317.png b/umn/source/_static/images/en-us_image_0000001243682317.png new file mode 100644 index 0000000..775bc36 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001243682317.png differ diff --git a/umn/source/_static/images/en-us_image_0000001258580523.png b/umn/source/_static/images/en-us_image_0000001258580523.png new file mode 100644 index 0000000..a3296c2 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001258580523.png differ diff --git a/umn/source/_static/images/en-us_image_0000001295153022.png b/umn/source/_static/images/en-us_image_0000001295153022.png new file mode 100644 index 0000000..045d657 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001295153022.png differ diff --git a/umn/source/_static/images/en-us_image_0000001383934230.png b/umn/source/_static/images/en-us_image_0000001383934230.png new file mode 100644 index 0000000..2257b47 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001383934230.png differ diff --git a/umn/source/_static/images/en-us_image_0000001399653186.png b/umn/source/_static/images/en-us_image_0000001399653186.png new file mode 100644 index 0000000..238e49e Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001399653186.png differ diff --git a/umn/source/_static/images/en-us_image_0000001426824994.png b/umn/source/_static/images/en-us_image_0000001426824994.png new file mode 100644 index 0000000..bd6f1f2 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001426824994.png differ diff --git a/umn/source/_static/images/en-us_image_0000001427131632.png b/umn/source/_static/images/en-us_image_0000001427131632.png new file mode 100644 index 0000000..14b93c8 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001427131632.png differ diff --git a/umn/source/_static/images/en-us_image_0000001427301842.png b/umn/source/_static/images/en-us_image_0000001427301842.png new file mode 100644 index 0000000..c98f936 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001427301842.png differ diff --git a/umn/source/_static/images/en-us_image_0000001432667421.png b/umn/source/_static/images/en-us_image_0000001432667421.png new file mode 100644 index 0000000..0c55e3f Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001432667421.png differ diff --git a/umn/source/_static/images/en-us_image_0000001434293421.png b/umn/source/_static/images/en-us_image_0000001434293421.png new file mode 100644 index 0000000..2257b47 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001434293421.png differ diff --git a/umn/source/_static/images/en-us_image_0000001435362757.png b/umn/source/_static/images/en-us_image_0000001435362757.png new file mode 100644 index 0000000..548a024 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001435362757.png differ diff --git a/umn/source/_static/images/en-us_image_0000001446449166.png b/umn/source/_static/images/en-us_image_0000001446449166.png new file mode 100644 index 0000000..34751de Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001446449166.png differ diff --git a/umn/source/_static/images/en-us_image_0000001477172813.png b/umn/source/_static/images/en-us_image_0000001477172813.png new file mode 100644 index 0000000..4c1b38b Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001477172813.png differ diff --git a/umn/source/_static/images/en-us_image_0000001477452077.png b/umn/source/_static/images/en-us_image_0000001477452077.png new file mode 100644 index 0000000..a4a7050 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001477452077.png differ diff --git a/umn/source/_static/images/en-us_image_0000001529948913.png b/umn/source/_static/images/en-us_image_0000001529948913.png new file mode 100644 index 0000000..9c35502 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001529948913.png differ diff --git a/umn/source/_static/images/en-us_image_0000001529950265.png b/umn/source/_static/images/en-us_image_0000001529950265.png new file mode 100644 index 0000000..fb489ba Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001529950265.png differ diff --git a/umn/source/_static/images/en-us_image_0152727234.png b/umn/source/_static/images/en-us_image_0152727234.png new file mode 100644 index 0000000..35e2831 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0152727234.png differ diff --git a/umn/source/_static/images/en-us_image_0184026531.png b/umn/source/_static/images/en-us_image_0184026531.png new file mode 100644 index 0000000..1303a51 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0184026531.png differ diff --git a/umn/source/_static/images/en-us_image_0275513364.png b/umn/source/_static/images/en-us_image_0275513364.png new file mode 100644 index 0000000..1909444 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0275513364.png differ diff --git a/umn/source/associations/association_overview.rst b/umn/source/associations/association_overview.rst new file mode 100644 index 0000000..69e8fe0 --- /dev/null +++ b/umn/source/associations/association_overview.rst @@ -0,0 +1,35 @@ +:original_name: er_01_0030.html + +.. _er_01_0030: + +Association Overview +==================== + +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 + :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 | | | + +-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/associations/creating_an_association.rst b/umn/source/associations/creating_an_association.rst new file mode 100644 index 0000000..e6a7dc1 --- /dev/null +++ b/umn/source/associations/creating_an_association.rst @@ -0,0 +1,68 @@ +:original_name: er_01_0031.html + +.. _er_01_0031: + +Creating an Association +======================= + +Scenarios +--------- + +This section describes how to create an association in a route table of an enterprise router to associate a specified attachment with the route table. + +Notes and Constraints +--------------------- + +Each attachment can only be associated with one route table. Packets from the attachment will be forwarded based on the route table. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table where you want to create an association. On the **Associations** tab page, click **Create Association**. + + The **Create Association** dialog box is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0031__table7204821194013: + + .. table:: **Table 1** Parameters for creating an association + + +-----------------------+-------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+=====================================================================================+=======================+ + | Attachment Type | Mandatory | VPC | + | | | | + | | Select an attachment type. | | + | | | | + | | - **VPC** | | + | | - **Virtual gateway** | | + | | - **VPN gateway** | | + | | | | + | | For more information, see :ref:`Attachment Overview `. | | + +-----------------------+-------------------------------------------------------------------------------------+-----------------------+ + | Attachment | Mandatory | er-attach-02 | + | | | | + | | In the drop-down list, select the attachment to be associated with the route table. | | + +-----------------------+-------------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The association list is displayed. You can view your association. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/associations/deleting_an_association.rst b/umn/source/associations/deleting_an_association.rst new file mode 100644 index 0000000..b87ffb3 --- /dev/null +++ b/umn/source/associations/deleting_an_association.rst @@ -0,0 +1,39 @@ +:original_name: er_01_0033.html + +.. _er_01_0033: + +Deleting an Association +======================= + +Scenarios +--------- + +This section describes how to delete an association from the route table of an enterprise router. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table that you want to delete an association from. On the **Associations** tab page, locate the row that contains the association you want to delete and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted association cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/associations/index.rst b/umn/source/associations/index.rst new file mode 100644 index 0000000..1bc3e07 --- /dev/null +++ b/umn/source/associations/index.rst @@ -0,0 +1,20 @@ +:original_name: er_01_0029.html + +.. _er_01_0029: + +Associations +============ + +- :ref:`Association Overview ` +- :ref:`Creating an Association ` +- :ref:`Viewing an Association ` +- :ref:`Deleting an Association ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + association_overview + creating_an_association + viewing_an_association + deleting_an_association diff --git a/umn/source/associations/viewing_an_association.rst b/umn/source/associations/viewing_an_association.rst new file mode 100644 index 0000000..066b63e --- /dev/null +++ b/umn/source/associations/viewing_an_association.rst @@ -0,0 +1,35 @@ +:original_name: er_01_0032.html + +.. _er_01_0032: + +Viewing an Association +====================== + +Scenarios +--------- + +This section describes how to view associations in the route table of an enterprise router. You can also view all the attachments associated with this route table. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. 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. + +.. |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 new file mode 100644 index 0000000..fb07e58 --- /dev/null +++ b/umn/source/attachments/adding_vpc_attachments_to_an_enterprise_router.rst @@ -0,0 +1,111 @@ +:original_name: er_01_0070.html + +.. _er_01_0070: + +Adding VPC Attachments to an Enterprise Router +============================================== + +Scenarios +--------- + +This section describes how to attach VPCs to an enterprise router so that these VPCs can communicate with each other. + +Notes and Constraints +--------------------- + +- If you use the propagated routes of a VPC attachment, the route table of the enterprise router automatically learns the VPC CIDR block as the destination of routes. The CIDR block cannot be changed. To ensure that routes in the route table do not conflict, the CIDR blocks of all VPCs attached to the enterprise router cannot overlap. Otherwise, communication fails. +- If your existing VPCs have overlapping CIDR blocks, do not use propagated routes. Instead, manually add static routes to the route table of the enterprise router. The destination of the routes can be VPC subnet CIDR blocks or smaller ones. + +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**. + +#. On the **Attachments** tab page, click **Create Attachment**. + + The **Create Attachment** dialog box is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0070__table7204821194013: + + .. table:: **Table 1** Parameters for creating an attachment + + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Parameter | Setting | Example Value | + +=======================+============================================================================================================================================================================================================================================================================================================+===========================+ + | Name | Mandatory | er-attach-01 | + | | | | + | | Enter the attachment name. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | 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 | + | | | | + | | The methods for creating attachments vary by 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. | | + | | | | + | | c. Select a subnet in the selected VPC. You can enter a subnet name to quickly find the target subnet. | | + | | | | + | | - You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC. | | + | | - You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller. | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Auto Add Routes | Optional | Enable | + | | | | + | | - Enable this option if you want to automatically add routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the selected VPC. | | + | | - Do not enable this option if an existing route in the VPC route tables has a destination set to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 because the routes will fail to be added. After the attachment is created, manually :ref:`Step 5: (Optional) Add Routes to VPC Route Tables `. | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Description | Optional | ``-`` | + | | | | + | | Describe the attachment for easy identification. | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Tag | Optional | **Tag key**: test | + | | | | + | | Add tags to help you quickly find your attachment. | **Tag value**: 01 | + | | | | + | | For details, see :ref:`Overview `. | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + +#. Click **OK**. + + The attachment list is displayed. + +#. Check the attachment status. + + If the status changes from **Creating** to **Normal**, the attachment is successfully created. + +.. _er_01_0070__section582517444316: + +Follow-up Procedure +------------------- + +- 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 propagation in the route table. For details, see :ref:`Creating a Propagation `. + + 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 `. + +.. |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 new file mode 100644 index 0000000..a6ae83e --- /dev/null +++ b/umn/source/attachments/attachment_overview.rst @@ -0,0 +1,26 @@ +:original_name: er_01_0019.html + +.. _er_01_0019: + +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 + :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 ` | + +----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+ diff --git a/umn/source/attachments/changing_the_name_of_an_attachment.rst b/umn/source/attachments/changing_the_name_of_an_attachment.rst new file mode 100644 index 0000000..e694914 --- /dev/null +++ b/umn/source/attachments/changing_the_name_of_an_attachment.rst @@ -0,0 +1,55 @@ +:original_name: er_01_0093.html + +.. _er_01_0093: + +Changing the Name of an Attachment +================================== + +Scenarios +--------- + +This section describes how to change the name of an attachment. + +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**. + +#. In the attachment list, click |image2| next to the attachment name. + + The **Edit** dialog box is displayed. + +#. Enter a new name. + + .. table:: **Table 1** Parameter description + + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+================================================================================+=======================+ + | Name | Mandatory | er-attach-01 | + | | | | + | | Enter the attachment name. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The attachment list is displayed. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001243682317.png diff --git a/umn/source/attachments/deleting_an_attachment/deleting_a_virtual_gateway_attachment.rst b/umn/source/attachments/deleting_an_attachment/deleting_a_virtual_gateway_attachment.rst new file mode 100644 index 0000000..6f4119e --- /dev/null +++ b/umn/source/attachments/deleting_an_attachment/deleting_a_virtual_gateway_attachment.rst @@ -0,0 +1,70 @@ +:original_name: er_01_0073.html + +.. _er_01_0073: + +Deleting a Virtual Gateway Attachment +===================================== + +Scenarios +--------- + +This section describes how to delete a virtual 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. + +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 virtual gateway attachment cannot be directly deleted on the **Attachments** page of the enterprise router. + + A virtual gateway attachment will be automatically deleted after you perform the following operations to delete the virtual gateway and its virtual interfaces. + +#. Locate the row that contains the target virtual gateway attachment and click the attached resource. + + Example: vgw-demo + + The virtual gateway attachment details page is displayed. + +#. On the details page, click the virtual gateway. + + The virtual gateway list is displayed. + +#. Check whether the virtual gateway has virtual interfaces. + + - If the virtual gateway has virtual interfaces, delete the virtual interfaces first. + + For details, see section "Deleting a Virtual Interface" in the **Direct Connect User Guide**. + + - If the virtual gateway has no virtual interfaces, go to :ref:`9 `. + +#. .. _er_01_0073__li1323115372813: + + Locate the row that contains the target virtual gateway and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted virtual gateway cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png 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 new file mode 100644 index 0000000..4e42075 --- /dev/null +++ b/umn/source/attachments/deleting_an_attachment/deleting_a_vpc_attachment.rst @@ -0,0 +1,45 @@ +:original_name: er_01_0072.html + +.. _er_01_0072: + +Deleting a VPC Attachment +========================= + +Scenarios +--------- + +This section describes how to delete a VPC attachment from an enterprise router. + +Notes and Constraints +--------------------- + +- Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table. +- After an attachment is deleted, the next hop of its related static routes will be **Blackhole**. If the destination of a packet matches the blackhole route, the packet will be discarded. + +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**. + +#. In the attachment list, locate the row that contains the target VPC attachment, and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted attachment cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png 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 new file mode 100644 index 0000000..21618cb --- /dev/null +++ b/umn/source/attachments/deleting_an_attachment/deleting_a_vpn_gateway_attachment.rst @@ -0,0 +1,61 @@ +: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. + +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 new file mode 100644 index 0000000..e92e3ed --- /dev/null +++ b/umn/source/attachments/deleting_an_attachment/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0022.html + +.. _er_01_0022: + +Deleting an Attachment +====================== + +- :ref:`Deleting a VPC Attachment ` +- :ref:`Deleting a Virtual Gateway Attachment ` +- :ref:`Deleting a VPN Gateway Attachment ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + deleting_a_vpc_attachment + deleting_a_virtual_gateway_attachment + deleting_a_vpn_gateway_attachment diff --git a/umn/source/attachments/index.rst b/umn/source/attachments/index.rst new file mode 100644 index 0000000..3fe7f6c --- /dev/null +++ b/umn/source/attachments/index.rst @@ -0,0 +1,22 @@ +:original_name: er_01_0018.html + +.. _er_01_0018: + +Attachments +=========== + +- :ref:`Attachment Overview ` +- :ref:`Adding VPC Attachments to an Enterprise Router ` +- :ref:`Changing the Name of an Attachment ` +- :ref:`Viewing Details About an Attachment ` +- :ref:`Deleting an Attachment ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + attachment_overview + adding_vpc_attachments_to_an_enterprise_router + changing_the_name_of_an_attachment + viewing_details_about_an_attachment + deleting_an_attachment/index diff --git a/umn/source/attachments/viewing_details_about_an_attachment.rst b/umn/source/attachments/viewing_details_about_an_attachment.rst new file mode 100644 index 0000000..9cbc5a0 --- /dev/null +++ b/umn/source/attachments/viewing_details_about_an_attachment.rst @@ -0,0 +1,39 @@ +:original_name: er_01_0021.html + +.. _er_01_0021: + +Viewing Details About an Attachment +=================================== + +Scenarios +--------- + +This section describes how to view details about the attachments of an enterprise router, including the attachment name, attachment type, and attached resources. + +The methods for viewing details about different types of attachments are the same. This section uses a VPC attachment as an example. + +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**. + +#. On the **Attachments** tab page, you can view: + + - In the attachment list, you can view the attachment status, attachment 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. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst new file mode 100644 index 0000000..0e22360 --- /dev/null +++ b/umn/source/change_history.rst @@ -0,0 +1,12 @@ +:original_name: UgChangeHistory.html + +.. _UgChangeHistory: + +Change History +============== + +=========== ========================================= +Released On Description +=========== ========================================= +2023-03-24 This issue is the first official release. +=========== ========================================= diff --git a/umn/source/conf.py b/umn/source/conf.py old mode 100755 new mode 100644 diff --git a/umn/source/docutils.conf b/umn/source/docutils.conf new file mode 100644 index 0000000..7cbe4c1 --- /dev/null +++ b/umn/source/docutils.conf @@ -0,0 +1,2 @@ +[html writers] +table-style: table, caption-top \ No newline at end of file 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 new file mode 100644 index 0000000..3984a8b --- /dev/null +++ b/umn/source/enterprise_routers/changing_the_azs_of_an_enterprise_router.rst @@ -0,0 +1,58 @@ +: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 new file mode 100644 index 0000000..fdd4486 --- /dev/null +++ b/umn/source/enterprise_routers/creating_an_enterprise_router.rst @@ -0,0 +1,143 @@ +:original_name: er_01_0069.html + +.. _er_01_0069: + +Creating an Enterprise Router +============================= + +Scenarios +--------- + +This section describes how to create an enterprise router. + +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. + +#. Click **Create Enterprise Router** in the upper right corner. + + The **Create Enterprise Router** page is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0069__table7204821194013: + + .. 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. | | + +---------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +#. Click **Create Now**. + +#. Confirm the enterprise router configurations and click **Submit**. + + The enterprise router list is displayed. + +#. Check the enterprise router status. + + If the status changes from **Creating** to **Normal**, the enterprise router is successfully created. + +Follow-Up Operations +-------------------- + +- After an enterprise router is created, attach network instances to the enterprise router and configure routes. For details, see :ref:`Getting Started `. + +- 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 propagation in the route table. For details, see :ref:`Creating a Propagation `. + + 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 `. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/enterprise_routers/deleting_an_enterprise_router.rst b/umn/source/enterprise_routers/deleting_an_enterprise_router.rst new file mode 100644 index 0000000..4a9dc0b --- /dev/null +++ b/umn/source/enterprise_routers/deleting_an_enterprise_router.rst @@ -0,0 +1,41 @@ +:original_name: er_01_0017.html + +.. _er_01_0017: + +Deleting an Enterprise Router +============================= + +Scenarios +--------- + +This section describes how to delete an enterprise router. + +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. + +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** > **Delete**. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted enterprise router cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/enterprise_routers/index.rst b/umn/source/enterprise_routers/index.rst new file mode 100644 index 0000000..62dd8bb --- /dev/null +++ b/umn/source/enterprise_routers/index.rst @@ -0,0 +1,22 @@ +:original_name: er_01_0012.html + +.. _er_01_0012: + +Enterprise Routers +================== + +- :ref:`Creating an Enterprise Router ` +- :ref:`Modifying Settings of an Enterprise Router ` +- :ref:`Changing the AZs of an Enterprise Router ` +- :ref:`Viewing an Enterprise Router ` +- :ref:`Deleting an Enterprise Router ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + creating_an_enterprise_router + modifying_settings_of_an_enterprise_router + changing_the_azs_of_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_settings_of_an_enterprise_router.rst new file mode 100644 index 0000000..bb1f10c --- /dev/null +++ b/umn/source/enterprise_routers/modifying_settings_of_an_enterprise_router.rst @@ -0,0 +1,102 @@ +:original_name: er_01_0013.html + +.. _er_01_0013: + +Modifying Settings of an Enterprise Router +========================================== + +Scenarios +--------- + +This section describes how to modify settings of an enterprise router. You can: + +- Modify the name of an enterprise router. +- Enable or disable **Default Route Table Association**. +- Enable or disable **Default Route Table Propagation**. + +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** > **Modify Settings**. + + The **Modify Settings** page is displayed. + +#. Modify the enterprise router based on :ref:`Table 1 `. + + .. _er_01_0013__table7204821194013: + + .. table:: **Table 1** Parameter description + + +---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=================================+========================================================================================================================================================================+=======================+ + | Name | Mandatory | er-test-01 | + | | | | + | | If you want to change the name of the enterprise router, enter a new name. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Default Route Table Association | Optional | Enable | + | | | | + | | Enabling **Default Route Table Association** can simplify network configurations. After this function is enabled: | | + | | | | + | | a. Select a route table for **Default Association Route Table**. | | + | | b. If you create an attachment to this enterprise router, the attachment will be automatically associated with the default association route table. | | + +---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Association Route Table | Optional | er-rtb-b931 | + | | | | + | | If you enable **Default Route Table Association**, select a route table for **Association Route Table**. | | + | | | | + | | - You can select a custom route table. | | + | | | | + | | - If you do not select a route table, the system will create a route table named **defaultRouteTable** as the default association route table. | | + | | | | + | | If a route table named **defaultRouteTable** already exists, the system will not create it again. | | + +---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Default Route Table Propagation | Optional | Enable | + | | | | + | | Enabling **Default Route Table Propagation** can simplify network configurations. After this function is enabled: | | + | | | | + | | a. Select a route table for **Association Route Table**. | | + | | b. If you create an attachment to this enterprise router, the attachment will be automatically propagated to the default propagation route table. | | + +---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Propagation Route Table | Optional | er-rtb-b931 | + | | | | + | | If you enable **Default Route Table Propagation**, select a route table for **Propagation Route Table**. | | + | | | | + | | - You can select a custom route table. | | + | | | | + | | - If you do not select a route table, the system will create a route table named **defaultRouteTable** as the default propagation route table. | | + | | | | + | | If a route table named **defaultRouteTable** already exists, the system will not create it again. | | + +---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Auto Accept Shared Attachments | Optional | Enable | + | | | | + | | 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 `. | | + +---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The enterprise router list is displayed. + +#. Check the enterprise router settings. + + The settings take effect immediately. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/enterprise_routers/viewing_an_enterprise_router.rst b/umn/source/enterprise_routers/viewing_an_enterprise_router.rst new file mode 100644 index 0000000..0bbd751 --- /dev/null +++ b/umn/source/enterprise_routers/viewing_an_enterprise_router.rst @@ -0,0 +1,40 @@ +:original_name: er_01_0016.html + +.. _er_01_0016: + +Viewing an Enterprise Router +============================ + +Scenarios +--------- + +This section describes how to view basic information about an enterprise router, including the AZs, default route table association and propagation, and creation time. + +You can also view other information about the enterprise router, including: + +- Attachments, such as their name, type, and attached resources. For details, see :ref:`Viewing Details About an Attachment `. +- Route tables, such as the default route table and custom route tables. For details, see :ref:`Viewing Route Tables `. +- Tags. For details, see :ref:`Viewing a Tag `. + +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 addition to the information shown in the enterprise router list, you can go to :ref:`5 ` to view more details. + +#. .. _er_01_0016__li25751958135516: + + Click the name of the target enterprise router to go to the **Basic Information** page. + + View detailed information about the enterprise router. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png 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 new file mode 100644 index 0000000..53f7c6f --- /dev/null +++ b/umn/source/faq/how_do_i_enable_two_attachments_of_an_enterprise_router_to_learn_routes_from_each_other.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0123.html + +.. _er_01_0123: + +How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Each Other? +======================================================================================== + +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: + +- Enterprise router: 64512 +- Virtual gateway attachment: 64513 (BGP ASN of the virtual gateway) +- VPN gateway attachment: 64515 (BGP ASN of the VPN gateway) + +.. note:: + + VPC attachments do not support route learning. 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 new file mode 100644 index 0000000..375c10c --- /dev/null +++ b/umn/source/faq/how_do_i_route_traffic_to_100.64.x.x_through_an_enterprise_router.rst @@ -0,0 +1,130 @@ +:original_name: er_01_0122.html + +.. _er_01_0122: + +How Do I Route Traffic to 100.64.x.x Through an Enterprise Router? +================================================================== + +Scenarios +--------- + +A route with 100.64.x.x as the destination and an enterprise router as the next hop cannot be added to a VPC route table. + +Solutions +--------- + +If you want to route traffic to 100.64.x.x through an enterprise router, you need to create a transit VPC. :ref:`Figure 1 ` shows the network diagram. + +.. _er_01_0122__en-us_topic_0000001135431190_fig121911186551: + +.. figure:: /_static/images/en-us_image_0000001446449166.png + :alt: **Figure 1** Transit VPC network diagram + + **Figure 1** Transit VPC network diagram + +The request traffic from the service VPC to the on-premises data center will be forwarded through the transit VPC, but the response traffic will not. For details, see :ref:`Table 1 `. + +.. _er_01_0122__table198114341557: + +.. table:: **Table 1** Network traffic flows + + +------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Path | Description | + +============================================================================================================+============================================================================================================================================================================================+ + | Request traffic: service VPC → transit VPC → enterprise router → virtual gateway → on-premises data center | #. The service VPC route table has a route with the VPC peering connection as the next hop to forward traffic from the service VPC to the transit VPC. | + | | #. The transit VPC route table has a route with next hop set to the enterprise router to forward traffic from the transit VPC to the enterprise router. | + | | #. The enterprise router route table has a route with next hop set to virtual gateway attachment to forward traffic from the enterprise router to the virtual gateway. | + | | #. The virtual gateway is connected to the virtual interface. Traffic from the virtual gateway is forwarded to the physical connection through the remote gateway of the virtual interface | + | | #. Traffic is sent to the on-premises data center over the connection. | + +------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Response traffic: on-premises data center → virtual gateway → enterprise router → service VPC | #. Traffic is forwarded to the virtual interface through the connection. | + | | #. The virtual interface is connected to the virtual gateway. Traffic from the virtual interface is forwarded to the virtual gateway through the local gateway of the virtual interface. | + | | #. Traffic is forwarded from the virtual gateway to enterprise router. | + | | #. The enterprise router route table has a route with next hop set to the service VPC attachment to forward traffic from the enterprise router to the service VPC. | + +------------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +The required resources and routes are as follows: + +- :ref:`Table 2 `: Required service VPC, transit VPC, enterprise router, and Direct Connect connection that connects the cloud and the on-premises data center +- :ref:`Table 3 `: Required routes of the service VPC, transit VPC, and enterprise router + +.. _er_01_0122__table14233740534: + +.. table:: **Table 2** Resource planning + + +-----------------------+-----------------------+----------------------------------------------------------------------------------------------------------------------------------+ + | Resource | Quantity | Description | + +=======================+=======================+==================================================================================================================================+ + | VPC | 2 | Service VPC that your services are deployed and needs to be attached to the enterprise router | + | | | | + | | | - VPC CIDR block: 10.1.0.0/16 | + | | | - Subnet CIDR block: 10.1.1.0/24 | + +-----------------------+-----------------------+----------------------------------------------------------------------------------------------------------------------------------+ + | | | Transit VPC that is connected to the service VPC over a VPC peering connection and needs to be attached to the enterprise router | + | | | | + | | | - VPC CIDR block: 192.168.0.0/16 | + | | | - Subnet CIDR block: 192.168.1.0/24 | + +-----------------------+-----------------------+----------------------------------------------------------------------------------------------------------------------------------+ + | Enterprise router | 1 | Three attachments on the enterprise router: | + | | | | + | | | - Service VPC attachment: service VPC | + | | | - Transit VPC attachment: transit VPC | + | | | - Virtual gateway attachment: virtual gateway of Direct Connect | + +-----------------------+-----------------------+----------------------------------------------------------------------------------------------------------------------------------+ + | Direct Connect | 1 | - Connection | + | | | - Virtual gateway that needs to be attached to the enterprise router | + | | | - Virtual interface | + | | | | + | | | - Local gateway: 10.0.0.1/30 | + | | | - Remote gateway: 10.0.0.2/30 | + | | | - Remote subnet: subnet of the on-premises data center (100.64.x.x) | + +-----------------------+-----------------------+----------------------------------------------------------------------------------------------------------------------------------+ + +.. _er_01_0122__en-us_topic_0000001135431190_table5325182820514: + +.. table:: **Table 3** Route planning + + +-------------------+-----------------------------------------------+----------------------------+-----------------------+ + | Route Table | Destination | Next Hop | Route Type | + +===================+===============================================+============================+=======================+ + | Service VPC | 100.64.x.x | VPC peering connection | Static route (custom) | + +-------------------+-----------------------------------------------+----------------------------+-----------------------+ + | Transit VPC | 2.2.2.2/32 | VPC peering connection | Static route (custom) | + | | | | | + | | .. note:: | | | + | | | | | + | | 2.2.2.2/32 is mandatory and must be added. | | | + +-------------------+-----------------------------------------------+----------------------------+-----------------------+ + | | 0.0.0.0/0 | Enterprise router | Static route (custom) | + +-------------------+-----------------------------------------------+----------------------------+-----------------------+ + | Enterprise router | 10.1.0.0/16 | Service VPC attachment | Propagated route | + +-------------------+-----------------------------------------------+----------------------------+-----------------------+ + | | 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. + + - An ECS in the VPC has an EIP bound. + - The VPC is being used by ELB, NAT Gateway, or VPC Endpoint. + +#. .. _er_01_0122__li14564823993: + + Create a VPC peering connection between the service VPC and transit VPC. + + .. important:: + + You do not need to add routes for the VPC peering connection. For details about the routes to be added, see :ref:`4 `. + +#. .. _er_01_0122__li92642018194217: + + Add routes to the VPC route tables. + + For details about required routes, see :ref:`Table 3 `. + + a. Add the route to the service VPC route table. + b. Add two routes to the transit VPC route table. diff --git a/umn/source/faq/index.rst b/umn/source/faq/index.rst new file mode 100644 index 0000000..d912e93 --- /dev/null +++ b/umn/source/faq/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0120.html + +.. _er_01_0120: + +FAQ +=== + +- :ref:`Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0 to Its Enterprise Router? ` +- :ref:`How Do I Route Traffic to 100.64.x.x Through an Enterprise Router? ` +- :ref:`How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Each Other? ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + why_traffic_cant_be_forwarded_from_a_vpc_with_a_route_destination_of_0.0.0.0_0_to_its_enterprise_router + how_do_i_route_traffic_to_100.64.x.x_through_an_enterprise_router + how_do_i_enable_two_attachments_of_an_enterprise_router_to_learn_routes_from_each_other 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 new file mode 100644 index 0000000..f9f8a44 --- /dev/null +++ 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 @@ -0,0 +1,46 @@ +:original_name: er_01_0121.html + +.. _er_01_0121: + +Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0 to Its Enterprise Router? +========================================================================================================= + +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: + +- An ECS in the VPC has an EIP bound. + + .. note:: + + Refer to solution 1. + +- The VPC is being used by ELB, NAT Gateway, or VPC Endpoint. + + .. note:: + + Refer to solution 1 or solution 2. + +Solutions +--------- + +Select a solution based on your actual service scenario. + +- Solution 1: Change the destination (0.0.0.0/0) of the default route to a specific IP address range, for example, 192.168.0.0/16. +- Solution 2: Add eight routes with specific IP address ranges as the destination to replace the default route (with a destination of 0.0.0.0/0). + + .. table:: **Table 1** Route destinations and next hops + + =========== ================= + Destination Next Hop + =========== ================= + 128.0.0.0/1 Enterprise router + 64.0.0.0/2 Enterprise router + 32.0.0.0/3 Enterprise router + 16.0.0.0/4 Enterprise router + 8.0.0.0/5 Enterprise router + 4.0.0.0/6 Enterprise router + 2.0.0.0/7 Enterprise router + 1.0.0.0/8 Enterprise router + =========== ================= diff --git a/umn/source/getting_started/index.rst b/umn/source/getting_started/index.rst new file mode 100644 index 0000000..2dc0148 --- /dev/null +++ b/umn/source/getting_started/index.rst @@ -0,0 +1,14 @@ +:original_name: er_01_0059.html + +.. _er_01_0059: + +Getting Started +=============== + +- :ref:`Using an Enterprise Router to Enable Communications Between VPCs in the Same Region ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index.rst new file mode 100644 index 0000000..6185f34 --- /dev/null +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index.rst @@ -0,0 +1,26 @@ +:original_name: er_01_0061.html + +.. _er_01_0061: + +Using an Enterprise Router to Enable Communications Between VPCs in the Same Region +=================================================================================== + +- :ref:`Quick Start ` +- :ref:`Step 1: Plan Networks and Resources ` +- :ref:`Step 2: Create an Enterprise Router ` +- :ref:`Step 3: (Optional) Create VPCs and ECSs ` +- :ref:`Step 4: Create VPC Attachments to the Enterprise Router ` +- :ref:`Step 5: (Optional) Add Routes to VPC Route Tables ` +- :ref:`Step 6: Verify Connectivity Among VPCs ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + quick_start + step_1_plan_networks_and_resources + step_2_create_an_enterprise_router + step_3_optional_create_vpcs_and_ecss + step_4_create_vpc_attachments_to_the_enterprise_router + step_5_optional_add_routes_to_vpc_route_tables + step_6_verify_connectivity_among_vpcs diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/quick_start.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/quick_start.rst new file mode 100644 index 0000000..9260f7a --- /dev/null +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/quick_start.rst @@ -0,0 +1,58 @@ +:original_name: er_01_0062.html + +.. _er_01_0062: + +Quick Start +=========== + +Background +---------- + +Four VPCs are created in region A on public cloud and they need to communicate with each other. + +You can create an enterprise router in region A and attach the four VPCs to the enterprise router. The enterprise router can route traffic among the VPCs so that they can communicate with each other. + + +.. figure:: /_static/images/en-us_image_0000001295153022.png + :alt: **Figure 1** Communications among VPCs in the same region + + **Figure 1** Communications among VPCs in the same region + +.. note:: + + This document describes how to use an enterprise router to quickly allow multiple VPCs in the same region to communicate with each other. + +Procedure +--------- + +:ref:`Figure 2 ` shows the procedure for using an enterprise router to allow multiple VPCs in the same region to communicate with each other. + +.. _er_01_0062__fig10285152624918: + +.. figure:: /_static/images/en-us_image_0000001160921916.png + :alt: **Figure 2** Flowchart for connecting VPCs in the same region + + **Figure 2** Flowchart for connecting VPCs in the same region + +.. table:: **Table 1** Steps for connecting VPCs in the same region + + +-----------------------+-----------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | No. | Step | Description | + +=======================+=============================================================================+==============================================================================================================================================================================================================================================================================================================================================+ + | 1 | :ref:`Step 1: Plan Networks and Resources ` | Plan CIDR blocks and the number of resources. | + +-----------------------+-----------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 2 | :ref:`Step 2: Create an Enterprise Router ` | Create one enterprise router for connecting VPCs in the same region. | + +-----------------------+-----------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 3 | :ref:`Step 3: (Optional) Create VPCs and ECSs ` | Create four VPCs and four ECSs. You can change the resource quantity and specifications as needed. | + | | | | + | | | If you already have these resources, skip this step. | + +-----------------------+-----------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 4 | :ref:`Step 4: Create VPC Attachments to the Enterprise Router ` | Attach the four VPCs to the enterprise router. | + +-----------------------+-----------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 5 | :ref:`Step 5: (Optional) Add Routes to VPC Route Tables ` | Add routes to the route tables of the VPCs for communication with the enterprise router. | + | | | | + | | | - If you enable **Auto Add Routes** when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC. | + | | | - If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not need to enable **Auto Add Routes**. After the attachment is created, manually add routes. | + +-----------------------+-----------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 6 | :ref:`Step 6: Verify Connectivity Among VPCs ` | Log in to the ECS and run the **ping** command to verify the connectivity among VPCs. | + +-----------------------+-----------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_1_plan_networks_and_resources.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_1_plan_networks_and_resources.rst new file mode 100644 index 0000000..34b0192 --- /dev/null +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_1_plan_networks_and_resources.rst @@ -0,0 +1,164 @@ +:original_name: er_01_0063.html + +.. _er_01_0063: + +Step 1: Plan Networks and Resources +=================================== + +To use an enterprise router to connect VPCs in the same region, you need to: + +- :ref:`Network Planning `: Plan CIDR blocks of VPCs and subnets, and route tables of VPCs and the enterprise router. +- :ref:`Resource Planning `: Plan the quantity, names, and parameters of cloud resources, including VPCs, ECSs, and the enterprise router. + +.. _er_01_0063__section2162184314336: + +Network Planning +---------------- + +:ref:`Figure 1 ` and :ref:`Table 2 ` show the network planning and its description for communications among VPCs in the same region. + +.. _er_01_0063__fig121911186551: + +.. figure:: /_static/images/en-us_image_0000001193598903.png + :alt: **Figure 1** Network planning for communications among VPCs in the same region + + **Figure 1** Network planning for communications among VPCs in the same region + +.. table:: **Table 1** Network traffic flows + + +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Scenario | Description | + +===================================+======================================================================================================================================================================+ + | Request from VPC 1 to VPC 3 | #. The route table of VPC 1 has a route with next hop set to the enterprise router to forward traffic from VPC 1 to the enterprise router. | + | | #. The route table of the enterprise router has a propagated route with next hop set to the VPC 3 attachment to forward traffic from the enterprise router to VPC 3. | + +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Response from VPC 3 to VPC 1 | #. The route table of VPC 3 has a route with next hop set to the enterprise router to forward traffic from VPC 3 to the enterprise router. | + | | #. The route table of the enterprise router has a propagated route with next hop set to the VPC 1 attachment to forward traffic from the enterprise router to VPC 1. | + +-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +.. _er_01_0063__table350914311846: + +.. table:: **Table 2** Network planning for communications among VPCs in the same region + + +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Resource | Description | + +===================================+======================================================================================================================================================================================================================================================+ + | VPC | - The CIDR blocks of the VPCs to be connected cannot overlap with each other. | + | | | + | | In this example, the CIDR blocks of the VPCs are propagated to the enterprise router route table as the destination in routes. The CIDR blocks cannot be modified and overlapping CIDR blocks may cause route conflicts. | + | | | + | | If your existing VPCs have overlapping CIDR blocks, do not use propagated routes. Instead, you need to manually add static routes to the route table of the enterprise router. The destination can be VPC subnet CIDR blocks or smaller ones. | + | | | + | | - Each VPC has a default route table. | + | | | + | | - Routes in the default route table can be: | + | | | + | | - Local: a system route for communications between subnets in a VPC. | + | | - Enterprise router: custom routes with 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations for routing traffic from a VPC subnet to the enterprise router. See :ref:`Table 3 ` for route details. | + +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Enterprise router | After **Default Route Table Association** and **Default Route Table Propagation** are enabled and a VPC attachment is created, the system will automatically: | + | | | + | | - Associate VPC attachments with the default route table of the enterprise router. | + | | - Propagate VPC attachments with the default route table of the enterprise router. The route table automatically learns the VPC CIDR block as the destination of routes. For details, see :ref:`Table 4 `. | + +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | ECS | The four ECSs are in different VPCs. If the ECSs are associated with different security groups, add rules to their security groups to allow access to each other. | + +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +.. _er_01_0063__table5325182820514: + +.. table:: **Table 3** VPC route table + + ============== ================= ==================== + Destination Next Hop Route Type + ============== ================= ==================== + 10.0.0.0/8 Enterprise router Static route: Custom + 172.16.0.0/12 Enterprise Router Static route: Custom + 192.168.0.0/16 Enterprise Router Static route: Custom + ============== ================= ==================== + +.. note:: + + - If you enable **Auto Add Routes** when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC. + - If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not to enable **Auto Add Routes**. After the attachment is created, manually add routes. + - Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router. + +.. _er_01_0063__table4211920161010: + +.. table:: **Table 4** Enterprise router route table + + +----------------------------------+--------------------------------+------------------+ + | Destination | Next Hop | Route Type | + +==================================+================================+==================+ + | VPC 1 CIDR block: 192.168.0.0/16 | VPC 1 attachment: er-attach-01 | Propagated route | + +----------------------------------+--------------------------------+------------------+ + | VPC 2 CIDR block: 172.16.0.0/16 | VPC 2 attachment: er-attach-02 | Propagated route | + +----------------------------------+--------------------------------+------------------+ + | VPC 3 CIDR block: 10.1.0.0/16 | VPC 3 attachment: er-attach-03 | Propagated route | + +----------------------------------+--------------------------------+------------------+ + | VPC 4 CIDR block: 10.2.0.0/16 | VPC 4 attachment: er-attach-04 | Propagated route | + +----------------------------------+--------------------------------+------------------+ + +.. _er_01_0063__section94881859164511: + +Resource Planning +----------------- + +The enterprise router, VPCs, and ECSs must be in the same region. You can select any AZ within the region. + +.. note:: + + The following resource details are only examples. You can modify them as required. + +- One enterprise router. + + .. table:: **Table 5** Enterprise router details + + +------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+ + | Enterprise Router Name | ASN | Default Route Table Association | Default Route Table Propagation | Association Route Table | Propagation Route Table | Attachment | + +========================+=======+=================================+=================================+=========================+=========================+==============+ + | er-test-01 | 64512 | Enable | Enable | Default route table | Default route table | er-attach-01 | + +------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+ + | | | | | | | er-attach-02 | + +------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+ + | | | | | | | er-attach-03 | + +------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+ + | | | | | | | er-attach-04 | + +------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+ + +- Four VPCs, each with a unique CIDR block. + + .. _er_01_0063__table195012516413: + + .. table:: **Table 6** VPC details + + +-------------+----------------+----------------+-------------------+-------------------------+ + | VPC Name | VPC CIDR Block | Subnet Name | Subnet CIDR Block | Association Route Table | + +=============+================+================+===================+=========================+ + | vpc-demo-01 | 192.168.0.0/16 | subnet-demo-01 | 192.168.1.0/24 | Default route table | + +-------------+----------------+----------------+-------------------+-------------------------+ + | vpc-demo-02 | 172.16.0.0/16 | subnet-demo-02 | 172.16.1.0/24 | Default route table | + +-------------+----------------+----------------+-------------------+-------------------------+ + | vpc-demo-03 | 10.1.0.0/16 | subnet-demo-03 | 10.1.1.0/24 | Default route table | + +-------------+----------------+----------------+-------------------+-------------------------+ + | vpc-demo-04 | 10.2.0.0/16 | subnet-demo-04 | 10.2.1.0/24 | Default route table | + +-------------+----------------+----------------+-------------------+-------------------------+ + +- Four ECSs in four different VPCs. + + .. _er_01_0063__table154151647412: + + .. table:: **Table 7** ECS details + + +-------------+---------------+-------------+----------------+------------------------------+--------------------+ + | ECS | Image | VPC | Subnet | Security Group | Private IP Address | + +=============+===============+=============+================+==============================+====================+ + | ecs-demo-01 | Public image: | vpc-demo-01 | subnet-demo-01 | sg-demo | 192.168.1.12 | + | | | | | | | + | | EulerOS 2.5 6 | | | (general-purpose web server) | | + +-------------+---------------+-------------+----------------+------------------------------+--------------------+ + | ecs-demo-02 | | vpc-demo-02 | subnet-demo-02 | | 172.16.1.189 | + +-------------+---------------+-------------+----------------+------------------------------+--------------------+ + | ecs-demo-03 | | vpc-demo-03 | subnet-demo-03 | | 10.1.1.105 | + +-------------+---------------+-------------+----------------+------------------------------+--------------------+ + | ecs-demo-04 | | vpc-demo-04 | subnet-demo-04 | | 10.2.1.83 | + +-------------+---------------+-------------+----------------+------------------------------+--------------------+ 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 new file mode 100644 index 0000000..21f9fa6 --- /dev/null +++ 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 @@ -0,0 +1,72 @@ +:original_name: er_01_0064.html + +.. _er_01_0064: + +Step 2: Create an Enterprise Router +=================================== + +Scenarios +--------- + +This section describes how to create an enterprise router. + +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. + +#. Click **Create Enterprise Router** in the upper right corner. + + The **Create Enterprise Router** page is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0064__table7204821194013: + + .. table:: **Table 1** Parameters for creating an enterprise router + + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=================================+================================================================================================================================================================================+=======================+ + | Region | Select the region nearest to your target users. Once the enterprise router is created, the region cannot be changed. | ``-`` | + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | AZ | Select two AZs to deploy your enterprise router. You can change them after the enterprise router is created. | AZ1 | + | | | | + | | | AZ2 | + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | 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 | + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | 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 | + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Enterprise Project | Select an enterprise project for the enterprise router. You can change it after the enterprise router is created. | default | + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Tag | Add tags to help you identify your enterprise router. You can change them after the enterprise router is created. | **Tag key**: test | + | | | | + | | | **Tag value**: 01 | + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | Provide supplementary information about the enterprise router. You can change it after the enterprise router is created. | ``-`` | + +---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +#. Click **Create Now**. + +#. Confirm the enterprise router configurations and click **Submit**. + + The enterprise router list is displayed. + +#. Check the enterprise router status. + + If the status changes from **Creating** to **Normal**, the enterprise router is successfully created. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_3_optional_create_vpcs_and_ecss.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_3_optional_create_vpcs_and_ecss.rst new file mode 100644 index 0000000..ba9f233 --- /dev/null +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_3_optional_create_vpcs_and_ecss.rst @@ -0,0 +1,39 @@ +:original_name: er_01_0065.html + +.. _er_01_0065: + +Step 3: (Optional) Create VPCs and ECSs +======================================= + +Scenarios +--------- + +This section describes how to create VPCs and ECSs. + +If you already have VPCs and ECS, skip this section. + +Notes and Constraints +--------------------- + +- The CIDR blocks of the VPCs to be connected cannot overlap with each other. + + In this example, the CIDR blocks of the VPCs are propagated to the enterprise router route table as the destination in routes. The CIDR blocks cannot be modified and overlapping CIDR blocks may cause route conflicts. + + If your existing VPCs have overlapping CIDR blocks, do not use propagated routes. Instead, you need to manually add static routes to the route table of the enterprise router. The destination can be VPC subnet CIDR blocks or smaller ones. + +- Four ECSs must be in the same security group. If your ECSs are in different security groups, add rules to their security groups to allow access to each other. + +Procedure +--------- + +#. Create four VPCs with subnets. + + For details, see "Creating a VPC" in the *Virtual Private Cloud User Guide*. + + For VPC and subnet details in this example, see :ref:`Table 6 `. + +#. Create four ECSs. + + For details, see "Creating an ECS" in the *Elastic Cloud Server User Guide*. + + For ECS details in this example, see :ref:`Table 7 `. 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 new file mode 100644 index 0000000..ce3d8b5 --- /dev/null +++ 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 @@ -0,0 +1,85 @@ +:original_name: er_01_0066.html + +.. _er_01_0066: + +Step 4: Create VPC Attachments to the Enterprise Router +======================================================= + +Scenarios +--------- + +This section describes how to attach the four VPCs to the enterprise router. + +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. + +#. .. _er_01_0066__li25751958135516: + + 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**. + +#. On the **Attachments** tab page, click **Create Attachment**. + + The **Create Attachment** dialog box is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0066__table7204821194013: + + .. table:: **Table 1** Parameter description + + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Parameter | Setting | Example Value | + +=======================+=====================================================================================================================================================================================================================================================================================================================================================================================================================================+===========================+ + | Name | Specify the name of the VPC attachment. You can change it after the attachment is created. | er-attach-01 | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Attachment Type | a. Select **VPC**. The type cannot be changed after the attachment is created. | - Attachment Type: VPC | + | | b. Select the VPC to be attached to the enterprise router from the drop-down list. The VPC cannot be changed after the attachment is created. | - VPC: vpc-demo-01 | + | | c. Select the subnet to be attached to the enterprise router from the drop-down list. The subnet cannot be changed after the attachment is created. | - Subnet: subnet-demo-01 | + | | | | + | | - You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC. | | + | | - You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Auto Add Routes | - If you enable **Auto Add Routes** when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC. | Enable | + | | - If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not to enable **Auto Add Routes**. After the attachment is created, manually add routes. | | + | | - Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Description | Provide supplementary description about the attachment. You can change it after the attachment is created. | ``-`` | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + | Tag | Add tags to help you identify your attachment. You can change them after the attachment is created. | **Tag key**: test | + | | | | + | | | **Tag value**: 01 | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+ + +#. Click **OK**. + + The attachment list is displayed. + +#. .. _er_01_0066__li1377219211383: + + Check the attachment status. + + If the status changes from **Creating** to **Normal**, the attachment is successfully created. + +#. Repeat :ref:`5 ` to :ref:`9 ` to attach the other three VPCs to the enterprise router. + + .. 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: + + - 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. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_5_optional_add_routes_to_vpc_route_tables.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_5_optional_add_routes_to_vpc_route_tables.rst new file mode 100644 index 0000000..6c8e645 --- /dev/null +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_5_optional_add_routes_to_vpc_route_tables.rst @@ -0,0 +1,89 @@ +:original_name: er_01_0067.html + +.. _er_01_0067: + +Step 5: (Optional) Add Routes to VPC Route Tables +================================================= + +Scenarios +--------- + +This section describes how to add routes to VPC route tables for traffic to route through the enterprise router. + +.. note:: + + - If you enable **Auto Add Routes** when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC. + - If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not need to enable **Auto Add Routes**. After the attachment is created, manually add routes. + +Notes and Constraints +--------------------- + +- If your VPC only has a default route table, all subnets in it are associated with the default route table. You only need to add routes to the default route table for traffic to route through the enterprise router. +- If your VPC has multiple custom route tables and different subnets in the VPC are associated with different route tables, you need to add routes to each route table associated with the subnets for traffic to route through the enterprise router. + +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**. + +#. .. _er_01_0067__li18721151820134: + + Locate the row that contains the target attachment and click the VPC in the **Attached Resource** column. + + The VPC basic information page is displayed. + +#. In the **Networking Components** area, click the number next to **Subnets**. + + The **Subnets** page is displayed. + +#. Locate the row that contains the target subnet and click the route table name in the **Route Table** column. + + The route table details page is displayed. + +#. Under **Routes**, click **Add Route**. + + The **Add Route** dialog box is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0067__table7204821194013: + + .. table:: **Table 1** Parameter description + + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+=====================================================================================================================================================================================================================================================================================================================================================================================================================================+=======================+ + | Destination | The destination is used to route traffic from this VPC to other VPCs attached to the enterprise router. You can change it after the route is created. | 10.0.0.0/8 | + | | | | + | | - Set the destination to the CIDR blocks of VPCs or their subnets that your VPC need to communicate with. | | + | | - Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Next Hop Type | Select **Enterprise Router**. You can change it after the route is created. | Enterprise Router | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Next Hop | Select the target enterprise router. You can change it after the route is created. | er-test-01 | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | Provide supplementary information about the route. You can change the route after it is created. | ``-`` | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +#. .. _er_01_0067__li484795713352: + + Click **OK**. + + You can view the route in the route list. + +#. Repeat :ref:`6 ` to :ref:`11 ` to add routes to route tables of other VPCs. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_6_verify_connectivity_among_vpcs.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_6_verify_connectivity_among_vpcs.rst new file mode 100644 index 0000000..5e32076 --- /dev/null +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_6_verify_connectivity_among_vpcs.rst @@ -0,0 +1,36 @@ +:original_name: er_01_0068.html + +.. _er_01_0068: + +Step 6: Verify Connectivity Among VPCs +====================================== + +Scenarios +--------- + +This section describes how to log in to ECSs and verify the connectivity between VPCs. + +Procedure +--------- + +#. .. _er_01_0068__li154091419132410: + + Log in to the ECS. + +#. .. _er_01_0068__li105742451915: + + Run the following command on the ECS: + + **ping** *IP address of the ECS* + + If you log in to ecs-demo-01 to verify the connectivity between vpc-demo-01 and vpc-demo-02, run the following command: + + **ping 10.1.1.105** + + If information similar to the following is displayed, the two VPCs can communicate with each other. + + |image1| + +#. Repeat :ref:`1 ` to :ref:`2 ` to verify the connectivity between other VPCs. + +.. |image1| image:: /_static/images/en-us_image_0000001195294363.png diff --git a/umn/source/index.rst b/umn/source/index.rst index a9b9fd5..46dcf8c 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -1,3 +1,22 @@ -================================================= -Welcome to the documentation of enterprise-router -================================================= +============================== +Enterprise Router - User Guide +============================== + +.. toctree:: + :maxdepth: 1 + + service_overview/index + getting_started/index + enterprise_routers/index + attachments/index + route_tables/index + associations/index + propagations/index + routes/index + sharing/index + monitoring/index + interconnecting_with_cts/index + tags/index + quotas/index + faq/index + change_history diff --git a/umn/source/interconnecting_with_cts/index.rst b/umn/source/interconnecting_with_cts/index.rst new file mode 100644 index 0000000..18e0552 --- /dev/null +++ b/umn/source/interconnecting_with_cts/index.rst @@ -0,0 +1,16 @@ +:original_name: er_01_0090.html + +.. _er_01_0090: + +Interconnecting with CTS +======================== + +- :ref:`Key Operations Recorded by CTS ` +- :ref:`Viewing Traces ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + key_operations_recorded_by_cts + viewing_traces 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 new file mode 100644 index 0000000..75d895e --- /dev/null +++ b/umn/source/interconnecting_with_cts/key_operations_recorded_by_cts.rst @@ -0,0 +1,58 @@ +:original_name: er_01_0091.html + +.. _er_01_0091: + +Key Operations Recorded by CTS +============================== + +An enterprise router is a central router that interconnects all of your VPCs and on-premises networks. + +With CTS, you can record operations associated with your enterprise routers for future query, audit, and backtracking. + +.. table:: **Table 1** Enterprise router operations recorded by CTS + + +--------------------------------------------+---------------+------------------------+ + | Operation | Resource Type | Trace Name | + +============================================+===============+========================+ + | Creating an Enterprise Router | erInstance | createInstance | + +--------------------------------------------+---------------+------------------------+ + | Modifying Settings of 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 | + +--------------------------------------------+---------------+------------------------+ + | Deleting an Attachment | erAttachment | deleteAttachment | + +--------------------------------------------+---------------+------------------------+ + | Accepting an Attachment Request | erAttachment | acceptAttachment | + +--------------------------------------------+---------------+------------------------+ + | Rejecting an Attachment Request | erAttachment | rejectAttachment | + +--------------------------------------------+---------------+------------------------+ + | Creating a Route Table | erRouteTable | createRouteTable | + +--------------------------------------------+---------------+------------------------+ + | Modifying Route Table Information | erRouteTable | updateRouteTable | + +--------------------------------------------+---------------+------------------------+ + | Deleting a Route Table | erRouteTable | deleteRouteTable | + +--------------------------------------------+---------------+------------------------+ + | Creating a Static Route | erStaticRoute | createStaticRoute | + +--------------------------------------------+---------------+------------------------+ + | Batch Creating Static Routes | erStaticRoute | batchCreateStaticRoute | + +--------------------------------------------+---------------+------------------------+ + | Deleting a Static Route | erStaticRoute | deleteStaticRoute | + +--------------------------------------------+---------------+------------------------+ + | Batch Deleting Static Routes | erStaticRoute | batchDeleteStaticRoute | + +--------------------------------------------+---------------+------------------------+ + | Modifying a Static Route | erStaticRoute | updateStaticRoute | + +--------------------------------------------+---------------+------------------------+ + | Creating an Association | erAssociation | createAssociation | + +--------------------------------------------+---------------+------------------------+ + | Deleting an Association | erAssociation | deleteAssociation | + +--------------------------------------------+---------------+------------------------+ + | Creating a Propagation | erPropagation | createPropagation | + +--------------------------------------------+---------------+------------------------+ + | Deleting a Propagation | erPropagation | deletePropagation | + +--------------------------------------------+---------------+------------------------+ diff --git a/umn/source/interconnecting_with_cts/viewing_traces.rst b/umn/source/interconnecting_with_cts/viewing_traces.rst new file mode 100644 index 0000000..9234ad8 --- /dev/null +++ b/umn/source/interconnecting_with_cts/viewing_traces.rst @@ -0,0 +1,50 @@ +:original_name: er_01_0092.html + +.. _er_01_0092: + +Viewing Traces +============== + +**Scenarios** +------------- + +After CTS is enabled, CTS starts recording operations on cloud resources. The CTS management console stores the last seven days of operation records. + +This section describes how to query or export the last seven days of operation records on the management console. + +Procedure +--------- + +#. Log in to the management console. + +#. Click |image1| in the upper left corner and select the desired region and project. + +#. Click **Service List**. Under **Management & Governance**, click **Cloud Trace Service**. + + The **Cloud Trace Service** console is displayed. + +#. In the navigation pane on the left, choose **Trace List**. + + The **Trace List** page is displayed. + +#. Specify filters as needed. + + The following filters are available: + + - **Trace Source**, **Resource Type**, and **Search By** + + - If you select **Trace name** for **Search By**, select a trace name. + - If you select **Resource ID** for **Search By**, select or enter a resource ID. + - If you select **Resource name** for **Search By**, select or enter a resource name. + + - **Operator**: Select a specific operator (a user other than an account). + - **Trace Status**: Select **All trace statuses**, **Normal**, **Warning**, or **Incident**. + - Time range: Select any time range in the last seven days. + +#. Expand the trace for details. + +#. 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*. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/monitoring/creating_alarm_rules.rst b/umn/source/monitoring/creating_alarm_rules.rst new file mode 100644 index 0000000..3a69d85 --- /dev/null +++ b/umn/source/monitoring/creating_alarm_rules.rst @@ -0,0 +1,51 @@ +:original_name: er_01_0105.html + +.. _er_01_0105: + +Creating Alarm Rules +==================== + +Scenarios +--------- + +This section describes how to create alarm rules and notifications for enterprise routers and their attachments. + +You can create an alarm rule to configure the conditions that trigger an alarm and determine whether to send notifications when there is the alarm. + +If you create an alarm rule for a metric, you can timely know metric exceptions and rectify the exceptions. + +Procedure +--------- + +#. Log in to the management console. + +#. Click |image1| in the upper left corner and select the desired region and project. + +#. Click **Service List**. Under **Management & Deployment**, click **Cloud Eye**. + + The **Cloud Eye** console is displayed. + +#. In the navigation pane on the left, choose **Cloud Service Monitoring** > **Enterprise Router**. + + The enterprise router list is displayed. + +#. Create alarm rules for enterprise routers and their attachments: + + - Enterprise router + + a. In the enterprise router list, locate the row that contains the enterprise router and click **Create Alarm Rule** in the **Operation** column. + + The **Create Alarm Rule** page is displayed. + + b. On the **Create Alarm Rule** page, set parameters as prompted. + + - Attachment + + a. In the enterprise router list, locate the row that contains the enterprise router, click |image2| to view its attachments, locate the row that contains the attachment, and click **Create Alarm Rule** in the **Operation** column. + + The **Create Alarm Rule** page is displayed. + + b. On the **Create Alarm Rule** page, set parameters as prompted. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001214183634.png diff --git a/umn/source/monitoring/index.rst b/umn/source/monitoring/index.rst new file mode 100644 index 0000000..1bdf65a --- /dev/null +++ b/umn/source/monitoring/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0102.html + +.. _er_01_0102: + +Monitoring +========== + +- :ref:`Supported Metrics ` +- :ref:`Viewing Metrics ` +- :ref:`Creating Alarm Rules ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + supported_metrics + viewing_metrics + creating_alarm_rules diff --git a/umn/source/monitoring/supported_metrics.rst b/umn/source/monitoring/supported_metrics.rst new file mode 100644 index 0000000..472f7c2 --- /dev/null +++ b/umn/source/monitoring/supported_metrics.rst @@ -0,0 +1,140 @@ +:original_name: er_01_0103.html + +.. _er_01_0103: + +Supported Metrics +================= + +Function +-------- + +This section describes monitoring metrics reported by Enterprise Router to Cloud Eye as well as their namespaces, metrics, and dimensions. You can use the Cloud Eye management console or APIs to obtain the monitoring metrics and alarms generated for Enterprise Router. + +Namespace +--------- + +SYS.ER + +Metrics +------- + +You can use Cloud Eye to monitor the network status of enterprise routes and their attachments. + +- :ref:`Table 1 ` +- :ref:`Table 2 ` + +.. _er_01_0103__en-us_topic_0024607920_table6444895193247: + +.. table:: **Table 1** Monitoring metrics of an enterprise router + + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | ID | Name | Description | Value Range | Monitored Object | Monitoring Interval (Raw Data) | + +=================================+===========================================+======================================================================+=============+===================+================================+ + | instance_bytes_in | Inbound Traffic | Network traffic going into the enterprise router | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: byte | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | instance_bytes_out | Outbound Traffic | Network traffic going out of the enterprise router | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: byte | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | instance_bits_rate_in | Inbound Bandwidth | Network traffic per second going into the enterprise router | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: bit/s | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | instance_bits_rate_out | Outbound Bandwidth | Network traffic per second going out of the enterprise router | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: bit/s | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | instance_packets_in | Inbound PPS | Packets per second going into the enterprise router | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: packet/s | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | instance_packets_out | Outbound PPS | Packets per second going out of the enterprise router | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: packet/s | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | instance_packets_drop_blackhole | Packets Dropped by Black Hole Route | Packets dropped by black hole route of the enterprise router | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: count | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + | instance_packets_drop_noroute | Packets Dropped Due to No Matching Routes | Packets dropped because the enterprise router has no matching routes | >= 0 | Enterprise router | 1 minute | + | | | | | | | + | | | Unit: count | | | | + +---------------------------------+-------------------------------------------+----------------------------------------------------------------------+-------------+-------------------+--------------------------------+ + +.. _er_01_0103__table1914912214313: + +.. table:: **Table 2** Monitoring metrics of an attachment + + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ID | Name | Description | Value Range | Monitored Object | Monitoring Interval (Raw Data) | + +===================================+===========================================+===============================================================+=============+==================+================================+ + | attachment_bytes_in | Inbound Traffic | Network traffic going into the attachment | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: byte | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | attachment_bytes_out | Outbound Traffic | Network traffic going out of the attachment | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: byte | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | attachment_bits_rate_in | Inbound Bandwidth | Network traffic per second going into the attachment | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: bit/s | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | attachment_bits_rate_out | Outbound Bandwidth | Network traffic per second going out of the attachment | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: bit/s | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | attachment_packets_in | Inbound PPS | Packets per second going into the attachment | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: packet/s | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | attachment_packets_out | Outbound PPS | Packets per second going out of the attachment | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: packet/s | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | attachment_packets_drop_blackhole | Packets Dropped by Black Hole Route | Packets dropped by black hole route of the attachment | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: count | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + | attachment_packets_drop_noroute | Packets Dropped Due to No Matching Routes | Packets dropped because the attachment has no matching routes | >= 0 | Attachment | 1 minute | + | | | | | | | + | | | Unit: count | | | | + +-----------------------------------+-------------------------------------------+---------------------------------------------------------------+-------------+------------------+--------------------------------+ + +If a monitored object has multiple dimensions, all dimensions are mandatory when you use APIs to query the metrics. + +- Query a single metric: + + .. code-block:: + + dim.0=er_instance_id,d9f7b61f-e211-4bce-ac5f-2b76f3d0cf1d&dim.1=er_attachment_id,659614a0-e559-46c0-86ca-00c03c3d61b8 + +- Query metrics in batches: + + .. code-block:: + + "dimensions": [ + { + "name": "er_instance_id", + "value": "d9f7b61f-e211-4bce-ac5f-2b76f3d0cf1d" + }, + { + "name": "er_attachment_id", + "value": "659614a0-e559-46c0-86ca-00c03c3d61b8" + } + ] + +Dimensions +---------- + +================ ================= +Key Value +================ ================= +er_instance_id Enterprise router +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**. diff --git a/umn/source/monitoring/viewing_metrics.rst b/umn/source/monitoring/viewing_metrics.rst new file mode 100644 index 0000000..be4f5a0 --- /dev/null +++ b/umn/source/monitoring/viewing_metrics.rst @@ -0,0 +1,47 @@ +:original_name: er_01_0104.html + +.. _er_01_0104: + +Viewing Metrics +=============== + +Scenarios +--------- + +This section describes how to view monitoring metrics of enterprise routers and their attachments. + +Procedure +--------- + +#. Log in to the management console. + +#. Click |image1| in the upper left corner and select the desired region and project. + +#. Click **Service List**. Under **Management & Deployment**, click **Cloud Eye**. + + The **Cloud Eye** console is displayed. + +#. In the navigation pane on the left, choose **Cloud Service Monitoring** > **Enterprise Router**. + + The enterprise router list is displayed. + +#. View the real-time monitoring metrics of enterprise routers and their attachments: + + - View metrics of an enterprise router. + + a. In the enterprise router list, locate the row that contains the enterprise router and click **View Metric** in the **Operation** column. + + The metrics are displayed. + + b. View metrics of the enterprise router. + + - View metrics of an attachment. + + a. In the enterprise router list, locate the row that contains the enterprise router, click |image2| to view its attachments, locate the row that contains the attachment, and click **View Metric** in the **Operation** column. + + The metrics are displayed. + + b. View metrics of the attachment. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001258580523.png diff --git a/umn/source/propagations/creating_a_propagation.rst b/umn/source/propagations/creating_a_propagation.rst new file mode 100644 index 0000000..f23a298 --- /dev/null +++ b/umn/source/propagations/creating_a_propagation.rst @@ -0,0 +1,68 @@ +:original_name: er_01_0036.html + +.. _er_01_0036: + +Creating a Propagation +====================== + +Scenarios +--------- + +This section describes how to create a propagation in the route table of an enterprise router. + +Notes and Constraints +--------------------- + +You can create propagations for the same attachment in different route tables. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table where you want to create a propagation. On the **Propagations** tab page, click **Create Propagation**. + + The **Create Propagation** dialog box is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0036__table7204821194013: + + .. table:: **Table 1** Parameters for creating a propagation + + +-----------------------+--------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+============================================================================================+=======================+ + | Attachment Type | Mandatory | VPC | + | | | | + | | Select an attachment type. | | + | | | | + | | - **VPC** | | + | | - **Virtual gateway** | | + | | - **VPN gateway** | | + | | | | + | | For more information, see :ref:`Attachment Overview `. | | + +-----------------------+--------------------------------------------------------------------------------------------+-----------------------+ + | Attachment | Mandatory | er-attach-02 | + | | | | + | | In the drop-down list, select the attachment who will propagate routes to the route table. | | + +-----------------------+--------------------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The propagation list is displayed. You can view your propagation. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/propagations/deleting_a_propagation.rst b/umn/source/propagations/deleting_a_propagation.rst new file mode 100644 index 0000000..871fc4d --- /dev/null +++ b/umn/source/propagations/deleting_a_propagation.rst @@ -0,0 +1,44 @@ +:original_name: er_01_0038.html + +.. _er_01_0038: + +Deleting a Propagation +====================== + +Scenarios +--------- + +This section describes how to delete a propagation from the route table of an enterprise router. + +Notes and Constraints +--------------------- + +Propagated routes are learned through propagation. Deleting a propagation will also delete the propagated routes. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table where you want to delete a propagation. On the **Propagations** tab page, locate the row that contains the propagation you want to delete and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted propagation cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/propagations/index.rst b/umn/source/propagations/index.rst new file mode 100644 index 0000000..2afed12 --- /dev/null +++ b/umn/source/propagations/index.rst @@ -0,0 +1,20 @@ +:original_name: er_01_0034.html + +.. _er_01_0034: + +Propagations +============ + +- :ref:`Propagation Overview ` +- :ref:`Creating a Propagation ` +- :ref:`Viewing a Propagation ` +- :ref:`Deleting a Propagation ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + propagation_overview + creating_a_propagation + viewing_a_propagation + deleting_a_propagation diff --git a/umn/source/propagations/propagation_overview.rst b/umn/source/propagations/propagation_overview.rst new file mode 100644 index 0000000..f2f3090 --- /dev/null +++ b/umn/source/propagations/propagation_overview.rst @@ -0,0 +1,34 @@ +:original_name: er_01_0035.html + +.. _er_01_0035: + +Propagation Overview +==================== + +You can create a propagation for each attachment to propagate routes to one or more route tables on an enterprise router. + +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: + +.. figure:: /_static/images/en-us_image_0000001477172813.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 | | | + +-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/propagations/viewing_a_propagation.rst b/umn/source/propagations/viewing_a_propagation.rst new file mode 100644 index 0000000..fb0ccf7 --- /dev/null +++ b/umn/source/propagations/viewing_a_propagation.rst @@ -0,0 +1,35 @@ +:original_name: er_01_0037.html + +.. _er_01_0037: + +Viewing a Propagation +===================== + +Scenarios +--------- + +This section describes how to view a propagation in the route table of an enterprise router. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. 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. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/quotas/increasing_quotas.rst b/umn/source/quotas/increasing_quotas.rst new file mode 100644 index 0000000..e7e2d70 --- /dev/null +++ b/umn/source/quotas/increasing_quotas.rst @@ -0,0 +1,30 @@ +:original_name: er_01_0058.html + +.. _er_01_0058: + +Increasing Quotas +================= + +Scenarios +--------- + +The following provides operations for you to increase the quotas of enterprise routers and related resources in your account. + +How Do I Apply for a Higher Quota? +---------------------------------- + +The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email. + +Before dialing the hotline number or sending an email, make sure that the following information has been obtained: + +- Domain name, project name, and project ID, which can be obtained by performing the following operations: + + Log in to the management console using the cloud account, click the username in the upper right corner, select **My Credentials** from the drop-down list, and obtain the domain name, project name, and project ID on the **My Credentials** page. + +- Quota information, which includes: + + - Service name + - Quota type + - Required quota + +`Learn how to obtain the service hotline and email address. `__ diff --git a/umn/source/quotas/index.rst b/umn/source/quotas/index.rst new file mode 100644 index 0000000..efe8aaa --- /dev/null +++ b/umn/source/quotas/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0055.html + +.. _er_01_0055: + +Quotas +====== + +- :ref:`Overview ` +- :ref:`Viewing Quotas ` +- :ref:`Increasing Quotas ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + overview + viewing_quotas + increasing_quotas diff --git a/umn/source/quotas/overview.rst b/umn/source/quotas/overview.rst new file mode 100644 index 0000000..7456557 --- /dev/null +++ b/umn/source/quotas/overview.rst @@ -0,0 +1,10 @@ +:original_name: er_01_0056.html + +.. _er_01_0056: + +Overview +======== + +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. + +You can also request for increased quotas if your existing quotas cannot meet your service requirements. diff --git a/umn/source/quotas/viewing_quotas.rst b/umn/source/quotas/viewing_quotas.rst new file mode 100644 index 0000000..78d13cb --- /dev/null +++ b/umn/source/quotas/viewing_quotas.rst @@ -0,0 +1,29 @@ +:original_name: er_01_0057.html + +.. _er_01_0057: + +Viewing Quotas +============== + +Scenarios +--------- + +The following provides operations for you to view the quotas of enterprise routers and related resources in your account. + +How Do I View My Quotas? +------------------------ + +#. Log in to the management console. + +#. Click |image1| in the upper left corner and select the desired region and project. + +#. In the upper right corner of the page, click |image2|. + + The **Service Quota** page is displayed. + +#. View the used and total quota of each type of resources on the displayed page. + + If a quota cannot meet service requirements, apply for a higher quota. + +.. |image1| image:: /_static/images/en-us_image_0275513364.png +.. |image2| image:: /_static/images/en-us_image_0152727234.png diff --git a/umn/source/route_tables/changing_the_name_and_description_of_a_route_table.rst b/umn/source/route_tables/changing_the_name_and_description_of_a_route_table.rst new file mode 100644 index 0000000..13749d6 --- /dev/null +++ b/umn/source/route_tables/changing_the_name_and_description_of_a_route_table.rst @@ -0,0 +1,64 @@ +:original_name: er_01_0026.html + +.. _er_01_0026: + +Changing the Name and Description of a Route Table +================================================== + +Scenarios +--------- + +This section describes how to change the name and description of a route table. + +Notes and Constraints +--------------------- + +Only the name and description of route tables named **defaultRouteTable** and custom route tables can be changed. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. In the route table list, click |image2| next to the name of the target route table. + + The **Modify Route Table** dialog box is displayed. + +#. Enter a new name. + + .. table:: **Table 1** Parameter description + + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+================================================================================+=======================+ + | Name | Mandatory | er-rtb-01 | + | | | | + | | Enter a new name for the route table. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + | Description | Optional | ``-`` | + | | | | + | | Modify the description of the route table. | | + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The route table list is displayed. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001188217841.png diff --git a/umn/source/route_tables/creating_a_route_table.rst b/umn/source/route_tables/creating_a_route_table.rst new file mode 100644 index 0000000..71df1d0 --- /dev/null +++ b/umn/source/route_tables/creating_a_route_table.rst @@ -0,0 +1,70 @@ +:original_name: er_01_0025.html + +.. _er_01_0025: + +Creating a Route Table +====================== + +Scenarios +--------- + +This section describes how to create a custom route table for an enterprise router. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. On the **Route Tables** tab page, click **Create Route Table**. + + The **Create Route Table** dialog box is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0025__table7204821194013: + + .. table:: **Table 1** Parameters for creating a route table for an enterprise router + + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+================================================================================+=======================+ + | Name | Mandatory | er-rtb-01 | + | | | | + | | Enter a name for the route table. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + | Description | Optional | ``-`` | + | | | | + | | Describe the route table for easy identification. | | + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + | Tag | Optional | **Tag key**: test | + | | | | + | | Add tags to help you quickly find your route table. | **Tag value**: 01 | + | | | | + | | For details, see :ref:`Overview `. | | + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The route table list is displayed. + +#. View the route table status. + + If the status changes from **Creating** to **Normal**, the route table is successfully created. + +.. |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 new file mode 100644 index 0000000..77f9e60 --- /dev/null +++ b/umn/source/route_tables/deleting_a_route_table.rst @@ -0,0 +1,57 @@ +:original_name: er_01_0028.html + +.. _er_01_0028: + +Deleting a Route Table +====================== + +Scenarios +--------- + +This section describes how to delete a route table of an enterprise router. + +Notes and Constraints +--------------------- + +- If a route table is used as the default association route table and/or default propagation route table, the route table cannot be deleted. + + - 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 `. + +- 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 `. + +- 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. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. In the route table list, click |image2| next to the name of the target route table. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted route table cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001142144144.png diff --git a/umn/source/route_tables/index.rst b/umn/source/route_tables/index.rst new file mode 100644 index 0000000..d7f27eb --- /dev/null +++ b/umn/source/route_tables/index.rst @@ -0,0 +1,22 @@ +:original_name: er_01_0023.html + +.. _er_01_0023: + +Route Tables +============ + +- :ref:`Route Table Overview ` +- :ref:`Creating a Route Table ` +- :ref:`Changing the Name and Description of a Route Table ` +- :ref:`Viewing Route Tables ` +- :ref:`Deleting a Route Table ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + route_table_overview + creating_a_route_table + changing_the_name_and_description_of_a_route_table + viewing_route_tables + deleting_a_route_table diff --git a/umn/source/route_tables/route_table_overview.rst b/umn/source/route_tables/route_table_overview.rst new file mode 100644 index 0000000..36555cd --- /dev/null +++ b/umn/source/route_tables/route_table_overview.rst @@ -0,0 +1,33 @@ +:original_name: er_01_0024.html + +.. _er_01_0024: + +Route Table Overview +==================== + +Route tables are used by enterprise routers to forward packets. Each route table contains associations, propagations, and routes. Route tables are classified into custom route tables and default route tables. + +.. table:: **Table 1** Route tables + + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Route Table | Description | + +===================================+=================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ + | Custom route table | - A custom route table is an additional route table you optionally create for an enterprise router. | + | | - An enterprise router can have multiple custom route tables. You can associate attachments with different route tables to enable communication or isolation between network instances. | + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Default route table | A default route table is automatically created when an enterprise router is created. There are two types of default route tables: default association route table and default propagation route table. You can specify a route table both as the default association route table and the default propagation route table. You can also specify one route table as the default association route and another route table as the default propagation route table. | + | | | + | | - If **Default Route Table Association** is enabled and the default association route table is specified, attachments will be associated with the default association route table. | + | | | + | | If no default association route table is specified, a route table named **defaultRouteTable** will be created and used as the default association route table. | + | | | + | | - If **Default Route Table Propagation** is enabled and the default propagation route table is specified, attachments will be propagated to the default propagation route table. | + | | | + | | If no default propagation route table is specified, a route table named **defaultRouteTable** will be created and used as the default propagation route table. | + | | | + | | - If both **Default Route Table Association** and **Default Route Table Propagation** are enabled but the default association route table and the default propagation route table are not specified, the route table named **defaultRouteTable** will be used as both the default association route table and the default propagation route table. | + | | | + | | - If there is already a route table named **defaultRouteTable**, no additional **defaultRouteTable** will be created. | + | | | + | | - You can replace the default route table with a custom route table if needed. | + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/route_tables/viewing_route_tables.rst b/umn/source/route_tables/viewing_route_tables.rst new file mode 100644 index 0000000..37d6ac6 --- /dev/null +++ b/umn/source/route_tables/viewing_route_tables.rst @@ -0,0 +1,35 @@ +:original_name: er_01_0027.html + +.. _er_01_0027: + +Viewing Route Tables +==================== + +Scenarios +--------- + +This section describes how to view route tables of an enterprise router. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. In the route table list, click different tabs to view the route table information. + + On the **Basic Information** tab page, you can view the status of the route table and whether **Default Route Table Association** and **Default Route Table Propagation** are enabled. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/routes/creating_a_static_route.rst b/umn/source/routes/creating_a_static_route.rst new file mode 100644 index 0000000..b3e74a8 --- /dev/null +++ b/umn/source/routes/creating_a_static_route.rst @@ -0,0 +1,72 @@ +:original_name: er_01_0041.html + +.. _er_01_0041: + +Creating a Static Route +======================= + +Scenarios +--------- + +You can create static routes in a route table of an enterprise router. + +Static routes are classified into common routes and blackhole routes. A blackhole route only has a destination and has no next hop. It drops all traffic sent to the specified destination. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table where you want to create a static route. On the **Routes** tab page, click **Create Route**. + + The **Create Route** dialog box is displayed. + +#. Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0041__table7204821194013: + + .. table:: **Table 1** Parameter description + + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+===============================================================================================================================================================================================================================================================================+=======================+ + | Destination | Mandatory | 192.168.2.0/24 | + | | | | + | | Enter the IP address or CIDR block of the attachment. For example, if it is a VPC attachment, enter the CIDR block of the VPC or a subnet of the VPC. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Blackhole Route | Optional | ``-`` | + | | | | + | | If **Blackhole Route** is enabled, you do not need to configure **Attachment Type** and **Next Hop** for the route. If the destination of a route is the same as, or is contained in, that of this blackhole route, all packets destined for the destination will be dropped. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Attachment Type | - If **Blackhole Route** is not enabled, you need to configure this parameter. | VPC | + | | - If **Blackhole Route** is enabled, you do not need to configure this parameter. | | + | | | | + | | **VPC**: Create a static route for a VPC attachment. | | + | | | | + | | For more information, see :ref:`Attachment Overview `. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Next Hop | - If **Blackhole Route** is not enabled, you need to configure this parameter. | er-attach-01 | + | | - If **Blackhole Route** is enabled, you do not need to configure this parameter. | | + | | | | + | | In the drop-down list, select the target attachment. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + Wait for 2 to 3 seconds, and click |image2| to refresh the route list. The created static route is displayed. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001383934230.png diff --git a/umn/source/routes/deleting_a_static_route.rst b/umn/source/routes/deleting_a_static_route.rst new file mode 100644 index 0000000..c37b969 --- /dev/null +++ b/umn/source/routes/deleting_a_static_route.rst @@ -0,0 +1,44 @@ +:original_name: er_01_0044.html + +.. _er_01_0044: + +Deleting a Static Route +======================= + +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 `. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table where you want to delete a route. On the **Routes** tab page, locate the route and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted static route cannot be recovered. + + Wait for 2 to 3 seconds, and click |image2| to refresh the route list. The route does not exist in the list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001434293421.png diff --git a/umn/source/routes/index.rst b/umn/source/routes/index.rst new file mode 100644 index 0000000..ae511a7 --- /dev/null +++ b/umn/source/routes/index.rst @@ -0,0 +1,22 @@ +:original_name: er_01_0039.html + +.. _er_01_0039: + +Routes +====== + +- :ref:`Route Overview ` +- :ref:`Creating a Static Route ` +- :ref:`Modifying a Static Route ` +- :ref:`Viewing Routes ` +- :ref:`Deleting a Static Route ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + route_overview + creating_a_static_route + modifying_a_static_route + viewing_routes + deleting_a_static_route diff --git a/umn/source/routes/modifying_a_static_route.rst b/umn/source/routes/modifying_a_static_route.rst new file mode 100644 index 0000000..51d5c10 --- /dev/null +++ b/umn/source/routes/modifying_a_static_route.rst @@ -0,0 +1,75 @@ +:original_name: er_01_0042.html + +.. _er_01_0042: + +Modifying a Static Route +======================== + +Scenarios +--------- + +This section describes how to modify static routes, including common routes and blackhole routes, in a route table of an enterprise router. For example, you can perform the following operations: + +- Change a common route to a blackhole route. +- Change the attachment type and next hop of a common route. + +Only static routes can be modified. Propagation routes cannot be modified. + +Notes and Constraints +--------------------- + +To change the destination of a static route, delete this static route and create another one with your desired destination. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table where you want to modify a route. On the **Routes** tab page, locate the route and click **Modify** in the **Operation** column. + + The **Modify Route** dialog box is displayed. + +#. Modify the route based on :ref:`Table 1 `. + + .. _er_01_0042__er_01_0041_table7204821194013: + + .. table:: **Table 1** Parameter description + + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+===============================================================================================================================================================================================================================================================================+=======================+ + | Blackhole Route | Optional | ``-`` | + | | | | + | | If **Blackhole Route** is enabled, you do not need to configure **Attachment Type** and **Next Hop** for the route. If the destination of a route is the same as, or is contained in, that of this blackhole route, all packets destined for the destination will be dropped. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Attachment Type | - If **Blackhole Route** is not enabled, you need to configure this parameter. | VPC | + | | - If **Blackhole Route** is enabled, you do not need to configure this parameter. | | + | | | | + | | **VPC**: You want to attach a VPC to an enterprise router. | | + | | | | + | | For more information, see :ref:`Attachment Overview `. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Next Hop | - If **Blackhole Route** is not enabled, you need to configure this parameter. | er-attach-01 | + | | - If **Blackhole Route** is enabled, you do not need to configure this parameter. | | + | | | | + | | Select the attachment from the drop-down list. | | + +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + View the modified static route in the route list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/routes/route_overview.rst b/umn/source/routes/route_overview.rst new file mode 100644 index 0000000..07cfc92 --- /dev/null +++ b/umn/source/routes/route_overview.rst @@ -0,0 +1,50 @@ +:original_name: er_01_0040.html + +.. _er_01_0040: + +Route Overview +============== + +What Is a Route? +---------------- + +Routes are used to forward packets. A route contains information such as the destination, next hop, and route type. + +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: + +.. figure:: /_static/images/en-us_image_0000001477172813.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 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 + +.. note:: + + - Static routes are manually configured and the destination of each static route must be unique in a route table. + - Propagated routes are automatically learned by the system and may have the same destination in a route table. + - A static route and a propagated route may have the same destination in a route table. diff --git a/umn/source/routes/viewing_routes.rst b/umn/source/routes/viewing_routes.rst new file mode 100644 index 0000000..f14bcb7 --- /dev/null +++ b/umn/source/routes/viewing_routes.rst @@ -0,0 +1,35 @@ +:original_name: er_01_0043.html + +.. _er_01_0043: + +Viewing Routes +============== + +Scenarios +--------- + +View propagated routes and static routes in a route table of an enterprise router. + +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 **Route Tables** tab page using either of the following methods: + + - In the upper right corner of the enterprise router, click **Manage Route Table**. + - Click the enterprise router name and click **Route Tables**. + +#. Click the route table whose routes you want to view. On the **Routes** tab page, view the routes. + + Each route includes information such as the destination, next hop, attachment type, and route type. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/service_overview/enterprise_router_and_other_services.rst b/umn/source/service_overview/enterprise_router_and_other_services.rst new file mode 100644 index 0000000..dad1160 --- /dev/null +++ b/umn/source/service_overview/enterprise_router_and_other_services.rst @@ -0,0 +1,26 @@ +:original_name: er_01_0009.html + +.. _er_01_0009: + +Enterprise Router and Other Services +==================================== + +.. table:: **Table 1** Interactions between an enterprise router and other cloud services + + +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Service | Interaction | + +======================================+============================================================================================================================================================================+ + | Virtual Private Cloud (VPC) | You can attach VPCs to an enterprise router to enable communication between multiple VPCs without configuring a large number of VPC peering connections. | + +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 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. | + +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Cloud Trace Service (CTS) | You can use CTS to record operations associated with your enterprise routers for future query, audit, and backtracking. | + +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Tag Management Service (TMS) | You can use tags to identify enterprise routers and route tables. | + +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/service_overview/functions.rst b/umn/source/service_overview/functions.rst new file mode 100644 index 0000000..ad1532f --- /dev/null +++ b/umn/source/service_overview/functions.rst @@ -0,0 +1,62 @@ +:original_name: er_01_0005.html + +.. _er_01_0005: + +Functions +========= + +An enterprise router provides the functions listed in :ref:`Table 1 `, allowing you to: + +- Manage attachments, custom route tables, associations, propagations, and routes. +- Manage permissions, tags, and quota to improve service security. + +.. _er_01_0005__table10511144911816: + +.. table:: **Table 1** Functions of an enterprise router + + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | 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. 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. | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | Propagation | 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. | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ + | 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 ` | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+ diff --git a/umn/source/service_overview/how_enterprise_routers_work.rst b/umn/source/service_overview/how_enterprise_routers_work.rst new file mode 100644 index 0000000..bf1a47c --- /dev/null +++ b/umn/source/service_overview/how_enterprise_routers_work.rst @@ -0,0 +1,171 @@ +:original_name: er_01_0011.html + +.. _er_01_0011: + +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. + +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: + +.. figure:: /_static/images/en-us_image_0000001529948913.png + :alt: **Figure 1** Processing of using an enterprise router + + **Figure 1** Processing of using an enterprise router + +The following describes how an enterprise router works. + + +.. figure:: /_static/images/en-us_image_0000001529950265.png + :alt: **Figure 2** How an enterprise router works + + **Figure 2** How an enterprise router works + +.. table:: **Table 1** Network traffic flows + + +-----+-------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | No. | Route | Description | + +=====+=======================================================+=======================================================================================================================================================================================================================+ + | 1 | Request from VPC 1 to Direct Connect virtual gateway | After receiving requests from VPC 1 to the virtual gateway, enterprise router 1 searches the default route table for the route to the virtual gateway and forwards the requests through this route. | + +-----+-------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Response from Direct Connect virtual gateway to VPC 1 | After receiving responses from the virtual gateway to VPC 1, enterprise router 1 searches the default route table for the route to VPC 1 and forwards the responses through this route. | + +-----+-------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 2 | Request from VPC 2 to Direct Connect virtual gateway | Enterprise router 1 cannot forward requests from VPC 2 to the virtual gateway because the custom route table of enterprise router 1 that is associated with VPC 2 does not contain the route to this virtual gateway. | + +-----+-------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +.. table:: **Table 2** Working principles of an enterprise router + + +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | No. | Action | Description | + +=======================+========================================================================================================================================================================================================================================+=================================================================================================================================================================================================================================+ + | 1 | Add :ref:`attachments ` to the enterprise router. | Attach network instances to enterprise router 1 in region A. | + | | | | + | | | - Network instances from the same region | + | | | | + | | | - **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 `. | | + | | | | + | | You can create multiple propagation records for the same attachment. | | + +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +.. _er_01_0011__section692619383113: + +Attachments +----------- + +If you want to attach a network instance to an enterprise router, you need to add an attachment of a specific type to the enterprise router. The attachment type varies according to the network instance, as listed in :ref:`Table 3 `. + +.. _er_01_0011__table1989203755810: + +.. table:: **Table 3** Attachments + + ========================== ================================= + Attachment Network Instance + ========================== ================================= + VPC attachment VPC + Virtual gateway attachment Virtual gateway of Direct Connect + VPN gateway attachment VPN gateway + ========================== ================================= + +.. _er_01_0011__section14844328152418: + +Route Tables +------------ + +Route tables are used by enterprise routers to forward packets. Route tables contain associations, propagations, and routes. Route tables are classified into custom and default route tables, as detailed in :ref:`Table 4 `. + +.. _er_01_0011__table113001814111111: + +.. table:: **Table 4** Route tables + + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Route Table | Description | + +===================================+==================================================================================================================================================================================================+ + | Custom route table | You can create multiple custom route tables on an enterprise router and use different routes for flexible communication and isolation between network instances. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Default route table | If you enable **Default Route Table Association** and **Default Route Table Propagation**, the system then automatically associates and propagates new attachments with the default route table. | + | | | + | | You can specify a custom route table as the default route table. If you do not specify any route table as the default route table, the system automatically creates a default route table. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +.. _er_01_0011__section131904714219: + +Associations +------------ + +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. + +Not all attachments can propagate routes. For details, see :ref:`Table 5 `. + +.. _er_01_0011__table11754113392813: + +.. table:: **Table 5** Associations + + =============== ================= + Attachment Route Propagation + =============== ================= + VPC Not supported + Virtual gateway Supported + VPN gateway Supported + =============== ================= + +.. _er_01_0011__section134131541823: + +Route Propagation +----------------- + +You can create a propagation for each attachment to propagate routes to one or more route tables on an enterprise router. + +For VPC attachments, their CIDR blocks are propagated to the enterprise router. For other attachments, all routes are propagated to the enterprise router. For details, see :ref:`Table 6 `. + +.. _er_01_0011__table18744443292: + +.. table:: **Table 6** Propagation + + =============== ====================================== + Attachment Propagated Routes to Enterprise Router + =============== ====================================== + VPC VPC CIDR blocks + Virtual gateway All routes + VPN gateway All routes + =============== ====================================== + +.. _er_01_0011__section11725172512435: + +Routes +------ + +Routes are used to forward packets. A route contains information such as the destination, next hop, and route type. :ref:`Table 7 ` describes the routes of different types. + +.. _er_01_0011__table132552223219: + +.. table:: **Table 7** Routes + + +-----------------------+----------------------------------------------------------------------------------------------------+-----------------------+ + | Route Type | Description | Attachment | + +=======================+====================================================================================================+=======================+ + | Propagated routes | Propagated routes are automatically learned through propagation and cannot be modified or deleted. | - VPC | + | | | - Virtual gateway | + | | | - VPN gateway | + +-----------------------+----------------------------------------------------------------------------------------------------+-----------------------+ + | Static routes | Static routes are manually created and can be modified or deleted. | - VPC | + +-----------------------+----------------------------------------------------------------------------------------------------+-----------------------+ diff --git a/umn/source/service_overview/index.rst b/umn/source/service_overview/index.rst new file mode 100644 index 0000000..596ee4d --- /dev/null +++ b/umn/source/service_overview/index.rst @@ -0,0 +1,30 @@ +:original_name: er_01_0001.html + +.. _er_01_0001: + +Service Overview +================ + +- :ref:`What's an Enterprise Router? ` +- :ref:`Why Using Enterprise Routers ` +- :ref:`When to Use Enterprise Routers ` +- :ref:`Functions ` +- :ref:`How Enterprise Routers Work ` +- :ref:`User Permissions ` +- :ref:`Notes and Constraints ` +- :ref:`Enterprise Router and Other Services ` +- :ref:`Region and AZ ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + whats_an_enterprise_router + why_using_enterprise_routers + when_to_use_enterprise_routers + functions + how_enterprise_routers_work + user_permissions + notes_and_constraints + enterprise_router_and_other_services + region_and_az diff --git a/umn/source/service_overview/notes_and_constraints.rst b/umn/source/service_overview/notes_and_constraints.rst new file mode 100644 index 0000000..4f55487 --- /dev/null +++ b/umn/source/service_overview/notes_and_constraints.rst @@ -0,0 +1,36 @@ +:original_name: er_01_0006.html + +.. _er_01_0006: + +Notes and Constraints +===================== + +Specifications +-------------- + +:ref:`Table 1 ` lists the specifications of the enterprise router. + +.. _er_01_0006__table591864733813: + +.. table:: **Table 1** Enterprise router specifications + + +--------------------------------------------------------------------------+------------------------+---------------------------+ + | Item | Default Specifications | Adjustable | + +==========================================================================+========================+===========================+ + | Maximum number of enterprise routers that can be created by each account | 1 | Contact customer service. | + +--------------------------------------------------------------------------+------------------------+---------------------------+ + | Maximum forwarding capability supported by each enterprise router | 100 Gbit/s | Contact customer service. | + +--------------------------------------------------------------------------+------------------------+---------------------------+ + + +Notes and Constraints +--------------------- + +- Enterprise routers cannot be used together with virtual IP addresses of VPCs. If virtual IP addresses are used, contact customer service. + +- Traffic cannot be forwarded from a VPC to its attached enterprise router 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. + - The VPC is being used by ELB, NAT Gateway, or VPC Endpoint. + + To solve this problem, refer to :ref:`Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0 to Its Enterprise Router? ` diff --git a/umn/source/service_overview/region_and_az.rst b/umn/source/service_overview/region_and_az.rst new file mode 100644 index 0000000..00bfc18 --- /dev/null +++ b/umn/source/service_overview/region_and_az.rst @@ -0,0 +1,41 @@ +:original_name: er_01_0071.html + +.. _er_01_0071: + +Region and AZ +============= + +Concept +------- + +A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ. + +- A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created. +- An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others. + +:ref:`Figure 1 ` shows the relationship between regions and AZs. + +.. _er_01_0071__en-us_topic_0184026189_fig8747114281212: + +.. figure:: /_static/images/en-us_image_0184026531.png + :alt: **Figure 1** Regions and AZs + + **Figure 1** Regions and AZs + +Selecting a Region +------------------ + +Select a region closest to your target users for lower network latency and quick access. + +Selecting an AZ +--------------- + +When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency. + +- For high DR capability, deploy resources in different AZs within the same region. +- For lower network latency, deploy resources in the same AZ. + +Regions and Endpoints +--------------------- + +Before you use an API to call resources, specify its region and endpoint. For more details, see `Regions and Endpoints `__. diff --git a/umn/source/service_overview/user_permissions.rst b/umn/source/service_overview/user_permissions.rst new file mode 100644 index 0000000..8c37ec4 --- /dev/null +++ b/umn/source/service_overview/user_permissions.rst @@ -0,0 +1,22 @@ +:original_name: er_01_0007.html + +.. _er_01_0007: + +User Permissions +================ + +The cloud system provides two types of user permissions by default, user management and resource management. User management refers to the management of users, user groups, and user group rights. Resource management refers to access control over cloud service resources. + +For details, see :ref:`Table 1 `. + +.. _er_01_0007__table8486434381: + +.. table:: **Table 1** User permissions + + +-------------------+----------------------------------------------------------------------------------------------------------------------------------------+ + | Permission | Description | + +===================+========================================================================================================================================+ + | ER FullAccess | Administrator permissions for enterprise routers. Users with such permissions can operate and use all resources on enterprise routers. | + +-------------------+----------------------------------------------------------------------------------------------------------------------------------------+ + | ER ReadOnlyAccess | Read-only permissions for enterprise routers. Users with such permissions can only view data on enterprise routers. | + +-------------------+----------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/service_overview/whats_an_enterprise_router.rst b/umn/source/service_overview/whats_an_enterprise_router.rst new file mode 100644 index 0000000..d3689df --- /dev/null +++ b/umn/source/service_overview/whats_an_enterprise_router.rst @@ -0,0 +1,40 @@ +:original_name: er_01_0002.html + +.. _er_01_0002: + +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. + +.. _er_01_0002__fig1160410331975: + +.. figure:: /_static/images/en-us_image_0000001427301842.png + :alt: **Figure 1** A network without enterprise routers + + **Figure 1** A network without enterprise routers + +.. _er_01_0002__fig12604833873: + +.. figure:: /_static/images/en-us_image_0000001426824994.png + :alt: **Figure 2** A network with enterprise routers + + **Figure 2** A network with enterprise routers + +.. _er_01_0002__table126045339718: + +.. 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. | + | | - 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. | + | | | | - Multiple lines work in load-sharing or active/standby mode to achieve higher availability. | + +------------------------------------------------------------+--------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------+ + +The comparison shows that the network with enterprise routers is simpler and highly scalable and is also easier to maintain. diff --git a/umn/source/service_overview/when_to_use_enterprise_routers.rst b/umn/source/service_overview/when_to_use_enterprise_routers.rst new file mode 100644 index 0000000..5c07112 --- /dev/null +++ b/umn/source/service_overview/when_to_use_enterprise_routers.rst @@ -0,0 +1,67 @@ +:original_name: er_01_0004.html + +.. _er_01_0004: + +When to Use Enterprise Routers +============================== + +You can use enterprise routers to build cloud, on-premises, or hybrid networks. Here are three typical application scenarios: + +- :ref:`Scenario 1: Multiple VPCs communicating or not communicating with each other on the cloud, but communicating with the on-premises data center through shared Direct Connect connections ` +- :ref:`Scenario 2: Dynamic switchover between multiple Direct Connect connections ` + +.. _er_01_0004__section16111115210: + +Scenario 1: Multiple VPCs communicating or not communicating with each other on the cloud, but communicating with the on-premises data center through shared Direct Connect connections +--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- + + +.. figure:: /_static/images/en-us_image_0000001190538519.png + :alt: **Figure 1** Diagram for scenario 1 + + **Figure 1** Diagram for scenario 1 + +.. table:: **Table 1** Using enterprise routers in scenario 1 + + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Customer Requirements | Multiple service networks communicate or do not communicate with each other on the cloud but communicate with the on-premises data center. For example, three VPCs running different services need to be isolated from each other, but these VPCs need to communicate with the VPC running the public services and the on-premises data center. | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Pain Points | - VPC peering connections are required for communications among these VPCs, but they will complicate the network topology and make the network hard to manage. | + | | - VPC peering connections and routes are required for the public service VPC to communicate with each VPC. However, VPC peering connections do not fit in large-scale networks because of the following limitations: | + | | | + | | - A maximum of 50 VPC peering connections can be created in one region. | + | | - A VPC route table can have a maximum of 200 routes. | + | | | + | | - Direct Connect connections are required for each VPC to communicate with the on-premises data center, but they will incur high costs. | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Benefits of Using Enterprise Routers | - VPCs can be associated with different route tables on the enterprise router to enable communication or isolation. The network topology is simple and easy to manage. | + | | - Enterprise routers can route traffic among all the connected VPCs without the need to configure a large number of VPC peering connections. | + | | | + | | - Each enterprise router can have a maximum of 2,000 routes in each route table, making it ideal for large-scale complex networks. | + | | | + | | - Multiple VPCs can access the on-premises data center over a shared Direct Connect connection, eliminating the need to configure multiple Direct Connect connections and reducing the costs. | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +.. _er_01_0004__section12577403566: + +Scenario 2: Dynamic switchover between multiple Direct Connect connections +-------------------------------------------------------------------------- + + +.. figure:: /_static/images/en-us_image_0000001144919892.png + :alt: **Figure 2** Diagram for scenario 2 + + **Figure 2** Diagram for scenario 2 + +.. table:: **Table 2** Using enterprise routers in scenario 2 + + +--------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Customer Requirements | Some services run on the public cloud and some in the on-premises data center. Two independent high-bandwidth Direct Connect connections are deployed between the public cloud and the data center to enable communication between them. | + +--------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Pain Points | Two Direct Connect connections are independent of each other and cannot work in load-sharing or active/standby mode. | + +--------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Benefits of Using Enterprise Routers | Direct Connect connections are connected to the enterprise router. | + | | | + | | - Two Direct Connect connections can work in load-sharing mode to ensure high bandwidth and reliability. | + | | - Two Direct Connect connections can also work in active/standby mode. If one of the connections becomes unavailable, services are switched over to the other available connection within seconds, preventing service interruptions. | + +--------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/service_overview/why_using_enterprise_routers.rst b/umn/source/service_overview/why_using_enterprise_routers.rst new file mode 100644 index 0000000..66b1767 --- /dev/null +++ b/umn/source/service_overview/why_using_enterprise_routers.rst @@ -0,0 +1,32 @@ +:original_name: er_01_0003.html + +.. _er_01_0003: + +Why Using Enterprise Routers +============================ + +Enterprise routers have the following advantages: + +High Performance +---------------- + +Enterprise routers use exclusive resources and are deployed in clusters to deliver the highest possible performance for workloads on large-scale networks. + +High Availability +----------------- + +Enterprise routers can be deployed in multiple availability zones to work in active-active or multi-active mode, thereby ensuring service continuity and real-time seamless switchovers. + +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. +- 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 +------------------------------- + +Enterprise routers use the Border Gateway Protocol (BGP) to select the best path from multiple lines working in load-sharing or active/standby mode. If a single line fails, services can be failed over to another functioning line within seconds to ensure service continuity. diff --git a/umn/source/sharing/accepting_an_attachment_request.rst b/umn/source/sharing/accepting_an_attachment_request.rst new file mode 100644 index 0000000..c43a89b --- /dev/null +++ b/umn/source/sharing/accepting_an_attachment_request.rst @@ -0,0 +1,44 @@ +:original_name: er_01_0099.html + +.. _er_01_0099: + +Accepting an Attachment Request +=============================== + +Scenarios +--------- + +This section describes how to accept a request from another user for creating an attachment to your enterprise router. + +.. note:: + + If **Auto Accept Shared Attachments** is disabled on your enterprise router, you can choose to accept the attachment request or not. + +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 **Sharing** 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 sharing 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**. + + - When the attachment status changes to **Normal**, the attachment is successfully created. + - When the attachment status changes to **Failed**, the attachment fails to be created. Contact customer service. + + After an attachment is created, you can perform :ref:`Follow-up Procedure `. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/sharing/changing_the_name_of_a_sharing.rst b/umn/source/sharing/changing_the_name_of_a_sharing.rst new file mode 100644 index 0000000..cdf16c2 --- /dev/null +++ b/umn/source/sharing/changing_the_name_of_a_sharing.rst @@ -0,0 +1,55 @@ +:original_name: er_01_0097.html + +.. _er_01_0097: + +Changing the Name of a Sharing +============================== + +Scenarios +--------- + +This section describes how to change the name of a sharing. + +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 **Sharing** 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 sharing list, click |image2| next to the sharing. + + The **Edit Sharing Name** dialog box is displayed. + +#. Enter a new name. + + .. table:: **Table 1** Parameter for changing the name of a sharing + + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=======================+================================================================================+=======================+ + | Name | Mandatory | ershare-cd | + | | | | + | | Enter the sharing name. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +-----------------------+--------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The sharing list is displayed. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png +.. |image2| image:: /_static/images/en-us_image_0000001243603657.png diff --git a/umn/source/sharing/creating_a_sharing.rst b/umn/source/sharing/creating_a_sharing.rst new file mode 100644 index 0000000..d9ca9c2 --- /dev/null +++ b/umn/source/sharing/creating_a_sharing.rst @@ -0,0 +1,60 @@ +:original_name: er_01_0096.html + +.. _er_01_0096: + +Creating a Sharing +================== + +Scenarios +--------- + +This section describes how to share your enterprise router with another user. After the enterprise router is shared, this user can view your enterprise router with its name followed by **Shared with me**. + +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 **Sharing** 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**. + +#. On the **Sharing** tab page, click **Share Enterprise Router**. + + The **Share Enterprise Router** dialog box is displayed. + + Configure the parameters based on :ref:`Table 1 `. + + .. _er_01_0096__table7204821194013: + + .. table:: **Table 1** Parameters for creating a sharing + + +--------------------------+--------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +==========================+================================================================================+=======================+ + | Sharing Name | Mandatory | ershare-ab | + | | | | + | | Enter a name for the sharing. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +--------------------------+--------------------------------------------------------------------------------+-----------------------+ + | Resource User Account ID | Mandatory | 2364e06b8XXXXXXdfeb | + | | | | + | | The ID of the account that you want to share the enterprise router with. | | + +--------------------------+--------------------------------------------------------------------------------+-----------------------+ + +#. Click **OK**. + + The sharing list is displayed. You can view your sharing. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/sharing/deleting_a_sharing.rst b/umn/source/sharing/deleting_a_sharing.rst new file mode 100644 index 0000000..1606880 --- /dev/null +++ b/umn/source/sharing/deleting_a_sharing.rst @@ -0,0 +1,44 @@ +:original_name: er_01_0101.html + +.. _er_01_0101: + +Deleting a Sharing +================== + +Scenarios +--------- + +This section describes how to delete a sharing. After a sharing is deleted, your enterprise router cannot be used by other users anymore. + +Notes and Constraints +--------------------- + +Deleting a sharing will not delete the attachments created by other users. + +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 **Sharing** 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**. + +#. Locate the row that contains the sharing you want to delete and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted sharing cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/sharing/index.rst b/umn/source/sharing/index.rst new file mode 100644 index 0000000..f97198b --- /dev/null +++ b/umn/source/sharing/index.rst @@ -0,0 +1,26 @@ +:original_name: er_01_0094.html + +.. _er_01_0094: + +Sharing +======= + +- :ref:`Sharing Overview ` +- :ref:`Creating a Sharing ` +- :ref:`Changing the Name of a Sharing ` +- :ref:`Viewing a Sharing ` +- :ref:`Accepting an Attachment Request ` +- :ref:`Rejecting an Attachment Request ` +- :ref:`Deleting a Sharing ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + sharing_overview + creating_a_sharing + changing_the_name_of_a_sharing + viewing_a_sharing + 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 new file mode 100644 index 0000000..0c886b4 --- /dev/null +++ b/umn/source/sharing/rejecting_an_attachment_request.rst @@ -0,0 +1,39 @@ +:original_name: er_01_0100.html + +.. _er_01_0100: + +Rejecting an Attachment Request +=============================== + +Scenarios +--------- + +This section describes how to reject a request from another user for creating an attachment to your enterprise router. + +.. note:: + + If **Auto Accept Shared Attachments** is disabled on your enterprise router, you can choose to accept the attachment request or not. + +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 **Sharing** 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 sharing 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. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/sharing/sharing_overview.rst b/umn/source/sharing/sharing_overview.rst new file mode 100644 index 0000000..391c0aa --- /dev/null +++ b/umn/source/sharing/sharing_overview.rst @@ -0,0 +1,143 @@ +:original_name: er_01_0095.html + +.. _er_01_0095: + +Sharing Overview +================ + +What Is Sharing? +---------------- + +You can share an enterprise router in your account with other accounts. + +- You are the owner of the enterprise router. +- Other accounts are the users of the enterprise router. + +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. + +You can share an enterprise router in your account with other accounts so that these other accounts can attach their VPCs to your enterprise router. + +This example uses account A, account B, and account C to describe how you can build a network using one enterprise router. :ref:`Table 1 ` describes the resources of each account. + +If account A shares enterprise router (ER-A) with account B and account C, the VPCs of accounts B and C can be attached to ER-A. :ref:`Figure 1 ` shows the networking. + +.. _er_01_0095__table04706348500: + +.. table:: **Table 1** Accounts and their resources + + +-----------------------+-----------------------+-----------------------+ + | Account | Enterprise Router | VPC | + +=======================+=======================+=======================+ + | A | ER-A | VPC-A-01 | + | | | | + | | | 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: + +.. figure:: /_static/images/en-us_image_0000001399653186.png + :alt: **Figure 1** Attaching VPCs in different accounts to the same enterprise router + + **Figure 1** Attaching VPCs in different accounts to the same enterprise router + +Allowed Operations by the Owner and Other Users +----------------------------------------------- + +The owner can perform all operations but these other users can perform only some of the operations. :ref:`Table 2 ` lists the operations that other users can perform. + +.. _er_01_0095__table168733271489: + +.. table:: **Table 2** Allowed operations by other users + + +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Role | Allowed Operation | Description | + +=============================+====================================================================+===================================================================================================================================================================================================+ + | 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**. | + +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Adding attachments to an enterprise router | Other users: | + | | | | + | | :ref:`Adding VPC Attachments to an Enterprise Router ` | - Can only create VPC attachments. | + | | | | + | | | - Can create attachments to the shared enterprise router only after the owner account accepts the attachment requests. | + | | | | + | | | If **Auto Accept Shared Attachments** is enabled, a request from a user for creating an attachment will be automatically accepted. | + | | | | + | | | - Cannot add tags to their created attachments to the shared enterprise router. | + | | | | + | | | For details about the process for creating an attachment for an enterprise router in another account, see :ref:`Sharing an Enterprise Router with Other Users `. | + +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | | :ref:`Viewing Details About an Attachment ` | Other users: | + | | | | + | | | Cannot view the tags added of their attachments. | + +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | | :ref:`Changing the Name of an Attachment ` | Other users can change the names of their attachments created for the shared enterprise router. | + +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | | :ref:`Deleting a VPC Attachment ` | Other users can delete their attachments created for the shared enterprise router without the approval of the owner account. | + +-----------------------------+--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +.. _er_01_0095__section169164232367: + +Sharing an Enterprise Router with Other Users +--------------------------------------------- + +As the owner, you can share your enterprise router with other users. These other users can create attachments for your enterprise router. + +- If **Auto Accept Shared Attachments** is not enabled on your enterprise router, you must accept the attachment creation requests from other users. + + + .. figure:: /_static/images/en-us_image_0000001213710098.png + :alt: **Figure 2** Accepting or rejecting attachment creation requests + + **Figure 2** Accepting or rejecting attachment creation requests + + .. table:: **Table 3** Process description + + +-----------------+--------------------------------------------------------------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | No. | Step | Role | Description | + +=================+====================================================================+=================+============================================================================================================================================================================================================================================+ + | 1 | :ref:`Creating a Sharing ` | Owner | The owner creates a sharing to share an enterprise router with another user. This user can easily identify the shared enterprise router because its name is followed by **Shared with me**. | + +-----------------+--------------------------------------------------------------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 2 | :ref:`Adding VPC Attachments to an Enterprise Router ` | User | The user creates an attachment to the shared enterprise router. The attachment will be in the **Pending acceptance** state because **Auto Accept Shared Attachments** is disabled on the enterprise router. | + +-----------------+--------------------------------------------------------------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 3 | :ref:`Accepting an Attachment Request ` | Owner | The owner accepts the attachment request. The attachment status changes from **Pending acceptance** to **Creating**. | + | | | | | + | | | | - When the attachment status changes to **Normal**, the attachment is successfully created. | + | | | | - When the attachment status changes to **Failed**, the attachment fails to be created. Contact customer service. | + | | | | | + | | | | After an attachment is created, you can perform :ref:`Follow-up Procedure `. | + +-----------------+--------------------------------------------------------------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | | :ref:`Rejecting an Attachment Request ` | | 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. | + +-----------------+--------------------------------------------------------------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +- If **Auto Accept Shared Attachments** is enabled on an enterprise router, the other users' requests to create attachments to this enterprise router will be automatically accepted without the approval from the owner. + + + .. figure:: /_static/images/en-us_image_0000001213710140.png + :alt: **Figure 3** Attachment requests automatically accepted + + **Figure 3** Attachment requests automatically accepted + + .. table:: **Table 4** Process description + + +-----------------+--------------------------------------------------------------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | No. | Step | Role | Description | + +=================+====================================================================+=================+=============================================================================================================================================================================================+ + | 1 | :ref:`Creating a Sharing ` | Owner | The owner creates a sharing to share an enterprise router with another user. This user can easily identify the shared enterprise router because its name is followed by **Shared with me**. | + +-----------------+--------------------------------------------------------------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | 2 | :ref:`Adding VPC Attachments to an Enterprise Router ` | User account | **Auto Accept Shared Attachments** is enabled on the enterprise router. | + | | | | | + | | | | The user creates an attachment to the shared enterprise router. The attachment will be in the **Creating** state. | + | | | | | + | | | | - When the attachment status changes to **Normal**, the attachment is successfully created. | + | | | | - When the attachment status changes to **Failed**, the attachment fails to be created. Contact customer service. | + +-----------------+--------------------------------------------------------------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/sharing/viewing_a_sharing.rst b/umn/source/sharing/viewing_a_sharing.rst new file mode 100644 index 0000000..659ef5b --- /dev/null +++ b/umn/source/sharing/viewing_a_sharing.rst @@ -0,0 +1,35 @@ +:original_name: er_01_0098.html + +.. _er_01_0098: + +Viewing a Sharing +================= + +Scenarios +--------- + +After you share an enterprise router with other users, you can view information about the sharing and the other users, for example, the time when the sharing was created and the other users' account ID. + +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 **Sharing** 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**. + +#. On the **Sharing** tab page, you can view: + + Sharing name, resource owner account ID, resource user account ID, and creation time. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/adding_a_tag/adding_a_tag_to_a_route_table.rst b/umn/source/tags/adding_a_tag/adding_a_tag_to_a_route_table.rst new file mode 100644 index 0000000..3116387 --- /dev/null +++ b/umn/source/tags/adding_a_tag/adding_a_tag_to_a_route_table.rst @@ -0,0 +1,38 @@ +:original_name: er_01_0077.html + +.. _er_01_0077: + +Adding a Tag to a Route Table +============================= + +Scenarios +--------- + +Add a tag to an existing route table. + +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. + +#. Click the enterprise router name and click **Route Tables**. + + The route table list is displayed. + +#. Locate the route table to which you want to add a tag. On the **Tags** tab page, click **Add Tag** in the right pane. + + The **Add Tag** dialog box is displayed. + +#. Set the tag key and tag value as prompted, and click **OK**. + + View the added tag in the tag list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/adding_a_tag/adding_a_tag_to_an_attachment.rst b/umn/source/tags/adding_a_tag/adding_a_tag_to_an_attachment.rst new file mode 100644 index 0000000..5d4dbae --- /dev/null +++ b/umn/source/tags/adding_a_tag/adding_a_tag_to_an_attachment.rst @@ -0,0 +1,42 @@ +:original_name: er_01_0076.html + +.. _er_01_0076: + +Adding a Tag to an Attachment +============================= + +Scenarios +--------- + +Add a tag to an existing attachment. + +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. + +#. Click the enterprise router name and click **Attachments**. + + The attachment list is displayed. + +#. Locate the row that contains the attachment that you want to add a tag to and click its name. + + The attachment details page is displayed. + +#. Click **Add Tag**. + + The **Add Tag** dialog box is displayed. + +#. Set the tag key and tag value as prompted, and click **OK**. + + View the added tag in the tag list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/adding_a_tag/adding_a_tag_to_an_enterprise_router.rst b/umn/source/tags/adding_a_tag/adding_a_tag_to_an_enterprise_router.rst new file mode 100644 index 0000000..a0251ab --- /dev/null +++ b/umn/source/tags/adding_a_tag/adding_a_tag_to_an_enterprise_router.rst @@ -0,0 +1,38 @@ +:original_name: er_01_0075.html + +.. _er_01_0075: + +Adding a Tag to an Enterprise Router +==================================== + +Scenarios +--------- + +Add a tag to an existing enterprise router. + +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. + +#. Click the enterprise router name and click **Tags**. + + The tag list is displayed. + +#. Click **Add Tag**. + + The **Add Tag** dialog box is displayed. + +#. Set the tag key and tag value as prompted, and click **OK**. + + View the added tag in the tag list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/adding_a_tag/index.rst b/umn/source/tags/adding_a_tag/index.rst new file mode 100644 index 0000000..d4a69e9 --- /dev/null +++ b/umn/source/tags/adding_a_tag/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0050.html + +.. _er_01_0050: + +Adding a Tag +============ + +- :ref:`Adding a Tag to an Enterprise Router ` +- :ref:`Adding a Tag to an Attachment ` +- :ref:`Adding a Tag to a Route Table ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + adding_a_tag_to_an_enterprise_router + adding_a_tag_to_an_attachment + adding_a_tag_to_a_route_table diff --git a/umn/source/tags/deleting_a_tag/deleting_a_route_table_tag.rst b/umn/source/tags/deleting_a_tag/deleting_a_route_table_tag.rst new file mode 100644 index 0000000..712f58f --- /dev/null +++ b/umn/source/tags/deleting_a_tag/deleting_a_route_table_tag.rst @@ -0,0 +1,38 @@ +:original_name: er_01_0089.html + +.. _er_01_0089: + +Deleting a Route Table Tag +========================== + +Scenarios +--------- + +Delete a tag added to a route table. + +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. + +#. Click the enterprise router name and click **Route Tables**. + + The route table list is displayed. + +#. Locate the row that contains the tag you want to delete and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted tag cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/deleting_a_tag/deleting_an_attachment_tag.rst b/umn/source/tags/deleting_a_tag/deleting_an_attachment_tag.rst new file mode 100644 index 0000000..69ac7d0 --- /dev/null +++ b/umn/source/tags/deleting_a_tag/deleting_an_attachment_tag.rst @@ -0,0 +1,42 @@ +:original_name: er_01_0088.html + +.. _er_01_0088: + +Deleting an Attachment Tag +========================== + +Scenarios +--------- + +Delete a tag added to an attachment. + +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. + +#. Click the enterprise router name and click **Attachments**. + + The attachment list is displayed. + +#. Locate the row that contains the attachment whose tag you want to delete and click its name. + + The attachment details page is displayed. + +#. Locate the row that contains the tag you want to delete and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted tag cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/deleting_a_tag/deleting_an_enterprise_router_tag.rst b/umn/source/tags/deleting_a_tag/deleting_an_enterprise_router_tag.rst new file mode 100644 index 0000000..ee7ac25 --- /dev/null +++ b/umn/source/tags/deleting_a_tag/deleting_an_enterprise_router_tag.rst @@ -0,0 +1,38 @@ +:original_name: er_01_0087.html + +.. _er_01_0087: + +Deleting an Enterprise Router Tag +================================= + +Scenarios +--------- + +Delete a tag from an enterprise router. + +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. + +#. Click the enterprise router name and click **Tags**. + + The tag list is displayed. + +#. Locate the row that contains the tag you want to delete and click **Delete** in the **Operation** column. + + A confirmation dialog box is displayed. + +#. Click **Yes**. + + A deleted tag cannot be recovered. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/deleting_a_tag/index.rst b/umn/source/tags/deleting_a_tag/index.rst new file mode 100644 index 0000000..44631ae --- /dev/null +++ b/umn/source/tags/deleting_a_tag/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0054.html + +.. _er_01_0054: + +Deleting a Tag +============== + +- :ref:`Deleting an Enterprise Router Tag ` +- :ref:`Deleting an Attachment Tag ` +- :ref:`Deleting a Route Table Tag ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + deleting_an_enterprise_router_tag + deleting_an_attachment_tag + deleting_a_route_table_tag diff --git a/umn/source/tags/editing_a_tag/editing_a_route_table_tag.rst b/umn/source/tags/editing_a_tag/editing_a_route_table_tag.rst new file mode 100644 index 0000000..951d588 --- /dev/null +++ b/umn/source/tags/editing_a_tag/editing_a_route_table_tag.rst @@ -0,0 +1,44 @@ +:original_name: er_01_0080.html + +.. _er_01_0080: + +Editing a Route Table Tag +========================= + +Scenarios +--------- + +Edit a tag added to an existing route table. + +Notes and Constraints +--------------------- + +- Each tag consists of a tag key and a tag value. Only the tag value can be edited. +- To edit the tag key, delete it and add it again. For details, see :ref:`Deleting a Route Table Tag ` and :ref:`Adding a Tag to a Route Table `. + +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. + +#. Click the enterprise router name and click **Route Tables**. + + The route table list is displayed. + +#. Locate the route table whose tag you want to edit. On the **Tags** tab page, locate the row that contains the tag you want to edit and click **Edit** in the **Operation** column. + + The **Edit Tag** dialog box is displayed. + +#. Edit the tag value as prompted and click **OK**. + + View the edited tag in the tag list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/editing_a_tag/editing_an_enterprise_router_tag.rst b/umn/source/tags/editing_a_tag/editing_an_enterprise_router_tag.rst new file mode 100644 index 0000000..6cf83f4 --- /dev/null +++ b/umn/source/tags/editing_a_tag/editing_an_enterprise_router_tag.rst @@ -0,0 +1,44 @@ +:original_name: er_01_0078.html + +.. _er_01_0078: + +Editing an Enterprise Router Tag +================================ + +Scenarios +--------- + +Edit a tag added to an existing enterprise router. + +Notes and Constraints +--------------------- + +- Each tag consists of a tag key and a tag value. Only the tag value can be edited. +- To edit the tag key, delete it and add it again. For details, see :ref:`Deleting an Enterprise Router Tag ` and :ref:`Adding a Tag to an Enterprise Router `. + +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. + +#. Click the enterprise router name and click **Tags**. + + The tag list is displayed. + +#. Locate the row that contains the tag you want to edit and click **Edit** in the **Operation** column. + + The **Edit Tag** dialog box is displayed. + +#. Edit the tag value as prompted and click **OK**. + + View the edited tag in the tag list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/editing_a_tag/index.rst b/umn/source/tags/editing_a_tag/index.rst new file mode 100644 index 0000000..31b448d --- /dev/null +++ b/umn/source/tags/editing_a_tag/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0051.html + +.. _er_01_0051: + +Editing a Tag +============= + +- :ref:`Editing an Enterprise Router Tag ` +- :ref:`Modifying an Attachment Tag ` +- :ref:`Editing a Route Table Tag ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + editing_an_enterprise_router_tag + modifying_an_attachment_tag + editing_a_route_table_tag diff --git a/umn/source/tags/editing_a_tag/modifying_an_attachment_tag.rst b/umn/source/tags/editing_a_tag/modifying_an_attachment_tag.rst new file mode 100644 index 0000000..cbb62e3 --- /dev/null +++ b/umn/source/tags/editing_a_tag/modifying_an_attachment_tag.rst @@ -0,0 +1,48 @@ +:original_name: er_01_0079.html + +.. _er_01_0079: + +Modifying an Attachment Tag +=========================== + +Scenarios +--------- + +Modify a tag added to an existing attachment. + +Notes and Constraints +--------------------- + +- Each tag consists of a tag key and a tag value. Only the tag value can be edited. +- To edit the tag key, delete it and add it again. For details, see :ref:`Deleting an Attachment Tag ` and :ref:`Adding a Tag to an Enterprise Router `. + +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. + +#. Click the enterprise router name and click **Attachments**. + + The attachment list is displayed. + +#. Locate the row that contains the attachment whose tag you want to edit and click its name. + + The attachment details page is displayed. + +#. Locate the row that contains the tag you want to edit and click **Edit** in the **Operation** column. + + The **Edit Tag** dialog box is displayed. + +#. Edit the tag value as prompted and click **OK**. + + View the edited tag in the tag list. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/index.rst b/umn/source/tags/index.rst new file mode 100644 index 0000000..5257fe0 --- /dev/null +++ b/umn/source/tags/index.rst @@ -0,0 +1,24 @@ +:original_name: er_01_0048.html + +.. _er_01_0048: + +Tags +==== + +- :ref:`Overview ` +- :ref:`Adding a Tag ` +- :ref:`Editing a Tag ` +- :ref:`Searching for a Cloud Resource by Tag ` +- :ref:`Viewing a Tag ` +- :ref:`Deleting a Tag ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + overview + adding_a_tag/index + editing_a_tag/index + searching_for_a_cloud_resource_by_tag/index + viewing_a_tag/index + deleting_a_tag/index diff --git a/umn/source/tags/overview.rst b/umn/source/tags/overview.rst new file mode 100644 index 0000000..ef27cce --- /dev/null +++ b/umn/source/tags/overview.rst @@ -0,0 +1,51 @@ +:original_name: er_01_0049.html + +.. _er_01_0049: + +Overview +======== + +What Is a Tag? +-------------- + +Tags are used to identify the cloud resources for purposes of easy categorization and quick search. You can add tags to enterprise routers, attachments, and route tables using either of the methods: + +- Add tags when you create an enterprise router, attachment, or route table. +- Add tags on the details page of an existing enterprise router, attachment, or route table. You can also edit or delete tags. + +Basic Knowledge About Tags +-------------------------- + +Tags are used to identify cloud resources. When you have many cloud resources of the same type, you can use tags to classify cloud resources by dimension (for example, use, owner, or environment). + +:ref:`Figure 1 ` shows how tags work. In this example, you assign two tags to each cloud resource. Each tag contains a key and a value that you define. The key of one tag is **Owner**, and the key of another tag is **Usage**. Each tag has a value. + +You can quickly search for specific cloud resources based on the tags added to them. For example, you can define a set of tags for cloud resources in an account to track the owner and usage of each cloud resource, making resource management easier. + +.. _er_01_0049__fig72351755194617: + +.. figure:: /_static/images/en-us_image_0000001147413690.png + :alt: **Figure 1** Example tags added for Enterprise Router + + **Figure 1** Example tags added for Enterprise Router + +Restrictions 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: + + Tag key + + - Cannot be left blank. + - Can contain a maximum of 36 characters. + - Can consist of only letters, digits, underscores (_), hyphens (-), and Unicode characters (\\u4E00-\\u9FFF). + + 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). + +- Up to 10 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/index.rst b/umn/source/tags/searching_for_a_cloud_resource_by_tag/index.rst new file mode 100644 index 0000000..e84e463 --- /dev/null +++ b/umn/source/tags/searching_for_a_cloud_resource_by_tag/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0052.html + +.. _er_01_0052: + +Searching for a Cloud Resource by Tag +===================================== + +- :ref:`Searching for an Enterprise Router by Tag ` +- :ref:`Searching for an Attachment by Tag ` +- :ref:`Searching for a Route Table by Tag ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + searching_for_an_enterprise_router_by_tag + searching_for_an_attachment_by_tag + searching_for_a_route_table_by_tag diff --git a/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_a_route_table_by_tag.rst b/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_a_route_table_by_tag.rst new file mode 100644 index 0000000..c38180e --- /dev/null +++ b/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_a_route_table_by_tag.rst @@ -0,0 +1,43 @@ +:original_name: er_01_0083.html + +.. _er_01_0083: + +Searching for a Route Table by Tag +================================== + +Scenarios +--------- + +Search for a route table using a tag added to that enterprise router. + +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. + +#. Click the enterprise router name and click **Route Tables**. + + The route table list is displayed. + +#. Click **Search by Tag**. + +#. 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. + +.. |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 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 new file mode 100644 index 0000000..b8dbdbf --- /dev/null +++ b/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_attachment_by_tag.rst @@ -0,0 +1,43 @@ +:original_name: er_01_0082.html + +.. _er_01_0082: + +Searching for an Attachment by Tag +================================== + +Scenarios +--------- + +Search for an attachment using a tag added to that attachment. + +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. + +#. Click the enterprise router name and click **Attachments**. + + The attachment list is displayed. + +#. Click **Search by Tag**. + +#. 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. + +.. |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 diff --git a/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_enterprise_router_by_tag.rst b/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_enterprise_router_by_tag.rst new file mode 100644 index 0000000..8513cde --- /dev/null +++ b/umn/source/tags/searching_for_a_cloud_resource_by_tag/searching_for_an_enterprise_router_by_tag.rst @@ -0,0 +1,37 @@ +:original_name: er_01_0081.html + +.. _er_01_0081: + +Searching for an Enterprise Router by Tag +========================================= + +Scenarios +--------- + +Search for an enterprise router using a tag added to that enterprise router. + +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. + +#. Click **Search by Tag**. + +#. 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. + +.. |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 diff --git a/umn/source/tags/viewing_a_tag/index.rst b/umn/source/tags/viewing_a_tag/index.rst new file mode 100644 index 0000000..7dc3d5a --- /dev/null +++ b/umn/source/tags/viewing_a_tag/index.rst @@ -0,0 +1,18 @@ +:original_name: er_01_0053.html + +.. _er_01_0053: + +Viewing a Tag +============= + +- :ref:`Viewing an Enterprise Router Tag ` +- :ref:`Viewing an Attachment Tag ` +- :ref:`Viewing a Route Table Tag ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + viewing_an_enterprise_router_tag + viewing_an_attachment_tag + viewing_a_route_table_tag diff --git a/umn/source/tags/viewing_a_tag/viewing_a_route_table_tag.rst b/umn/source/tags/viewing_a_tag/viewing_a_route_table_tag.rst new file mode 100644 index 0000000..edc9896 --- /dev/null +++ b/umn/source/tags/viewing_a_tag/viewing_a_route_table_tag.rst @@ -0,0 +1,32 @@ +:original_name: er_01_0086.html + +.. _er_01_0086: + +Viewing a Route Table Tag +========================= + +Scenarios +--------- + +View a tag added to a route table. + +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. + +#. Click the enterprise router name and click **Route Tables**. + + The route table list is displayed. + +#. Locate the tag and view its details, including the tag key and tag value. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/viewing_a_tag/viewing_an_attachment_tag.rst b/umn/source/tags/viewing_a_tag/viewing_an_attachment_tag.rst new file mode 100644 index 0000000..712189f --- /dev/null +++ b/umn/source/tags/viewing_a_tag/viewing_an_attachment_tag.rst @@ -0,0 +1,36 @@ +:original_name: er_01_0085.html + +.. _er_01_0085: + +Viewing an Attachment Tag +========================= + +Scenarios +--------- + +View a tag added to an attachment. + +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. + +#. Click the enterprise router name and click **Attachments**. + + The attachment list is displayed. + +#. Locate the row that contains the attachment whose tag you want to view and click its name. + + The attachment details page is displayed. + +#. Locate the tag and view its details, including the tag key and tag value. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png diff --git a/umn/source/tags/viewing_a_tag/viewing_an_enterprise_router_tag.rst b/umn/source/tags/viewing_a_tag/viewing_an_enterprise_router_tag.rst new file mode 100644 index 0000000..3f3f379 --- /dev/null +++ b/umn/source/tags/viewing_a_tag/viewing_an_enterprise_router_tag.rst @@ -0,0 +1,32 @@ +:original_name: er_01_0084.html + +.. _er_01_0084: + +Viewing an Enterprise Router Tag +================================ + +Scenarios +--------- + +View a tag added to an enterprise router. + +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. + +#. Click the enterprise router name and click **Tags**. + + The tag list is displayed. + +#. Locate the tag and view its details, including the tag key and tag value. + +.. |image1| image:: /_static/images/en-us_image_0000001190483836.png