Networking Requirements

Updated on 2024-05-29 GMT+08:00

View PDF

Network Topology

Learn the definitions of edge gateway, local gateway, and VPN gateway in Basic Concepts before you proceed with the CloudPond network topology.

Figure 1 Network topology
Click to enlarge

An edge site connects to the cloud through the Internet or a private line. There are four network connections between the edge site and the cloud as shown in Table 1.

**Table 1** CloudPond network connections
Connection Name	Position in the Figure	Description
O&M connection	Blue line connected by public IP addresses (1) and (2)	This connection is used for O&M at the edge site. With this connection, the latest version of cloud services that can run on premises can be pushed to the edge site, platform status information can be collected for easy O&M, and image file used by the ECSs can be cached for the edge site. To ensure network reliability, two public IP addresses are required for dual-channel communications. Your data is not transmitted over this connection, ensuring data security and meeting data compliance requirements.
Service communication connection	Red line connected by public IP addresses (3) and (4)	This connection is used to transmit your data and management data between the edge site and the cloud. To ensure data security, network encryption technologies are used to encrypt your data transmitted over this connection.
Connection for publishing Internet-accessible services	Green line connected using IP address (5)	This connection is used to provide services to Internet users. You need to purchase a public IP address from a carrier.
Connection for on-premises network communications	Black line in the on-premises data center	This connection is used by the edge site to communicate with other on-premises devices. To enable the edge site to communicate with the on-premises network, you need to configure routes.

Public IP Addresses describes the public IP addresses required for network communications between an edge site and the cloud.

With the four connections, the following can be achieved:

ECS 3 at the edge site can communicate with ECS 1 and ECS 2 on the cloud over a private network.
ECS 3 at the edge site can communicate with on-premises network devices over a private network.
ECS 3 can use IP address (5) to provide web services for Internet users.
The Huawei Cloud O&M team can use the O&M connection to monitor the edge site status. For example, if the disk of a server is damaged, the Huawei Cloud O&M team can receive a warning and arrange replacement in a timely manner.

Public IP Addresses

**Table 2** Public IP addresses for network communications between the edge site and the cloud
No.	Category	Quantity	Provider	Description
(1)	Management EIP used by the cloud	2	Huawei Cloud	Used to connect to the active-active VPN gateways on the cloud
(2)	Management public IP address used at the edge site	2	Customer	Purchase public IP addresses from a carrier for interconnecting with the management plane of the cloud. For each public IP address, the minimum downlink bandwidth and the minimum uplink bandwidth are 100 Mbit/s and 30 Mbit/s, respectively.
(3)	EIP used by the cloud for interconnection with the edge site	1	Customer	The EIP is used by an ECS on the cloud to communicate with the edge site. The bandwidth is at least 10 Mbit/s.
(4)	Edge site public IP address for interconnection with the cloud	1	Customer	Purchase a public IP address and the same bandwidth from the same carrier you select when buying the EIP used by the cloud for interconnection with the edge site.

**Table 3** Public IP addresses for providing Internet-accessible services
No.	Category	Quantity	Provider	Description
(5)	Public IP addresses for service release	0-N	Customer	Used to provide services accessible from the Internet. You need to purchase public IP addresses from a carrier. Contact the Huawei Cloud O&M team to record the carrier's line information (public IP address and bandwidth) into CloudPond. Buy an EIP for each of your public IP addresses on the EIP console. Locate your public IP addresses and bind them to the ECSs running at the edge site. For details, see Provisioning Cloud Resources to an Edge Site.