Configuration on the Cloud Console
Prerequisites
- A VPC and its subnets have been created on the management console.
Procedure
- Log in to the management console, and choose .
- Create a VPN gateway.
- Choose Buy VPN Gateway. , and click
- Set parameters as prompted.
Table 1 only describes the key parameters for creating a VPN gateway.
Table 1 VPN gateway parameters Parameter
Description
Value
Name
Name of a VPN gateway.
vpngw-001
Associate With
Select VPC.
VPC
VPC
VPC that the on-premises data center needs to access.
vpc-001(192.168.0.0/16)
Interconnection Subnet
Subnet used for communication between the VPN gateway and VPC. Ensure that the selected interconnection subnet has four or more assignable IP addresses.
192.168.2.0/24
Local Subnet
VPC subnets that the on-premises data center needs to access.
192.168.0.0/24,192.168.1.0/24
BGP ASN
BGP AS number.
64512
HA Mode
Working mode of the VPN gateway.
Active-active
Active EIP
EIP 1 used by the VPN gateway to access the on-premises data center.
1.1.1.2
Active EIP 2
EIP 2 used by the VPN gateway to access the on-premises data center.
2.2.2.2
- Create a customer gateway, that is, an AR router.
- Choose Create Customer Gateway. , and click
- Set parameters as prompted.
Table 2 only describes the key parameters for creating a customer gateway.
- Create VPN connections.
In this scenario, a VPN connection is created between the AR router and each of the active EIP and active EIP 2 of the VPN gateway.
- Choose Buy VPN Connection. , and click
- Create VPN connection 1.
Table 3 only describes the key parameters for creating a VPN connection.
Table 3 Parameter settings for VPN connection 1 Parameter
Description
Value
Name
Name of a VPN connection.
vpn-001
VPN Gateway
VPN gateway for which the VPN connection is created.
vpngw-001
Gateway IP Address
Active EIP bound to the VPN gateway.
1.1.1.2
Customer Gateway
Name of a customer gateway.
cgw-ar
VPN Type
Select Static routing.
Static routing
Customer Subnet
Customer-side subnet that needs to access the VPC on the cloud through VPN connections.
- A customer subnet cannot be included in any local subnet or any subnet of the VPC to which the VPN gateway is attached.
- Reserved VPC CIDR blocks such as 100.64.0.0/10 and 214.0.0.0/8 cannot be used as customer subnets.
172.16.0.0/16
Interface IP Address Assignment
- Manually specify
- Automatically assign
Manually specify
Local Tunnel Interface Address
Tunnel IP address of the VPN gateway.
169.254.70.2/30
Customer Tunnel Interface Address
Tunnel IP address of the AR router.
169.254.70.1/30
Link Detection
Whether to enable route reachability detection in multi-link scenarios. When enabling this function, ensure that the customer gateway supports ICMP and is correctly configured with the customer interface IP address. After this function is enabled, the VPN gateway automatically performs Network Quality Analysis (NQA) on the tunnel interface IP address of the customer gateway.
NQA enabled
PSK, Confirm PSK
The value must be the same as the PSK configured on the AR router.
Set this parameter based on the site requirements.
Policy Settings
The policy settings must be the same as those on the AR router.
- IKE Policy
- Version: v2
- Authentication Algorithm: SHA2-256
- Encryption Algorithm: AES-128
- DH Algorithm: Group 14
- Lifetime (s): 86400
- Local ID: IP Address
- Customer ID: IP Address
- IPsec Policy
- Authentication Algorithm: SHA2-256
- Encryption Algorithm: AES-128
- PFS: DH group 14
- Transfer Protocol: ESP
- Lifetime (s): 3600
- Create VPN connection 2.
For VPN connection 2, you are advised to use the same parameter settings as VPN connection 1, except the parameters listed in the following table.
Table 4 Parameter settings for VPN connection 2 Parameter
Description
Value
Name
Name of a VPN connection.
vpn-002
Gateway IP Address
Active EIP 2 bound to the VPN gateway.
2.2.2.2
Local Tunnel Interface Address
Tunnel IP address of the VPN gateway.
169.254.71.2/30
Customer Tunnel Interface Address
Tunnel IP address of the AR router.
169.254.71.1/30
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