dadrobna/enterprise-router
1
0
Fork 0
forked from docs/enterprise-router
Code Pull Requests Activity

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2023-09-22 08:04:53 +00:00
parent 3e38590841
commit 9f56c7ed0b
70 changed files with 361 additions and 486 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
umn/source/_static/images/en-us_image_0000001294957952.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 48 KiB

BIN
umn/source/_static/images/en-us_image_0000001347633729.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 46 KiB

BIN
umn/source/_static/images/en-us_image_0000001347641769.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 91 KiB

BIN
umn/source/_static/images/en-us_image_0000001347809009.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 93 KiB

BIN
umn/source/_static/images/en-us_image_0000001427131632.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 49 KiB

BIN
umn/source/_static/images/en-us_image_0000001427301842.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 57 KiB

BIN
umn/source/_static/images/en-us_image_0000001432667421.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 247 B

BIN
umn/source/_static/images/en-us_image_0000001477172813.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 97 KiB

BIN
umn/source/_static/images/en-us_image_0000001477452077.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 95 KiB

BIN
umn/source/_static/images/en-us_image_0000001529830673.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 99 KiB

BIN
umn/source/_static/images/en-us_image_0000001529948913.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 14 KiB

BIN
umn/source/_static/images/en-us_image_0000001529950265.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 113 KiB

BIN
umn/source/_static/images/en-us_image_0000001530148853.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 11 KiB

BIN
umn/source/_static/images/en-us_image_0000001559118632.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 46 KiB

BIN
umn/source/_static/images/en-us_image_0000001609438833.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 36 KiB

BIN
umn/source/_static/images/en-us_image_0000001656353678.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 84 KiB

BIN
umn/source/_static/images/en-us_image_0000001656513070.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 88 KiB

23
umn/source/associations/association_overview.rst
View File

@ -10,26 +10,23 @@ Each attachment can be associated with one route table for:
- Packet forwarding: Packets from the attachment are forwarded through the routes specified in the associated route table.
- Route propagation: The routes in the associated route tables are automatically propagated to the route table of the attachment.
.. _er_01_0030__fig13563243183610:
.. figure:: /_static/images/en-us_image_0000001477452077.png
.. figure:: /_static/images/en-us_image_0000001347641769.png
:alt: **Figure 1** Associations
**Figure 1** Associations
.. table:: **Table 1** Association description
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attachment Type | Route Propagation | Way to Create Association | Description |
+=================+===================+==============================================================================================================================================================================================================+=======================================================================================================================================================================================+
| VPC | Not supported | - Auto creation: If **Default Route Table Association** is enabled and the default association route table is specified, attachments are automatically associated with the default association route table. | Each attachment can only be associated with one route table. Associations between attachments in :ref:`Figure 1 <er_01_0030__fig13563243183610>` are described as follows: |
+-----------------+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attachment Type | Route Learning | Way to Create Association | Description |
+=================+=================+====================================================================================================================================================================================================================================+===========================================================================================================================================================================================+
| VPC | Not supported | - Auto creation: If **Default Route Table Association** is enabled and the default association route table is specified, attachments are automatically associated with the default association route table. | Each attachment can only be associated with one route table. Associations between attachments in :ref:`Association Overview <er_01_0030>` are described as follows: |
| | | | |
| | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router <er_01_0069>`. | - 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 <er_01_0013>`. | - 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. |
| | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router <er_01_0069>`. | - Auto creation: The system automatically associates attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments, with the default route table of the enterprise router. |
| | | - If you want to enable this function after an enterprise router is created, refer to :ref:`Modifying an Enterprise Router <er_01_0013>`. | - Manual creation: You need to manually create associations in the custom route table of the enterprise router for attachments, such as VPC 3, VPC 4, and virtual gateway 2 attachments. |
| | | | |
| | | - Manual creation: You can select a route table and create an association in it to associate an attachment with the route table. For details, see :ref:`Creating an Association <er_01_0031>`. | |
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | | - Manual creation: You can select a route table and create an association in it to associate an attachment with the route table. For details, see :ref:`Creating an Association for an Attachment in a Route Table <er_01_0031>`. | |
+-----------------+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Virtual gateway | Supported | | |
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| VPN gateway | Supported | | |
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------+-----------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

5
umn/source/associations/creating_an_association.rst → umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst
View File

@ -2,8 +2,8 @@
.. _er_01_0031:
Creating an Association
=======================
Creating an Association for an Attachment in a Route Table
==========================================================
Scenarios
---------
@ -52,7 +52,6 @@ Procedure
| | | |
| | - **VPC** | |
| | - **Virtual gateway** | |
| | - **VPN gateway** | |
| | | |
| | For more information, see :ref:`Attachment Overview <er_01_0019>`. | |
+-----------------------+-------------------------------------------------------------------------------------+-----------------------+

4
umn/source/associations/deleting_an_association.rst → umn/source/associations/deleting_an_association_from_a_route_table.rst
View File

@ -2,8 +2,8 @@
.. _er_01_0033:
Deleting an Association
=======================
Deleting an Association from a Route Table
==========================================
Scenarios
---------

12
umn/source/associations/index.rst
View File

@ -6,15 +6,15 @@ Associations
============
- :ref:`Association Overview <er_01_0030>`
- :ref:`Creating an Association <er_01_0031>`
- :ref:`Viewing an Association <er_01_0032>`
- :ref:`Deleting an Association <er_01_0033>`
- :ref:`Creating an Association for an Attachment in a Route Table <er_01_0031>`
- :ref:`Viewing Associations in a Route Table <er_01_0032>`
- :ref:`Deleting an Association from a Route Table <er_01_0033>`
.. toctree::
:maxdepth: 1
:hidden:
association_overview
creating_an_association
viewing_an_association
deleting_an_association
creating_an_association_for_an_attachment_in_a_route_table
viewing_associations_in_a_route_table
deleting_an_association_from_a_route_table

12
umn/source/associations/viewing_an_association.rst → umn/source/associations/viewing_associations_in_a_route_table.rst
View File

@ -2,8 +2,8 @@
.. _er_01_0032:
Viewing an Association
======================
Viewing Associations in a Route Table
=====================================
Scenarios
---------
@ -28,8 +28,14 @@ Procedure
- In the upper right corner of the enterprise router, click **Manage Route Table**.
- Click the enterprise router name and click **Route Tables**.
.. figure:: /_static/images/en-us_image_0000001656513070.png
:alt: **Figure 1** Viewing associations
**Figure 1** Viewing associations
#. Click the route table where you want to view its associations. On the **Associations** tab page, view the associations.
All attachments associated with the route table are also displayed.
All attachments associated with the route table are displayed in the list. You can view their settings such as the ID, status, and name of each attachment.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

12
umn/source/attachments/adding_vpc_attachments_to_an_enterprise_router.rst
View File

@ -42,7 +42,7 @@ Procedure
.. _er_01_0070__table7204821194013:
.. table:: **Table 1** Parameters for creating an attachment
.. table:: **Table 1** Parameters for adding a VPC attachment
+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+
| Parameter | Setting | Example Value |
@ -56,9 +56,9 @@ Procedure
+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+
| Attachment Type | Mandatory | - Attachment Type: VPC |
| | | - VPC: vpc-demo-01 |
| | a. **VPC** is selected by default, indicating that the instance to be attached to the enterprise router is a VPC. | - Subnet: subnet-demo-01 |
| | a. Select the attachment type. Select **VPC**, indicating that the instance to be attached to the enterprise router is a VPC. | - Subnet: subnet-demo-01 |
| | | |
| | The methods for creating attachments vary by attachment type. For details, see :ref:`Attachment Overview <er_01_0019>`. | |
| | The methods for creating attachments vary depending on the attachment type. For details, see :ref:`Attachment Overview <er_01_0019>`. | |
| | | |
| | b. Select the VPC to be attached to the enterprise router. You can enter a VPC name to quickly find the target VPC. | |
| | | |
@ -96,13 +96,13 @@ Procedure
Follow-up Procedure
-------------------
- If **Default Route Table Association** and **Default Route Table Propagation** are not enabled for an enterprise router, you need to:
If **Default Route Table Association** and **Default Route Table Propagation** are not enabled for an enterprise router, you need to:
#. Create a custom route table for the enterprise router. For details, see :ref:`Creating a Route Table <er_01_0025>`.
#. Create associations for the attachments of the enterprise router. For details, see :ref:`Creating an Association <er_01_0031>`.
#. Create associations for the attachments of the enterprise router. For details, see :ref:`Creating an Association for an Attachment in a Route Table <er_01_0031>`.
#. 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 <er_01_0036>`.
- Create a propagation in the route table. For details, see :ref:`Creating a Propagation for an Attachment in the Route Table <er_01_0036>`.
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.

14
umn/source/attachments/attachment_overview.rst
View File

@ -8,19 +8,17 @@ Attachment Overview
You can create an attachment to attach a network instance to an enterprise router. The attachment type varies according to the network instance.
.. figure:: /_static/images/en-us_image_0000001427131632.png
.. figure:: /_static/images/en-us_image_0000001294957952.png
:alt: **Figure 1** Attachments
**Figure 1** Attachments
.. table:: **Table 1** Attachments
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
| Attachment Type | Network Instance | Create Attachment | View Attachment | Delete Attachment |
+============================+===================================+========================================================================================================================================================================+=========================================================+===========================================================+
+============================+===================================+====================================================================================================================================================================================================================================================================================+=========================================================+===========================================================+
| VPC attachment | VPC | :ref:`Adding VPC Attachments to an Enterprise Router <er_01_0070>` | :ref:`Viewing Details About an Attachment <er_01_0021>` | :ref:`Deleting a VPC Attachment <er_01_0072>` |
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
| 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 <er_01_0073>` |
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
| 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 <er_01_0114>` |
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
| Virtual gateway attachment | Virtual gateway of Direct Connect | Attach a virtual gateway to an enterprise router. For details, see `Connecting Your On-Premises Data Center to the Cloud <https://docs.otc.t-systems.com/direct-connect/umn/getting_started/enabling_direct_connect/connecting_your_on-premises_data_center_to_the_cloud.html>`__. | | :ref:`Deleting a Virtual Gateway Attachment <er_01_0073>` |
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+

2
umn/source/attachments/deleting_an_attachment/deleting_a_vpc_attachment.rst
View File

@ -39,7 +39,7 @@ Procedure
A confirmation dialog box is displayed.
#. Click **Yes**.
#. Confirm the information and click **Yes**.
A deleted attachment cannot be recovered.

63
umn/source/attachments/deleting_an_attachment/deleting_a_vpn_gateway_attachment.rst
View File

@ -1,63 +0,0 @@
:original_name: er_01_0114.html
.. _er_01_0114:
Deleting a VPN Gateway Attachment
=================================
Scenarios
---------
This section describes how to delete a VPN gateway attachment from an enterprise router.
Notes and Constraints
---------------------
- Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.
- Deleting an attachment will also delete its flow logs.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Attachments** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Attachment**.
- Click the enterprise router name and click **Attachments**.
.. important::
A VPN gateway attachment cannot be directly deleted on the **Attachments** page of the enterprise router.
A VPN gateway attachment will be automatically deleted after you perform the following operations to delete its VPN connections, unbind the EIP from the VPN gateway, and delete the VPN gateway.
#. Locate the row that contains the target VPN gateway attachment and click the attached resource.
Example: vpngw-demo
The VPN gateway attachment details page is displayed.
#. On the attachment details page, click |image2| in the upper left corner.
The VPN gateway list is displayed.
#. In the VPN gateway list, locate the row that contains the target VPN gateway, click **More** in the **Operation** column, and click **Delete**.
A confirmation dialog box is displayed.
#. Click **Yes**.
A deleted VPN gateway cannot be recovered.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png
.. |image2| image:: /_static/images/en-us_image_0000001432667421.png

2
umn/source/attachments/deleting_an_attachment/index.rst
View File

@ -7,7 +7,6 @@ Deleting an Attachment
- :ref:`Deleting a VPC Attachment <er_01_0072>`
- :ref:`Deleting a Virtual Gateway Attachment <er_01_0073>`
- :ref:`Deleting a VPN Gateway Attachment <er_01_0114>`
.. toctree::
:maxdepth: 1
@ -15,4 +14,3 @@ Deleting an Attachment
deleting_a_vpc_attachment
deleting_a_virtual_gateway_attachment
deleting_a_vpn_gateway_attachment

2
umn/source/attachments/viewing_details_about_an_attachment.rst
View File

@ -32,7 +32,7 @@ Procedure
#. On the **Attachments** tab page, you can view:
- In the attachment list, you can view the attachment status, attachment type, and attached resource.
- In the attachment list, you can view information such as the name, status, type, and attached resource.
- If you click the attachment name, you can view more information about the attachment on the displayed page, including the attachment ID, creation time, and tags.
- If you click the attached resource, you will go to the details page of the attached resource.

19
umn/source/change_history.rst
View File

@ -5,12 +5,19 @@
Change History
==============
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Released On | Description |
+===================================+==========================================================================================================================================================================================================================================================================================================================+
| 2023-05-30 | Updated the following content: |
+===================================+==================================================================================================================================================================================================================================================================+
| 2023-09-22 | Modified the following content: |
| | |
| | Added descriptions of flow logs in :ref:`Functions <er_01_0005>`, :ref:`Deleting an Enterprise Router <er_01_0017>`, :ref:`Deleting a VPC Attachment <er_01_0072>`, :ref:`Deleting a Virtual Gateway Attachment <er_01_0073>`, :ref:`Deleting a VPN Gateway Attachment <er_01_0114>`, and :ref:`Flow Logs <er_01_0107>`. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | - Added the link to the Direct Connect operation guide in :ref:`Attachment Overview <er_01_0019>`. |
| | - Modified the maximum number of tags that can be added in :ref:`Overview <er_01_0049>`. |
| | - Added detailed descriptions and screenshots in :ref:`Viewing Associations in a Route Table <er_01_0032>` and :ref:`Viewing a Propagation in a Route Table <er_01_0037>`. |
| | - Added the link to the *Cloud Trace Service User Guide* in :ref:`Viewing Traces <er_01_0092>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-05-30 | Modified the following content: |
| | |
| | Added descriptions of flow logs in :ref:`Functions <er_01_0005>`, :ref:`Deleting an Enterprise Router <er_01_0017>`, :ref:`Deleting a VPC Attachment <er_01_0072>`, :ref:`Deleting a Virtual Gateway Attachment <er_01_0073>` and :ref:`Flow Logs <er_01_0107>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-03-24 | This issue is the first official release. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2
umn/source/conf.py
View File

@ -18,7 +18,7 @@ import os
import sys
extensions = [
'otcdocstheme'
'otcdocstheme',
]
otcdocs_auto_name = False

58
umn/source/enterprise_routers/changing_the_azs_of_an_enterprise_router.rst
View File

@ -1,58 +0,0 @@
:original_name: er_01_0015.html
.. _er_01_0015:
Changing the AZs of an Enterprise Router
========================================
Scenarios
---------
This section describes how to change the AZs of an enterprise router, which will not interrupt network communication.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. In the upper right corner of the target enterprise router, choose **More** > **Change AZ**.
The **Change AZ** page is displayed.
#. Change AZs according to :ref:`Table 1 <er_01_0015__table7204821194013>`.
.. _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

36
umn/source/enterprise_routers/creating_an_enterprise_router.rst
View File

File diff suppressed because it is too large Load Diff

2
umn/source/enterprise_routers/deleting_an_enterprise_router.rst
View File

@ -15,7 +15,7 @@ Notes and Constraints
- An enterprise router that has attachments cannot be deleted. To delete such an enterprise router, delete its attachments first. For details, see :ref:`Deleting an Attachment <er_01_0022>`.
- An enterprise router that has route tables can be deleted directly.
- An enterprise router that has sharings can be deleted directly.
- An enterprise router that is shared with other accounts can be deleted directly.
- Deleting an enterprise router will also delete all of its flow logs.
Procedure

6
umn/source/enterprise_routers/index.rst
View File

@ -6,8 +6,7 @@ Enterprise Routers
==================
- :ref:`Creating an Enterprise Router <er_01_0069>`
- :ref:`Modifying Settings of an Enterprise Router <er_01_0013>`
- :ref:`Changing the AZs of an Enterprise Router <er_01_0015>`
- :ref:`Modifying an Enterprise Router <er_01_0013>`
- :ref:`Viewing an Enterprise Router <er_01_0016>`
- :ref:`Deleting an Enterprise Router <er_01_0017>`
@ -16,7 +15,6 @@ Enterprise Routers
:hidden:
creating_an_enterprise_router
modifying_settings_of_an_enterprise_router
changing_the_azs_of_an_enterprise_router
modifying_an_enterprise_router
viewing_an_enterprise_router
deleting_an_enterprise_router

4
umn/source/enterprise_routers/modifying_settings_of_an_enterprise_router.rst → umn/source/enterprise_routers/modifying_an_enterprise_router.rst
View File

@ -2,8 +2,8 @@
.. _er_01_0013:
Modifying Settings of an Enterprise Router
==========================================
Modifying an Enterprise Router
==============================
Scenarios
---------

6
umn/source/faq/how_do_i_enable_two_attachments_of_an_enterprise_router_to_learn_routes_from_each_other.rst
View File

@ -7,11 +7,11 @@ How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Eac
If you want two attachments of an enterprise router to learn routes from each other, the router and each attachment must have a unique ASN. In this way, the enterprise router advertises the learned route information between the attachments.
If you want a virtual gateway and a VPN gateway attached to an enterprise router to learn routes from each other, their ASNs can be as follows:
If you want two virtual gateways attached to the same enterprise router to learn routes from each other, their ASNs can be as follows:
- Enterprise router: 64512
- Virtual gateway attachment: 64513 (BGP ASN of the virtual gateway)
- VPN gateway attachment: 64515 (BGP ASN of the VPN gateway)
- Virtual gateway attachment A: 64513 (BGP ASN of virtual gateway A)
- Virtual gateway attachment B: 64515 (BGP ASN of virtual gateway B)
.. note::

10
umn/source/faq/how_do_i_route_traffic_to_100.64.x.x_through_an_enterprise_router.rst
View File

@ -102,15 +102,13 @@ The required resources and routes are as follows:
| | 100.64.x.x | Virtual gateway attachment | Propagated route |
+-------------------+-----------------------------------------------+----------------------------+-----------------------+
#. to request 100.64.x.x as the destination for :ref:`4 <er_01_0122__li92642018194217>`.
#. 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 <er_01_0122__li14564823993>` 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 <er_01_0122__li92642018194217>` cannot forward traffic.
- The subnet of the transit VPC cannot overlap with that of the service VPC. Otherwise, the VPC peering connection to be created in :ref:`2 <er_01_0122__li14564823993>` cannot take effect.
- The transit VPC cannot have the following situations. Otherwise, the default route (0.0.0.0/0) to be configured in :ref:`3 <er_01_0122__li92642018194217>` cannot forward traffic.
- An ECS in the VPC has an EIP bound.
- The VPC is being used by ELB, NAT Gateway, or VPC Endpoint.
- The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS.
#. .. _er_01_0122__li14564823993:
@ -118,7 +116,7 @@ The required resources and routes are as follows:
.. important::
You do not need to add routes for the VPC peering connection. For details about the routes to be added, see :ref:`4 <er_01_0122__li92642018194217>`.
You do not need to add routes for the VPC peering connection. For details about the routes to be added, see :ref:`3 <er_01_0122__li92642018194217>`.
#. .. _er_01_0122__li92642018194217:

4
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
View File

@ -8,7 +8,7 @@ Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0
Scenarios
---------
Traffic cannot be forwarded from a VPC to the enterprise router that the VPC is attached if you set the destination of a route in the VPC route table to 0.0.0.0/0 and:
Traffic cannot be forwarded from a VPC to the enterprise router that it is attached to if you set the destination of a route in the VPC route table to 0.0.0.0/0 and:
- An ECS in the VPC has an EIP bound.
@ -16,7 +16,7 @@ Traffic cannot be forwarded from a VPC to the enterprise router that the VPC is
Refer to solution 1.
- The VPC is being used by ELB, NAT Gateway, or VPC Endpoint.
- The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS.
.. note::

5
umn/source/flow_logs/creating_a_flow_log.rst
View File

@ -30,9 +30,9 @@ Procedure
#. Click the enterprise router name and click **Flow Logs**.
#. On the **Flow Logs** tab, click **Create Flow Log**.
#. On the **Flow Logs** tab page, click **Create Flow Log**.
The **Create Flow Log** page is displayed.
The **Create Flow Log** dialog box is displayed.
Configure the parameters based on :ref:`Table 1 <er_01_0109__table7204821194013>`.
@ -56,7 +56,6 @@ Procedure
| | | |
| | - VPC | |
| | - Virtual gateway: Virtual gateway of Direct Connect | |
| | - VPN gateway | |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Resource | Mandatory | vgw-ab |
| | | |

1
umn/source/flow_logs/flow_log_overview.rst
View File

@ -14,7 +14,6 @@ Flow logs can capture traffic of the following types of attachments:
- VPC
- Virtual gateway
- VPN gateway
Creation Process
----------------

5
umn/source/flow_logs/viewing_details_about_a_flow_log.rst
View File

@ -10,6 +10,11 @@ Scenarios
This section describes how to view details about a flow log, including the attachment ID, source/destination address, source/destination port, data packet size, and packet quantity.
Constraints
-----------
Flow logs are generated every 10 minutes. After creating a VPC flow log, you need to wait about 10 minutes before you can view the flow log record.
Procedure
---------

4
umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_2_create_an_enterprise_router.rst
View File

@ -42,13 +42,13 @@ Procedure
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Name | Specify the enterprise router name. You can change it after the enterprise router is created. | er-test-01 |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| ASN | Set the Autonomous System Number for the cloud side of a Border Gateway Protocol (BGP) session. You can change it after the enterprise router is created. | 64512 |
| ASN | Set the Autonomous System Number (ASN) for the cloud side of a Border Gateway Protocol (BGP) session. You cannot change it after the enterprise router is created. | 64512 |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Default Route Table Association | If you select this option, you do not need to create route tables or associations. You can change your option after the enterprise router is created. | Enable |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Default Route Table Propagation | If you select this option, you do not need to create route tables, propagations, or routes. You can change your option after the enterprise router is created. | Enable |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Auto Accept Shared Attachments | If you do not select this option, you must accept the requests for creating attachments to this enterprise router from other users that this enterprise router is shared with. | Disable |
| Auto Accept Shared Attachments | If you do not select this option, you must accept the requests for creating attachments to this enterprise router from other users with whom this enterprise router is shared. | Disable |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Enterprise Project | Select an enterprise project for the enterprise router. You can change it after the enterprise router is created. | default |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+

2
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
View File

@ -77,7 +77,7 @@ Procedure
.. important::
In the example given, **Default Route Table Association** and **Default Route Table Propagation** are enabled when you create the enterprise router. Therefore, after the VPCs are attached to the enterprise router, the system will automatically:
In the example given, **Default Route Table Association** and **Default Route Table Propagation** are enabled when you create the enterprise router. After the VPCs are attached to the enterprise router, the system will automatically:
- Associate VPC attachments with the route table of the enterprise router.
- Propagate VPC attachments to the route table of the enterprise router. The CIDR blocks of the VPCs are propagated to the route table.

12
umn/source/interconnecting_with_cts/key_operations_recorded_by_cts.rst
View File

@ -16,12 +16,10 @@ With CTS, you can record operations associated with your enterprise routers for
+============================================+===============+========================+
| Creating an Enterprise Router | erInstance | createInstance |
+--------------------------------------------+---------------+------------------------+
| Modifying Settings of an Enterprise Router | erInstance | updateInstance |
| Modifying an Enterprise Router | erInstance | updateInstance |
+--------------------------------------------+---------------+------------------------+
| Deleting an Enterprise Router | erInstance | deleteInstance |
+--------------------------------------------+---------------+------------------------+
| Changing AZs of an Enterprise Router | erInstance | changeAvailableZone |
+--------------------------------------------+---------------+------------------------+
| Adding Attachments to an Enterprise Router | erAttachment | createAttachment |
+--------------------------------------------+---------------+------------------------+
| Modifying an Attachment | erAttachment | updateAttachment |
@ -56,3 +54,11 @@ With CTS, you can record operations associated with your enterprise routers for
+--------------------------------------------+---------------+------------------------+
| Deleting a Propagation | erPropagation | deletePropagation |
+--------------------------------------------+---------------+------------------------+
| Creating a Flow Log | erFlowLog | createFlowLog |
+--------------------------------------------+---------------+------------------------+
| Disabling a Flow Log | erFlowLog | updateFlowLog |
+--------------------------------------------+---------------+------------------------+
| Enabling a Flow Log | erFlowLog | updateFlowLog |
+--------------------------------------------+---------------+------------------------+
| Deleting a Flow Log | erFlowLog | deleteFlowLog |
+--------------------------------------------+---------------+------------------------+

2
umn/source/interconnecting_with_cts/viewing_traces.rst
View File

@ -45,6 +45,6 @@ Procedure
#. Click **View Trace**. A dialog box is displayed, in which the trace details are displayed.
For more information about CTS, see *Cloud Trace Service User Guide*.
For more information about CTS, see `Cloud Trace Service User Guide <https://docs.otc.t-systems.com/cloud-trace-service/umn/overview/index.html>`__.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

2
umn/source/monitoring/supported_metrics.rst
View File

@ -137,4 +137,4 @@ er_attachment_id Attachment
================ =================
- The monitoring metric measurement dimension of an enterprise router is **er_instance_id**.
- The monitoring metric measurement dimension of an attachment is **er_instance_id,er_attachment_id**.
- The monitoring metric measurement dimensions of an attachment are **er_instance_id** and **er_attachment_id**.

9
umn/source/propagations/creating_a_propagation.rst → umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst
View File

@ -2,16 +2,16 @@
.. _er_01_0036:
Creating a Propagation
======================
Creating a Propagation for an Attachment in the Route Table
===========================================================
Scenarios
---------
This section describes how to create a propagation in the route table of an enterprise router.
Notes and Constraints
---------------------
Notes
-----
You can create propagations for the same attachment in different route tables.
@ -52,7 +52,6 @@ Procedure
| | | |
| | - **VPC** | |
| | - **Virtual gateway** | |
| | - **VPN gateway** | |
| | | |
| | For more information, see :ref:`Attachment Overview <er_01_0019>`. | |
+-----------------------+--------------------------------------------------------------------------------------------+-----------------------+

4
umn/source/propagations/deleting_a_propagation.rst → umn/source/propagations/deleting_a_propagation_from_a_route_table.rst
View File

@ -2,8 +2,8 @@
.. _er_01_0038:
Deleting a Propagation
======================
Deleting a Propagation from a Route Table
=========================================
Scenarios
---------

12
umn/source/propagations/index.rst
View File

@ -6,15 +6,15 @@ Propagations
============
- :ref:`Propagation Overview <er_01_0035>`
- :ref:`Creating a Propagation <er_01_0036>`
- :ref:`Viewing a Propagation <er_01_0037>`
- :ref:`Deleting a Propagation <er_01_0038>`
- :ref:`Creating a Propagation for an Attachment in the Route Table <er_01_0036>`
- :ref:`Viewing a Propagation in a Route Table <er_01_0037>`
- :ref:`Deleting a Propagation from a Route Table <er_01_0038>`
.. toctree::
:maxdepth: 1
:hidden:
propagation_overview
creating_a_propagation
viewing_a_propagation
deleting_a_propagation
creating_a_propagation_for_an_attachment_in_the_route_table
viewing_a_propagation_in_a_route_table
deleting_a_propagation_from_a_route_table

24
umn/source/propagations/propagation_overview.rst
View File

@ -9,26 +9,24 @@ You can create a propagation for each attachment to propagate routes to one or m
If you do not want to create a propagation, you can manually add static routes for attachments to the route tables.
.. _er_01_0035__fig421415328433:
.. _er_01_0035__fig16423163124017:
.. figure:: /_static/images/en-us_image_0000001477172813.png
.. figure:: /_static/images/en-us_image_0000001347809009.png
:alt: **Figure 1** Propagated routes and static routes
**Figure 1** Propagated routes and static routes
.. table:: **Table 1** Propagation description
+-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------+-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attachment Type | Propagated Info | Way to Create Propagation | Description |
+=================+=================+==============================================================================================================================================================================================================+======================================================================================================================================================================================================================+
| VPC | VPC CIDR blocks | - Auto creation: If **Default Route Table Propagation** is enabled and the default propagation route table is specified, attachments automatically propagate routes to the default propagation route table. | An attachment can be propagated to different route tables. You can create propagations for attachments in :ref:`Figure 1 <er_01_0035__fig421415328433>` as follows: |
+=================+=================+===================================================================================================================================================================================================================+=================================================================================================================================================================================================================+
| 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 <er_01_0035__fig16423163124017>` as follows: |
| | | | |
| | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router <er_01_0069>`. | - 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 <er_01_0013>`. | - 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 <er_01_0036>`. | |
+-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | | - If you want to enable this function when you create an enterprise router, refer to :ref:`Creating an Enterprise Router <er_01_0069>`. | - Auto creation: Propagations are automatically created for the attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments, in the default propagation route table of the enterprise router. |
| | | - If you want to enable this function after an enterprise router is created, refer to :ref:`Modifying an Enterprise Router <er_01_0013>`. | - Manual creation: You need to manually create propagations in the custom route table of the enterprise router for attachments, such as VPC 1, virtual gateway 1, and virtual gateway 2 attachments. |
| | | | - No propagation: If you do not want to use propagated routes, you need to manually add static routes to the custom route table of the enterprise router for attachments, such as VPC 3 and VPC 4 attachments. |
| | | - Manual creation: You can select a route table and create a propagation for an attachment in the route table. For details, see :ref:`Creating a Propagation for an Attachment in the Route Table <er_01_0036>`. | |
+-----------------+-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Virtual gateway | All routes | | |
+-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| VPN gateway | All routes | | |
+-----------------+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------+-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Some files were not shown because too many files have changed in this diff Show More