Planning Networks and Resources
Data Plan
Category |
Item |
Data |
---|---|---|
VPC |
Subnet to be interconnected |
|
Enterprise router |
Enterprise router attached to VPC1 and VPC2. |
|
ECS |
Three ECSs are in different VPCs. If the ECSs are in different security groups, add rules to the security groups to allow access to each other. |
|
VPN gateway 1 |
Access subnet |
Subnet used for communication between the VPN gateway and VPCs. Ensure that the selected access subnet has four or more assignable IP addresses. 192.168.2.0/24 |
HA mode |
Active-active |
|
EIP |
EIPs are automatically generated when you buy them. By default, VPN gateway 1 uses two EIPs. In this example, the EIPs are as follows:
|
|
Tunnel interface addresses under Connection 1's Configuration |
IP addresses used to establish an IPsec tunnel between VPN gateway 1 and customer gateway 1. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
IP addresses used to establish an IPsec tunnel between VPN gateway 1 and customer gateway 2. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
|
|
Tunnel interface addresses under Connection 2's Configuration |
IP addresses used to establish an IPsec tunnel between VPN gateway 1 and customer gateway 1. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
IP addresses used to establish an IPsec tunnel between VPN gateway 1 and customer gateway 2. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
|
|
VPN gateway 2 |
Access subnet |
Subnet used for communication between the VPN gateway and VPCs. Ensure that the selected access subnet has four or more assignable IP addresses. 192.168.3.0/24 |
HA mode |
Active-active |
|
EIP |
EIPs are automatically generated when you buy them. By default, VPN gateway 2 uses two EIPs. In this example, the EIPs are as follows:
|
|
Tunnel interface addresses under Connection 1's Configuration |
IP addresses used to establish an IPsec tunnel between VPN gateway 2 and customer gateway 1. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
IP addresses used to establish an IPsec tunnel between VPN gateway 2 and customer gateway 2. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
|
|
Tunnel interface addresses under Connection 2's Configuration |
IP addresses used to establish an IPsec tunnel between VPN gateway 2 and customer gateway 1. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
IP addresses used to establish an IPsec tunnel between VPN gateway 2 and customer gateway 2. At the two ends of the IPsec tunnel, the configured local and remote tunnel interface addresses must be reversed.
|
|
On-premises data center |
Subnet to be interconnected |
172.16.0.0/16 |
Customer gateway 1 |
Public IP address |
Public IP address assigned by a carrier. In this example, the public IP address is as follows: 1.1.1.1 |
Customer gateway 2 |
Public IP address |
Public IP address assigned by a carrier. In this example, the public IP address is as follows: 2.2.2.1 |
IKE and IPsec policies |
PSK |
Test@123 |
IKE policy |
|
|
IPsec policy |
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot