Verifying the Network Connectivity and Reachability

Context

After the VPN configuration is complete, run the ping command with ipv6 vpn-instance vpn-instance-name on the PE to check whether the PE and the CE that belongs to the same VPN can communicate with each other. If the ping operation fails, you can use the tracert command with ipv6 vpn-instance vpn-instance-name to locate the fault.

If multiple interfaces bound with the same VPN exist on the PE, specify the source IP address, that is, -a source-ipv6-address when you ping the remote CE that accesses the peer PE. If you do not specify a source IP address, the PE selects the smallest IPv6 address of the interface bound to the IPv6 VPN on the PE as the source address of the ICMPv6 packet. If the CE does not have the route to the selected IPv6 address, the ICMPv6 packet sent back from the peer PE is discarded.

Procedure

Run the ping ipv6 host command to check whether the IPv6 network is correctly set up to send IPv6 packets from the transmitting end to the destination address.
Run the tracert ipv6 ipv6-host command to check the gateways through which the IPv6 packets are sent from the transmitting end to the destination address.
Run the ping [ ip ] [ -a source-ip-address | -c count | -d | -f | -h ttl-value | -i interface-type interface-number | -m time | -n | -p pattern | -q | -r | -s packetsize |-t timeout | -tos tos-value | -v | -vpn-instance vpn-instance-name ]^*host command to check whether the IPv4 backbone network is correctly set up to send IPv4 packets from the transmitting end to the destination address.
Run the tracert [ -a source-ip-address | -f first-ttl | -m max-ttl | -p port | -q nqueries | -vpn-instance vpn-instance-name | -w timeout ]^*host command to check the gateways through which the IPv4 packets are sent from the transmitting end of the IPv4 backbone network to the destination address of the IPv4 backbone network.