2023-11-21
|
Modified the following content:
Added a screenshot in Viewing Quotas.
diff --git a/docs/er/umn/er_01_0004.html b/docs/er/umn/er_01_0004.html
index 29986b5a..3091020f 100644
--- a/docs/er/umn/er_01_0004.html
+++ b/docs/er/umn/er_01_0004.html
@@ -7,7 +7,7 @@
Table 1 Using enterprise routers in scenario 1Customer Requirements
|
-Multiple service networks communicate or do not communicate with each other on the cloud but communicate with the on-premises data center. For example, an enterprise requires three VPCs for running their workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 and the on-premises data center.
+ | Multiple service networks communicate or do not communicate with each other on the cloud but communicate with the on-premises data center. Suppose you require three VPCs for running the workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 and your on-premises data center.
|
|---|
Pain Points
diff --git a/docs/er/umn/er_01_0005.html b/docs/er/umn/er_01_0005.html
index 2d3f8b62..0a3c33cb 100644
--- a/docs/er/umn/er_01_0005.html
+++ b/docs/er/umn/er_01_0005.html
@@ -22,8 +22,8 @@
|
|---|
Attachments
|
-You can add attachments to attach network instances to the enterprise router.
-Different network instances are attached through different consoles. - VPCs are attached through the Enterprise Router console.
- Virtual gateways are attached through the Direct Connect console.
+ You can attach network instances to the enterprise router.
+Network instances are attached to the enterprise router in different ways. - VPCs are attached to the enterprise router on the Enterprise Router console.
- Virtual gateways are attached through the Direct Connect console.
|
Attachment Overview
diff --git a/docs/er/umn/er_01_0011.html b/docs/er/umn/er_01_0011.html
index d53f9cd1..410e467a 100644
--- a/docs/er/umn/er_01_0011.html
+++ b/docs/er/umn/er_01_0011.html
@@ -2,11 +2,11 @@
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.
- Currently, enterprise routers support the following attachments: - VPC attachment: Attach VPCs from the same region as that of an enterprise router to the router.
- Virtual gateway attachment: Attach Direct Connect virtual gateways from the same region as that of an enterprise router to the router.
+ 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.
Figure 1 Processing of using an enterprise router
- The following describes how an enterprise router works.
- Figure 2 How an enterprise router works
+ 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.
|
@@ -39,35 +39,30 @@
|---|
- Table 2 Working principles of an enterprise routerNo.
+Table 2 Working principles of an enterprise routerNo.
|
-Action
+ | Action
|
-Description
+ | Description
|
|---|
-1
+ | 1
|
-Add attachments to the enterprise router.
+ | 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
-
+ Attach network instances to enterprise router 1 in region A.
+Network instances from the same region - VPC attachments: VPC 1, VPC 2, and VPC 3
- Virtual gateway attachment: Virtual gateway
|
|
-2
+ | 2
|
-Associate the attachments with the route tables of the enterprise router.
-Each attachment can only be associated with one route table.
+ | - Associate the attachments with the route tables of the enterprise router.
Each attachment can only be associated with one route table.
+ - 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.
- |
-
-3
- |
-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.
|
diff --git a/docs/er/umn/er_01_0016.html b/docs/er/umn/er_01_0016.html
index 8202acd1..7b395956 100644
--- a/docs/er/umn/er_01_0016.html
+++ b/docs/er/umn/er_01_0016.html
@@ -3,7 +3,7 @@
Viewing an Enterprise Router
ScenariosThis section describes how to view basic information about an enterprise router, including the AZs, default route table association and propagation, and creation time.
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.
- 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.
diff --git a/docs/er/umn/er_01_0017.html b/docs/er/umn/er_01_0017.html
index 286cb4f8..22a219be 100644
--- a/docs/er/umn/er_01_0017.html
+++ b/docs/er/umn/er_01_0017.html
@@ -3,7 +3,7 @@
Deleting an Enterprise Router
ScenariosThis section describes how to delete an enterprise router.
- Notes and Constraints- An enterprise router that has attachments cannot be deleted. To delete such an enterprise router, delete its attachments first. For details, see Deleting an Attachment.
- 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.
+ 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.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
diff --git a/docs/er/umn/er_01_0018.html b/docs/er/umn/er_01_0018.html
index 2be305a5..bb072f3e 100644
--- a/docs/er/umn/er_01_0018.html
+++ b/docs/er/umn/er_01_0018.html
@@ -10,13 +10,13 @@
diff --git a/docs/er/umn/er_01_0019.html b/docs/er/umn/er_01_0019.html
index a116bbde..2ca7354e 100644
--- a/docs/er/umn/er_01_0019.html
+++ b/docs/er/umn/er_01_0019.html
@@ -19,9 +19,9 @@
VPC
|
- Adding VPC Attachments to an Enterprise Router
+ | Creating a VPC Attachment
|
- Viewing Details About an Attachment
+ | Viewing an Attachment
|
Deleting a VPC Attachment
@@ -31,7 +31,7 @@
|
Virtual gateway of Direct Connect
|
- Attach a virtual gateway to an enterprise router. For details, see Connecting Your On-Premises Data Center to the Cloud.
+ | Creating a Virtual Gateway Attachment
|
Deleting a Virtual Gateway Attachment
|
diff --git a/docs/er/umn/er_01_0021.html b/docs/er/umn/er_01_0021.html
index 051445e7..4fcf0ea9 100644
--- a/docs/er/umn/er_01_0021.html
+++ b/docs/er/umn/er_01_0021.html
@@ -1,6 +1,6 @@
- Viewing Details About an Attachment
+ Viewing an Attachment
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.
diff --git a/docs/er/umn/er_01_0028.html b/docs/er/umn/er_01_0028.html
index 5903aebc..9acd3bc3 100644
--- a/docs/er/umn/er_01_0028.html
+++ b/docs/er/umn/er_01_0028.html
@@ -4,7 +4,7 @@
ScenariosThis section describes how to delete a route table of an enterprise router.
Notes and Constraints- If a route table is used as the default association route table and/or default propagation route table, the route table cannot be deleted.
- If Default Route Association is set to Yes on the basic information page of the route table, the route table is used as the default association route table.
- Also, if Default Route Propagation is set to Yes on the basic information of the route table, the route table is used as the default propagation route table.
-To delete such a route table, disable Default Route Association and Default Route Propagation first. For details, see Modifying an Enterprise Router.
+To delete such a route table, change Default Route Association and Default Route Propagation settings. For details, see Modifying an Enterprise Router.
- A route table cannot be deleted if it contains an association or a propagation. You need to delete the association and propagation before deleting this route table.
- A route table can be deleted if it contains only static routes. Ensure that the routes are no longer required before deleting their route table.
diff --git a/docs/er/umn/er_01_0031.html b/docs/er/umn/er_01_0031.html
index 7309ac1f..ca26459f 100644
--- a/docs/er/umn/er_01_0031.html
+++ b/docs/er/umn/er_01_0031.html
@@ -22,7 +22,7 @@
Attachment Type
|
Mandatory
-Select an attachment type.
+ Select an attachment type. - VPC: A VPC is attached to the enterprise router.
- Virtual gateway: A Direct Connect virtual gateway is attached to the enterprise router.
For more information, see Attachment Overview.
|
diff --git a/docs/er/umn/er_01_0036.html b/docs/er/umn/er_01_0036.html
index d6c62e77..50233c5b 100644
--- a/docs/er/umn/er_01_0036.html
+++ b/docs/er/umn/er_01_0036.html
@@ -22,7 +22,7 @@
Attachment Type
|
Mandatory
-Select an attachment type.
+ Select an attachment type. - VPC: A VPC is attached to the enterprise router.
- Virtual gateway: A Direct Connect virtual gateway is attached to the enterprise router.
For more information, see Attachment Overview.
|
diff --git a/docs/er/umn/er_01_0041.html b/docs/er/umn/er_01_0041.html
index 36904d15..c2b3af88 100644
--- a/docs/er/umn/er_01_0041.html
+++ b/docs/er/umn/er_01_0041.html
@@ -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_0046.html b/docs/er/umn/er_01_0046.html
index 9876d22c..f4f99996 100644
--- a/docs/er/umn/er_01_0046.html
+++ b/docs/er/umn/er_01_0046.html
@@ -2,18 +2,15 @@
Creating a User and Granting Permissions
This section describes how to use IAM to implement fine-grained permissions control for your Enterprise Router resources. With IAM, you can:
- - Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to Enterprise Router resources.
- Assign only the minimum permissions required for users to perform a given task.
- Entrust an account or a cloud service to perform professional and efficient O&M on your Enterprise Router resources.
- If your account does not require individual IAM users, skip over this section.
+ - Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to Enterprise Router resources.
- Grant only the minimum permissions required for users to perform a given task.
- Entrust an account or a cloud service to perform professional and efficient O&M on your Enterprise Router resources.
+ If your account does not require individual IAM users, skip this topic.
Figure 1 shows the procedure for granting permissions.
- PrerequisitesYou have learned about the permissions supported by Enterprise Router and choose policies or roles according to your requirements. For details, see 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.
Process FlowFigure 1 Process for granting Enterprise Router permissions
- - Create a user group and assign permissions to it.
Create a user group on the IAM console, and assign the ER ReadOnlyAccess permission to the group.
- - Create an IAM user and add it to the user group.
Create a user on the IAM console and add the user to the group created in 1.
- - Log in and verify permissions.
Log in to the management console as the created user, switch to the authorized region, and verify that the user has only the ER ReadOnlyAccess permission.
-- 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 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.
diff --git a/docs/er/umn/er_01_0061.html b/docs/er/umn/er_01_0061.html
index 7df30a35..62aaab4f 100644
--- a/docs/er/umn/er_01_0061.html
+++ b/docs/er/umn/er_01_0061.html
@@ -4,7 +4,7 @@
-- Quick Start
+ - Overview
- Step 1: Plan Networks and Resources
diff --git a/docs/er/umn/er_01_0062.html b/docs/er/umn/er_01_0062.html
index 9d1954cd..20774e25 100644
--- a/docs/er/umn/er_01_0062.html
+++ b/docs/er/umn/er_01_0062.html
@@ -1,7 +1,7 @@
-Quick Start
-BackgroundFour VPCs are created in region A on public cloud and they need to communicate with each other.
+ Overview
+ BackgroundFour 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.
diff --git a/docs/er/umn/er_01_0063.html b/docs/er/umn/er_01_0063.html
index 1b45a9fe..0bf036be 100644
--- a/docs/er/umn/er_01_0063.html
+++ b/docs/er/umn/er_01_0063.html
@@ -151,7 +151,7 @@
er-test-01
|
-64512
+ | 64800
|
Enable
|
diff --git a/docs/er/umn/er_01_0064.html b/docs/er/umn/er_01_0064.html
index ce42b11f..63436f81 100644
--- a/docs/er/umn/er_01_0064.html
+++ b/docs/er/umn/er_01_0064.html
@@ -39,9 +39,10 @@
ASN
|
-Set the Autonomous System Number (ASN) for the cloud side of a Border Gateway Protocol (BGP) session. You cannot change it after the enterprise router is created.
+ | Enter an ASN based on your network plan. It cannot be changed after the enterprise router is created.
+Default ASN: 64800
|
-64512
+ | 64800
|
Default Route Table Association
diff --git a/docs/er/umn/er_01_0066.html b/docs/er/umn/er_01_0066.html
index ac7b0d8d..9f11390c 100644
--- a/docs/er/umn/er_01_0066.html
+++ b/docs/er/umn/er_01_0066.html
@@ -25,10 +25,16 @@
|
Attachment Type
|
-- Select VPC. The type cannot be changed after the attachment is created.
- Select the VPC to be attached to the enterprise router from the drop-down list. The VPC cannot be changed after the attachment is created.
- Select the subnet to be attached to the enterprise router from the drop-down list. The subnet cannot be changed after the attachment is created.
- You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC.
- You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller.
-
+ | Select VPC. The type cannot be changed after the attachment is created.
|
-- Attachment Type: VPC
- VPC: vpc-demo-01
- Subnet: subnet-demo-01
+ | VPC
+ |
+
+Attached Resource
+ |
+- Select the VPC to be attached to the enterprise router from the drop-down list. The VPC cannot be changed after the attachment is created.
- Select the subnet to be attached to the enterprise router from the drop-down list. The subnet cannot be changed after the attachment is created.
+ |
+- VPC: vpc-demo-01
- Subnet: subnet-demo-01
|
Auto Add Routes
diff --git a/docs/er/umn/er_01_0067.html b/docs/er/umn/er_01_0067.html
index 3f7d6bd0..045561f9 100644
--- a/docs/er/umn/er_01_0067.html
+++ b/docs/er/umn/er_01_0067.html
@@ -23,7 +23,14 @@
|
-Destination
+ | Destination Type
+ |
+The destination can only be IP address. You can set a single IP address or network segment.
+ |
+IP address
+ |
+
+Destination
|
The destination is used to route traffic from this VPC to other VPCs attached to the enterprise router. You can change it after the route is created.
- 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.
diff --git a/docs/er/umn/er_01_0069.html b/docs/er/umn/er_01_0069.html
index 62068504..acc21fe0 100644
--- a/docs/er/umn/er_01_0069.html
+++ b/docs/er/umn/er_01_0069.html
@@ -46,11 +46,13 @@
| ASN
|
Mandatory
-An autonomous system is an IP network that is managed by an entity and has the same routing policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them.
-You can use the default ASN, or specify one from 64512 to 65534 or from 4200000000 to 4294967294.
+An autonomous system is an IP network that is managed by an entity and has the same route policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them.
+Specify a dedicated ASN in the range of 64512-65534 or 4200000000-4294967294.
Networks in the same region can be considered as an AS.
+When Direct Connect and Enterprise Router are used to set up a hybrid cloud network, it is recommended that you set the ASN of the enterprise router different from the BGP ASN of the Direct Connect virtual gateway. If there are multiple Direct Connect connections associated with the enterprise router and the connections do not work in load balancing or active/standby mode, set different BGP ASNs for the virtual gateways of these connections.
+Default ASN: 64800
|
-64512
+ | 64800
|
Default Route Table Association
diff --git a/docs/er/umn/er_01_0070.html b/docs/er/umn/er_01_0070.html
index 8407dc5b..509e872a 100644
--- a/docs/er/umn/er_01_0070.html
+++ b/docs/er/umn/er_01_0070.html
@@ -1,7 +1,7 @@
-Adding VPC Attachments to an Enterprise Router
-ScenariosThis section describes how to attach VPCs to an enterprise router so that these VPCs can communicate with each other.
+ Creating a VPC Attachment
+ ScenariosThis section describes how to attach a VPC to an enterprise router so that the VPCs attached to the enterprise router can communicate with each other.
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.
@@ -31,17 +31,27 @@
Attachment Type
|
Mandatory
-- Select the attachment type. Select VPC, indicating that the instance to be attached to the enterprise router is a VPC.
The methods for creating attachments vary depending on the attachment type. For details, see Attachment Overview.
- - Select the VPC to be attached to the enterprise router. You can enter a VPC name to quickly find the target VPC.
- Select a subnet in the selected VPC. You can enter a subnet name to quickly find the target subnet.
- You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC.
- You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller.
+Select VPC, indicating that a VPC is to be attached to the enterprise router.
+The methods for creating attachments vary depending on the attachment type. For details, see Attachment Overview.
+
|
+VPC
+ |
+
+ Attached Resource
+ |
+Mandatory
+- Select the VPC to be attached to the enterprise router. You can enter a VPC name to quickly find the target VPC.
- Select a subnet in the selected VPC. You can enter a subnet name to quickly find the target subnet.
- You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC.
- You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller.
|
-- Attachment Type: VPC
- VPC: vpc-A
- Subnet: subnet-A01
+ | - VPC: vpc-A
- Subnet: subnet-A01
|
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.
+ NOTE: This parameter is only displayed when a VPC attachment is created. It cannot be enabled after the VPC attachment is created.
+
|
Enable
|
@@ -79,7 +89,7 @@
diff --git a/docs/er/umn/er_01_0072.html b/docs/er/umn/er_01_0072.html
index 24d49163..fb17a039 100644
--- a/docs/er/umn/er_01_0072.html
+++ b/docs/er/umn/er_01_0072.html
@@ -3,7 +3,7 @@
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.
- Deleting an attachment will also delete its flow logs.
+ 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.
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.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
@@ -15,7 +15,7 @@
diff --git a/docs/er/umn/er_01_0073.html b/docs/er/umn/er_01_0073.html
index 63b4b7b8..14dd24f3 100644
--- a/docs/er/umn/er_01_0073.html
+++ b/docs/er/umn/er_01_0073.html
@@ -4,12 +4,12 @@
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.
- - Deleting an attachment will also delete its flow logs.
+ - If flow logging is enabled for an 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.
- 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 page of the enterprise router.
+ A virtual gateway attachment cannot be directly deleted on the Attachments tab.
A virtual gateway attachment will be automatically deleted after you perform the following operations to delete the virtual gateway and its virtual interfaces.
- Locate the target virtual gateway attachment and click the attached resource.
Example: vgw-demo
@@ -24,7 +24,7 @@
diff --git a/docs/er/umn/er_01_0092.html b/docs/er/umn/er_01_0092.html
index 93a66e1a..ce63c380 100644
--- a/docs/er/umn/er_01_0092.html
+++ b/docs/er/umn/er_01_0092.html
@@ -4,7 +4,7 @@
ScenariosAfter CTS is enabled, CTS starts recording operations on cloud resources. The CTS management console stores the last seven days of operation records.
This section describes how to query or export the last seven days of operation records on the management console.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List. Under Management & Governance, click Cloud Trace Service.
The Cloud Trace Service console 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. Under Management and Deployment, click Cloud Trace Service.
The Cloud Trace Service console is displayed.
- In the navigation pane on the left, choose Trace List.
The Trace List page is displayed.
- Specify filters as needed.
The following filters are available:
- Trace Source, Resource Type, and Search By
- If you select Trace name for Search By, select a trace name.
- If you select Resource ID for Search By, select or enter a resource ID.
- If you select Resource name for Search By, select or enter a resource name.
diff --git a/docs/er/umn/er_01_0095.html b/docs/er/umn/er_01_0095.html
index eee47eaa..d064b578 100644
--- a/docs/er/umn/er_01_0095.html
+++ b/docs/er/umn/er_01_0095.html
@@ -61,7 +61,7 @@
Adding attachments to an enterprise router
-Adding VPC Attachments to an Enterprise Router
+Creating a VPC Attachment
|
Other users:
- Can only create VPC attachments.
- Can create attachments to the shared enterprise router only after the owner account accepts the attachment requests.
If Auto Accept Shared Attachments is enabled, a request from a user for creating an attachment will be automatically accepted.
@@ -69,7 +69,7 @@
For details about the process for creating an attachment for an enterprise router in another account, see Sharing an Enterprise Router with Other Users.
|
- Viewing Details About an Attachment
+ | Viewing an Attachment
|
Other users:
Cannot view the tags added of their attachments.
@@ -95,7 +95,7 @@
Sharing an Enterprise Router with Other UsersAs the owner, you can share your enterprise router with other users. These other users can create attachments for your enterprise router. - If Auto Accept Shared Attachments is not enabled on your enterprise router, you must accept the attachment creation requests from other users.
Figure 2 Accepting or rejecting attachment creation requests
-Table 3 Process descriptionNo.
+Table 3 Process descriptionNo.
|
Step
|
@@ -116,28 +116,22 @@
|---|
2
|
-Adding VPC Attachments to an Enterprise Router
+ | Creating a VPC Attachment
|
User
|
The user creates an attachment to the shared enterprise router. The attachment will be in the Pending acceptance state because Auto Accept Shared Attachments is disabled on the enterprise router.
|
-3
+ | 3
|
-Accepting an Attachment Request
+ |
|
-Owner
-
+ | Owner
|
-The owner accepts the attachment request. The attachment status changes from Pending acceptance to Creating. - When the attachment status changes to Normal, the attachment is successfully created.
- When the attachment status changes to Failed, the attachment fails to be created. Contact customer service.
- | |
-
-Rejecting an Attachment Request
- |
-The owner can also reject the attachment request. If the owner rejects the request, the attachment status changes from Pending acceptance to Rejected, and the attachment fails to be created. If this happens, contact the owner.
+- The owner can also reject the attachment request. If the owner rejects the request, the attachment status changes from Pending acceptance to Rejected, and the attachment fails to be created. If this happens, contact the owner.
|
@@ -166,7 +160,7 @@
2
|
-Adding VPC Attachments to an Enterprise Router
+ | Creating a VPC Attachment
|
User account
|
diff --git a/docs/er/umn/er_01_0111.html b/docs/er/umn/er_01_0111.html
index 16cceaaf..954c7d40 100644
--- a/docs/er/umn/er_01_0111.html
+++ b/docs/er/umn/er_01_0111.html
@@ -1,7 +1,7 @@
Disabling a Flow Log
-ScenariosThis section describes how to disable a flow log. After a flow log is disabled, the enterprise router will not send log information to LTS.
+ ScenariosIf flow logging is disabled, no flow logs will be collected in the next log collection period. Collected flow logs can still be viewed.
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.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
diff --git a/docs/er/umn/er_01_0112.html b/docs/er/umn/er_01_0112.html
index 9c81127f..56f08092 100644
--- a/docs/er/umn/er_01_0112.html
+++ b/docs/er/umn/er_01_0112.html
@@ -1,7 +1,7 @@
Enabling a Flow Log
-ScenariosThis section describes how to enable a flow log. After a flow log is enabled, the enterprise router will send log information to LTS.
+ ScenariosIf flow logging is enabled, flow logs will be collected from the next log collection period.
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.
- Search for the target enterprise router by name.
Figure 1 Searching for an enterprise router
diff --git a/docs/er/umn/er_01_0122.html b/docs/er/umn/er_01_0122.html
index cb1d315f..b10e663c 100644
--- a/docs/er/umn/er_01_0122.html
+++ b/docs/er/umn/er_01_0122.html
@@ -126,7 +126,7 @@
- Create a transit VPC, attach it to the enterprise router, and associate the transit VPC with the default route table of the enterprise router.
- The subnet of the transit VPC cannot overlap with that of the service VPC. Otherwise, the VPC peering connection to be created in 2 cannot take effect.
- The transit VPC cannot have the following situations. Otherwise, the default route (0.0.0.0/0) to be configured in 3 cannot forward traffic.
- An ECS in the VPC has an EIP bound.
- The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS.
+- Create a transit VPC, attach it to the enterprise router, and associate the transit VPC with the default route table of the enterprise router.
- The subnet of the transit VPC cannot overlap with that of the service VPC, or the VPC peering connection to be created in 2 cannot take effect.
- The transit VPC cannot have the following situations. Otherwise, the default route (0.0.0.0/0) to be configured in 3 cannot forward traffic.
- An ECS in the VPC has an EIP bound.
- The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS.
- Create a VPC peering connection between the service VPC and transit VPC.
You do not need to add routes for the VPC peering connection. For details about the routes to be added, see 3.
diff --git a/docs/er/umn/er_01_0123.html b/docs/er/umn/er_01_0123.html
index 33ad0c8f..f72c7454 100644
--- a/docs/er/umn/er_01_0123.html
+++ b/docs/er/umn/er_01_0123.html
@@ -2,7 +2,7 @@
How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Each Other?
If you want two attachments of an enterprise router to learn routes from each other, the router and each attachment must have a unique ASN. In this way, the enterprise router advertises the learned route information between the attachments.
- If you want two virtual gateways attached to the same enterprise router to learn routes from each other, their ASNs can be as follows: - Enterprise router: 64512
- Virtual gateway attachment A: 64513 (BGP ASN of virtual gateway A)
- Virtual gateway attachment B: 64515 (BGP ASN of virtual gateway B)
+ If you want two virtual gateways attached to the same enterprise router to learn routes from each other, their ASNs can be as follows: - Enterprise router: 64800
- Virtual gateway attachment A: 64513 (BGP ASN of virtual gateway A)
- Virtual gateway attachment B: 64515 (BGP ASN of virtual gateway B)
VPC attachments do not support route learning.
diff --git a/docs/er/umn/er_01_0022.html b/docs/er/umn/er_01_0167.html
similarity index 51%
rename from docs/er/umn/er_01_0022.html
rename to docs/er/umn/er_01_0167.html
index 1d023cb1..df422077 100644
--- a/docs/er/umn/er_01_0022.html
+++ b/docs/er/umn/er_01_0167.html
@@ -1,12 +1,16 @@
-
+
+
+
+ VPC Attachments
+
+
- Deleting an Attachment
-
diff --git a/docs/er/umn/er_01_0168.html b/docs/er/umn/er_01_0168.html
new file mode 100644
index 00000000..798abf04
--- /dev/null
+++ b/docs/er/umn/er_01_0168.html
@@ -0,0 +1,21 @@
+
+
+
+ Virtual Gateway Attachments
+
+
+
+
+
diff --git a/docs/er/umn/er_01_0169.html b/docs/er/umn/er_01_0169.html
new file mode 100644
index 00000000..1b8b50ec
--- /dev/null
+++ b/docs/er/umn/er_01_0169.html
@@ -0,0 +1,14 @@
+
+
+ Creating a Virtual Gateway Attachment
+ ScenariosAttach a Direct Connect virtual gateway to an enterprise router to set up a hybrid cloud network using Direct Connect and Enterprise Router.
+
+
+
+
+
|
|---|
| |
|
|---|
| | |