Configuring Local Network Connectivity

Scenarios

Use a local gateway to connect the edge site to the on-premises system so that they can communicate with each other over a private network.

To establish network connectivity between the edge site and the on-premises system, you need to associate a VPC with the local gateway route table and add routes to the on-premises network in the route table. Test network connectivity by checking whether ECSs at the edge site can communicate with on-premises servers.

For the overall networking plan and requirements, see Overview and Networking Requirements.

Prerequisites

The edge site is in the Available state.

Configuring Routes Between the Edge Site and the On-premises System

1. Log in to the management console.
2. Click in the upper left corner and select a region.
3. Click . In the service list displayed, choose Content Delivery & Edge Computing > CloudPond, or enter CloudPond in the search box.

   The dashboard is displayed.

4. In the left navigation pane, choose Edge Sites.
5. Click the name of the edge site for which you want to create a VPC.
6. In the Available Cloud Services area, locate Virtual Private Cloud and click Create.
7. On the Create VPC page, configure the parameters.
   • Select Edge for AZ when you create a subnet.
   • For details, see Creating a VPC.

8. Confirm the configuration and click Create Now.
9. Click . In the service list displayed, choose Content Delivery & Edge Computing > CloudPond, or enter CloudPond in the search box.

   The dashboard is displayed.

10. In the left navigation pane, choose Local Gateways.
11. Locate the local gateway and click Manage Route Table in the Operation column.
12. On the Associated VPCs tab page, click Associate VPC.
13. In the Associate VPC dialog box, select the VPC that you just created.
14. Click OK.
15. On the Routes tab page, click Add Route.
16. Configure the parameters based on Table 1.

    Table 1 Parameter description

    Parameter	Description	Example Value
    IP Address Version	The value is fixed at IPv4. IPv6 addresses are not supported.	-
    Next Hop Type	Type of the next-hop resource. The value can be VPC or Local network. To enable network communications between an edge site and an on-premises system, you need to configure two routes. Select a VPC as the next hop for one route and the on-premises network as the next hop for the other route.	-
    Next Hop	Select the next hop. If Next Hop Type is set to VPC, select the VPC to be associated with the local gateway route table. If you set the Next Hop Type to Local network, select the local gateway used by the on-premises network.	-
    Destination	Enter the destinations. If you set Next Hop Type to VPC, enter the CIDR block of the VPC. You can set this parameter to the CIDR block of the subnet in the edge AZ or the CIDR block of the VPC. If you set it to the CIDR block of the VPC, the edge site connects to the on-premises network and the cloud so that the on-premises network can communicate with the cloud over a private network. If Next Hop Type is set to Local network, enter the CIDR block used by your on-premises network. The CIDR block used by your on-premises network cannot conflict with the VPC's CIDR block.	VPC: 10.0.3.0/24 or 10.0.0.0/16 On-premises network: 192.168.0.0/16

17. Click OK.

Testing Local Network Connectivity

In the following steps, a Windows ECS is used to test network connectivity.

1. Create an ECS named ECS03 in the edge AZ and place it in VPC01 (CIDR block: 10.0.3.0/24).
   • Select the same edge AZ you selected when you created the VPC. Configure other parameters as prompted.

     For details, see Purchasing an ECS with Customized Configurations.

   • Add inbound rules for the security group containing ECS03 to allow ICMP packets. By default, ICMP packets are allowed in the outbound direction. For details, see Security Group Configuration Examples.

2. Locate ECS03 and record its private IP address (for example, 10.0.3.110).
3. Log in to the on-premises server Server01 and ping ECS03.

   ping 10.0.3.110

4. Check the command output. If the ECS can be pinged, the network connectivity has been established. If the ECS cannot be pinged, locate the cause and contact the Huawei Cloud O&M team.

Testing Network Connectivity Between the On-Premises System and the Central AZ

If you have configured a route between the central AZ and your on-premises system (you have set Destination to the CIDR block of the VPC), or if you have added a route for the subnet of the on-premises network, your on-premises system can access cloud services in the central AZ through the VPC.

In the following steps, a Windows ECS is used to test network connectivity.

1. Create an ECS named ECS01 in the central AZ and place it in VPC01 (CIDR block: 10.0.0.0/16).
   • Select General for AZ.

     For details, see Purchasing an ECS with Customized Configurations.

   • Add inbound rules for the security group containing ECS01 to allow ICMP packets. By default, ICMP packets are allowed in the outbound direction. For details, see Security Group Configuration Examples.

2. Locate ECS01 and record its private IP address (for example, 10.0.1.110).
3. Log in to the on-premises server Server01 and ping ECS01.

   ping 10.0.1.110

4. Check the command output. If the ECS can be pinged, network connectivity has been established. If the ECS cannot be pinged, locate the cause and contact the Huawei Cloud O&M team.

Related Operations

• Testing Network Connectivity Between an Edge Site and the Central AZ
• Testing Network Connectivity Between an Edge Site and the Central AZ
• Managing Local Gateway Route Tables