VPN Gateway：Diagnose a VPN gateway

Category

Diagnostic item

Description

Configurations

Instance configurations

Checks whether a VPN gateway is being configured.

If a VPN gateway is being configured, wait until its status changes to Available before you perform an operation on the VPN gateway.

Version

Checks whether the VPN gateway is of the latest version.

We recommend that you upgrade your VPN gateway to the latest version. For more information, see Upgrade a VPN gateway.

IPsec negotiations

Checks the status of Phase 1 and Phase 2 negotiations for each IPsec-VPN connection on the VPN gateway.

If an exception occurs during the negotiations, see the solution displayed in the console or relevant topics for troubleshooting. For more information, see Troubleshoot IPsec-VPN connection issues.

VPN tunnel configurations

Checks whether the IPsec-VPN connections configured on the VPN gateway.

If the system detects that the required configuration items of a IPsec-VPN connection are missing, you need to configure the IPsec-VPN connection based on your network requirements. For more information, see Create and manage IPsec-VPN connections in single-tunnel mode or Create and manage IPsec-VPN connections in dual-tunnel mode.

CIDR block conflicts

Checks whether the destination CIDR blocks of the policy-based routes, destination-based routes, and Border Gateway Protocol (BGP) routes on the VPN gateway conflict with 100.64.0.0/10.

100.64.0.0/10 is reserved by Alibaba Cloud. Make sure that the destination CIDR blocks of the policy-based routes, destination-based routes, and BGP routes on the VPN gateway do not conflict with 100.64.0.0/10 or its subnets. Otherwise, the VPN gateway cannot work as expected.

If such conflicts exist, modify the conflicted CIDR blocks or use NAT Gateway for address translation. For more information, see Use a VPC NAT gateway and a VPN gateway to connect a data center and a VPC.

BGP consistency

Checks whether Phase 2 negotiations succeed but BGP negotiations failed.

If Phase 2 negotiations succeed but BGP negotiations fail, check the BGP configurations and transmission of BGP packets. For more information, see the "What do I do if the system prompts that Phase 2 negotiations succeeded but the BGP negotiation is in the Abnormal state?" section of the FAQ about IPsec-VPN connections topic.

Shared Phase 1 IPsec negotiations

Checks whether the configurations of multiple IPsec-VPN connections are the same if the IPsec-VPN connections share Phase 1 negotiations.

If multiple IPsec-VPN connections are associated with the same VPN gateway and customer gateway, and use the same Internet Key Exchange (IKE) version, the IPsec-VPN connections share the same Phase 1 negotiation. In scenarios in which multiple IPsec-VPN connections share the same Phase 1 negotiation, the IPsec-VPN connections must have the same Pre-Shared Key and IKE settings, including the version, negotiation mode, encryption algorithm, authentication algorithm, DH group, and SA lifetime (in seconds). This ensures that the IKE settings of each IPsec-VPN connection can be shared during IPsec negotiations.

Modify the IPsec-VPN connection configurations based on your business requirements to ensure that the IPsec-VPN connections use the same configurations. For more information, see the "Modify an IPsec-VPN connection" section of the Create and manage IPsec-VPN connections in single-tunnel mode topic.

Quotas

VPN gateway bandwidth usage

Checks whether the bandwidth usage of the VPN gateway reaches 80% of the upper limit.

If the bandwidth usage of the VPN gateway reaches 80% of the upper limit, you can upgrade the bandwidth of the VPN gateway based on your network requirements. For more information, see Upgrade or downgrade a VPN gateway.

Fees

Overdue payments

Checks whether the VPN gateway has overdue payments.

If the VPN gateway has overdue payments, add funds to your account.

Overdue payment alert

Checks whether the VPN gateway expires within seven days.

Routes

Unadvertised routes

Checks whether the VPN gateway has unadvertised policy-based or destination-based routes.

If unadvertised policy-based or destination-based routes exist, delete or advertise the routes based on your network communication requirements. For more information, see the Advertise a policy-based route and Delete a policy-based route sections of the "Configure policy-based routes" topic, or the Advertise a destination-based route and Delete a destination-based route sections of the "Manage destination-based routes" topic.

Improper BGP configurations

Checks whether the VPN gateway uses proper BGP configurations if an IPsec-VPN connection uses BGP.

• If an IPsec-VPN connection uses BGP, we recommend that you do not configure policy-based or destination-based routes. We recommend that you use BGP for networking.

• If an IPsec-VPN connection uses BGP, we recommend that you disable the health check feature.

• If an IPsec-VPN connection uses BGP, we recommend that you set the Routing Mode parameter of the IPsec-VPN connection to Destination Routing Mode.

VPN route configurations

• Checks whether required route configurations are missing for the VPN gateway when you use an IPsec-VPN connection.

  For more information about how to add destination-based routes, policy-based routes, or BGP configurations for the VPN gateway, see Configure policy-based routes, Manage destination-based routes, Create and manage IPsec-VPN connections in single-tunnel mode, or Create and manage IPsec-VPN connections in dual-tunnel mode.

• Checks whether automatic BGP route propagation is enabled for the VPN gateway if an IPsec-VPN connection uses BGP.

  FFor more information, see the Procedure section of the "Configure BGP dynamic routing" topic.

Destination-based route conflicts

Checks whether the destination CIDR blocks of destination-based routes on the VPN gateway overlap with each other.

If such conflicts exist, delete the conflicted destination-based routes and create new ones. Make sure that the destination CIDR blocks of destination-based routes do not overlap with each other. For more information, see Manage destination-based routes.

You can also use BGP for networking. For more information, see Connect a VPC to a data center in dual-tunnel and BGP routing mode.

Policy-based route conflicts

Checks whether the destination CIDR blocks of policy-based routes on the VPN gateway overlap with each other.

If such conflicts exist, delete the conflicted policy-based routes and create new ones. Make sure that the destination CIDR blocks of policy-based routes do not overlap with each other. For more information, see Configure policy-based routes.

You can also use BGP for networking. For more information, see Connect a VPC to a data center in dual-tunnel and BGP routing mode.

BGP route conflicts

• Checks whether the destination CIDR blocks of BGP routes overlap with each other.

• Checks whether the destination CIDR blocks of BGP routes and destination-based routes overlap.

• Checks whether the destination CIDR blocks of BGP routes and policy-based routes overlap.

If such conflicts exist, troubleshoot the issues by following the on-screen instructions displayed in the console.

Match between VPC routes and VPN routes

Checks whether the destination CIDR block of the route in a VPC route table that points to the VPN gateway overlaps with the destination CIDR block of the policy-based route on the VPN gateway.

Make sure that the destination CIDR block of the policy-based route contains the destination CIDR block of the route in the VPC route table that points to the VPN gateway.

If the preceding condition is not met, you need to modify the destination CIDR block of the policy-based route. You must delete the policy-based route and create a new one that meets the condition. For more information, see Configure policy-based routes.