2024-09-18
|
Modified the following content:
Modified the figure name of scheme 1 in Selecting a Networking Scheme.
diff --git a/docs/er/umn/en-us_image_0000001764265877.png b/docs/er/umn/en-us_image_0000001764265877.png
deleted file mode 100644
index ddcd5b21..00000000
Binary files a/docs/er/umn/en-us_image_0000001764265877.png and /dev/null differ
diff --git a/docs/er/umn/en-us_image_0000002074955185.png b/docs/er/umn/en-us_image_0000002074955185.png
new file mode 100644
index 00000000..0a18df80
Binary files /dev/null and b/docs/er/umn/en-us_image_0000002074955185.png differ
diff --git a/docs/er/umn/er_01_0002.html b/docs/er/umn/er_01_0002.html
index a2ab5e26..188f8629 100644
--- a/docs/er/umn/er_01_0002.html
+++ b/docs/er/umn/er_01_0002.html
@@ -1,7 +1,7 @@
What Is an Enterprise Router?
-An enterprise router connects virtual private clouds (VPCs) and on-premises networks to build a central hub network. It has high specifications, provides high bandwidth, and delivers high performance. Enterprise routers use the Border Gateway Protocol (BGP) to learn, dynamically select, or switch between routes, thereby ensuring the service continuity and significantly improving network scalability and O&M efficiency.
+ An enterprise router connects VPCs and on-premises networks to build a central hub network. It has high specifications, provides high bandwidth, and delivers high performance. Enterprise routers use the Border Gateway Protocol (BGP) to learn, dynamically select, or switch between routes, thereby ensuring the service continuity and significantly improving network scalability and O&M efficiency.
Figure 1 and Figure 2 show the networks with and without enterprise routers, respectively. Table 1 compares the two networks. Figure 1 A network without enterprise routers
Figure 2 A network with enterprise routers
diff --git a/docs/er/umn/er_01_0005.html b/docs/er/umn/er_01_0005.html
index e7f08688..9bc2f7aa 100644
--- a/docs/er/umn/er_01_0005.html
+++ b/docs/er/umn/er_01_0005.html
@@ -4,7 +4,7 @@
An enterprise router provides the functions listed in Table 1, allowing you to: - Manage attachments, custom route tables, associations, propagations, and routes.
- Manage permissions, tags, and quota to improve service security.
- Table 1 Functions of an enterprise routerFunction
+Table 1 Enterprise router functionsFunction
|
Description
|
diff --git a/docs/er/umn/er_01_0006.html b/docs/er/umn/er_01_0006.html
index a9d29043..11559d78 100644
--- a/docs/er/umn/er_01_0006.html
+++ b/docs/er/umn/er_01_0006.html
@@ -29,7 +29,7 @@
|---|
Constraints- Enterprise routers cannot be used together with virtual IP addresses of VPCs. If virtual IP addresses are used, contact customer service.
- Traffic cannot be forwarded from a VPC to the enterprise router that it attached to if you set the destination of a route whose next hop is the enterprise router to 0.0.0.0/0 in the VPC route table and if:
- An ECS in the VPC has an EIP bound.
- The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or Distributed Cache Service (DCS).
+Constraints
diff --git a/docs/er/umn/er_01_0011.html b/docs/er/umn/er_01_0011.html
index 77a31bd6..6a45d4b2 100644
--- a/docs/er/umn/er_01_0011.html
+++ b/docs/er/umn/er_01_0011.html
@@ -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
- VPN gateway attachment: VPN 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
|
|
|---|
@@ -68,7 +68,7 @@
- AttachmentsIf you want to attach a network instance to an enterprise router, you need to add an attachment of a specific type to the enterprise router. The attachment type varies according to the network instance, as listed in Table 3.
+ AttachmentsIf you want to attach a network instance to an enterprise router, you need to add an attachment of a specific type to the enterprise router. The attachment type varies by type of the network instance, as listed in Table 3.
Table 3 AttachmentsAttachment Type
|
diff --git a/docs/er/umn/er_01_0013.html b/docs/er/umn/er_01_0013.html
index b86ffcdd..117aa70a 100644
--- a/docs/er/umn/er_01_0013.html
+++ b/docs/er/umn/er_01_0013.html
@@ -39,7 +39,7 @@
Optional
If you enable Default Route Table Association, select a route table for Association Route Table.
- |
er-rtb-b931
@@ -58,7 +58,7 @@
|
Optional
If you enable Default Route Table Propagation, select a route table for Propagation Route Table.
- |
er-rtb-b931
@@ -67,7 +67,7 @@
|
|---|
Auto Accept Shared Attachments
|
Optional
-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.
+ 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 attachments from the accounts that this enterprise router is shared with will be automatically accepted.
For details, see Sharing Overview.
|
diff --git a/docs/er/umn/er_01_0022.html b/docs/er/umn/er_01_0022.html
new file mode 100644
index 00000000..e12472b8
--- /dev/null
+++ b/docs/er/umn/er_01_0022.html
@@ -0,0 +1,17 @@
+
+
+
+ Monitoring and Auditing
+
+
+
+
+
diff --git a/docs/er/umn/er_01_0057.html b/docs/er/umn/er_01_0057.html
index 11360e14..6a0a113f 100644
--- a/docs/er/umn/er_01_0057.html
+++ b/docs/er/umn/er_01_0057.html
@@ -4,7 +4,7 @@
ScenariosThe following provides operations for you to view the quotas of enterprise routers and related resources in your account.
diff --git a/docs/er/umn/er_01_0062.html b/docs/er/umn/er_01_0062.html
index 6d4fc6de..6590b5ce 100644
--- a/docs/er/umn/er_01_0062.html
+++ b/docs/er/umn/er_01_0062.html
@@ -1,7 +1,7 @@
Overview
- BackgroundFour VPCs are created in region A on the public cloud and they need to communicate with each other.
+ SolutionFour VPCs are created in region A on the public cloud and they need to communicate with each other.
You can create an enterprise router in region A and attach the four VPCs to the enterprise router. The enterprise router can route traffic among the VPCs so that they can communicate with each other.
Figure 1 Communications among VPCs in the same region
 This document describes how to use an enterprise router to quickly allow multiple VPCs in the same region to communicate with each other.
@@ -11,56 +11,42 @@
ProcedureFigure 2 shows the procedure for using an enterprise router to allow multiple VPCs in the same region to communicate with each other.
Figure 2 Flowchart for connecting VPCs in the same region
- Table 1 Steps for connecting VPCs in the same regionNo.
+Table 1 Steps for connecting VPCs in the same regionStep
|
-Step
- |
-Description
+ | Description
|
|---|
-1
+ | Step 1: Plan Networks and Resources
|
-Step 1: Plan Networks and Resources
- |
-Plan CIDR blocks and the number of resources.
+ | Plan CIDR blocks and the number of resources.
|
-2
+ | Step 2: Create an Enterprise Router
|
-Step 2: Create an Enterprise Router
- |
-Create one enterprise router for connecting VPCs in the same region.
+ | Create one enterprise router for connecting VPCs in the same region.
|
-3
+ | Step 3: (Optional) Create VPCs and ECSs
|
-Step 3: (Optional) Create VPCs and ECSs
- |
-Create four VPCs and four ECSs. You can change the resource quantity and specifications as needed.
+ | Create four VPCs and four ECSs. You can change the resource quantity and specifications as needed.
If you already have these resources, skip this step.
|
-4
+ | Step 4: Create VPC Attachments for the Enterprise Router
|
-Step 4: Create VPC Attachments for the Enterprise Router
- |
-Attach the four VPCs to the enterprise router.
+ | Attach the four VPCs to the enterprise router.
|
-5
+ | Step 5: (Optional) Add Routes to VPC Route Tables
|
-Step 5: (Optional) Add Routes to VPC Route Tables
- |
-Add routes to the route tables of the VPCs for communication with the enterprise router.
+ | 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 enable Auto Add Routes. After the attachment is created, manually add routes.
|
-6
+ | Step 6: Verify Connectivity Among VPCs
|
-Step 6: Verify Connectivity Among VPCs
- |
-Log in to the ECS and run the ping command to verify the connectivity among VPCs.
+ | Log in to the ECS and run the ping command to verify the connectivity among VPCs.
|
diff --git a/docs/er/umn/er_01_0064.html b/docs/er/umn/er_01_0064.html
index 80bfd685..f053c1d3 100644
--- a/docs/er/umn/er_01_0064.html
+++ b/docs/er/umn/er_01_0064.html
@@ -1,8 +1,7 @@
Step 2: Create an Enterprise Router
-ScenariosCreate an enterprise router.
-
+ To connect VPCs in the same region, you only need to create one enterprise router. Perform the following operations to create 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 page is displayed.
- Click Create Enterprise Router in the upper right corner.
The Create Enterprise Router page is displayed.
Figure 1 Create Enterprise Router
@@ -15,7 +14,7 @@
-Region
+ | Region
|
Select the region nearest to your target users. Once the enterprise router is created, the region cannot be changed.
|
diff --git a/docs/er/umn/er_01_0065.html b/docs/er/umn/er_01_0065.html
index 1ca4f7bc..81e95d85 100644
--- a/docs/er/umn/er_01_0065.html
+++ b/docs/er/umn/er_01_0065.html
@@ -1,9 +1,7 @@
Step 3: (Optional) Create VPCs and ECSs
-ScenariosThis section describes how to create VPCs and ECSs.
- If you already have VPCs and ECS, skip this section.
-
+ Perform the following operations to create VPCs and ECSs. If you already have VPCs and ECS, skip this step.
Notes and Constraints- The CIDR blocks of the VPCs to be connected cannot overlap with each other.
In this example, the CIDR blocks of the VPCs are propagated to the enterprise router route table as the destination in routes. The CIDR blocks cannot be modified and overlapping CIDR blocks may cause route conflicts.
If your existing VPCs have overlapping CIDR blocks, do not use propagated routes. Instead, you need to manually add static routes to the route table of the enterprise router. The destination can be VPC subnet CIDR blocks or smaller ones.
- Four ECSs must be in the same security group. If your ECSs are in different security groups, add rules to their security groups to allow access to each other.
diff --git a/docs/er/umn/er_01_0066.html b/docs/er/umn/er_01_0066.html
index 69dbdd11..c179353f 100644
--- a/docs/er/umn/er_01_0066.html
+++ b/docs/er/umn/er_01_0066.html
@@ -1,8 +1,7 @@
Step 4: Create VPC Attachments for the Enterprise Router
- ScenariosThis section describes how to attach the four VPCs to the enterprise router.
-
+ Perform the following operations 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 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 page is displayed.
diff --git a/docs/er/umn/er_01_0067.html b/docs/er/umn/er_01_0067.html
index 189f89ff..95b526c1 100644
--- a/docs/er/umn/er_01_0067.html
+++ b/docs/er/umn/er_01_0067.html
@@ -1,10 +1,9 @@
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.
+ Perform the following operations to configure the routes for the enterprise router in the VPC route table:
- 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 page is displayed.
@@ -15,48 +14,48 @@
- Locate the target subnet and click the route table name in the Route Table column.
The route table details page is displayed.
- Under Routes, click Add Route.
The Add Route dialog box is displayed.
- Configure the parameters based on Table 1.
- Table 1 Parameter descriptionParameter
+Table 1 Parameter descriptionParameter
|
-Setting
+ | Setting
|
-Example Value
+ | Example Value
|
|---|
-Destination Type
+ | Destination Type
|
-The destination can only be IP address. You can set a single IP address or network segment.
+ | The destination can only be IP address. You can set a single IP address or network segment.
|
-IP address
+ | IP address
|
-Destination
+ | Destination
|
-The destination is used to route traffic from this VPC to other VPCs attached to the enterprise router. You can change it after the route is created.
+ | The destination is used to route traffic from this VPC to other VPCs attached to the enterprise router. You can change it after the route is created.
- Set the destination to the CIDR blocks of VPCs or their subnets that your VPC need to communicate with.
- 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.
|
-10.0.0.0/8
+ | 10.0.0.0/8
|
-Next Hop Type
+ | Next Hop Type
|
-Select Enterprise Router. You can change it after the route is created.
+ | Select Enterprise Router. You can change it after the route is created.
|
-Enterprise Router
+ | Enterprise Router
|
-Next Hop
+ | Next Hop
|
-Select the target enterprise router. You can change it after the route is created.
+ | Select the target enterprise router. You can change it after the route is created.
|
-er-test-01
+ | er-test-01
|
-Description
+ | Description
|
-Provide supplementary information about the route. You can change the route after it is created.
+ | Provide supplementary information about the route. You can change the route after it is created.
|
--
+ | -
|
diff --git a/docs/er/umn/er_01_0068.html b/docs/er/umn/er_01_0068.html
index 88cdd962..d59ce575 100644
--- a/docs/er/umn/er_01_0068.html
+++ b/docs/er/umn/er_01_0068.html
@@ -1,8 +1,7 @@
Step 6: Verify Connectivity Among VPCs
-ScenariosThis section describes how to log in to ECSs and verify the connectivity between VPCs.
-
+ Perform the following operations to log in to each ECS and verify the network connectivity between VPCs:
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
diff --git a/docs/er/umn/er_01_0069.html b/docs/er/umn/er_01_0069.html
index 0bd17f96..da8d7bfb 100644
--- a/docs/er/umn/er_01_0069.html
+++ b/docs/er/umn/er_01_0069.html
@@ -15,7 +15,7 @@
-Region
+ | Region
|
Mandatory
Select the region nearest to you to ensure the lowest latency possible.
@@ -81,7 +81,7 @@
| Auto Accept Shared Attachments
|
Optional
-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.
+ 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 attachments from the accounts that this enterprise router is shared with will be automatically accepted.
For details, see Sharing Overview.
|
@@ -92,7 +92,7 @@
Mandatory
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.
+An enterprise project facilitates project-level management and grouping of cloud resources and users. The default project is default.
|
default
|
diff --git a/docs/er/umn/er_01_0090.html b/docs/er/umn/er_01_0090.html
index edba597c..8b1025e6 100644
--- a/docs/er/umn/er_01_0090.html
+++ b/docs/er/umn/er_01_0090.html
@@ -1,7 +1,7 @@
- Interconnecting with CTS
+ CTS Auditing
@@ -13,5 +13,9 @@
- Viewing Traces
+
+
diff --git a/docs/er/umn/er_01_0091.html b/docs/er/umn/er_01_0091.html
index adc7439d..730ea007 100644
--- a/docs/er/umn/er_01_0091.html
+++ b/docs/er/umn/er_01_0091.html
@@ -186,7 +186,7 @@
diff --git a/docs/er/umn/er_01_0092.html b/docs/er/umn/er_01_0092.html
index 972e4bbf..d4634307 100644
--- a/docs/er/umn/er_01_0092.html
+++ b/docs/er/umn/er_01_0092.html
@@ -16,7 +16,7 @@
diff --git a/docs/er/umn/er_01_0102.html b/docs/er/umn/er_01_0102.html
index 8abfc56f..a28a612f 100644
--- a/docs/er/umn/er_01_0102.html
+++ b/docs/er/umn/er_01_0102.html
@@ -1,7 +1,7 @@
- Monitoring
+ Cloud Eye Monitoring
@@ -15,5 +15,9 @@
- Creating Alarm Rules
+
+
diff --git a/docs/er/umn/er_01_0103.html b/docs/er/umn/er_01_0103.html
index e3cc9bdc..7c0a66fc 100644
--- a/docs/er/umn/er_01_0103.html
+++ b/docs/er/umn/er_01_0103.html
@@ -307,7 +307,7 @@
diff --git a/docs/er/umn/er_01_0104.html b/docs/er/umn/er_01_0104.html
index f46e1954..90ce89de 100644
--- a/docs/er/umn/er_01_0104.html
+++ b/docs/er/umn/er_01_0104.html
@@ -15,7 +15,7 @@
diff --git a/docs/er/umn/er_01_0105.html b/docs/er/umn/er_01_0105.html
index d543c0d2..2cb4514c 100644
--- a/docs/er/umn/er_01_0105.html
+++ b/docs/er/umn/er_01_0105.html
@@ -17,7 +17,7 @@
diff --git a/docs/er/umn/er_01_0121.html b/docs/er/umn/er_01_0121.html
index ba4081c8..3895f374 100644
--- a/docs/er/umn/er_01_0121.html
+++ b/docs/er/umn/er_01_0121.html
@@ -1,7 +1,7 @@
Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0 to Its Enterprise Router?
-ScenariosTraffic cannot be forwarded from a VPC to the enterprise router that it is attached to if you set the destination of a route in the VPC route table to 0.0.0.0/0 and: - An ECS in the VPC has an EIP bound.
Refer to solution 1.
+ ScenariosTraffic cannot be forwarded from a VPC to the enterprise router that the VPC is attached to if you set the destination of a route to 0.0.0.0/0 in the VPC route table and: - An ECS in the VPC has an EIP bound.
- ELB, NAT Gateway, VPC Endpoint and DCS are deployed in the VPC.
Refer to solution 1 or solution 2.
When method 2 is used, if a VPC wants to access public network, the traffic from the VPC is forwarded to the enterprise router and then to the public network. For this reason, if a VPC accesses the public network using an EIP, do not use this method.
diff --git a/docs/er/umn/er_01_0129.html b/docs/er/umn/er_01_0129.html
index cd7a0ab5..45ae6056 100644
--- a/docs/er/umn/er_01_0129.html
+++ b/docs/er/umn/er_01_0129.html
@@ -29,14 +29,14 @@
In Figure 2:
The two service VPCs (VPC-A and VPC-B) are not attached to the enterprise router. Instead, a transit VPC (VPC-Transit) is used. The transit VPC and the Direct Connect virtual gateway are attached to the enterprise router.
|
- - Each service VPC is connected to the transit VPC over a VPC peering connection.
- Direct Connect enables the on-premises data center to access the cloud, and the enterprise router connects the on-premises data center to the two service VPCs.
+ | - Each service VPC is connected to the transit VPC over a VPC peering connection.
- Direct Connect enables the on-premises data center to access the cloud, and the enterprise router connects the on-premises data center to the two service VPCs.
|
How Do I Select a Networking Scheme?In scheme 1, the service VPCs are directly attached to the enterprise router. In scheme 2, a transit VPC is used and attached to the enterprise router. Each service VPC is connected to the transit VPC over a VPC peering connection. Compared with scheme 1, scheme 2 costs less and eliminates some constraints, as detailed below: - Scheme 2 frees you from the following constraints that scheme 1 has on attaching service VPCs to an enterprise router:
- If a service VPC is used by ELB, VPC Endpoint, NAT Gateway (private NAT gateways), or DCS, contact customer service to confirm the service compatibility and preferentially use a transit VPC for networking.
- Traffic cannot be forwarded from a VPC to the enterprise router if you set the destination of a route in the VPC route table to 0.0.0.0/0 and:
- An ECS in the VPC has an EIP bound.
- The VPC is being used by ELB (either dedicated or shared load balancers), NAT Gateway, VPC Endpoint, and DCS.
+How Do I Select a Networking Scheme?In scheme 1, the service VPCs are directly attached to the enterprise router. In scheme 2, a transit VPC is used and attached to the enterprise router. Each service VPC is connected to the transit VPC over a VPC peering connection. Compared with scheme 1, scheme 2 costs less and eliminates some constraints, as detailed below: - Scheme 2 frees you from the following constraints that scheme 1 has on attaching service VPCs to an enterprise router:
- If a service VPC is used by ELB, VPC Endpoint, NAT Gateway (private NAT gateways), or DCS, contact customer service to confirm the service compatibility and preferentially use a transit VPC for networking.
- Traffic cannot be forwarded from a VPC to the enterprise router if you set the destination of a route to 0.0.0.0/0 in the VPC route table and:
- An ECS in the VPC has an EIP bound.
- The VPC is being used by ELB (either dedicated or shared load balancers), NAT Gateway, VPC Endpoint, and DCS.
|
|---|
|
|---|
|
