Update content

This commit is contained in:
OpenTelekomCloud Proposal Bot 2023-03-27 11:16:27 +00:00 committed by vladimirhasko
parent 75ff3106f7
commit daba52d992
138 changed files with 4861 additions and 3 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 292 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 259 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 1004 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 148 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 306 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 289 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 259 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 259 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 289 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 583 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 247 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 583 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 292 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 97 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 95 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 113 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 221 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1004 B

View File

@ -0,0 +1,35 @@
:original_name: er_01_0030.html
.. _er_01_0030:
Association Overview
====================
Each attachment can be associated with one route table for:
- Packet forwarding: Packets from the attachment are forwarded through the routes specified in the associated route table.
- Route propagation: The routes in the associated route tables are automatically propagated to the route table of the attachment.
.. _er_01_0030__fig13563243183610:
.. figure:: /_static/images/en-us_image_0000001477452077.png
:alt: **Figure 1** Associations
**Figure 1** Associations
.. table:: **Table 1** Association description
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attachment Type | Route Propagation | Way to Create Association | Description |
+=================+===================+==============================================================================================================================================================================================================+=======================================================================================================================================================================================+
| VPC | Not supported | - Auto creation: If **Default Route Table Association** is enabled and the default association route table is specified, attachments are automatically associated with the default association route table. | Each attachment can only be associated with one route table. Associations between attachments in :ref:`Figure 1 <er_01_0030__fig13563243183610>` 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. |
| | | | |
| | | - 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>`. | |
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Virtual gateway | Supported | | |
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| VPN gateway | Supported | | |
+-----------------+-------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

View File

@ -0,0 +1,68 @@
:original_name: er_01_0031.html
.. _er_01_0031:
Creating an Association
=======================
Scenarios
---------
This section describes how to create an association in a route table of an enterprise router to associate a specified attachment with the route table.
Notes and Constraints
---------------------
Each attachment can only be associated with one route table. Packets from the attachment will be forwarded based on the route table.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Route Tables** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Route Table**.
- Click the enterprise router name and click **Route Tables**.
#. Click the route table where you want to create an association. On the **Associations** tab page, click **Create Association**.
The **Create Association** dialog box is displayed.
#. Configure the parameters based on :ref:`Table 1 <er_01_0031__table7204821194013>`.
.. _er_01_0031__table7204821194013:
.. table:: **Table 1** Parameters for creating an association
+-----------------------+-------------------------------------------------------------------------------------+-----------------------+
| Parameter | Setting | Example Value |
+=======================+=====================================================================================+=======================+
| Attachment Type | Mandatory | VPC |
| | | |
| | Select an attachment type. | |
| | | |
| | - **VPC** | |
| | - **Virtual gateway** | |
| | - **VPN gateway** | |
| | | |
| | For more information, see :ref:`Attachment Overview <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**.
The association list is displayed. You can view your association.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

View File

@ -0,0 +1,39 @@
:original_name: er_01_0033.html
.. _er_01_0033:
Deleting an Association
=======================
Scenarios
---------
This section describes how to delete an association from the route table of an enterprise router.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Route Tables** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Route Table**.
- Click the enterprise router name and click **Route Tables**.
#. Click the route table that you want to delete an association from. On the **Associations** tab page, locate the row that contains the association you want to delete and click **Delete** in the **Operation** column.
A confirmation dialog box is displayed.
#. Click **Yes**.
A deleted association cannot be recovered.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

View File

@ -0,0 +1,20 @@
:original_name: er_01_0029.html
.. _er_01_0029:
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>`
.. toctree::
:maxdepth: 1
:hidden:
association_overview
creating_an_association
viewing_an_association
deleting_an_association

View File

@ -0,0 +1,35 @@
:original_name: er_01_0032.html
.. _er_01_0032:
Viewing an Association
======================
Scenarios
---------
This section describes how to view associations in the route table of an enterprise router. You can also view all the attachments associated with this route table.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Route Tables** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Route Table**.
- Click the enterprise router name and click **Route Tables**.
#. Click the route table where you want to view its associations. On the **Associations** tab page, view the associations.
All attachments associated with the route table are also displayed.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,26 @@
:original_name: er_01_0019.html
.. _er_01_0019:
Attachment Overview
===================
You can create an attachment to attach a network instance to an enterprise router. The attachment type varies according to the network instance.
.. figure:: /_static/images/en-us_image_0000001427131632.png
:alt: **Figure 1** Attachments
**Figure 1** Attachments
.. table:: **Table 1** Attachments
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+
| Attachment Type | Network Instance | Create Attachment | View Attachment | Delete Attachment |
+============================+===================================+========================================================================================================================================================================+=========================================================+===========================================================+
| VPC attachment | VPC | :ref:`Adding VPC Attachments to an Enterprise Router <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>` |
+----------------------------+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------+-----------------------------------------------------------+

View File

@ -0,0 +1,55 @@
:original_name: er_01_0093.html
.. _er_01_0093:
Changing the Name of an Attachment
==================================
Scenarios
---------
This section describes how to change the name of an attachment.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Attachments** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Attachment**.
- Click the enterprise router name and click **Attachments**.
#. In the attachment list, click |image2| next to the attachment name.
The **Edit** dialog box is displayed.
#. Enter a new name.
.. table:: **Table 1** Parameter description
+-----------------------+--------------------------------------------------------------------------------+-----------------------+
| Parameter | Setting | Example Value |
+=======================+================================================================================+=======================+
| Name | Mandatory | er-attach-01 |
| | | |
| | Enter the attachment name. The name: | |
| | | |
| | - Must contain 1 to 64 characters. | |
| | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | |
+-----------------------+--------------------------------------------------------------------------------+-----------------------+
#. Click **OK**.
The attachment list is displayed.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png
.. |image2| image:: /_static/images/en-us_image_0000001243682317.png

View File

@ -0,0 +1,70 @@
:original_name: er_01_0073.html
.. _er_01_0073:
Deleting a Virtual Gateway Attachment
=====================================
Scenarios
---------
This section describes how to delete a virtual gateway attachment from an enterprise router.
Notes and Constraints
---------------------
- Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Attachments** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Attachment**.
- Click the enterprise router name and click **Attachments**.
.. important::
A virtual gateway attachment cannot be directly deleted on the **Attachments** page of the enterprise router.
A virtual gateway attachment will be automatically deleted after you perform the following operations to delete the virtual gateway and its virtual interfaces.
#. Locate the row that contains the target virtual gateway attachment and click the attached resource.
Example: vgw-demo
The virtual gateway attachment details page is displayed.
#. On the details page, click the virtual gateway.
The virtual gateway list is displayed.
#. Check whether the virtual gateway has virtual interfaces.
- If the virtual gateway has virtual interfaces, delete the virtual interfaces first.
For details, see section "Deleting a Virtual Interface" in the **Direct Connect User Guide**.
- If the virtual gateway has no virtual interfaces, go to :ref:`9 <er_01_0073__li1323115372813>`.
#. .. _er_01_0073__li1323115372813:
Locate the row that contains the target virtual gateway and click **Delete** in the **Operation** column.
A confirmation dialog box is displayed.
#. Click **Yes**.
A deleted virtual gateway cannot be recovered.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

View File

@ -0,0 +1,45 @@
:original_name: er_01_0072.html
.. _er_01_0072:
Deleting a VPC Attachment
=========================
Scenarios
---------
This section describes how to delete a VPC attachment from an enterprise router.
Notes and Constraints
---------------------
- Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.
- After an attachment is deleted, the next hop of its related static routes will be **Blackhole**. If the destination of a packet matches the blackhole route, the packet will be discarded.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Attachments** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Attachment**.
- Click the enterprise router name and click **Attachments**.
#. In the attachment list, locate the row that contains the target VPC attachment, and click **Delete** in the **Operation** column.
A confirmation dialog box is displayed.
#. Click **Yes**.
A deleted attachment cannot be recovered.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

View File

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

View File

@ -0,0 +1,18 @@
: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>`
- :ref:`Deleting a VPN Gateway Attachment <er_01_0114>`
.. toctree::
:maxdepth: 1
:hidden:
deleting_a_vpc_attachment
deleting_a_virtual_gateway_attachment
deleting_a_vpn_gateway_attachment

View File

@ -0,0 +1,22 @@
:original_name: er_01_0018.html
.. _er_01_0018:
Attachments
===========
- :ref:`Attachment Overview <er_01_0019>`
- :ref:`Adding VPC Attachments to an Enterprise Router <er_01_0070>`
- :ref:`Changing the Name of an Attachment <er_01_0093>`
- :ref:`Viewing Details About an Attachment <er_01_0021>`
- :ref:`Deleting an Attachment <er_01_0022>`
.. toctree::
:maxdepth: 1
:hidden:
attachment_overview
adding_vpc_attachments_to_an_enterprise_router
changing_the_name_of_an_attachment
viewing_details_about_an_attachment
deleting_an_attachment/index

View File

@ -0,0 +1,39 @@
:original_name: er_01_0021.html
.. _er_01_0021:
Viewing Details About an Attachment
===================================
Scenarios
---------
This section describes how to view details about the attachments of an enterprise router, including the attachment name, attachment type, and attached resources.
The methods for viewing details about different types of attachments are the same. This section uses a VPC attachment as an example.
Procedure
---------
#. Log in to the management console.
#. Click |image1| in the upper left corner and select the desired region and project.
#. Click **Service List** and choose **Networking** > **Enterprise Router**.
The **Enterprise Router** homepage is displayed.
#. Search for the target enterprise router by name.
#. Go to the **Attachments** tab page using either of the following methods:
- In the upper right corner of the enterprise router, click **Manage Attachment**.
- Click the enterprise router name and click **Attachments**.
#. On the **Attachments** tab page, you can view:
- In the attachment list, you can view the attachment status, attachment type, and attached resource.
- If you click the attachment name, you can view more information about the attachment on the displayed page, including the attachment ID, creation time, and tags.
- If you click the attached resource, you will go to the details page of the attached resource.
.. |image1| image:: /_static/images/en-us_image_0000001190483836.png

View File

@ -0,0 +1,12 @@
:original_name: UgChangeHistory.html
.. _UgChangeHistory:
Change History
==============
=========== =========================================
Released On Description
=========== =========================================
2023-03-24 This issue is the first official release.
=========== =========================================

0
umn/source/conf.py Executable file → Normal file
View File

2
umn/source/docutils.conf Normal file
View File

@ -0,0 +1,2 @@
[html writers]
table-style: table, caption-top

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