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

Compare commits

base: dadrobna:main
Branches Tags
dadrobna:main
dadrobna:remove_environment_internal
dadrobna:propose-er_api-ref-1049
dadrobna:propose-er_umn-1048
dadrobna:zuul-tox-update
dadrobna:update_config_pdf
dadrobna:propose-er_api-ref-716
dadrobna:propose-er_api-ref-997
dadrobna:fix_sbv
dadrobna:propose-er_umn-680
dadrobna:minify_sphinx_gitea
dadrobna:minify_sphinx_internal
dadrobna:propose-er_umn-941
dadrobna:propose-er_api-ref-941
dadrobna:propose-er_umn-936
dadrobna:propose-er_api-ref-936
dadrobna:propose-er_umn-931
dadrobna:propose-er_api-ref-931
dadrobna:propose-er_umn-928
dadrobna:propose-er_api-ref-928
dadrobna:propose-er_umn-834
dadrobna:propose-er_api-ref-834
dadrobna:propose-er_umn-833
dadrobna:propose-er_api-ref-833
dadrobna:constraints
dadrobna:service_based_view
dadrobna:confpy
..
compare: dadrobna:propose-er_api-ref-1049
Branches Tags
dadrobna:remove_environment_internal
dadrobna:main
dadrobna:propose-er_api-ref-1049
dadrobna:propose-er_umn-1048
dadrobna:zuul-tox-update
dadrobna:update_config_pdf
dadrobna:propose-er_api-ref-716
dadrobna:propose-er_api-ref-997
dadrobna:fix_sbv
dadrobna:propose-er_umn-680
dadrobna:minify_sphinx_gitea
dadrobna:minify_sphinx_internal
dadrobna:propose-er_umn-941
dadrobna:propose-er_api-ref-941
dadrobna:propose-er_umn-936
dadrobna:propose-er_api-ref-936
dadrobna:propose-er_umn-931
dadrobna:propose-er_api-ref-931
dadrobna:propose-er_umn-928
dadrobna:propose-er_api-ref-928
dadrobna:propose-er_umn-834
dadrobna:propose-er_api-ref-834
dadrobna:propose-er_umn-833
dadrobna:propose-er_api-ref-833
dadrobna:constraints
dadrobna:service_based_view
dadrobna:confpy

2 Commits
main ... propose-er

Author SHA1 Message Date
OpenTelekomCloud Proposal Bot
5530631aa4 Update content 2024-03-05 12:43:24 +00:00
OpenTelekomCloud Proposal Bot
ed3e59b568 Update content 2024-02-06 08:41:43 +00:00
33 changed files with 357 additions and 416 deletions
Show Stats Expand all files Collapse all files

32
umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst
View File

@ -55,22 +55,22 @@ Procedure
.. table:: **Table 1** Parameters for creating an association
+-----------------------+------------------------------------------------------------------------------------------------+-----------------------+
| Parameter | Setting | Example Value |
+=======================+================================================================================================+=======================+
| Attachment Type | Mandatory | VPC |
| | | |
| | Select an attachment type. | |
| | | |
| | - **VPC**: A VPC is attached to the enterprise router. | |
| | - **Virtual gateway**: A Direct Connect virtual gateway is attached to the enterprise router. | |
| | | |
| | For more information, see :ref:`Attachment Overview <er_01_0019>`. | |
+-----------------------+------------------------------------------------------------------------------------------------+-----------------------+
| Attachment | Mandatory | er-attach-02 |
| | | |
| | In the drop-down list, select the attachment to be associated with the route table. | |
+-----------------------+------------------------------------------------------------------------------------------------+-----------------------+
+-----------------------+-------------------------------------------------------------------------------------+-----------------------+
| Parameter | Setting | Example Value |
+=======================+=====================================================================================+=======================+
| Attachment Type | Mandatory | VPC |
| | | |
| | Select an attachment type. | |
| | | |
| | - **VPC** | |
| | - **Virtual gateway** | |
| | | |
| | For more information, see :ref:`Attachment Overview <er_01_0019>`. | |
+-----------------------+-------------------------------------------------------------------------------------+-----------------------+
| Attachment | Mandatory | er-attach-02 |
| | | |
| | In the drop-down list, select the attachment to be associated with the route table. | |
+-----------------------+-------------------------------------------------------------------------------------+-----------------------+
#. Click **OK**.

87
umn/source/attachments/vpc_attachments/creating_a_vpc_attachment.rst → umn/source/attachments/adding_vpc_attachments_to_an_enterprise_router.rst
View File

File diff suppressed because it is too large Load Diff

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

@ -15,10 +15,10 @@ You can create an attachment to attach a network instance to an enterprise route
.. table:: **Table 1** Attachments
+----------------------------+-----------------------------------+-----------------------------------------------------------+-------------------------------------------+-----------------------------------------------------------+
| Attachment Type | Network Instance | Create Attachment | View Attachment | Delete Attachment |
+============================+===================================+===========================================================+===========================================+===========================================================+
| VPC attachment | VPC | :ref:`Creating a VPC Attachment <er_01_0070>` | :ref:`Viewing an Attachment <er_01_0021>` | :ref:`Deleting a VPC Attachment <er_01_0072>` |
+----------------------------+-----------------------------------+-----------------------------------------------------------+-------------------------------------------+-----------------------------------------------------------+
| Virtual gateway attachment | Virtual gateway of Direct Connect | :ref:`Creating a Virtual Gateway Attachment <er_01_0169>` | | :ref:`Deleting a Virtual Gateway Attachment <er_01_0073>` |
+----------------------------+-----------------------------------+-----------------------------------------------------------+-------------------------------------------+-----------------------------------------------------------+
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
| 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 | 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>` |
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+

4
umn/source/attachments/virtual_gateway_attachments/deleting_a_virtual_gateway_attachment.rst → umn/source/attachments/deleting_an_attachment/deleting_a_virtual_gateway_attachment.rst
View File

@ -15,7 +15,7 @@ Notes and Constraints
- Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.
- If flow logging is enabled for an attachment, flow logging will be disabled, but collected flow logs will not be deleted.
- Deleting an attachment will also delete its flow logs.
Procedure
---------
@ -43,7 +43,7 @@ Procedure
.. important::
A virtual gateway attachment cannot be directly deleted on the **Attachments** tab.
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.

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

@ -15,7 +15,7 @@ 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.
- If flow logging is enabled for an attachment, flow logging will be disabled, but collected flow logs will not be deleted.
- Deleting an attachment will also delete its flow logs.
Procedure
---------

16
umn/source/attachments/deleting_an_attachment/index.rst Normal file
View File

@ -0,0 +1,16 @@
:original_name: er_01_0022.html
.. _er_01_0022:
Deleting an Attachment
======================
- :ref:`Deleting a VPC Attachment <er_01_0072>`
- :ref:`Deleting a Virtual Gateway Attachment <er_01_0073>`
.. toctree::
:maxdepth: 1
:hidden:
deleting_a_vpc_attachment
deleting_a_virtual_gateway_attachment

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

@ -6,17 +6,17 @@ Attachments
===========
- :ref:`Attachment Overview <er_01_0019>`
- :ref:`VPC Attachments <er_01_0167>`
- :ref:`Virtual Gateway Attachments <er_01_0168>`
- :ref:`Adding VPC Attachments to an Enterprise Router <er_01_0070>`
- :ref:`Changing the Name of an Attachment <er_01_0093>`
- :ref:`Viewing an Attachment <er_01_0021>`
- :ref:`Viewing Details About an Attachment <er_01_0021>`
- :ref:`Deleting an Attachment <er_01_0022>`
.. toctree::
:maxdepth: 1
:hidden:
attachment_overview
vpc_attachments/index
virtual_gateway_attachments/index
adding_vpc_attachments_to_an_enterprise_router
changing_the_name_of_an_attachment
viewing_an_attachment
viewing_details_about_an_attachment
deleting_an_attachment/index

4
umn/source/attachments/viewing_an_attachment.rst → umn/source/attachments/viewing_details_about_an_attachment.rst
View File

@ -2,8 +2,8 @@
.. _er_01_0021:
Viewing an Attachment
=====================
Viewing Details About an Attachment
===================================
Scenarios
---------

16
umn/source/attachments/virtual_gateway_attachments/creating_a_virtual_gateway_attachment.rst
View File

@ -1,16 +0,0 @@
:original_name: er_01_0169.html
.. _er_01_0169:
Creating a Virtual Gateway Attachment
=====================================
Scenarios
---------
Attach a Direct Connect virtual gateway to an enterprise router to set up a hybrid cloud network using Direct Connect and Enterprise Router.
Procedure
---------
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>`__.

16
umn/source/attachments/virtual_gateway_attachments/index.rst
View File

@ -1,16 +0,0 @@
:original_name: er_01_0168.html
.. _er_01_0168:
Virtual Gateway Attachments
===========================
- :ref:`Creating a Virtual Gateway Attachment <er_01_0169>`
- :ref:`Deleting a Virtual Gateway Attachment <er_01_0073>`
.. toctree::
:maxdepth: 1
:hidden:
creating_a_virtual_gateway_attachment
deleting_a_virtual_gateway_attachment

16
umn/source/attachments/vpc_attachments/index.rst
View File

@ -1,16 +0,0 @@
:original_name: er_01_0167.html
.. _er_01_0167:
VPC Attachments
===============
- :ref:`Creating a VPC Attachment <er_01_0070>`
- :ref:`Deleting a VPC Attachment <er_01_0072>`
.. toctree::
:maxdepth: 1
:hidden:
creating_a_vpc_attachment
deleting_a_vpc_attachment

90
umn/source/change_history.rst
View File

@ -5,59 +5,37 @@
Change History
==============
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Released On | Description |
+===================================+================================================================================================================================================================================================================================================================================================+
| 2024-02-22 | Modified the following content: |
| | |
| | Added the default ASN of enterprise routers in :ref:`Step 2: Create an Enterprise Router <er_01_0064>` and :ref:`Creating an Enterprise Router <er_01_0069>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2024-02-18 | Modified the following content: |
| | |
| | - Modified the description of the **Destination Type** parameter in :ref:`Step 5: (Optional) Add Routes to VPC Route Tables <er_01_0067>`. |
| | - Modified the table style and canceled cell combination of :ref:`Table 2 <er_01_0011__table133841251278>` in :ref:`How Enterprise Routers Work <er_01_0011>`. |
| | - Modified the table style and canceled cell combination of :ref:`Table 3 <er_01_0095__table16962125143812>` in :ref:`Sharing Overview <er_01_0095>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2024-02-08 | Modified the following content: |
| | |
| | - Added the **Destination Type** parameter in :ref:`Step 5: (Optional) Add Routes to VPC Route Tables <er_01_0067>`. |
| | - Modified the example ASN values of enterprise routers in :ref:`Step 1: Plan Networks and Resources <er_01_0063>`, :ref:`Step 2: Create an Enterprise Router <er_01_0064>`, and :ref:`How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Each Other? <er_01_0123>` |
| | - Changed the title of :ref:`Overview <er_01_0062>`. |
| | - Added constraints on the 100.64.x.x network segment in :ref:`Notes and Constraints <er_01_0006>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2024-02-05 | Modified the following content: |
| | |
| | - Modified description about the **ASN** parameter in :ref:`Creating an Enterprise Router <er_01_0069>`. |
| | - Added a note to **Auto Add Routes** in :ref:`Creating a VPC Attachment <er_01_0070>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-11-21 | Modified the following content: |
| | |
| | Added a screenshot in :ref:`Viewing Quotas <er_01_0057>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-11-17 | Modified the following content: |
| | |
| | Added permission information in :ref:`Permissions <er_01_0008>` and :ref:`Permissions Management <er_01_0045>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-10-12 | Modified the following content: |
| | |
| | - Added console screenshots in "Tags" and "Flow Logs". |
| | - Modified the tag format description in :ref:`Overview <er_01_0049>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-10-09 | Modified the following content: |
| | |
| | - Added the description of the permission on shared enterprise routers in :ref:`Permissions <er_01_0008>`. |
| | - Added console screenshots for operations. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-09-22 | Modified the following content: |
| | |
| | - 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. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Released On | Description |
+===================================+==================================================================================================================================================================================================================================================================+
| 2023-11-21 | Modified the following content: |
| | |
| | Added a screenshot in :ref:`Viewing Quotas <er_01_0057>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-11-17 | Modified the following content: |
| | |
| | Added permission information in :ref:`Permissions <er_01_0008>` and :ref:`Permissions Management <er_01_0045>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-10-12 | Modified the following content: |
| | |
| | - Added console screenshots in "Tags" and "Flow Logs". |
| | - Modified the tag format description in :ref:`Overview <er_01_0049>`. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-10-09 | Modified the following content: |
| | |
| | - Added the description of the permission on shared enterprise routers in :ref:`Permissions <er_01_0008>`. |
| | - Added console screenshots for operations. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2023-09-22 | Modified the following content: |
| | |
| | - 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. |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

166
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

@ -13,7 +13,7 @@ This section describes how to delete an enterprise router.
Notes and Constraints
---------------------
- An enterprise router that has attachments cannot be deleted. Delete the attachments first. For details, see :ref:`Attachment Overview <er_01_0019>`.
- 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 is shared with other accounts can be deleted directly.
- Deleting an enterprise router will also delete all of its flow logs.

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

@ -12,7 +12,7 @@ This section describes how to view basic information about an enterprise router,
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 an Attachment <er_01_0021>`.
- Attachments, such as their name, type, and attached resources. For details, see :ref:`Viewing Details About an Attachment <er_01_0021>`.
- Route tables, such as the default route table and custom route tables. For details, see :ref:`Viewing Route Tables <er_01_0027>`.
- Tags. For details, see :ref:`Viewing a Tag <er_01_0053>`.

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

@ -9,7 +9,7 @@ If you want two attachments of an enterprise router to learn routes from each ot
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: 64800
- Enterprise router: 64512
- Virtual gateway attachment A: 64513 (BGP ASN of virtual gateway A)
- Virtual gateway attachment B: 64515 (BGP ASN of virtual gateway B)

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

@ -104,7 +104,7 @@ The required resources and routes are as follows:
#. 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, or the VPC peering connection to be created in :ref:`2 <er_01_0122__li14564823993>` cannot take effect.
- 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.

2
umn/source/flow_logs/disabling_a_flow_log.rst
View File

@ -8,7 +8,7 @@ Disabling a Flow Log
Scenarios
---------
If flow logging is disabled, no flow logs will be collected in the next log collection period. Collected flow logs can still be viewed.
This section describes how to disable a flow log. After a flow log is disabled, the enterprise router will not send log information to LTS.
Procedure
---------

2
umn/source/flow_logs/enabling_a_flow_log.rst
View File

@ -8,7 +8,7 @@ Enabling a Flow Log
Scenarios
---------
If flow logging is enabled, flow logs will be collected from the next log collection period.
This section describes how to enable a flow log. After a flow log is enabled, the enterprise router will send log information to LTS.
Procedure
---------

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

@ -5,7 +5,7 @@
Using an Enterprise Router to Enable Communications Between VPCs in the Same Region
===================================================================================
- :ref:`Overview <er_01_0062>`
- :ref:`Quick Start <er_01_0062>`
- :ref:`Step 1: Plan Networks and Resources <er_01_0063>`
- :ref:`Step 2: Create an Enterprise Router <er_01_0064>`
- :ref:`Step 3: (Optional) Create VPCs and ECSs <er_01_0065>`
@ -17,7 +17,7 @@ Using an Enterprise Router to Enable Communications Between VPCs in the Same Reg
:maxdepth: 1
:hidden:
overview
quick_start
step_1_plan_networks_and_resources
step_2_create_an_enterprise_router
step_3_optional_create_vpcs_and_ecss

6
umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/overview.rst → umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/quick_start.rst
View File

@ -2,13 +2,13 @@
.. _er_01_0062:
Overview
========
Quick Start
===========
Background
----------
Four VPCs are created in region A on the public cloud and they need to communicate with each other.
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.

2
umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/step_1_plan_networks_and_resources.rst
View File

@ -116,7 +116,7 @@ The enterprise router, VPCs, and ECSs must be in the same region. You can select
+------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+
| Enterprise Router Name | ASN | Default Route Table Association | Default Route Table Propagation | Association Route Table | Propagation Route Table | Attachment |
+========================+=======+=================================+=================================+=========================+=========================+==============+
| er-test-01 | 64800 | Enable | Enable | Default route table | Default route table | er-attach-01 |
| er-test-01 | 64512 | Enable | Enable | Default route table | Default route table | er-attach-01 |
+------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+
| | | | | | | er-attach-02 |
+------------------------+-------+---------------------------------+---------------------------------+-------------------------+-------------------------+--------------+

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

@ -48,9 +48,7 @@ Procedure
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Name | Specify the enterprise router name. You can change it after the enterprise router is created. | er-test-01 |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| ASN | Enter an ASN based on your network plan. It cannot be changed after the enterprise router is created. | 64800 |
| | | |
| | Default ASN: 64800 | |
| 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 |
+---------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+

10
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

@ -51,10 +51,12 @@ Procedure
+=======================+=====================================================================================================================================================================================================================================================================================================================================================================================================================================+===========================+
| Name | Specify the name of the VPC attachment. You can change it after the attachment is created. | er-attach-01 |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+
| Attachment Type | Select **VPC**. The type cannot be changed after the attachment is created. | VPC |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+
| Attached Resource | a. 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 |
| | b. 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 |
| 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. | |

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

@ -72,8 +72,6 @@ Procedure
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| Parameter | Setting | Example Value |
+=======================+=====================================================================================================================================================================================================================================================================================================================================================================================================================================+=======================+
| Destination Type | The destination can only be **IP address**. You can set a single IP address or network segment. | IP address |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+
| 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. | |

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

@ -19,7 +19,7 @@ Procedure
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List**. Under **Management and Deployment**, click **Cloud Trace Service**.
#. Click **Service List**. Under **Management & Governance**, click **Cloud Trace Service**.
The **Cloud Trace Service** console is displayed.

20
umn/source/permissions_management/creating_a_user_and_granting_permissions.rst
View File

@ -8,17 +8,17 @@ Creating a User and Granting Permissions
This section describes how to use IAM to implement fine-grained permissions control for your Enterprise Router resources. With IAM, you can:
- Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to Enterprise Router resources.
- Grant only the minimum permissions required for users to perform a given task.
- Assign only the minimum permissions required for users to perform a given task.
- Entrust an account or a cloud service to perform professional and efficient O&M on your Enterprise Router resources.
If your account does not require individual IAM users, skip this topic.
If your account does not require individual IAM users, skip over this section.
:ref:`Figure 1 <er_01_0046__fig208811382017>` shows the procedure for granting permissions.
Prerequisites
-------------
You have learned about Enterprise Router permissions that can be added to the user group. For details about the system permissions supported by enterprise routers, see :ref:`Permissions <er_01_0008>`.
You have learned about the permissions supported by Enterprise Router and choose policies or roles according to your requirements. For details, see :ref:`Permissions <er_01_0008>`.
For the permissions of other services, see `Permission Description <https://docs.otc.t-systems.com/permissions/index.html>`__.
@ -32,9 +32,19 @@ Process Flow
**Figure 1** Process for granting Enterprise Router permissions
#. `Create a user group and assign permissions to it <https://docs.otc.t-systems.com/usermanual/iam/iam_01_0030.html>`__ (**ER ReadOnlyAccess** as an example).
#. .. _er_01_0046__li10176121316284:
`Create a user group and assign permissions to it <https://docs.otc.t-systems.com/usermanual/iam/iam_01_0030.html>`__.
Create a user group on the IAM console, and assign the **ER ReadOnlyAccess** permission to the group.
#. `Create an IAM user and add it to the user group <https://docs.otc.t-systems.com/usermanual/iam/iam_01_0031.html>`__.
#. `Log in <https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html>`__ to the management console as the created user, switch to the authorized region, and verify that the user has only the **ER ReadOnlyAccess** permission.
Create a user on the IAM console and add the user to the group created in :ref:`1 <er_01_0046__li10176121316284>`.
#. `Log in <https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html>`__ and verify permissions.
Log in to the management console as the created user, switch to the authorized region, and verify that the user has only the **ER ReadOnlyAccess** permission.
a. Click **Service List** and choose **Enterprise Router**. Then click **Create Enterprise Router** in the upper right corner. If the enterprise router fails to be created, the **ER ReadOnlyAccess** permission has taken effect.
b. Choose any other service in the **Service List**. If a message appears indicating insufficient permissions to access the service, the **ER ReadOnlyAccess** permission has already taken effect.

32
umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst
View File

@ -55,22 +55,22 @@ Procedure
.. table:: **Table 1** Parameters for creating a propagation
+-----------------------+------------------------------------------------------------------------------------------------+-----------------------+
| Parameter | Setting | Example Value |
+=======================+================================================================================================+=======================+
| Attachment Type | Mandatory | VPC |
| | | |
| | Select an attachment type. | |
| | | |
| | - **VPC**: A VPC is attached to the enterprise router. | |
| | - **Virtual gateway**: A Direct Connect virtual gateway is attached to the enterprise router. | |
| | | |
| | For more information, see :ref:`Attachment Overview <er_01_0019>`. | |
+-----------------------+------------------------------------------------------------------------------------------------+-----------------------+
| Attachment | Mandatory | er-attach-02 |
| | | |
| | In the drop-down list, select the attachment who will propagate routes to the route table. | |
+-----------------------+------------------------------------------------------------------------------------------------+-----------------------+
+-----------------------+--------------------------------------------------------------------------------------------+-----------------------+
| Parameter | Setting | Example Value |
+=======================+============================================================================================+=======================+
| Attachment Type | Mandatory | VPC |
| | | |
| | Select an attachment type. | |
| | | |
| | - **VPC** | |
| | - **Virtual gateway** | |
| | | |
| | For more information, see :ref:`Attachment Overview <er_01_0019>`. | |
+-----------------------+--------------------------------------------------------------------------------------------+-----------------------+
| Attachment | Mandatory | er-attach-02 |
| | | |
| | In the drop-down list, select the attachment who will propagate routes to the route table. | |
+-----------------------+--------------------------------------------------------------------------------------------+-----------------------+
#. Click **OK**.

2
umn/source/route_tables/deleting_a_route_table.rst
View File

@ -18,7 +18,7 @@ Notes and Constraints
- If **Default Route Association** is set to **Yes** on the basic information page of the route table, the route table is used as the default association route table.
- Also, if **Default Route Propagation** is set to **Yes** on the basic information of the route table, the route table is used as the default propagation route table.
To delete such a route table, change **Default Route Association** and **Default Route Propagation** settings. For details, see :ref:`Modifying an Enterprise Router <er_01_0013>`.
To delete such a route table, disable **Default Route Association** and **Default Route Propagation** first. For details, see :ref:`Modifying an Enterprise Router <er_01_0013>`.
- 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.

6
umn/source/service_overview/functions.rst
View File

@ -21,11 +21,11 @@ An enterprise router provides the functions listed in :ref:`Table 1 <er_01_0005_
| | | |
| | After an enterprise router is created, you can still change its parameters based on service requirements. | |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+
| Attachments | You can attach network instances to the enterprise router. | :ref:`Attachment Overview <er_01_0019>` |
| Attachments | You can add attachments to attach network instances to the enterprise router. | :ref:`Attachment Overview <er_01_0019>` |
| | | |
| | Network instances are attached to the enterprise router in different ways. | |
| | Different network instances are attached through different consoles. | |
| | | |
| | - VPCs are attached to the enterprise router on the Enterprise Router console. | |
| | - VPCs are attached through the Enterprise Router console. | |
| | - Virtual gateways are attached through the Direct Connect console. | |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+
| Route tables | Route tables are used by enterprise routers to forward packets. Route tables contain associations, propagations, and routes. | :ref:`Route Table Overview <er_01_0024>` |

48
umn/source/service_overview/how_enterprise_routers_work.rst
View File

@ -7,10 +7,10 @@ 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 <er_01_0011__fig9264191913235>` shows the process of using an enterprise router, including creating an enterprise router, adding attachments to the enterprise router, and configure routes.
Enterprise routers support the following attachments:
Currently, enterprise routers support the following attachments:
- **VPC attachment**: Attach a VPC from the same region as that of an enterprise router.
- **Virtual gateway attachment**: Attach a Direct Connect virtual gateway from the same region as that of an enterprise router.
- **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.
.. _er_01_0011__fig9264191913235:
@ -19,9 +19,8 @@ Enterprise routers support the following attachments:
**Figure 1** Processing of using an enterprise router
:ref:`Figure 2 <er_01_0011__fig1520692752815>` shows how an enterprise router works. :ref:`Table 2 <er_01_0011__table133841251278>` describes the traffic flows in detail if an enterprise router is used for networking.
The following describes how an enterprise router works.
.. _er_01_0011__fig1520692752815:
.. figure:: /_static/images/en-us_image_0000001529830673.png
:alt: **Figure 2** How an enterprise router works
@ -40,28 +39,27 @@ Enterprise routers support the following attachments:
| 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. |
+-----+-------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. _er_01_0011__table133841251278:
.. table:: **Table 2** Working principles of an enterprise router
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| No. | Action | Description |
+=======================+===========================================================================================================================================================================================================================================+=================================================================================================================================================================================================================================+
| 1 | Add :ref:`attachments <er_01_0011__section692619383113>` 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 |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2 | #. Associate the :ref:`attachments <er_01_0011__section131904714219>` with the :ref:`route tables <er_01_0011__section14844328152418>` 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. |
| | #. Create :ref:`propagation <er_01_0011__section134131541823>` for the attachments to propagate the :ref:`routes <er_01_0011__section11725172512435>` to the enterprise router's :ref:`route tables <er_01_0011__section14844328152418>`. | |
| | | |
| | You can create multiple propagation records for the same attachment. | |
+-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| No. | Action | Description |
+=======================+========================================================================================================================================================================================================================================+=================================================================================================================================================================================================================================+
| 1 | Add :ref:`attachments <er_01_0011__section692619383113>` 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 |
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2 | Associate the :ref:`attachments <er_01_0011__section131904714219>` with the :ref:`route tables <er_01_0011__section14844328152418>` 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. |
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 3 | Create :ref:`propagation <er_01_0011__section134131541823>` for the attachments to propagate the :ref:`routes <er_01_0011__section11725172512435>` to the enterprise router's :ref:`route tables <er_01_0011__section14844328152418>`. | |
| | | |
| | You can create multiple propagation records for the same attachment. | |
+-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. _er_01_0011__section692619383113:

36
umn/source/service_overview/when_to_use_enterprise_routers.rst
View File

@ -23,24 +23,24 @@ Scenario 1: Multiple VPCs communicating or not communicating with each other on
.. 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. Suppose you require three VPCs for running the workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 and your 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 Direct Connect connection, eliminating the need to configure multiple Direct Connect connections and reducing the costs. |
+--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 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, an enterprise requires three VPCs for running their workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 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 Direct Connect connection, eliminating the need to configure multiple Direct Connect connections and reducing the costs. |
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. _er_01_0004__section12577403566:

112
umn/source/sharing/sharing_overview.rst
View File

File diff suppressed because it is too large Load Diff