diff --git a/umn/source/_static/images/en-us_image_0152727234.png b/umn/source/_static/images/en-us_image_0152727234.png new file mode 100644 index 0000000..35e2831 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0152727234.png differ diff --git a/umn/source/_static/images/en-us_image_0275513364.png b/umn/source/_static/images/en-us_image_0275513364.png new file mode 100644 index 0000000..1909444 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0275513364.png differ diff --git a/umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst b/umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst index 8075a54..6dd5c4b 100644 --- a/umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst +++ b/umn/source/associations/creating_an_association_for_an_attachment_in_a_route_table.rst @@ -55,23 +55,22 @@ Procedure .. table:: **Table 1** Parameters for creating an association - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Setting | Example Value | - +=======================+=====================================================================================================================================================+=======================+ - | Attachment Type | Mandatory | VPC | - | | | | - | | Select an attachment type. | | - | | | | - | | - **VPC** | | - | | - **Virtual gateway** | | - | | - **Peering connection**: indicates that the enterprise router will connect to another enterprise router in the same region or a different region. | | - | | | | - | | For more information, see :ref:`Attachment Overview `. | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Attachment | Mandatory | er-attach-02 | - | | | | - | | In the drop-down list, select the attachment to be associated with the route table. | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +-----------------------+------------------------------------------------------------------------------------------------+-----------------------+ + | 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 `. | | + +-----------------------+------------------------------------------------------------------------------------------------+-----------------------+ + | Attachment | Mandatory | er-attach-02 | + | | | | + | | In the drop-down list, select the attachment to be associated with the route table. | | + +-----------------------+------------------------------------------------------------------------------------------------+-----------------------+ #. Click **OK**. diff --git a/umn/source/enterprise_routers/creating_an_enterprise_router.rst b/umn/source/enterprise_routers/creating_an_enterprise_router.rst index 0766293..7cb725f 100644 --- a/umn/source/enterprise_routers/creating_an_enterprise_router.rst +++ b/umn/source/enterprise_routers/creating_an_enterprise_router.rst @@ -37,89 +37,89 @@ Procedure .. table:: **Table 1** Parameters for creating an enterprise router - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Setting | Example Value | - +=================================+=========================================================================================================================================================================================================================================================================================================================================================================================================================================+=======================+ - | Region | Mandatory | ``-`` | - | | | | - | | Select the region nearest to you to ensure the lowest latency possible. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | AZ | Mandatory | AZ1 | - | | | | - | | An AZ is a physical location where resources use independent power supplies and networks. AZs are physically isolated but interconnected through an internal network. Each region contains multiple AZs. If one AZ is unavailable, the other AZs in the same region continue to provide services. | AZ2 | - | | | | - | | We recommend you to select two AZs. The enterprise router will be deployed in both AZs that work in active-active mode, ensuring reliability and disaster recovery. | | - | | | | - | | Traffic in an AZ is preferentially transmitted to the enterprise router in the same AZ to reduce latency. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Name | Mandatory | er-test-01 | - | | | | - | | Enter a name for the enterprise router. The name: | | - | | | | - | | - Must contain 1 to 64 characters. | | - | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | ASN | Mandatory | 64512 | - | | | | - | | An autonomous system is an IP network that is managed by an entity and has the same route policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them. | | - | | | | - | | Specify a dedicated ASN in the range of 64512-65534 or 4200000000-4294967294. | | - | | | | - | | Networks in the same region can be considered as an AS. | | - | | | | - | | When Direct Connect and Enterprise Router are used to set up a hybrid cloud network, it is recommended that you set the ASN of the enterprise router different from the BGP ASN of the Direct Connect virtual gateway. If there are multiple Direct Connect connections associated with an enterprise router and the connections do not work in load balancing or active/standby mode, set different BGP ASNs for the virtual gateways. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Default Route Table Association | Optional | Enable | - | | | | - | | Enabled by default | | - | | | | - | | Enabling **Default Route Table Association** can simplify network configurations. After this function is enabled: | | - | | | | - | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default association route table. | | - | | | | - | | After the enterprise router is created, you can create a custom route table and set it as the default association route table to replace the original one if needed. For details, see :ref:`Modifying an Enterprise Router `. | | - | | | | - | | b. If you create an attachment to this enterprise router, the attachment will be automatically associated with the default association route table. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Default Route Table Propagation | Optional | Enable | - | | | | - | | Enabled by default | | - | | | | - | | Enabling **Default Route Table Propagation** can simplify network configurations. After this function is enabled: | | - | | | | - | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default propagation route table. | | - | | | | - | | If both **Default Route Table Association** and **Default Route Table Propagation** are enabled, **defaultRouteTable** is not only the default association route table but also the default propagation route table. | | - | | | | - | | After the enterprise router is created, you can create a custom route table and set it as the default propagation route table to replace the original one if needed. For details, see :ref:`Modifying an Enterprise Router `. | | - | | | | - | | b. If you create an attachment to this enterprise router, the attachment will be automatically propagated to the default propagation route table. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Auto Accept Shared Attachments | Optional | Disable | - | | | | - | | As the owner, you can share your enterprise router with other users. These other users can create attachments for your enterprise router. | | - | | | | - | | - If you do not select this option, you must manually accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | - | | - If you select this option, the system will automatically accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | - | | | | - | | For details, see :ref:`Sharing Overview `. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Enterprise Project | Mandatory | default | - | | | | - | | Select an enterprise project that the enterprise router will be added to. | | - | | | | - | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The default project is **default**. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Tag | Optional | **Tag key**: test | - | | | | - | | Add tags to help you quickly find your enterprise router. | **Tag value**: 01 | - | | | | - | | For details, see :ref:`Overview `. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Description | Optional | ``-`` | - | | | | - | | Describe the enterprise router for easy identification. | | - +---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Setting | Example Value | + +=================================+===============================================================================================================================================================================================================================================================================================================================================================================================================================================================+=======================+ + | Region | Mandatory | ``-`` | + | | | | + | | Select the region nearest to you to ensure the lowest latency possible. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | AZ | Mandatory | AZ1 | + | | | | + | | An AZ is a physical location where resources use independent power supplies and networks. AZs are physically isolated but interconnected through an internal network. Each region contains multiple AZs. If one AZ is unavailable, the other AZs in the same region continue to provide services. | AZ2 | + | | | | + | | We recommend you to select two AZs. The enterprise router will be deployed in both AZs that work in active-active mode, ensuring reliability and disaster recovery. | | + | | | | + | | Traffic in an AZ is preferentially transmitted to the enterprise router in the same AZ to reduce latency. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Name | Mandatory | er-test-01 | + | | | | + | | Enter a name for the enterprise router. The name: | | + | | | | + | | - Must contain 1 to 64 characters. | | + | | - Can contain letters, digits, underscores (_), hyphens (-), and periods (.). | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | ASN | Mandatory | 64800 | + | | | | + | | An autonomous system is an IP network that is managed by an entity and has the same route policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them. | | + | | | | + | | Specify a dedicated ASN in the range of 64512-65534 or 4200000000-4294967294. | | + | | | | + | | Networks in the same region can be considered as an AS. | | + | | | | + | | When Direct Connect and Enterprise Router are used to set up a hybrid cloud network, it is recommended that you set the ASN of the enterprise router different from the BGP ASN of the Direct Connect virtual gateway. If there are multiple Direct Connect connections associated with the enterprise router and the connections do not work in load balancing or active/standby mode, set different BGP ASNs for the virtual gateways of these connections. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Default Route Table Association | Optional | Enable | + | | | | + | | Enabled by default | | + | | | | + | | Enabling **Default Route Table Association** can simplify network configurations. After this function is enabled: | | + | | | | + | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default association route table. | | + | | | | + | | After the enterprise router is created, you can create a custom route table and set it as the default association route table to replace the original one if needed. For details, see :ref:`Modifying an Enterprise Router `. | | + | | | | + | | b. If you create an attachment to this enterprise router, the attachment will be automatically associated with the default association route table. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Default Route Table Propagation | Optional | Enable | + | | | | + | | Enabled by default | | + | | | | + | | Enabling **Default Route Table Propagation** can simplify network configurations. After this function is enabled: | | + | | | | + | | a. An enterprise router automatically comes with a route table named **defaultRouteTable**. By default, this route table is the default propagation route table. | | + | | | | + | | If both **Default Route Table Association** and **Default Route Table Propagation** are enabled, **defaultRouteTable** is not only the default association route table but also the default propagation route table. | | + | | | | + | | After the enterprise router is created, you can create a custom route table and set it as the default propagation route table to replace the original one if needed. For details, see :ref:`Modifying an Enterprise Router `. | | + | | | | + | | b. If you create an attachment to this enterprise router, the attachment will be automatically propagated to the default propagation route table. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Auto Accept Shared Attachments | Optional | Disable | + | | | | + | | As the owner, you can share your enterprise router with other users. These other users can create attachments for your enterprise router. | | + | | | | + | | - If you do not select this option, you must manually accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | + | | - If you select this option, the system will automatically accept attachments to this enterprise router from the accounts that this enterprise router is shared with. | | + | | | | + | | For details, see :ref:`Sharing Overview `. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Enterprise Project | Mandatory | default | + | | | | + | | Select an enterprise project that the enterprise router will be added to. | | + | | | | + | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The default project is **default**. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Tag | Optional | **Tag key**: test | + | | | | + | | Add tags to help you quickly find your enterprise router. | **Tag value**: 01 | + | | | | + | | For details, see :ref:`Overview `. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | Optional | ``-`` | + | | | | + | | Describe the enterprise router for easy identification. | | + +---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ #. Click **Create Now**. diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/quick_start.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/before_you_start.rst similarity index 99% rename from umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/quick_start.rst rename to umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/before_you_start.rst index f7618b1..6ebb19f 100644 --- a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/quick_start.rst +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/before_you_start.rst @@ -2,8 +2,8 @@ .. _er_01_0062: -Quick Start -=========== +Before You Start +================ Background ---------- diff --git a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index.rst b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index.rst index 6185f34..532499d 100644 --- a/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index.rst +++ b/umn/source/getting_started/using_an_enterprise_router_to_enable_communications_between_vpcs_in_the_same_region/index.rst @@ -5,7 +5,7 @@ Using an Enterprise Router to Enable Communications Between VPCs in the Same Region =================================================================================== -- :ref:`Quick Start ` +- :ref:`Before You Start ` - :ref:`Step 1: Plan Networks and Resources ` - :ref:`Step 2: Create an Enterprise Router ` - :ref:`Step 3: (Optional) Create VPCs and ECSs ` @@ -17,7 +17,7 @@ Using an Enterprise Router to Enable Communications Between VPCs in the Same Reg :maxdepth: 1 :hidden: - quick_start + before_you_start step_1_plan_networks_and_resources step_2_create_an_enterprise_router step_3_optional_create_vpcs_and_ecss diff --git a/umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst b/umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst index 1fd24d6..58ded3b 100644 --- a/umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst +++ b/umn/source/propagations/creating_a_propagation_for_an_attachment_in_the_route_table.rst @@ -55,23 +55,22 @@ Procedure .. table:: **Table 1** Parameters for creating a propagation - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Setting | Example Value | - +=======================+=====================================================================================================================================================+=======================+ - | Attachment Type | Mandatory | VPC | - | | | | - | | Select an attachment type. | | - | | | | - | | - **VPC** | | - | | - **Virtual gateway** | | - | | - **Peering connection**: indicates that the enterprise router will connect to another enterprise router in the same region or a different region. | | - | | | | - | | For more information, see :ref:`Attachment Overview `. | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Attachment | Mandatory | er-attach-02 | - | | | | - | | In the drop-down list, select the attachment who will propagate routes to the route table. | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +-----------------------+------------------------------------------------------------------------------------------------+-----------------------+ + | 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 `. | | + +-----------------------+------------------------------------------------------------------------------------------------+-----------------------+ + | Attachment | Mandatory | er-attach-02 | + | | | | + | | In the drop-down list, select the attachment who will propagate routes to the route table. | | + +-----------------------+------------------------------------------------------------------------------------------------+-----------------------+ #. Click **OK**. diff --git a/umn/source/quotas/viewing_quotas.rst b/umn/source/quotas/viewing_quotas.rst index 9530533..743b0a8 100644 --- a/umn/source/quotas/viewing_quotas.rst +++ b/umn/source/quotas/viewing_quotas.rst @@ -10,8 +10,8 @@ Scenarios The following provides operations for you to view the quotas of enterprise routers and related resources in your account. -How Do I View My Quota? ------------------------ +How Do I View My Quotas? +------------------------ #. Log in to the management console. @@ -21,6 +21,21 @@ How Do I View My Quota? The **Service Quota** page is displayed. +#. View the used and total quota of each type of resources on the displayed page. + + If a quota cannot meet service requirements, apply for a higher quota. + +How Do I View My Quota? +----------------------- + +#. Log in to the management console. + +#. Click |image3| in the upper left corner and select the desired region and project. + +#. In the upper right corner of the page, click |image4|. + + The **Service Quota** page is displayed. + .. figure:: /_static/images/en-us_image_0000001764265877.png :alt: **Figure 1** Service Quota @@ -31,5 +46,7 @@ How Do I View My Quota? If a quota cannot meet your needs, apply for a higher quota by performing the operations in the next section. -.. |image1| image:: /_static/images/en-us_image_0000001716625548.png -.. |image2| image:: /_static/images/en-us_image_0000001716466100.png +.. |image1| image:: /_static/images/en-us_image_0275513364.png +.. |image2| image:: /_static/images/en-us_image_0152727234.png +.. |image3| image:: /_static/images/en-us_image_0000001716625548.png +.. |image4| image:: /_static/images/en-us_image_0000001716466100.png