Procedure for Setting Up a Hybrid Cloud Network Using an Enterprise Router and a Global DC Gateway

Step 1: Create Cloud Resources

Create an enterprise router, two service VPCs, two ECSs, as described in Table 5.

Create an enterprise router.
For details, see Creating an Enterprise Router.
Create two service VPCs.
For details, see Creating a VPC.
Create an ECS in each VPC.
In this example, the ECSs are used to verify the communications between the VPC and the on-premises data center. The ECS quantity and configuration are for reference only.

For details, see Overview.

Step 2: Attach the VPCs to the Enterprise Router

Attach the two service VPCs to the enterprise router.
For details, see Creating VPC Attachments for the Enterprise Router.
Check the routes with destinations set to the VPC CIDR blocks in the enterprise router route table.
In this example, Default Route Table Association and Default Route Table Propagation are enabled for the enterprise router, and routes with destinations set to VPC CIDR blocks are automatically added when you attach the VPCs to the enterprise router.

For details about enterprise router route planning, see Table 2 and Table 4. In this example, the next hops of the two routes are VPC-A and VPC-B, respectively.

To view enterprise routes, see Viewing Routes.
In the route tables of the two VPCs, add a route with the next hop set to the enterprise router and destination to the on-premises network CIDR block.
For details about VPC route planning, see Table 3. In this example, set the route destination to 10.1.123.0/24.

For details, see Adding Routes to VPC Route Tables.

Step 3: Attach the Global DC Gateway to the Enterprise Router

For details about Direct Connect resources, see Table 5.

Create a connection.
For details, see Creating a Connection.
Create a global DC gateway for the enterprise router.
1. On the Direct Connect console, perform the following operations:
  1. Create a global DC gateway.
  2. Create a virtual interface.
  3. Attach the global DC gateway to the enterprise router.
  For details, see Creating a Global DC Gateway.
2. On the Enterprise Router console, view the global DC gateway attachment created for the enterprise router.
  For details, see Viewing Details About an Attachment.
  
  If the status of the global DC gateway attachment is Normal, the attachment has been created.
  Default Route Table Association and Default Route Table Propagation are enabled when you create the enterprise router. After the global DC gateway is attached to the enterprise router, the system will automatically:
  - Associate the global DC gateway attachment with the default route table of the enterprise router.
  - Propagate the global DC gateway attachment to the default route table of the enterprise router. The routes to the on-premises data center are propagated to the route table.
    You can view routes to the on-premises data center in the route table of the enterprise router only after taking the following steps.

Configure routes on the network device in the on-premises data center to point to the Huawei Cloud.

The following uses a Huawei network device as an example to describe how to configure a BGP route.

bgp 64515

peer 10.0.0.1 as-number 64512

peer 10.0.0.1 password simple 12345678

network 10.1.123.0 255.255.255.0

**Table 1** BGP route
Command	Description
bgp 64515	Enables BGP. 64515 is the ASN used by the on-premises data center.
peer 10.0.0.1 as-number 64512	Creates a BGP peer. 10.0.0.1 is the gateway on the cloud. 64512 is the BGP ASN of the global DC gateway.
peer 10.0.0.1 password simple 12345678	Performs MD5 authentication on BGP messages when a TCP connection is established between BGP peers. 12345678 is the BGP MD5 authentication password.
network 10.1.123.0 255.255.255.0	Adds routes in the IP route table to the BGP route table. 10.1.123.0 is the network used by the on-premises data center. 255.255.255.0 is the subnet mask of the on-premises network.

Step 4: Verify Network Connectivity

Log in to the ECS.
Multiple methods are available for logging in to an ECS. For details, see Logging In to an ECS.

In this example, use VNC provided on the management console to log in to an ECS.
Verify the network connectivity.
1. Verify the network connectivity between VPCs.
  ping IP address of the ECS
  
  To verify the network connectivity between VPC-A and VPC-B, log in to ECS-A and run the following command:
  
  ping 172.16.1.137
  If information similar to the following is displayed, VPC-A can communicate with VPC-B through the enterprise router.
```
[root@ecs-A ~]# ping 172.16.1.137
PING 172.16.1.137 (172.16.1.137) 56(84) bytes of data.
64 bytes from 172.16.1.137: icmp_seq=1 ttl=64 time=0.849 ms
64 bytes from 172.16.1.137: icmp_seq=2 ttl=64 time=0.455 ms
64 bytes from 172.16.1.137: icmp_seq=3 ttl=64 time=0.385 ms
64 bytes from 172.16.1.137: icmp_seq=4 ttl=64 time=0.372 ms
...
--- 172.16.1.137 ping statistics ---
```
2. Verify the network connectivity between a VPC and the Direct Connect connection.
  ping IP address of the local gateway (on the cloud)
  
  ping IP address of the remote gateway (on premises)
  
  ping IP address used in the on-premises data center
  
  To verify the network connectivity between VPC-A and the local gateway on the cloud, log in to ECS-A and run the following command:
  
  ping 10.0.0.1
  
  If information similar to the following is displayed, the network between the VPC and the local gateway is connected.
```
[root@ecs-A ~]# ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.849 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.455 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.385 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.372 ms
...
--- 10.0.0.1 ping statistics ---
```
Repeat 1 to 2 to verify the network connectivity between the other VPC and the Direct Connect connection.