All Products
Search
Document Center

Virtual Private Cloud:Check the connectivity of VPC peering connections

Last Updated:Apr 11, 2024

This topic describes how to use the reachability analyzer to check the connectivity of a Virtual Private Cloud (VPC) peering connection.

Prerequisites

  • Network Intelligence Service (NIS) is activated. You can activate NIS on the Service activation page.

  • If this is the first time that you perform an instance diagnostic, the system automatically creates the service-linked role AliyunServiceRoleForNis. For more information, see Service-linked roles.

  • A VPC peering connection is created. For more information, see Create and manage a VPC peering connection.

Procedure

  1. Log on to the VPC console.

  2. In the left-side navigation pane, click VPC Peering Connection.

  3. In the top navigation bar, select the region of the VPC peering connection.

  4. On the VPC Peering Connection page, find the VPC peering connection and choose one of the following methods to use the reachability analyzer.

    • In the Diagnose column, choose Diagnose > Reachability Analyzer. In the Reachability Analyzer panel, specify the parameters.

    • Click the ID of the VPC peering connection. On the Reachability Analyzer tab, specify the parameters.

  5. Specify the source instance type, destination instance type, source instance ID, destination instance ID, protocol, destination port, and path name, and then click Start Analyzing.

    After the analysis is complete, the system displays hop-by-hop details of the virtual network path between the source instance and the destination instance.

    • If the destination is inaccessible, the reachability analyzer pinpoints the error and the cause of the error.

    • If the destination is accessible, you can click reverse path analytics to go to the Start Analyzing page in the Network Intelligence Service (NIS) console. On this page, specify the parameters and click Start Analyzing. This allows you to check the connectivity of the reverse path.

    During the analysis process, testing data packets are sent instead of service data packets. Therefore, your services are not affected.

Example

As shown in the following figure, the reachability analyzer checks the connectivity in two directions: from the requester VPC to the accepter VPC and from the accepter VPC to the requester VPC.

image

Specify the following parameters:

Parameter

Description

Source

Specify Source Type.

In this example, ECS Instance ID is selected and ECS1 is selected.

Destination

Specify Destination Type.

In this example, ECS Instance ID is selected and ECS2 is selected.

Protocol

Select a protocol.

In this example, the default protocol TCP is used.

Note

Select a protocol and a destination port based on the actual network environment.

Destination Port

Enter the port number of the destination resource.

In this example, the default value 80 is used.

Name

Enter a name for the path from the source to the destination.

References

  • For more information about the reachability analyzer, see Work with the reachability analyzer.

  • You can use the troubleshooting feature to troubleshoot VPC connection exceptions, unexpected fees, and quota issues. For more information, see Troubleshooting.