Help Center> Enterprise Router> Best Practices> Using Enterprise Router and Cloud Connect Central Network to Allow Communications Among VPCs Across Regions> Procedure for Enabling Cross-Region VPC Communications over a Central Network> Verifying Network Connectivity
Updated on 2024-01-18 GMT+08:00
View PDF

Verifying Network Connectivity

  1. Log in to the ECS.

    Multiple methods are available for logging in to an ECS. For details, see Logging In to an ECS.

    In this example, use VNC provided on the management console to log in to an ECS.

  2. Verify the network connectivity between every two VPCs.

    1. Verify the network connectivity between VPCs.

      ping IP address of the ECS

      Use ECS-A as an example to verify the network connectivity between VPC-A and VPC-B:

      ping 192.168.0.5

      If information similar to the following is displayed, the communications between VPC-A and VPC-B are normal: 
      [root@ECS-A ~]# ping 192.168.0.5
PING 192.168.0.5 (192.168.0.5) 56(84) bytes of data.
64 bytes from 192.168.0.5: icmp_seq=1 ttl=62 time=30.6 ms
64 bytes from 192.168.0.5: icmp_seq=2 ttl=62 time=30.2 ms
64 bytes from 192.168.0.5: icmp_seq=3 ttl=62 time=30.1 ms
64 bytes from 192.168.0.5: icmp_seq=4 ttl=62 time=30.1 ms
...
--- 192.168.0.5 ping statistics ---
    2. Verify the network connectivity between VPCs.

      ping IP address of the ECS

      Use ECS-A as an example to verify the network connectivity between VPC-A and VPC-C:

      ping 10.0.0.29

      If information similar to the following is displayed, the communications between VPC-A and VPC-C are normal: 
      [root@ECS-A ~]# ping 10.0.0.29
PING 10.0.0.29 (10.0.0.29) 56(84) bytes of data.
64 bytes from 10.0.0.29: icmp_seq=1 ttl=62 time=27.4 ms
64 bytes from 10.0.0.29: icmp_seq=2 ttl=62 time=27.0 ms
64 bytes from 10.0.0.29: icmp_seq=3 ttl=62 time=26.10 ms
64 bytes from 10.0.0.29: icmp_seq=4 ttl=62 time=26.9 ms
...
--- 10.0.0.29 ping statistics ---

  3. Repeat 1 to 2 to verify the network connectivity between VPC-B and VPC-C.