Currently, VPN gateway and VPN tunnel collect data at a different interval. The statistical granularity of the VPN gateway is 1 minute, and that of the VPN tunnel is 10 seconds. Therefore, the statistical data shown on the monitoring page of the VPN gateway may be different from that of the VPN tunnel.
You can fully configure the IPsec VPN on the console. For more information, see Getting Started Overview.
You can log in to the VPC console to create a VPN gateway as instructed in Step 1: Create a VPN Gateway.
You can log in to the VPC console to create a VPN gateway as instructed in Step 3: Create a VPN Tunnel.
You can log in to the VPC console to query the VPN connection monitoring data as instructed in Viewing Monitoring Data.
You can log in to the VPC console to set a VPN connection alarm as instructed in Setting Alarms.
You can log in to the VPC console to query the VPN gateway details as instructed in Viewing a VPN Gateway.
You can log in to the VPC console to modify the VPN tunnel configuration as instructed in Modifying VPN Tunnel.
You can log in to the Anti-DDoS Pro console to bind an Anti-DDoS instance as instructed in Binding an Anti-DDoS Instance.
Note:
- Create the primary and secondary VPN tunnels before configuring health check to avoid affecting your business.
- The IP addresses of the VPN gateway and the customer gateway do not conflict. If the two IP addresses belong to one IP range, there is no need to configure a separate route to specify the customer gateway.
The outbound traffic of the VPN gateway will be charged. Delete the unused VPN gateway to avoid fee deduction.
Was this page helpful?