Cloud Connect provides central networks that allow you to connect Virtual Private Clouds (VPCs) in different regions, so that these VPCs can communicate over a private network as if they were within the same network. Cloud Connect can also work with Direct Connect to set up a hybrid cloud network that enables on-premises data centers to access the VPCs across regions.
+
+
Table 1 Cloud Connect featuresFeature
+ |
+Application Scenarios
+ |
+Bandwidth
+ |
+Advantages
+ |
+
|---|
+
+Central Network
+ |
+- Connect VPCs in different regions by attaching them to enterprise routers in the corresponding regions.
- Connect on-premises data centers to VPCs in different regions by attaching them to enterprise routers in the corresponding regions.
+ |
+You need to buy and bind a global connection bandwidth to the central network and assign cross-site connection bandwidths to enable communication between the resources in different regions.
+ |
+- Flexible networking
- Dynamic routing
- A variety of attachments and network scenarios
- Enterprise routers in different regions are connected.
+
+ |
+
+
+
+
+
Central Network
Relying on the cloud backbone network, a central network allows you to easily set up a reliable, intelligent enterprise-grade network and manage global network resources on premises and on the cloud. By setting up a central network, you can enable communication between enterprise routers, in the same region or different regions.
+
In Figure 1, the two VPCs (VPC-A01 and VPC-A02) are attached to an enterprise router (ER-A) in region A, two VPCs (VPC-B01 and VPC-B02) are attached to an enterprise router (ER-B) in region B, and two VPCs (VPC-C01 and VPC-C02) are attached to an enterprise router (ER-C) in region C.
+
The three enterprise routers (ER-A, ER-B, and ER-C) are connected over a central network. In this way, the enterprise routers can communicate with each other across regions, and the VPCs in these regions can communicate with each other.
+
+
Figure 1 How a central network works
+
+
Table 2 Central network conceptsConcept
+ |
+Description
+ |
+
|---|
+
+Enterprise router
+ |
+An enterprise router enables the VPCs in the same region to communicate with each other. Enterprise routers in different regions can be connected using a central network to allow for cross-region communication between VPCs.
+ |
+
+Global connection bandwidth
+ |
+A global connection bandwidth can be bound to a central network to allow the resources to communicate with each other over the backbone network, regardless of whether:
+- The resources are in the same geographic region.
- The resources are in different geographic regions.
+ |
+
+
+
+
+
+
Accessing Cloud Connect
You can access Cloud Connect through the management console or by calling HTTPS-based APIs.
- Using the management console
The management console is a web-based GUI where you can easily perform various operations. Log in to the management console and choose Cloud Connect from the main menu.
+ - Using APIs
If you need to integrate Cloud Connect into a third-party system for secondary development, you can use APIs to access Cloud Connect. For details, see the Cloud Connect API Reference.
+
+
+
+
If you need to assign different permissions to employees in your enterprise, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM allows you to control access to your Cloud Connect resources.
+
With IAM, you can create IAM users for certain employees in your enterprise and assign permissions to control their access to Cloud Connect resources. For example, you can assign permissions to software developers so that they use Cloud Connect but cannot delete Cloud Connect resources or perform any other high-risk operations.
+
Skip this part if you do not require individual IAM users for refined permissions management.
+
IAM is a free service. For more information about IAM, see the What Is IAM?
+
Cloud Connect Permissions
By default, new IAM users do not have permissions assigned. To assign permissions to these new users, add them to one or more groups and attach permissions policies or roles to these groups.
+
Cloud Connect is a global service for access from any region. You can assign IAM permissions to users in the global service project. In this way, users do not need to switch regions when they access IAM.
+
You can grant permissions by using roles or policies.
+
- Roles: A type of coarse-grained authorization mechanism that defines permissions based on user responsibility. This mechanism provides only a limited number of service-level roles. When using roles to grant permissions, you may need to also assign other dependency roles. Roles are not an ideal choice for fine-grained authorization.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, the administrator can grant Cloud Connect users only the permissions for managing cloud connections.
+
Table 1 lists the system-defined roles or policies supported by Cloud Connect.
+
Table 1 Cloud Connect system-defined roles or policiesSystem Role/Policy Name
+ |
+Description
+ |
+Type
+ |
+Dependency
+ |
+
|---|
+
+Cross Connect Administrator
+ |
+Administrator permissions for Cloud Connect. Users with this role must also have the Tenant Guest and VPC Administrator permissions.
+ NOTE: Users who have these permissions can only view Cloud Connect resources. You are advised to use the CC FullAccess policy.
+
+ |
+System-defined role
+ |
+Tenant Guest and VPC Administrator
+- VPC Administrator: project-level policy, which must be assigned for the same project
- Tenant Guest: project-level policy, which must be assigned for the same project
+ |
+
+CC FullAccess
+ |
+All permissions on Cloud Connect.
+ |
+System-defined policy
+ |
+CC Network Depend QueryAccess
+ |
+
+CC ReadOnlyAccess
+ |
+Read-only permissions for Cloud Connect. Users who have these permissions can only view Cloud Connect resources.
+ |
+System-defined policy
+ |
+-
+ |
+
+CC Network Depend QueryAccess
+ |
+Read-only permissions required to access dependency resources when using Cloud Connect.
+Users who have these permissions can view VPCs.
+ NOTE: If you only have the CC FullAccess permission, you cannot select Enterprise Router on the console. In this case, you need the CC Network Depend QueryAccess, Tenant Guest, or ER FullAccess permission.
+
+ |
+System-defined policy
+ |
+-
+ |
+
+
+
+
+
+
Table 2 lists common operations supported by each system-defined role.
+
When you configure system policies CC FullAccess and CC ReadOnlyAccess, select Global services for Scope. In this case, the two system policies can take effect for resources such as network instances, inter-domain bandwidths, and routes.
+
+
+
Table 2 Common operations supported by system-defined permissionsOperation
+ |
+Cross Connect Administrator
+ |
+CC FullAccess
+ |
+CC ReadOnlyAccess
+ |
+CC Network Depend QueryAccess
+ |
+
|---|
+
+Creating a central network
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Updating a central network
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Deleting a central network
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Querying details of a central network
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Querying central networks
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Adding a central network policy
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Applying a central network policy
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Deleting a central network policy
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Querying central network policies
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Querying policy changes
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Querying central network connections
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Updating a central network connection
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Querying quotas
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Querying the capabilities
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Creating a global connection bandwidth
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Updating a global connection bandwidth
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+Querying a global connection bandwidth
+ |
+√
+ |
+√
+ |
+√
+ |
+×
+ |
+
+Deleting a global connection bandwidth
+ |
+×
+ |
+√
+ |
+×
+ |
+×
+ |
+
+
+
+
+
+
A central network enables enterprise routers to communicate with each other, no matter whether they are in the same region or different regions.
+
+
Cloud Connect has the following advantages:
+
+
+
+
+
Relying on the backbone network, you can set up a central network to manage global network resources on premises and on the cloud easily and securely. After attaching the VPCs to enterprise routers in each region, you can add the enterprise routers to a central network, so that all the VPCs attached to the enterprise routers can communicate with each other across regions.
+
In this topic, a central network and enterprise routers are used to connect the VPCs in the same account but different regions.
+
Architecture
For nearby access, an enterprise runs workloads in regions A, B, and C. The VPCs in each region need to communicate with each other. To achieve this, you can:
- Create an enterprise router in each region: ER-A in region A, ER-B in region B, and ER-C in region C.
- Create a central network and add ER-A, ER-B, and ER-C to the central network as attachments so that the three enterprise routers can communicate with each other.
- In region A, attach VPC-A01 and VPC-A02 to ER-A so that the two VPCs can communicate with each other. Perform the same operations in regions B and C. In this way, the VPCs in the three regions can communicate with each other over the central network.
+
+
Figure 1 Communication between VPCs in different regions
+
+
Network and Resource Planning
To use a central network and enterprise routers to connect VPCs across regions, you need to:
- Plan the central network, VPCs and their subnets, VPC route tables, and enterprise router route tables.
- Plan the quantities, names, and main parameters of cloud resources, including central network, enterprise router, VPC, and ECS.
+
+
Network Planning
+
+
Figure 2 shows the network planning for communication between VPCs across regions. For details about the network planning, see Table 2.
+
In this example, one VPC is created and attached to an enterprise router in each region. Make the plan based on your service requirements.
+
+
Figure 2 Cross-region VPC network planning
+
+
Table 1 Network traffic flowsTraffic Flow
+ |
+What to Do
+ |
+
|---|
+
+Request traffic: from VPC-A to VPC-B
+ |
+- In the route table of VPC-A, there are routes with the next hop set to enterprise router ER-A to forward traffic from VPC-A to ER-A.
- In the route table of enterprise router ER-A, there is a route with the next hop set to the peering connection attachment and destination to 192.168.0.0/16 to forward traffic from ER-A to enterprise router ER-B.
- In the route table of enterprise router ER-B, there is a route with the next hop set to the VPC-B attachment to forward traffic from ER-B to VPC-B.
+ |
+
+Response traffic: from VPC-B to VPC-A
+ |
+- In the route table of VPC-B, there are routes with the next hop set to enterprise router ER-B to forward traffic from VPC-B to ER-B.
- In the route table of enterprise router ER-B, there is a route with the next hop set to the peering connection attachment and destination to 172.16.0.0/16 to forward traffic from ER-B to enterprise router ER-A.
- In the route table of enterprise router ER-A, there is a route with the next hop set to the VPC-A attachment to forward traffic from ER-A to VPC-A.
+ |
+
+
+
+
+
+
Table 2 Description for cross-region VPC communicationResource
+ |
+Description
+ |
+
|---|
+
+VPC
+ |
+- 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 a subnet CIDR block or a smaller CIDR block.
+ - Each VPC has a default route table.
- Routes in the default route table can be:
- Local: a system route for communications between subnets in a VPC.
- Enterprise router: automatically added routes with 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations for routing traffic from a VPC subnet to the enterprise router. See Table 3 for details.
+
+ |
+
+Central network
+ |
+- Enterprise routers in different regions are added to the central network as attachments.
- Global connection bandwidths are required for assigning cross-site connection bandwidths to for communication across regions.
+ |
+
+Enterprise router
+ |
+The network configuration for the enterprise router in the three regions is the same. Table 4 lists all routes required by the enterprise router.
+When a central network is set up to connect the enterprise routers, you must enable Default Route Table Association and Default Route Table Propagation for the enterprise routers. In this way, when an instance is added to an enterprise router, a route pointing to the attachment will be automatically added for the enterprise router.
+ |
+
+ECS
+ |
+An ECS is created in each VPC. If the ECSs are in different security groups, add rules to the security groups to allow access to each other.
+ |
+
+
+
+
+
+
Table 3 VPC route tablesDestination
+ |
+Next Hop
+ |
+Route Type
+ |
+
|---|
+
+10.0.0.0/8
+ |
+Enterprise router
+ |
+Static route (custom)
+ |
+
+172.16.0.0/12
+ |
+Enterprise router
+ |
+Static route (custom)
+ |
+
+192.168.0.0/16
+ |
+Enterprise router
+ |
+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 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 tablesEnterprise router
+ |
+Destination
+ |
+Next Hop
+ |
+Route Type
+ |
+
|---|
+
+Region A: ER-A
+ |
+VPC-A CIDR block: 172.16.0.0/16
+ |
+VPC-A attachment: er-attach-VPC-A
+ |
+Propagated route
+ |
+
+VPC-B CIDR block: 192.168.0.0/16
+ |
+Peering connection attachment: region-A-region-B
+ |
+Propagated route
+ |
+
+VPC-C CIDR block: 10.0.0.0/16
+ |
+Peering connection attachment: region-A-region-C
+ |
+Propagated route
+ |
+
+Region B: ER-B
+ |
+VPC-B CIDR block: 192.168.0.0/16
+ |
+VPC-B attachment: er-attach-VPC-B
+ |
+Propagated route
+ |
+
+VPC-A CIDR block: 172.16.0.0/16
+ |
+Peering connection attachment: region-B-region-A
+ |
+Propagated route
+ |
+
+VPC-C CIDR block: 10.0.0.0/16
+ |
+Peering connection attachment: region-B-region-C
+ |
+Propagated route
+ |
+
+Region C: ER-C
+ |
+VPC-C CIDR block: 10.0.0.0/16
+ |
+VPC-C attachment: er-attach-VPC-C
+ |
+Propagated route
+ |
+
+VPC-A CIDR block: 172.16.0.0/16
+ |
+Peering connection attachment: region-C-region-A
+ |
+Propagated route
+ |
+
+VPC-B CIDR block: 192.168.0.0/16
+ |
+Peering connection attachment: region-C-region-B
+ |
+Propagated route
+ |
+
+
+
+
+
Resource Planning
+
The enterprise router, VPCs, and ECSs must be in the same region, but they can be in different AZs.
The following resource planning is only for your reference.
+
+
+
+
Table 5 Resource planning for cross-region VPC communicationsResource
+ |
+Quantity
+ |
+Description
+ |
+
|---|
+
+VPC
+ |
+3
+ |
+A service VPC is required in each region for running workloads. Each VPC needs to be attached to an enterprise router in the same region. - Name: Set it based on site requirements. In this example, the names are as follows:
- Region A: VPC-A
- Region B: VPC-B
- Region C: VPC-C
+ - IPv4 CIDR Block: The CIDR blocks of VPCs must be unique. Plan the CIDR blocks based on site requirements. In this example, the CIDR blocks are as follows:
- VPC-A: 172.16.0.0/16
- VPC-B: 192.168.0.0/16
- VPC-C: 10.0.0.0/16
+ - Subnet name and IPv4 CIDR block: The subnet CIDR blocks that need to communicate with each other must be unique. Plan the subnets based on site requirements. In this example, the subnets are as follows:
- Subnet-A01: 172.16.0.0/24
- Subnet-B01: 192.168.0.0/24
- Subnet-C01: 10.0.0.0/24
+
+ |
+
+Enterprise router
+ |
+3
+ |
+An enterprise router is required in each region. The VPC in each region is attached to the corresponding enterprise router, and a peering connection attachment is created between every two enterprise routers. - Name: Set it based on site requirements. In this example, the names are as follows:
- Region A: ER-A
- Region B: ER-B
- Region C: ER-C
+ - ASN: Set different ASNs for enterprise routers. In this example, the ASNs are as follows:
- ER-A: 64512
- ER-B: 64513
- ER-C: 64514
+ - Default Route Table Association: Enable this option.
- Default Route Table Propagation: Enable this option.
- Auto Accept Shared Attachments: Set it based on site requirements. In this example, this option is enabled.
- Attachment: Three attachments are required for each enterprise router. In this example, the attachments are as follows:
ER-A - VPC attachment er-attach-VPC-A: connects the network between VPC-A and ER-A.
- Peering connection attachment region-A-region-B: connects the network between ER-A and ER-B.
- Peering connection attachment region-A-region-C: connects the network between ER-A and ER-C.
+ ER-B - VPC attachment er-attach-VPC-B: connects the network between VPC-B and ER-B.
- Peering connection attachment region-B-region-A: connects the network between ER-B and ER-A.
- Peering connection attachment region-B-region-C: connects the network between ER-B and ER-C.
+ ER-C - VPC attachment er-attach-VPC-C: connects the network between VPC-C and ER-C.
- Peering connection attachment region-C-region-A: connects the network between ER-C and ER-A.
- Peering connection attachment region-C-region-B: connects the network between ER-C and ER-B.
+
+ NOTICE: When a central network is set up to connect the enterprise routers, you must enable Default Route Table Association and Default Route Table Propagation for the enterprise routers.
+
+ |
+
+Central network
+ |
+1
+ |
+A central network is required, and all enterprise routers are added to it as attachments. - Name: Set it based on site requirements. In this example, the name is gcn-A-B-C.
- Policy
- Region A: enterprise router ER-A
- Region B: enterprise router ER-B
- Region C: enterprise router ER-C
+ - Cross-site connection bandwidths:
- Region A-Region B: 10 Mbit/s
- Region A-Region C: 5 Mbit/s
- Region B-Region C: 20 Mbit/s
+
+ |
+
+Global connection bandwidth
+ |
+3
+ |
+Three global connection bandwidths are required to connect the cloud backbone networks in different regions.
+- Name: Set it based on site requirements. In this example, the names are as follows:
- Global connection bandwidth for communication between region A and region B: bandwidth-A-B
- Global connection bandwidth for communication between region A and region C: bandwidth-A-C
- Global connection bandwidth for communication between region B and region C: bandwidth-B-C
+ - Bandwidth Type: Set it based on site requirements. In this example, select Geographic-region because the three regions are in the same geographic region.
- Connect Regions: Select the regions based on site requirements.
+ |
+
+ECS
+ |
+3
+ |
+Create an ECS in each VPC to verify network connectivity. - ECS Name: Set it based on site requirements. In this example, the names are as follows:
- Region A: ECS-A
- Region B: ECS-B
- Region C: ECS-C
+ - Network: Select the VPC and subnet based on site requirements. In this example, the VPCs and subnets are as follows:
- ECS-A: VPC-A, Subnet-A01
- ECS-B: VPC-B, Subnet-B01
- ECS-C: VPC-C, Subnet-C01
+ - Security Group: Select a security group based on site requirements. In this example, the security group sg-demo uses a general-purpose web server template.
- Private IP addresses:
- ECS-A: 172.16.0.91
- ECS-B: 192.168.0.5
- ECS-C: 10.0.0.29
+
+ |
+
+
+
+
+
+
Step 1: Create Cloud Resources
In this example, you need to create a central network, three enterprise routers, three VPCs, and three ECSs based on Table 5.
+
- Create an enterprise router in each of the three regions.
For details, see section "Creating an Enterprise Router" in the Enterprise Router User Guide.
+ Specify a unique ASN for each enterprise router.
+
+ - Create a VPC in each of the three regions.
- Create an ECS in each of the three regions.
- Create a central network and add the enterprise routers to the central network as attachments.
- Create a central network and add the enterprise routers to the central network as attachments.
- On the Enterprise Router console, view the peering connection attachments.
For details, see section "Viewing Details About an Attachment" in the Enterprise Router User Guide.
+If the status of the peering connection attachments is Normal, the attachments are available.
+Default Route Table Association and
Default Route Table Propagation are enabled when you create enterprise routers. After peering connection attachments are created for the enterprise routers, Enterprise Router will automatically:
- Associate the peering connection attachment with the default route table of each enterprise router.
- Propagate the peering connection attachment to the default route table of each enterprise router. The route tables automatically learn routes from each other.
+
+
+ - Purchase three global connection bandwidths to connect networks in different regions.
+
+
Step 2: Create a VPC Attachment for Each Enterprise Router
Create a VPC attachment for each enterprise router. For details about resource planning, see Table 5.
+
- In region A, attach VPC-A to enterprise router ER-A.
- Attach the VPC to the enterprise router.
In this example, enable Auto Add Routes to save you from manually configuring routes in the VPC route table.
+For details, see section "Creating VPC Attachments for an Enterprise Router" in the Enterprise Router User Guide.
+Default Route Table Association and
Default Route Table Propagation are enabled when you create the enterprise router. After VPCs are attached to the enterprise routers, Enterprise Router will automatically:
- Associate the VPC attachments with the default route table of the enterprise router.
- Propagate the VPC attachments to the default route table of the enterprise router. The route table automatically learns the VPC CIDR blocks as the destination of routes.
+
+ - (Optional) Add routes to the VPC route table for traffic to route through the enterprise router.
Skip this step if you have enabled Auto Add Routes in the previous step. For details about routes, see Table 3.
+For details, see "Adding Routes to VPC Route Tables" in the Enterprise Router User Guide.
+
+ - In region B, attach VPC-B to enterprise router ER-B by referring to 1.
- In region C, attach VPC-C to enterprise router ER-C by referring to 1.
+
+
Step 3: Assign Cross-Site Connection Bandwidths for the Central Network
To allow cross-region VPC communications, you need to assign cross-region connection bandwidths on the central network based on service requirements by referring to Table 5.
+
By default, Cloud Connect allocates 10 kbit/s of bandwidth for testing connectivity between regions. After the peering connection attachments are created, you can verify the network connectivity between VPCs. For details, see Step 4: Verify Network Connectivity.
+
To ensure your workloads run normally, you need to purchase global connection bandwidths and assign cross-site connection bandwidths.
+
+
- Assign a cross-site connection bandwidth from the purchased global connection bandwidth for the communication between region A and region B.
- Assign a cross-site connection bandwidth from the purchased global connection bandwidth for the communication between region A and region C.
- Assign a cross-site connection bandwidth from the purchased global connection bandwidth for the communication between region B and region C
+
+
Step 4: Verify Network Connectivity
- Log in to an ECS.
- In the remote login window of the ECSs, use ping to verify the network connectivity:
- Verify the network connectivity between two VPCs.
ping <private-IP-address-of-the-ECS>
+Log in to ECS-A to verify the network connectivity between VPC-A and VPC-B:
+ping 192.168.0.5
+If information similar to the following is displayed, VPC-A and VPC-B can communicate with each other normally:
[root@ECS-A ~]# ping 192.168.0.5
+PING 192.168.0.5 (192.168.0.5) 56(84) bytes of data.
+64 bytes from 192.168.0.5: icmp_seq=1 ttl=62 time=30.6 ms
+64 bytes from 192.168.0.5: icmp_seq=2 ttl=62 time=30.2 ms
+64 bytes from 192.168.0.5: icmp_seq=3 ttl=62 time=30.1 ms
+64 bytes from 192.168.0.5: icmp_seq=4 ttl=62 time=30.1 ms
+...
+--- 192.168.0.5 ping statistics ---
+
- Verify the network connectivity between another two VPCs.
ping <private-IP-address-of-the-ECS>
+Log in to ECS-A to verify the network connectivity between VPC-A and VPC-C:
+ping 10.0.0.29
+If information similar to the following is displayed, VPC-A and VPC-C can communicate with each other normally:
[root@ECS-A ~]# ping 10.0.0.29
+PING 10.0.0.29 (10.0.0.29) 56(84) bytes of data.
+64 bytes from 10.0.0.29: icmp_seq=1 ttl=62 time=27.4 ms
+64 bytes from 10.0.0.29: icmp_seq=2 ttl=62 time=27.0 ms
+64 bytes from 10.0.0.29: icmp_seq=3 ttl=62 time=26.10 ms
+64 bytes from 10.0.0.29: icmp_seq=4 ttl=62 time=26.9 ms
+...
+--- 10.0.0.29 ping statistics ---
+
+ - Repeat 1 and 2 to verify the network connectivity between VPC-B and VPC-C.
+
+
Description
By setting up a central network, you can enable communication between enterprise routers, as well as between enterprise routers and your on-premises data center, in the same region or across regions. When a central network is used, attachments on the enterprise routers used in the central network policy will be monitored.
+
This section describes metrics reported by enterprise routers in the central network policy to Cloud Eye as well as their namespaces and dimensions. You can view the metrics on the Cloud Eye console.
+
+
+
Metrics
+
Table 1 Monitoring metrics of an attachmentID
+ |
+Name
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+Conversion Rule
+ |
+Monitored Object (Dimension)
+ |
+Monitoring Interval (Raw Data)
+ |
+
|---|
+
+attachment_bytes_in
+ |
+Inbound Traffic
+ |
+Network traffic going into the attachment
+ |
+≥ 0
+ |
+Byte
+ |
+1024 (IEC)
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+attachment_bytes_out
+ |
+Outbound Traffic
+ |
+Network traffic going out of the attachment
+ |
+≥ 0
+ |
+Byte
+ |
+1024 (IEC)
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+attachment_bits_rate_in
+ |
+Inbound Bandwidth
+ |
+Network traffic per second going into the attachment
+ |
+≥ 0
+ |
+bit/s
+ |
+1000 (SI)
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+attachment_bits_rate_out
+ |
+Outbound Bandwidth
+ |
+Network traffic per second going out of the attachment
+ |
+≥ 0
+ |
+bit/s
+ |
+1000 (SI)
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+attachment_packets_in
+ |
+Inbound PPS
+ |
+Packets per second going into the attachment
+ |
+≥ 0
+ |
+PPS
+ |
+1000 (SI)
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+attachment_packets_out
+ |
+Outbound PPS
+ |
+Packets per second going out of the attachment
+ |
+≥ 0
+ |
+PPS
+ |
+1000 (SI)
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+attachment_packets_drop_blackhole
+ |
+Packets Dropped by Black Hole Route
+ |
+The number of packets dropped because they matched a black hole route on the attachment
+ |
+≥ 0
+ |
+Count
+ |
+N/A
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+attachment_packets_drop_noroute
+ |
+Packets Dropped Due to No Route Matched
+ |
+The number of packets dropped because they did not match a route on the attachment
+ |
+≥ 0
+ |
+Count
+ |
+N/A
+ |
+er_instance_id,er_attachment_id
+ |
+1 minute
+ |
+
+
+
+
+
+
Dimensions
+
Key
+ |
+Value
+ |
+
|---|
+
+er_attachment_id
+ |
+Enterprise router attachment
+ |
+
+
+
+
+
+
Scenarios
You can view the metrics of attachments on the enterprise routers in a central network policy on the Cloud Eye 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 & Deployment, click Cloud Eye.
The Cloud Eye console is displayed.
+ - In the navigation pane on the left, choose Cloud Service Monitoring > Enterprise Router.
The enterprise router list is displayed.
+ - View the real-time metrics of enterprise router attachments.
- In the enterprise router list, locate the enterprise router, click
to view its attachments, locate the attachment, and click View Metric in the Operation column.The metrics are displayed.
+ - View metrics of the attachment.
+
+
+
Scenarios
This section describes how to create alarm rules and notifications for enterprise router attachments.
+
The alarm function provides the alarm service for monitoring data. By creating alarm rules, you define how the alarm system checks monitoring data and sends alarm notifications when monitoring data meets alarm policies.
+
After creating alarm rules for important metrics, you can timely know metric data exceptions and quickly rectify the faults.
+
+
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 & Deployment, click Cloud Eye.
The Cloud Eye console is displayed.
+ - In the navigation pane on the left, choose Cloud Service Monitoring > Enterprise Router.
The enterprise router list is displayed.
+ - Create an alarm rule and notification for an enterprise router attachment.
- In the enterprise router list, locate the enterprise router, click
to view its attachments, locate the attachment, and click Create Alarm Rule in the Operation column.The Create Alarm Rule page is displayed.
+ - On the Create Alarm Rule page, configure the parameters as prompted.
+ For details about the parameters on the Create Alarm Rule page, see the Cloud Eye User Guide.
+
+ - Click Create.
After the alarm rule is configured, if you have enabled alarm notifications and configured related parameters, you will receive notifications once an alarm is triggered.
+
+
+
+
Scenarios
After CTS is enabled, it starts recording operations on cloud resources. You can view the operation records of the last seven days on the CTS console.
+
This section describes how you can query or export the operation records of the last seven days on the CTS console.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the upper left corner of the page, click
to go to the service list. Under Management & Deployment, click Cloud Trace Service. - In the navigation pane on the left, choose Trace List
- Specify filters as needed. The following filters are available:
Figure 1 Filters
+- Trace Source, Resource Type, and Search By
Select filters from the drop-down list.
+After you select Trace name for Search By, you also need to select a trace name.
+After you select Resource ID for Search By, you also need to select or enter a resource ID.
+After you select Resource name for Search By, you also need to select or enter a resource name.
+ - Operator: Select a specific operator (at the user level rather than the tenant level).
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Search time range: In the upper right corner, choose Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range.
+
- Click the arrow on the left of the required trace to expand its details.
- Click View Trace in the Operation column to view trace details.
+
+
Use IAM to implement fine-grained permissions control for your Cloud Connect resources. With IAM, you can:
+
- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing Cloud Connect resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Entrust an account or cloud service to perform efficient O&M on your Cloud Connect resources.
+
Skip this part if you do not require individual IAM users for refined permissions management.
+
Figure 1 shows the process of granting permissions.
+
Prerequisites
Before you assign permissions to a user group, you need to know the permissions that you can assign to the user group and select permissions based on service requirements. For details about the system permissions, see Permissions. For the system policies of other services, see System Permissions.
+
+
Process Flow
Figure 1 Process of granting permissions
+
- Create a user group and assign permissions (the Cross Connect Administrator policy used as an example).
- Create an IAM user and add it to a group.
On the IAM console, create a user and add it to the user group created in 1.
+ - Log in and verify permissions.
After logging in to the Cloud Connect console using the user's credentials, verify that the user has all permissions for Cloud Connect resources.
+- In the service list, choose Network > Cloud Connect. In the navigation pane on the left, choose Cloud Connect > Central Networks. Click Create Central Network in the upper right corner. If the creation is successful, the Cross Connect Administrator policy has taken effect.
- Choose any other service in the service list. A message will appear indicating that you have sufficient permissions to access the service.
+
+
+
Custom policies can be created to supplement the system-defined policies.
+
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: Create a JSON policy or edit an existing one.
+
For details, see Creating a Custom Policy. The following section contains examples of common custom policies.
+
Example Custom Policies
- Example 1: Allowing users to delete central networks
{
+ "Version": "1.1",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "cc:centralNetwork:delete"
+ ]
+ }
+ ]
+}
+ - Example 2: Denying the deletion of central network policies
A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
+The following method can be used if you need to assign permissions of the CC FullAccess policy to a user but also forbid the user from deleting central network policies. Create a custom policy and assign both policies to the group that the user belongs to. Then the user can perform all operations on Cloud Connect resources except deleting central network policies. The following is an example of a deny policy:
+{
+ "Version": "1.1",
+ "Statement": [
+ {
+ "Effect": "Deny",
+ "Action": [
+ "cc:centralNetwork:deletePolicy"
+ ]
+ }
+ ]
+}
+ - Example 3: Create a custom policy containing multiple actions.
A custom policy can contain the actions of multiple services that are of the global or project-level type. The following is an example policy containing actions of multiple services:
+{
+ "Version": "1.1",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "cc:centralNetwork:create",
+ "cc:centralNetwork:update",
+ "cc:centralNetwork:delete",
+ "cc:centralNetwork:get"
+ ]
+ },
+ {
+ "Effect": "Allow",
+ "Action": [
+ "er:instances:create",
+ "er:instances:update",
+ "er:instances:delete",
+ "er:instances:get"
+ ]
+ }
+ ]
+}
+
+
+
Central Network
Relying on the cloud backbone network, a central network allows you to easily set up a reliable, intelligent enterprise-grade network and manage global network resources on premises and on the cloud. By setting up a central network, you can enable communication between enterprise routers, in the same region or different regions.
+
+
Application Scenarios
- Cross-region communication on the cloud: Enterprise routers in different regions are added to a central network as attachments so that resources in these regions can communicate with each other over one network.
Figure 1 Cross-region communication between enterprise routers
+ - Global network: By flexibly changing the central network policies, you can build a global network more conveniently.
+
+
Central Network Constraints
- To use a central network, the following resources must have been created:
- Enterprise router: used to set up a central network
If you are not the owner of an enterprise router, you cannot use the enterprise router to set up a central network.
+
+
+ - Policy management
- A central network can only have one policy. If you apply another policy for this central network, the policy that was previously applied will be automatically cancelled.
- In each policy, only one enterprise router can be added for a region. All added enterprise routers can communicate with each other by default.
- A policy that is being applied or cancelled cannot be deleted.
+ - Cross-site connection bandwidth management
- A cross-site connection bandwidth cannot be changed or deleted when it is being created, updated, deleted, frozen, unfrozen, or is recovering.
- The total of cross-site connection bandwidths cannot exceed the global connection bandwidth.
- If a cross-site connection bandwidth is deleted, you will still be billed for the global connection bandwidth.
+
+
+
Configuration Process
Figure 2 shows the process of configuring a central network to manage global network resources.
+
Figure 2 Central network configuration process
+
+
Table 1 Steps for configuring a central networkNo.
+ |
+Step
+ |
+Description
+ |
+Reference
+ |
+
|---|
+
+1
+ |
+Create a central network.
+ |
+After an enterprise router is created, you can create a central network and add the enterprise router to a policy of the central network. In this way, resources can communicate with each other across regions, and network resources in each region can be managed centrally.
+ |
+Creating a Central Network
+ |
+
+2
+ |
+Assign cross-site connection bandwidth.
+ |
+After adding enterprise routers in different regions to the same policy, purchase a global connection bandwidth and assign a bandwidth for cross-site connections.
+ |
+Assigning a Cross-Site Connection Bandwidth
+ |
+
+
+
+
+
+
Scenarios
After an enterprise router is created, you can create a central network and add the enterprise router to a policy of the central network. In this way, resources can communicate with each other across regions, and network resources in each region can be managed centrally.
+
+
Constraints
- Before building a central network, you need to create enterprise routers and enable Default Route Table Association and Default Route Table Propagation for them.
+
+
Creating a Central Network
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- In the upper right corner of the page, click Create Central Network.
- Enter the name and description and then configure policies for the central network. Table 1 describes the parameters required for creating a central network.
Figure 1 Creating a central network
+
+
Table 1 Parameters for creating a central networkParameter
+ |
+Setting
+ |
+
|---|
+
+Name
+ |
+Enter a name for the central network.
+ |
+
+Description
+ |
+Describe the central network for easy identification.
+ |
+
+Policy
+ |
+- Region
Add a policy to record your configuration. You need to select a region for the policy.
+ - Enterprise Router
Add only one enterprise router for a region. All added enterprise routers can communicate with each other by default.
+ NOTE: Please select all the ERs which needs to be connected in one go in Create Central Network page.
+
+10 kbit/s of bandwidth is provided for testing connectivity between enterprise routers.
+
+ |
+
+
+
+
+
- Click OK.
+
+
Viewing a Central Network
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- In the central network list, click the name of the target central network.
- On the Basic Information tab, you can view the details about the central network.
Figure 2 Viewing the basic information about a central network
+
+
+
Modifying a Central Network
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- In the central network list, click the name of the target central network.
- On the Basic Information page, you can change the name and description of the central network.
+
+
Deleting a Central Network
- Log in to the management console.
- Click in the upper left corner to select a region and a project.
- In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- In the central network list, locate the central network you want to delete and click Delete in the Operation column.
- In the displayed dialog box, enter DELETE to confirm the deletion.
Figure 3 Deleting a central network
+
+
+
Scenarios
Policies record the enterprises routers that have been added to a central network to allow you to better manage your network. You can apply policies of any version.
+
+
Constraints
- A central network can only have one policy. If you apply another policy for this central network, the policy that was previously applied will be automatically cancelled.
- In each policy, only one enterprise router can be added for a region. All added enterprise routers can communicate with each other by default.
- A policy that is being applied or cancelled cannot be deleted.
+
+
Creating a Policy
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- Locate the central network and click its name.
- On the Policies tab, click Add Policy.
- Select the target region and enterprise router in that region.
You can click Add Enterprise Router to add an enterprise router in another region.
+Figure 1 Creating a policy
+ - Click OK.
+
+
Applying a Policy
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- Locate the central network and click its name.
- On the Policies tab, locate the policy you want to apply and click Apply on the right.
Figure 2 Applying a policy
+ - In the Policy Changes area on the right, check the change of the enterprise router in the policy.
- Click OK.
+
+
Deleting a Policy
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- Locate the central network and click its name.
- On the Policies tab, locate the policy you want to delete and click Delete on the right.
Figure 3 Deleting a policy
+ - In the displayed dialog box, click OK.
+
+
Scenarios
Enterprise routers in different regions added to the same policy can communicate with each other after you purchase a global connection bandwidth and assign cross-site connection bandwidths for these network resources.
+
+
Constraints
- Changing Cross-Site Connection Bandwidth and Deleting a Cross-Site Connection Bandwidth cannot be performed when a cross-site connection is being created, updated, deleted, frozen, unfrozen, or is recovering.
- The total of cross-site connection bandwidths cannot exceed the global connection bandwidth.
- Cross site connection bandwidths are displayed only when a central network is created with at least 2 enterprise routers (1 per region) under policies.
+
+
Assigning a Cross-Site Connection Bandwidth
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- Locate the central network and click its name.
- Click the Cross-Site Connection Bandwidths tab.
- Locate the cross-site connection and click Assign now in the Global Connection Bandwidth column.
- On the Assign Bandwidth page, select the global connection bandwidth.
You can also click create Now if there are no available global connection bandwidths.
+Figure 1 Assigning a cross-site connection bandwidth
+ - Enter the bandwidth.
- Click OK.
+
+
Viewing Monitoring Metrics of Cross-Site Connection Bandwidths
You can view the status of each cross-site connection bandwidth assigned for communication between network resources.
+
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- Locate the central network and click its name.
- Switch to the Cross-Site Connection Bandwidths tab and click the icon in the Monitoring column to view the monitoring data.
Figure 2 Cross-site connection bandwidth monitoring
+
+
By setting up a central network, you can enable communications between enterprise routers in the same region or across regions. When a central network is used, attachments on the enterprise routers used in the central network policy will be monitored. For details about monitoring, see Central Network Metrics.
+
+
+
Changing Cross-Site Connection Bandwidth
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- Locate the central network and click its name.
- Click the Cross-Site Connection Bandwidths tab.
- Locate the cross-site connection and click Change Bandwidth in the Operation column.
- In the displayed dialog box, change the global connection bandwidth of the cross-site connection.
You can also change the bandwidth of the cross-site connection.
+Figure 3 Modifying a bandwidth
+ - Click OK.
+
+
Deleting a Cross-Site Connection Bandwidth
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- Locate the central network and click its name.
- Click the Cross-Site Connection Bandwidths tab.
- Locate the cross-site connection and click Delete Bandwidth in the Operation column.
- In the displayed dialog box, click OK.
Figure 4 Deleting a cross-site connection bandwidth
+ - Click Go to Delete to delete the global connection bandwidth if you no longer need it to avoid unnecessary charges.
Figure 5 Confirming whether to delete the global connection bandwidth
+
+
After you delete a cross-site connection bandwidth, you still need to pay for the global connection bandwidth.
+
+
+
Global Connection Bandwidth
A global connection bandwidth is used by instances to allow communication over the backbone network.
+
+
+
Table 1 Global connection bandwidth typesBandwidth Type
+ |
+Instance Type
+ |
+Description
+ |
+Scenario
+ |
+
|---|
+
+Geographic-region
+ |
+Central network
+ |
+Select this type of bandwidth if you need communication within a geographic region.
+ |
+Enterprise routers on a central network must be in the same geographic region.
+ |
+
+
+
+
+
Constraints on Global Connection Bandwidths
- Instances that can be added to a global connection bandwidth must be in the same region as the bandwidth.
- A global connection bandwidth can only be used by instances of the same type. If you want another type of instances to use a global connection bandwidth that already has instances, you need to remove the instances first.
- To use a global connection bandwidth on a central network, you need to configure cross-site connections by referring to the following:
+
- Before an instance is removed from a global connection bandwidth, ensure the instance is not used to run workloads or establish network connectivity, or the workloads will be unavailable or the network will be interrupted.
- If a global connection bandwidth has been used to assign cross-site connection bandwidths for a central network, the global connection bandwidth cannot be unbound from the central network. You need to delete the cross-site connection bandwidths first.
- If a global connection bandwidth is in use by instances, it cannot be deleted.
+
+
Geographic-Region Bandwidth Application Scenario (Central Network)
In this example, enterprise routers are connected over a central network.
+
Enterprise router ER-A in Germany and enterprise router ER-B in Netherlands are from the same geographic region, so a geographic-region bandwidth can be used for communication between the two enterprise routers.
+
Figure 1 Cross-region communication between enterprise routers
+
+
Scenarios
This section describes how to create a global connection bandwidth for communication over the backbone network.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Intra-Cloud > Global Connection Bandwidths.
- Click Create Global Connection Bandwidth.
- Configure the parameters based on Table 1.
Figure 1 Creating a global connection bandwidth
+
+
Table 1 Parameters required for creating a global connection bandwidthParameter
+ |
+Description
+ |
+
|---|
+
+Bandwidth Type
+ |
+Mandatory
+Only geographic-region bandwidths are supported. You need to select a geographic region and specify the regions that need to communicate with each other.
+ |
+
+Geographic Region
+ |
+Only Europe is supported if Geographic-region is selected for Bandwidth Type.
+ |
+
+Connect Regions
+ |
+Regions that need to communicate with each other in a geographic region.
+ |
+
+Billed By
+ |
+Mandatory
+The price of a global connection bandwidth varies by its size.
+- After a bandwidth is purchased, the billing starts immediately regardless of whether the bandwidth is used.
- If a bandwidth is no longer required, delete it in a timely manner to avoid unnecessary fees.
+ |
+
+Bandwidth
+ |
+Mandatory
+Select the bandwidth, in Mbit/s.
+ |
+
+Bandwidth Name
+ |
+Mandatory
+Enter the name of the bandwidth. The name: - Must contain 1 to 64 characters.
- Can contain letters, digits, underscores (_), hyphens (-), and periods (.).
+ |
+
+Enterprise Project
+ |
+Mandatory
+Provides a cloud resource management mode, in which cloud resources and members are centrally managed by project.
+ |
+
+
+
+
+
- Click Next.
- Confirm the configurations and click Submit.
The global connection bandwidth list page is displayed.
+ - In the global connection bandwidth list, view the status of the bandwidth.
If the bandwidth status becomes Normal, the creation is successful.
+
+
+
Scenarios
Central networks can use global connection bandwidths for communication.
+
+
Constraints
- Instances that can be added to a global connection bandwidth must be from the same region as the bandwidth.
- A global connection bandwidth can only be used by instances of the same type. If you want another type of instances to use a global connection bandwidth that already has instances, you need to remove the instances first.
- You can bind one global connection bandwidth to or unbind it from a central network at a time.
+ - To use a global connection bandwidth on a central network, you need to configure cross-site connections by referring to the following:
+
+
+
Using a Global Connection Bandwidth on a Central Network
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- In the central network list, click the name of the target central network.
- Click the Cross-Site Connection Bandwidths tab.
- Locate the cross-site connection and click Assign now in the Global Connection Bandwidth column.
- On the Assign Bandwidth page, select the global connection bandwidth.
- Specify the bandwidth and click OK.
+
+
Scenarios
You can unbind a global connection bandwidth from a central network.
+
+
Constraints
- Before an instance is removed from a global connection bandwidth, the instance is not used to run workloads or establish network connectivity, or the workloads will be unavailable or the network will be interrupted.
- A global connection bandwidth can only be used by one type of instances. If you want to change the instance type, remove all the instances from the global connection bandwidth and then add instances of another type by referring to Adding Instances to a Global Connection Bandwidth.
- If a global connection bandwidth has been used to assign cross-site connection bandwidths for a central network, the global connection bandwidth cannot be unbound from the central network. You need to delete the cross-site connection bandwidths first.
+
+
Deleting Cross-Site Connection Bandwidth
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Cloud Connect > Central Networks.
- In the central network list, click the name of the target central network.
- Click the Cross-Site Connection Bandwidths tab.
- Locate the cross-site connection and click Delete Bandwidth in the Operation column.
- In the displayed dialog box, click OK.
+
+
Scenarios
This section describes how to modify a global connection bandwidth.
+
You can only modify the bandwidth name and bandwidth. If you modify the bandwidth, the new bandwidth takes effect immediately.
+
+
Modifying a Global Connection Bandwidth
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Intra-Cloud > Global Connection Bandwidths.
- Locate the global connection bandwidth and click Modify Bandwidth in the Operation column.
- On the Modify Global Connection Bandwidth page, modify the bandwidth name and bandwidth and click Next.
- Confirm the information and click Submit.
+
+
Scenarios
If a pay-per-use global connection bandwidth is no longer needed, delete the bandwidth in a timely manner to avoid extra expenditures.
+
+
Constraints
If a global connection bandwidth is in use by instances, it cannot be deleted. Remove the instances from the global connection bandwidth first.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner to select a region and a project. - In the service list, choose Network > Cloud Connect.
- In the navigation pane on the left, choose Intra-Cloud > Global Connection Bandwidths.
- Locate the global connection bandwidth you want to delete and click Delete in the Operation column.
- In the displayed dialog box, click OK.
+
+
Scenarios
With CTS, you can record operations associated with central networks and global connection bandwidths for later query, audit, and backtracking.
+
+
Prerequisites
You have enabled CTS.
+
+
Key Operations Recorded by CTS
+
Table 1 Central network operations that can be recorded by CTSOperation
+ |
+Resource
+ |
+Trace
+ |
+
|---|
+
+Creating a central network
+ |
+centralNetwork
+ |
+createCentralNetwork
+ |
+
+Updating a central network
+ |
+centralNetwork
+ |
+updateCentralNetwork
+ |
+
+Deleting a central network
+ |
+centralNetwork
+ |
+deleteCentralNetwork
+ |
+
+Adding a central network policy
+ |
+centralNetworkPolicy
+ |
+createCentralNetworkPolicy
+ |
+
+Applying a central network policy
+ |
+centralNetworkPolicy
+ |
+applyCentralNetworkPolicy
+ |
+
+Deleting a central network policy
+ |
+centralNetworkPolicy
+ |
+deleteCentralNetworkPolicy
+ |
+
+Updating a central network connection
+ |
+centralNetworkConnection
+ |
+updateCentralNetworkConnection
+ |
+
+
+
+
+
+
Table 2 Global connection bandwidth operations recorded by CTSOperation
+ |
+Resource
+ |
+Trace
+ |
+
|---|
+
+Creating a global connection bandwidth
+ |
+globalConnectionBandwidth
+ |
+createGcBandwidth
+ |
+
+Updating a global connection bandwidth
+ |
+globalConnectionBandwidth
+ |
+updateGcBandwidth
+ |
+
+Deleting a global connection bandwidth
+ |
+globalConnectionBandwidth
+ |
+deleteGcBandwidth
+ |
+
+Binding a global connection bandwidth to an instance
+ |
+globalConnectionBandwidth
+ |
+bindGcBandwidth
+ |
+
+Unbinding a global connection bandwidth from an instance
+ |
+globalConnectionBandwidth
+ |
+unbindGcBandwidth
+ |
+
+
+
+
+
+