Peering in the Connected state is not a guarantee that the connection between the two VPC Networks is functioning (especially if you manually configured the CIDR values); it only confirms that you linked the two networks using peering routes.
After correctly configuring peering and creating peering routes between two VPC Networks, it is essential to test the connection to ensure that network traffic flows correctly.
There are multiple ways to verify this, depending on the resources present within the VPC Networks. Here are some use cases:
- VMs in the VPC Networks
- Access a VM in one VPC Network via SSH or RDP;
- run the ping command to the IP address of a VM in the other VPC Network;
- if you receive a reply, the peering configuration is correct;
- Application communicating between the VPC Networks
- Try connecting through its interface;
- if you receive a response, the peering configuration is correct;
- DNS configured for hostnames between the VPC Networks
- Access a VM in one VPC Network via SSH or RDP;
- run the nslookup command;
- if you receive a response, the peering configuration is correct;