When different tenants create a VPC Peering, after the request is accepted, to make the VPCs of the Peering to communicate with each other, it is also necessary to add the route information of the peer VPC. Since a local tenant does not have the rights of the peer tenant, the local tenant can only add the local route information, and the corresponding peer route information needs to be added by the peer tenant. Adding route information for the local tenant is the same as adding route information for the peer tenant. The specific operation is as follows.

Operation Steps

Log in to the Console.
On the home page of the system, choose Network > VPC.
Select Peeringin the left navigation bar.
Find the name of the Peering whose route information needs to be added in the Created Peering List.
Click the name link of the Peering to enter the Peering details page.
On the VPC Peering details page, clickLocal Route.
In the Local Route tab area, click Add Local Route to add local route information. For parameter descriptions, see the table below.
Click OKto return to the Peering details page.
On the Peering details page, click Peer Route.
In thePeer Routetab area, click Add Peer Route to add peer route information.
Click OK to complete adding route information of the VPC Peering. After the Peering is established, you can use your private IP to communicate between the two VPCs. Use the "ping" command to check whether networks at both ends are connected.

Parameters	Descriptions
Destination address	Destination address, example of the value of the network segment or the subnet of the peer VPC: 192.168.0.0/24
Next hop address	Next hop address, i.e. Peering ID, which does not need to configure by default

VPC Peering Connection