Identity and Access Management (IAM)
|
You can use IAM to assign different permissions to different users to control their access to enterprise router resources.
diff --git a/docs/er/umn/er_01_0011.html b/docs/er/umn/er_01_0011.html
index 410e467a..77a31bd6 100644
--- a/docs/er/umn/er_01_0011.html
+++ b/docs/er/umn/er_01_0011.html
@@ -1,38 +1,38 @@
How Enterprise Routers Work
-You can attach your network connections to an enterprise router to quickly construct diversified networks and meet various service requirements. Figure 1 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: - 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.
+ You can attach your network connections to an enterprise router to quickly construct diversified networks and meet various service requirements. Figure 1 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: - 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.
- VPN gateway attachment: Attach a VPN gateway from the same region as that of an enterprise router.
- Figure 1 Processing of using an enterprise router
- Figure 2 shows how an enterprise router works. Table 2 describes the traffic flows in detail if an enterprise router is used for networking.
- Figure 2 How an enterprise router works
+ Figure 1 Processing of using an enterprise router
+ Figure 2 shows how an enterprise router works. Table 2 describes the traffic flows in detail if an enterprise router is used for networking.
+ Figure 2 How an enterprise router works
- Table 1 Network traffic flowsNo.
+Table 1 Network traffic flowsNo.
|
-Route
+ | Route
|
-Description
+ | Description
|
|---|
-1
+ | 1
|
-Request from VPC 1 to Direct Connect virtual gateway
+ | Request from VPC 1 to Direct Connect virtual gateway
|
-After receiving requests from VPC 1 to the virtual gateway, enterprise router 1 searches the default route table for the route to the virtual gateway and forwards the requests through this route.
+ | After receiving requests from VPC 1 to the virtual gateway, enterprise router 1 searches the default route table for the route to the virtual gateway and forwards the requests through this route.
|
-Response from Direct Connect virtual gateway to VPC 1
+ | Response from Direct Connect virtual gateway to VPC 1
|
-After receiving responses from the virtual gateway to VPC 1, enterprise router 1 searches the default route table for the route to VPC 1 and forwards the responses through this route.
+ | After receiving responses from the virtual gateway to VPC 1, enterprise router 1 searches the default route table for the route to VPC 1 and forwards the responses through this route.
|
-2
+ | 2
|
-Request from VPC 2 to Direct Connect virtual gateway
+ | 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.
+ | 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.
|
@@ -52,7 +52,7 @@
Add attachments to the enterprise router.
|
Attach network instances to enterprise router 1 in region A.
-Network instances from the same region - VPC attachments: VPC 1, VPC 2, and VPC 3
- Virtual gateway attachment: Virtual gateway
+ Network instances from the same region - VPC attachments: VPC 1, VPC 2, and VPC 3
- Virtual gateway attachment: Virtual gateway
- VPN gateway attachment: VPN gateway
|
@@ -62,7 +62,7 @@
Create propagation for the attachments to propagate the routes to the enterprise router's route tables.You can create multiple propagation records for the same attachment.
-- 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.
- Associate VPC 3 with the custom route table of enterprise router 1, and add static routes for VPC 3 to this custom route table.
- Associate the Direct Connect virtual gateway with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from the virtual gateway attachment to the default route table.
+ | - Associate 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.
- Associate VPC 3 with the custom route table of enterprise router 1, and add static routes for VPC 3 to this custom route table.
- Associate the Direct Connect virtual gateway with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from the virtual gateway attachment to the default route table.
- Associate the VPN gateway with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from the VPN gateway attachment to the default route table.
|
@@ -86,13 +86,18 @@
Virtual gateway of Direct Connect
|
+VPN gateway attachment
+ |
+VPN gateway
+ |
+
Route TablesRoute tables are used by enterprise routers to forward packets. Route tables contain associations, propagations, and routes. Route tables are classified into custom and default route tables, as detailed in Table 4.
- Table 4 Route tablesRoute Table
+Table 4 Route tablesRoute Table Type
|
Description
|
@@ -116,7 +121,7 @@
AssociationsEach attachment can be associated with one route table for: - Packet forwarding: Packets from the attachment are forwarded through the routes specified in the associated route table.
- Route propagation: The routes in the associated route tables are automatically propagated to the route table of the attachment.
Not all attachments can propagate routes. For details, see Table 5.
- Table 5 AssociationsAttachment
+Table 5 AssociationsAttachment Type
|
Route Learning
|
@@ -132,6 +137,11 @@
Supported
|
|---|
+VPN gateway
+ |
+Supported
+ |
+
Route PropagationYou can create a propagation for each attachment to propagate routes to one or more route tables on an enterprise router.
For VPC attachments, their CIDR blocks are propagated to the enterprise router. For other attachments, all routes are propagated to the enterprise router. For details, see Table 6.
- Table 6 PropagationAttachment
+Table 6 PropagationAttachment Type
|
Propagated Routes to Enterprise Router
|
@@ -155,6 +165,11 @@
All routes
|
|---|
+VPN gateway
+ |
+All routes
+ |
+
| Propagated routes are automatically learned through propagation and cannot be modified or deleted.
|
-
+ | - VPC
- Virtual gateway
- VPN gateway
|
|---|
Static routes
diff --git a/docs/er/umn/er_01_0013.html b/docs/er/umn/er_01_0013.html
index a11b63b0..b86ffcdd 100644
--- a/docs/er/umn/er_01_0013.html
+++ b/docs/er/umn/er_01_0013.html
@@ -4,7 +4,7 @@
ScenariosThis section describes how to modify settings of an enterprise router. You can: - Modify the name of an enterprise router.
- Enable or disable Default Route Table Association.
- Enable or disable Default Route Table Propagation.
- Procedure- Log in to the management console.
- Click
 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- In the upper right corner of the target enterprise router, choose More > Modify Settings.
The Modify Settings page is displayed.
Figure 2 Modify Settings
diff --git a/docs/er/umn/er_01_0016.html b/docs/er/umn/er_01_0016.html
index 7b395956..282403d9 100644
--- a/docs/er/umn/er_01_0016.html
+++ b/docs/er/umn/er_01_0016.html
@@ -5,7 +5,7 @@
You can also view other information about the enterprise router, including:
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
In addition to the information shown in the enterprise router list, you can go to 5 to view more details.
Figure 1 Searching for an enterprise router
- Click the name of the target enterprise router to go to the Basic Information page.
View detailed information about the enterprise router.
diff --git a/docs/er/umn/er_01_0017.html b/docs/er/umn/er_01_0017.html
index 22a219be..d46dc214 100644
--- a/docs/er/umn/er_01_0017.html
+++ b/docs/er/umn/er_01_0017.html
@@ -1,14 +1,14 @@
Deleting an Enterprise Router
-ScenariosThis section describes how to delete an enterprise router.
+ ScenariosDelete an enterprise router that is no longer needed.
Notes and Constraints- An enterprise router that has attachments cannot be deleted. Delete the attachments first. For details, see Attachment Overview.
- 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.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- In the upper right corner of the target enterprise router, choose More > Delete.
A confirmation dialog box is displayed.
- - Click Yes.
A deleted enterprise router cannot be recovered.
+ - Click Yes.
A deleted enterprise router cannot be recovered.
diff --git a/docs/er/umn/er_01_0018.html b/docs/er/umn/er_01_0018.html
index bb072f3e..8affa4ec 100644
--- a/docs/er/umn/er_01_0018.html
+++ b/docs/er/umn/er_01_0018.html
@@ -14,6 +14,8 @@
- Virtual Gateway Attachments
+ - VPN Gateway Attachments
+
- Changing the Name of an Attachment
- Viewing an Attachment
diff --git a/docs/er/umn/er_01_0019.html b/docs/er/umn/er_01_0019.html
index 2ca7354e..64eb7ce1 100644
--- a/docs/er/umn/er_01_0019.html
+++ b/docs/er/umn/er_01_0019.html
@@ -1,45 +1,58 @@
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 1 Attachments
+ You can create an attachment to attach a network instance to an enterprise router. The attachment type varies by the type of network instance. Figure 1 Attachments
- Table 1 AttachmentsAttachment Type
+
+
diff --git a/docs/er/umn/er_01_0021.html b/docs/er/umn/er_01_0021.html
index 4fcf0ea9..d7c0a088 100644
--- a/docs/er/umn/er_01_0021.html
+++ b/docs/er/umn/er_01_0021.html
@@ -4,12 +4,13 @@
ScenariosThis 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 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Attachments tab 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.
Figure 2 Viewing attachments
- On the Attachments tab, you can view:
- In the attachment list, you can view information such as the name, status, type, and attached resource.
- If you click the attachment name, you can view more information about the attachment on the displayed page, including the attachment ID, creation time, and tags.
- If you click the attached resource, you will go to the details page of the attached resource.
-Figure 3 Viewing attachment details
+Figure 3 Viewing attachment details (virtual gateway attachment)
+Figure 4 Viewing attachment details (VPN gateway attachment)
diff --git a/docs/er/umn/er_01_0025.html b/docs/er/umn/er_01_0025.html
index 8f1da4d3..9b27a6f0 100644
--- a/docs/er/umn/er_01_0025.html
+++ b/docs/er/umn/er_01_0025.html
@@ -3,7 +3,7 @@
Creating a Route Table
ScenariosThis section describes how to create a custom route table for an enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Route Tables
diff --git a/docs/er/umn/er_01_0026.html b/docs/er/umn/er_01_0026.html
index 1eb96338..7a445fff 100644
--- a/docs/er/umn/er_01_0026.html
+++ b/docs/er/umn/er_01_0026.html
@@ -5,11 +5,11 @@
Notes and ConstraintsOnly the name and description of route tables named defaultRouteTable and custom route tables can be changed.
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Renaming a route table
- - In the route table list, click
 next to the name of the target route table.The Modify Route Table dialog box is displayed.
+ - In the route table list, click
 next to the name of the target route table.The Modify Route Table dialog box is displayed.
- Enter a new name.
Table 1 Parameter descriptionParameter
|
diff --git a/docs/er/umn/er_01_0027.html b/docs/er/umn/er_01_0027.html
index 9648df4a..f3bd13af 100644
--- a/docs/er/umn/er_01_0027.html
+++ b/docs/er/umn/er_01_0027.html
@@ -3,7 +3,7 @@
Viewing Route Tables
ScenariosThis section describes how to view route tables of an enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Route Tables
diff --git a/docs/er/umn/er_01_0028.html b/docs/er/umn/er_01_0028.html
index 9acd3bc3..b045e472 100644
--- a/docs/er/umn/er_01_0028.html
+++ b/docs/er/umn/er_01_0028.html
@@ -1,14 +1,14 @@
Deleting a Route Table
-ScenariosThis section describes how to delete a route table of an enterprise router.
+ ScenariosDelete an enterprise router route table that is no longer needed.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Deleting a route table
diff --git a/docs/er/umn/er_01_0030.html b/docs/er/umn/er_01_0030.html
index 0ed01b49..391dcd85 100644
--- a/docs/er/umn/er_01_0030.html
+++ b/docs/er/umn/er_01_0030.html
@@ -3,32 +3,37 @@
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.
- Figure 1 Associations
+ Figure 1 Associations
- Table 1 Association descriptionAttachment Type
+Table 1 Association descriptionAttachment Type
|
-Route Learning
+ | Route Learning
|
-Way to Create Association
+ | Way to Create Association
|
-Description
+ | Description
|
|---|
-VPC
+ | VPC
|
-Not supported
+ | 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.
-
- 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 Creating an Association for an Attachment in a Route Table.
+ | - 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.
+
- 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 Creating an Association for an Attachment in a Route Table.
|
-Each attachment can only be associated with one route table. Associations between attachments in Association Overview are described as follows:
-- Auto creation: The system automatically associates attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments, with the default route table of the enterprise router.
- Manual creation: You need to manually create associations in the custom route table of the enterprise router for attachments, such as VPC 3, VPC 4, and virtual gateway 2 attachments.
+ | Each attachment can only be associated with one route table. Associations between attachments in Figure 1 are described as follows:
+- 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.
- 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.
|
-Virtual gateway
+ | Virtual gateway
|
-Supported
+ | Supported
+ |
+
+VPN gateway
+ |
+Supported
|
diff --git a/docs/er/umn/er_01_0031.html b/docs/er/umn/er_01_0031.html
index ca26459f..63da3cd4 100644
--- a/docs/er/umn/er_01_0031.html
+++ b/docs/er/umn/er_01_0031.html
@@ -5,7 +5,7 @@
Notes and ConstraintsEach 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 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Create Association
@@ -22,7 +22,7 @@
Attachment Type
|
Mandatory
-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.
+ 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.
- VPN gateway: A VPN gateway is attached to the enterprise router.
For more information, see Attachment Overview.
|
diff --git a/docs/er/umn/er_01_0032.html b/docs/er/umn/er_01_0032.html
index 43f31e5e..6f94b6f2 100644
--- a/docs/er/umn/er_01_0032.html
+++ b/docs/er/umn/er_01_0032.html
@@ -3,7 +3,7 @@
Viewing Associations in a Route Table
ScenariosThis 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 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Viewing associations
diff --git a/docs/er/umn/er_01_0033.html b/docs/er/umn/er_01_0033.html
index d8755169..cef2715a 100644
--- a/docs/er/umn/er_01_0033.html
+++ b/docs/er/umn/er_01_0033.html
@@ -3,7 +3,7 @@
Deleting an Association from a Route Table
ScenariosThis section describes how to delete an association from the route table of an enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Deleting an association
diff --git a/docs/er/umn/er_01_0035.html b/docs/er/umn/er_01_0035.html
index 38c5e1e3..4910d8ba 100644
--- a/docs/er/umn/er_01_0035.html
+++ b/docs/er/umn/er_01_0035.html
@@ -3,33 +3,37 @@
Propagation Overview
You can create a propagation for each attachment to propagate routes to one or more route tables on an enterprise router.
If you do not want to create a propagation, you can manually add static routes for attachments to the route tables.
- Figure 1 Propagated routes and static routes
+ Figure 1 Propagated routes and static routes
- Table 1 Propagation descriptionAttachment Type
+Table 1 Propagation descriptionAttachment Type
|
-Propagated Info
+ | Propagated Info
|
-Way to Create Propagation
+ | Way to Create Propagation
|
-Description
+ | Description
|
|---|
-VPC
+ | VPC
|
-VPC CIDR blocks
+ | VPC CIDR blocks
|
-- Auto creation: If Default Route Table Propagation is enabled and the default propagation route table is specified, attachments automatically propagate routes to the default propagation route table.
-
- Manual creation: You can select a route table and create a propagation for an attachment in the route table. For details, see Creating a Propagation for an Attachment in the Route Table.
-
+ | - Auto creation: If Default Route Table Propagation is enabled and the default propagation route table is specified, attachments automatically propagate routes to the default propagation route table.
+
- Manual creation: You can select a route table and create a propagation for an attachment in the route table. For details, see Creating a Propagation for an Attachment in the Route Table.
|
-An attachment can be propagated to different route tables. You can create propagations for attachments in Figure 1 as follows:
-- Auto creation: Propagations are automatically created for the attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments, in the default propagation route table of the enterprise router.
- Manual creation: You need to manually create propagations in the custom route table of the enterprise router for attachments, such as VPC 1, virtual gateway 1, and virtual gateway 2 attachments.
- No propagation: If you do not want to use propagated routes, you need to manually add static routes to the custom route table of the enterprise router for attachments, such as VPC 3 and VPC 4 attachments.
+ | An attachment can be propagated to different route tables. You can create propagations for attachments in Figure 1 as follows:
+- Auto creation: Propagations are automatically created for the attachments, such as virtual gateway 1, VPN gateway 1, and VPC 1 attachments, in the default propagation route table of the enterprise router.
- Manual creation: You need to manually create propagations in the custom route table of the enterprise router for attachments, such as virtual gateway 1, VPC 1, VPN gateway 2, and virtual gateway 2 attachments.
- No propagation: If you do not want to use propagated routes, you need to manually add static routes to the custom route table of the enterprise router for attachments, such as VPC 2 attachment.
|
-Virtual gateway
+ | Virtual gateway
|
-All routes
+ | All routes
+ |
+
+VPN gateway
+ |
+All routes
|
diff --git a/docs/er/umn/er_01_0036.html b/docs/er/umn/er_01_0036.html
index 50233c5b..7bf02b5d 100644
--- a/docs/er/umn/er_01_0036.html
+++ b/docs/er/umn/er_01_0036.html
@@ -5,7 +5,7 @@
NotesYou can create propagations for the same attachment in different route tables.
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Create Propagation
@@ -22,7 +22,7 @@
Attachment Type
|
Mandatory
-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.
+ 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.
- VPN gateway: A VPN gateway is attached to the enterprise router.
For more information, see Attachment Overview.
|
diff --git a/docs/er/umn/er_01_0037.html b/docs/er/umn/er_01_0037.html
index 0e4e49d3..18c436f3 100644
--- a/docs/er/umn/er_01_0037.html
+++ b/docs/er/umn/er_01_0037.html
@@ -3,7 +3,7 @@
Viewing a Propagation in a Route Table
ScenariosThis section describes how to view a propagation in the route table of an enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Viewing a propagation
diff --git a/docs/er/umn/er_01_0038.html b/docs/er/umn/er_01_0038.html
index b7b4532b..f151f6dc 100644
--- a/docs/er/umn/er_01_0038.html
+++ b/docs/er/umn/er_01_0038.html
@@ -5,7 +5,7 @@
Notes and ConstraintsPropagated routes are learned through propagation. Deleting a propagation will also delete the propagated routes.
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Deleting a propagation
diff --git a/docs/er/umn/er_01_0040.html b/docs/er/umn/er_01_0040.html
index f9fdb5d8..5e630f9e 100644
--- a/docs/er/umn/er_01_0040.html
+++ b/docs/er/umn/er_01_0040.html
@@ -3,7 +3,7 @@
Route Overview
What Is a Route?Routes are used to forward packets. A route contains information such as the destination, next hop, and route type.
You can create a propagation for attachments to automatically propagate routes to route tables or manually add static routes to route tables.
- Figure 1 Propagated routes and static routes
+ Figure 1 Propagated routes and static routes
Table 1 Route typesRoute Type
|
@@ -21,8 +21,8 @@
To create a propagation, see Creating a Propagation for an Attachment in the Route Table.
|
-Routes are classified into propagated routes and static routes. The routes shown in Figure 1 are described as follows: - Propagated routes are from:
- Propagations automatically created in the default route table of the enterprise router for attachments, such as VPC 1, VPC 2, and virtual gateway 1 attachments.
- Propagations manually created in the custom route table of the enterprise router for attachments, such as VPC 1, virtual gateway 1, and virtual gateway 2 attachments.
- - Static routes are manually added to the custom route table of the enterprise router for attachments, such as VPC 3 and VPC 4 attachments.
+ Routes are classified into propagated routes and static routes. The routes shown in Figure 1 are described as follows: - Propagated routes are from:
- Propagations automatically created in the default route table of the enterprise router for attachments, such as virtual gateway 1, VPN gateway 1 and VPC 1 attachments.
- Propagations manually created in the custom route table of the enterprise router for attachments, such as virtual gateway 1, VPC 1, VPN gateway 2, and virtual gateway 2 attachments.
+ - Static routes are manually added to the custom route table of the enterprise router for attachments, such as VPC 2 attachment.
|
|
|---|
@@ -38,7 +38,7 @@
Route PriorityIf there are multiple routes with the same destination but different targets in a route table, the route priority is as follows:
- Static route > propagated route for VPC attachment > propagated route for virtual gateway attachment route
+ Static route > Propagated route for VPC attachment > Propagated route for virtual gateway attachment > Propagated route for VPN gateway attachment
 - Static routes are manually configured and the destination of each static route must be unique in a route table.
- Propagated routes are automatically learned by the system and may have the same destination in a route table.
- A static route and a propagated route may have the same destination in a route table.
ScenariosYou can create static routes in a route table of an enterprise router.
Static routes are classified into common routes and blackhole routes. A blackhole route only has a destination and has no next hop. It drops all traffic sent to the specified destination.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Creating a static route
@@ -36,7 +36,7 @@
Attachment Type
|
-- If Blackhole Route is not enabled, you need to configure this parameter.
- If Blackhole Route is enabled, you do not need to configure this parameter.
+ | - If Blackhole Route is not enabled, you need to configure this parameter.
- If Blackhole Route is enabled, you do not need to configure this parameter.
VPC: Create a static route for a VPC attachment.
For more information, see Attachment Overview.
|
diff --git a/docs/er/umn/er_01_0042.html b/docs/er/umn/er_01_0042.html
index 8de031fb..05a21d38 100644
--- a/docs/er/umn/er_01_0042.html
+++ b/docs/er/umn/er_01_0042.html
@@ -7,7 +7,7 @@
Notes and ConstraintsTo change the destination of a static route, delete this static route and create another one with your desired destination.
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Modifying a static route
@@ -32,7 +32,7 @@
Attachment Type
|
- If Blackhole Route is not enabled, you need to configure this parameter.
- If Blackhole Route is enabled, you do not need to configure this parameter.
-VPC: You want to attach a VPC to an enterprise router.
+VPC: A VPC is attached to the enterprise router.
For more information, see Attachment Overview.
|
VPC
@@ -41,7 +41,7 @@
| Next Hop
|
- If Blackhole Route is not enabled, you need to configure this parameter.
- If Blackhole Route is enabled, you do not need to configure this parameter.
-Select the attachment from the drop-down list.
+In the drop-down list, select the target attachment.
|
er-attach-01
|
diff --git a/docs/er/umn/er_01_0043.html b/docs/er/umn/er_01_0043.html
index 245e5c28..4b868a4d 100644
--- a/docs/er/umn/er_01_0043.html
+++ b/docs/er/umn/er_01_0043.html
@@ -3,7 +3,7 @@
Viewing Routes
ScenariosView propagated routes and static routes in a route table of an enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Viewing routes
diff --git a/docs/er/umn/er_01_0044.html b/docs/er/umn/er_01_0044.html
index 365ebf59..3b933975 100644
--- a/docs/er/umn/er_01_0044.html
+++ b/docs/er/umn/er_01_0044.html
@@ -4,7 +4,7 @@
ScenariosDelete a static route from a route table of an enterprise router.
Only static routes can be deleted. To delete a propagated route, you need to delete its propagation. The route will be deleted together with the propagation. For details, see Deleting a Propagation from a Route Table.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Route Tables tab 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.
Figure 2 Deleting a static route
diff --git a/docs/er/umn/er_01_0046.html b/docs/er/umn/er_01_0046.html
index f4f99996..725f7188 100644
--- a/docs/er/umn/er_01_0046.html
+++ b/docs/er/umn/er_01_0046.html
@@ -6,11 +6,13 @@
If your account does not require individual IAM users, skip this topic.
Figure 1 shows the procedure for granting permissions.
PrerequisitesYou 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 Permissions.
- For the permissions of other services, see Permission Description.
+ For the permissions of other services, see Permission Description.
Process FlowFigure 1 Process for granting Enterprise Router permissions
- - Create a user group and assign permissions to it (ER ReadOnlyAccess as an example).
- Create an IAM user and add it to the user group.
- 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.
- 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.
- 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.
+- Create a user group and assign permissions.
Create a user group on the IAM console, and assign the ER ReadOnlyAccess permission to the group.
+ - Create a user and add the user to the user group.
Create a user on the IAM console and add the user to the group created in 1.
+ - 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.
- 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.
- 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.
Enterprise Router Custom Policies
-Custom policies can be created to supplement the system-defined policies of Enterprise Router.
+ Custom policies can be created to supplement system-defined policies of Enterprise Router.
You can create custom policies in either of the following ways:
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
For details about how to create custom policies, see Creating a Custom Policy. The following section contains examples of common Enterprise Router custom policies.
diff --git a/docs/er/umn/er_01_0049.html b/docs/er/umn/er_01_0049.html
index b80102a2..58cda271 100644
--- a/docs/er/umn/er_01_0049.html
+++ b/docs/er/umn/er_01_0049.html
@@ -1,7 +1,7 @@
Overview
- What Is a Tag?Tags are used to identify the cloud resources for purposes of easy categorization and quick search. You can add tags to enterprise routers, attachments, and route tables using either of the methods: - Add tags when you create an enterprise router, attachment, or route table.
- Add tags on the details page of an existing enterprise router, attachment, or route table. You can also edit or delete tags.
+ What Is a Tag?Tags are used to identify cloud resources for purposes of easy categorization and quick search. You can add tags to enterprise routers, attachments, and route tables using either of the methods: - Add tags when you create an enterprise router, attachment, or route table.
- Add tags on the details page of an existing enterprise router, attachment, or route table. You can also edit or delete tags.
Basic Knowledge About TagsTags are used to identify cloud resources. When you have many cloud resources of the same type, you can use tags to classify cloud resources by dimension (for example, use, owner, or environment).
@@ -13,7 +13,7 @@
Tag value - Can be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- - Up to 20 tags can be added to each cloud resource.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
+ - Up to 20 tags can be added to a cloud resource.
- For each resource, each tag key must be unique, and each tag key can only have one tag value.
diff --git a/docs/er/umn/er_01_0058.html b/docs/er/umn/er_01_0058.html
index c8c3b3a0..2c086b21 100644
--- a/docs/er/umn/er_01_0058.html
+++ b/docs/er/umn/er_01_0058.html
@@ -5,7 +5,7 @@
How Do I Apply for a Higher Quota?The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.
Before dialing the hotline number or sending an email, make sure that the following information has been obtained:
- - Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
+- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
- Quota information, which includes:
- Service name
- Quota type
- Required quota
Learn how to obtain the service hotline and email address.
diff --git a/docs/er/umn/er_01_0061.html b/docs/er/umn/er_01_0061.html
index 62aaab4f..957a79dc 100644
--- a/docs/er/umn/er_01_0061.html
+++ b/docs/er/umn/er_01_0061.html
@@ -12,7 +12,7 @@
- Step 3: (Optional) Create VPCs and ECSs
-- Step 4: Create VPC Attachments to the Enterprise Router
+ - Step 4: Create VPC Attachments for the Enterprise Router
- Step 5: (Optional) Add Routes to VPC Route Tables
diff --git a/docs/er/umn/er_01_0062.html b/docs/er/umn/er_01_0062.html
index 20774e25..6d4fc6de 100644
--- a/docs/er/umn/er_01_0062.html
+++ b/docs/er/umn/er_01_0062.html
@@ -43,7 +43,7 @@
4
|
-Step 4: Create VPC Attachments to the Enterprise Router
+ | Step 4: Create VPC Attachments for the Enterprise Router
|
Attach the four VPCs to the enterprise router.
|
@@ -53,7 +53,7 @@
Step 5: (Optional) Add Routes to VPC Route Tables
|
Add routes to the route tables of the VPCs for communication with the enterprise router.
-- If you enable Auto Add Routes when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not need to enable Auto Add Routes. After the attachment is created, manually add routes.
+- If you enable Auto Add Routes when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not enable Auto Add Routes. After the attachment is created, manually add routes.
|
6
diff --git a/docs/er/umn/er_01_0063.html b/docs/er/umn/er_01_0063.html
index 0bf036be..8fc4c965 100644
--- a/docs/er/umn/er_01_0063.html
+++ b/docs/er/umn/er_01_0063.html
@@ -67,27 +67,27 @@
|
Enterprise router
|
-Static route: Custom
+ | Static route (custom)
|
172.16.0.0/12
|
Enterprise Router
|
-Static route: Custom
+ | Static route (custom)
|
192.168.0.0/16
|
Enterprise Router
|
-Static route: Custom
+ | Static route (custom)
|
- - If you enable Auto Add Routes when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not to enable Auto Add Routes. After the attachment is created, manually add routes.
- Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router.
+ - If you enable Auto Add Routes when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not enable Auto Add Routes. After the attachment is created, manually add routes.
- Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router.
Table 4 Enterprise router route tableDestination
@@ -132,7 +132,7 @@
Resource PlanningThe enterprise router, VPCs, and ECSs must be in the same region. You can select any AZ within the region. The following resource details are only examples. You can modify them as required.
- - One enterprise router.
+
- One enterprise router
Table 5 Enterprise router detailsEnterprise Router Name
|
ASN
@@ -176,7 +176,7 @@
|
|---|
- Four VPCs, each with a unique CIDR block.
+
- Four VPCs, each with a unique CIDR block
Table 6 VPC detailsVPC Name
|
VPC CIDR Block
@@ -236,7 +236,7 @@
|
|---|
- Four ECSs in four different VPCs.
+
- An ECS in each VPC, a total of four ECSs
Table 7 ECS detailsECS
|
Image
diff --git a/docs/er/umn/er_01_0064.html b/docs/er/umn/er_01_0064.html
index 63436f81..80bfd685 100644
--- a/docs/er/umn/er_01_0064.html
+++ b/docs/er/umn/er_01_0064.html
@@ -1,9 +1,9 @@
Step 2: Create an Enterprise Router
-ScenariosThis section describes how to create an enterprise router.
+ ScenariosCreate an enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Click Create Enterprise Router in the upper right corner.
The Create Enterprise Router page is displayed.
Figure 1 Create Enterprise Router
- Configure the parameters based on Table 1.
diff --git a/docs/er/umn/er_01_0066.html b/docs/er/umn/er_01_0066.html
index 9f11390c..69dbdd11 100644
--- a/docs/er/umn/er_01_0066.html
+++ b/docs/er/umn/er_01_0066.html
@@ -1,11 +1,11 @@
- Step 4: Create VPC Attachments to the Enterprise Router
+Step 4: Create VPC Attachments for the Enterprise Router
ScenariosThis section describes how to attach the four VPCs to the enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
- Go to the Attachments tab 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, click Create Attachment.
The Create Attachment dialog box is displayed.
+ - On the Attachments tab, click Create Attachment.
The Create Attachment page is displayed.
Figure 1 Create Attachment
- Configure the parameters based on Table 1.
Table 1 Parameter descriptionParameter
@@ -39,7 +39,7 @@
|
|---|
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.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not to enable Auto Add Routes. After the attachment is created, manually add routes.
- Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router.
+ | - If you enable Auto Add Routes when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not enable Auto Add Routes. After the attachment is created, manually add routes.
- Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router.
|
Enable
|
@@ -62,7 +62,7 @@
- Click OK.
The attachment list is displayed.
+ - Click Create Now.
The attachment list is displayed.
- Check the attachment status.
If the status changes from Creating to Normal, the attachment is successfully created.
- Repeat 5 to 9 to attach the other three VPCs to the enterprise router.
 In the example given, Default Route Table Association and Default Route Table Propagation are enabled when you create the enterprise router. After the VPCs are attached to the enterprise router, the system will automatically: - Associate VPC attachments with the route table of the enterprise router.
- Propagate VPC attachments to the route table of the enterprise router. The CIDR blocks of the VPCs are propagated to the route table.
diff --git a/docs/er/umn/er_01_0067.html b/docs/er/umn/er_01_0067.html
index 045561f9..189f89ff 100644
--- a/docs/er/umn/er_01_0067.html
+++ b/docs/er/umn/er_01_0067.html
@@ -2,12 +2,12 @@
Step 5: (Optional) Add Routes to VPC Route Tables
ScenariosThis section describes how to add routes to VPC route tables for traffic to route through the enterprise router.
- - If you enable Auto Add Routes when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not need to enable Auto Add Routes. After the attachment is created, manually add routes.
+ - If you enable Auto Add Routes when creating a VPC attachment, you do not need to manually add static routes to the VPC route table. Instead, the system automatically adds routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the VPC.
- If an existing route in the VPC route tables has a destination to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16, the routes will fail to be added. In this case, do not enable Auto Add Routes. After the attachment is created, manually add routes.
Notes and Constraints- If your VPC only has a default route table, all subnets in it are associated with the default route table. You only need to add routes to the default route table for traffic to route through the enterprise router.
- If your VPC has multiple custom route tables and different subnets in the VPC are associated with different route tables, you need to add routes to each route table associated with the subnets for traffic to route through the enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Attachments tab 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.
- Locate the target attachment and click the VPC in the Attached Resource column.
The VPC basic information page is displayed.
diff --git a/docs/er/umn/er_01_0068.html b/docs/er/umn/er_01_0068.html
index 1c58b33a..88cdd962 100644
--- a/docs/er/umn/er_01_0068.html
+++ b/docs/er/umn/er_01_0068.html
@@ -3,7 +3,7 @@
Step 6: Verify Connectivity Among VPCs
ScenariosThis section describes how to log in to ECSs and verify the connectivity between VPCs.
- Procedure- Log in to the ECS.
- Run the following command on the ECS:
ping IP address of the ECS
+Procedure- Log in to an ECS.
- Run the following command on the ECS:
ping IP address of the ECS
If you log in to ecs-demo-01 to verify the connectivity between vpc-demo-01 and vpc-demo-02, run the following command:
ping 10.1.1.105
If information similar to the following is displayed, the two VPCs can communicate with each other.
diff --git a/docs/er/umn/er_01_0069.html b/docs/er/umn/er_01_0069.html
index acc21fe0..0bd17f96 100644
--- a/docs/er/umn/er_01_0069.html
+++ b/docs/er/umn/er_01_0069.html
@@ -1,9 +1,9 @@
Creating an Enterprise Router
-ScenariosThis section describes how to create an enterprise router.
+ ScenariosCreate an enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Click Create Enterprise Router in the upper right corner.
The Create Enterprise Router page is displayed.
Figure 1 Create Enterprise Router
- Configure the parameters based on Table 1.
diff --git a/docs/er/umn/er_01_0070.html b/docs/er/umn/er_01_0070.html
index 509e872a..f6dbd8b8 100644
--- a/docs/er/umn/er_01_0070.html
+++ b/docs/er/umn/er_01_0070.html
@@ -5,10 +5,10 @@
Notes and Constraints- If you use the propagated routes of a VPC attachment, the route table of the enterprise router automatically learns the VPC CIDR block as the destination of routes. The CIDR block cannot be changed. To ensure that routes in the route table do not conflict, the CIDR blocks of all VPCs attached to the enterprise router cannot overlap. Otherwise, communication fails.
- If your existing VPCs have overlapping CIDR blocks, do not use propagated routes. Instead, manually add static routes to the route table of the enterprise router. The destination of the routes can be VPC subnet CIDR blocks or smaller ones.
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Attachments tab 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, click Create Attachment.
The Create Attachment dialog box is displayed.
+ - On the Attachments tab, click Create Attachment.
The Create Attachment page is displayed.
Figure 2 Create Attachment
- Configure the parameters based on Table 1.
Table 1 Parameters for adding a VPC attachmentParameter
@@ -22,7 +22,7 @@
|
|---|
Name
|
Mandatory
-Enter the attachment name. The name: - Must contain 1 to 64 characters.
- Can contain letters, digits, underscores (_), hyphens (-), and periods (.).
+ Enter an attachment name. The name: - Must contain 1 to 64 characters.
- Can contain letters, digits, underscores (_), hyphens (-), and periods (.).
|
er-attach-01
@@ -49,7 +49,7 @@
| Auto Add Routes
|
Optional
-- Enable this option if you want to automatically add routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the selected VPC.
- Do not enable this option if an existing route in the VPC route tables has a destination set to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 because the routes will fail to be added. After the attachment is created, manually Step 5: (Optional) Add Routes to VPC Route Tables.
+- Enable this option if you want to automatically add routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the selected VPC.
- Do not enable this option if an existing route in the VPC route tables has a destination set to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 because the routes will fail to be added. After the attachment is created, manually add routes to the VPC route tables. For details, see Step 5: (Optional) Add Routes to VPC Route Tables.
NOTE: This parameter is only displayed when a VPC attachment is created. It cannot be enabled after the VPC attachment is created.
|
@@ -77,7 +77,7 @@
- Click OK.
The attachment list is displayed.
+ - Click Create Now.
The attachment list is displayed.
- Check the attachment status.
If the status changes from Creating to Normal, the attachment is successfully created.
Selecting an AZWhen deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
Regions and EndpointsBefore you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+ Regions and EndpointsBefore you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
diff --git a/docs/er/umn/er_01_0072.html b/docs/er/umn/er_01_0072.html
index fb17a039..7ad4e91d 100644
--- a/docs/er/umn/er_01_0072.html
+++ b/docs/er/umn/er_01_0072.html
@@ -3,13 +3,13 @@
Deleting a VPC Attachment
ScenariosThis 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.
- If flow logging is enabled for an attachment, flow logging will be disabled, but collected flow logs will not be deleted.
+ Notes and Constraints- Deleting a VPC attachment will also delete its associations, propagations, and propagated routes in the route table.
- If a VPC 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 a VPC attachment, flow logging will be disabled, but collected flow logs will not be deleted.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Attachments tab 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 target VPC attachment, and click Delete in the Operation column.
A confirmation dialog box is displayed.
- - Confirm the information and click Yes.
A deleted attachment cannot be recovered.
+ - Confirm the information and click Yes.
A deleted attachment cannot be recovered.
diff --git a/docs/er/umn/er_01_0073.html b/docs/er/umn/er_01_0073.html
index 14dd24f3..a5730544 100644
--- a/docs/er/umn/er_01_0073.html
+++ b/docs/er/umn/er_01_0073.html
@@ -3,10 +3,10 @@
Deleting a Virtual Gateway Attachment
ScenariosThis 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.
- - If flow logging is enabled for an attachment, flow logging will be disabled, but collected flow logs will not be deleted.
+ Notes and Constraints- Deleting a VPC attachment will also delete its associations, propagations, and propagated routes in the route table.
+ - If flow logging is enabled for a VPC attachment, flow logging will be disabled, but collected flow logs will not be deleted.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Go to the Attachments tab 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.
A virtual gateway attachment cannot be directly deleted on the Attachments tab.
@@ -18,7 +18,8 @@
- Check whether the virtual gateway has virtual interfaces.
- Locate 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.
+Figure 2 Deleting a virtual gateway
+ - Confirm the information and click Yes.
A deleted virtual gateway cannot be recovered.
diff --git a/docs/er/umn/er_01_0075.html b/docs/er/umn/er_01_0075.html
index 1c35dd11..3ef4c5bf 100644
--- a/docs/er/umn/er_01_0075.html
+++ b/docs/er/umn/er_01_0075.html
@@ -3,12 +3,12 @@
Adding a Tag to an Enterprise Router
ScenariosAdd a tag to an existing enterprise router.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Click the enterprise router name and click Tags.
The tag list is displayed.
Figure 2 Adding a tag to an enterprise router
- Click Add Tag.
The Add Tag dialog box is displayed.
- - Set the tag key and tag value as prompted, and click OK.
View the added tag in the tag list.
+ - Set the tag key and tag value as prompted and click OK.
View the added tag in the tag list.
diff --git a/docs/er/umn/er_01_0076.html b/docs/er/umn/er_01_0076.html
index 6bb0091e..be02f240 100644
--- a/docs/er/umn/er_01_0076.html
+++ b/docs/er/umn/er_01_0076.html
@@ -3,14 +3,14 @@
Adding a Tag to an Attachment
ScenariosAdd a tag to an existing attachment.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Click the enterprise router name and click Attachments.
The attachment list is displayed.
Figure 2 Viewing attachments
- Locate the attachment that you want to add a tag to and click its name.
The attachment details page is displayed.
Figure 3 Adding a tag to an attachment
- Click Add Tag.
The Add Tag dialog box is displayed.
- - Set the tag key and tag value as prompted, and click OK.
View the added tag in the tag list.
+ - Set the tag key and tag value as prompted and click OK.
View the added tag in the tag list.
diff --git a/docs/er/umn/er_01_0077.html b/docs/er/umn/er_01_0077.html
index 217b2e22..7eef71e8 100644
--- a/docs/er/umn/er_01_0077.html
+++ b/docs/er/umn/er_01_0077.html
@@ -3,12 +3,12 @@
Adding a Tag to a Route Table
ScenariosAdd a tag to an existing route table.
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Click the enterprise router name and click Route Tables.
The route table list is displayed.
Figure 2 Adding a tag to a route table
- Locate the route table to which you want to add a tag. On the Tags tab, click Add Tag in the right pane.
The Add Tag dialog box is displayed.
- - Set the tag key and tag value as prompted, and click OK.
View the added tag in the tag list.
+ - Set the tag key and tag value as prompted and click OK.
View the added tag in the tag list.
diff --git a/docs/er/umn/er_01_0078.html b/docs/er/umn/er_01_0078.html
index 2a7c179c..bac03aed 100644
--- a/docs/er/umn/er_01_0078.html
+++ b/docs/er/umn/er_01_0078.html
@@ -5,7 +5,7 @@
- Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Click the enterprise router name and click Tags.
The tag list is displayed.
Figure 2 Modifying an enterprise router tag
diff --git a/docs/er/umn/er_01_0079.html b/docs/er/umn/er_01_0079.html
index f0b531f3..f678e17d 100644
--- a/docs/er/umn/er_01_0079.html
+++ b/docs/er/umn/er_01_0079.html
@@ -5,7 +5,7 @@
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Click the enterprise router name and click Attachments.
The attachment list is displayed.
Figure 2 Viewing attachments
diff --git a/docs/er/umn/er_01_0080.html b/docs/er/umn/er_01_0080.html
index 85e23b15..602b5e65 100644
--- a/docs/er/umn/er_01_0080.html
+++ b/docs/er/umn/er_01_0080.html
@@ -5,7 +5,7 @@
Procedure- Log in to the management console.
- Click 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.
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router page is displayed.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
- Click the enterprise router name and click Route Tables.
The route table list is displayed.
Figure 2 Modifying a route table tag
diff --git a/docs/er/umn/er_01_0081.html b/docs/er/umn/er_01_0081.html
index a63860a5..ad1c06ed 100644
--- a/docs/er/umn/er_01_0081.html
+++ b/docs/er/umn/er_01_0081.html
@@ -3,9 +3,9 @@
Searching for an Enterprise Router by Tag
ScenariosSearch for an enterprise router using a tag added to that enterprise router.
-
|
|---|
|
|---|
|
|---|
|
|---|
|---|
|
|---|
| |
|---|
|---|
|
|---|
|
|---|
|
