No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


NE40 as the PE Cannot Successfully Ping the Peer VPN Gateway

Publication Date:  2019-07-17 Views:  146 Downloads:  0

Issue Description

The networking diagram is as follows:
In the MPLS VPN constituted by NE40-1 and NE40-2, the service runs normally on the VPN instance, vpn_112jiankong.
Add a segment of VPN "ip address" to the VPN instance of NE40-2, vpn_112jiankong.
NE40-1 has learned the new VPN segment:
disp bgp vpnv4 vpn-instance vpn_112jiankong routing-table
#^I            100         0/1083
# I                                            100         0/1083
However, the gateway of this VPN segment cannot be pinged on NE40-1.
<ne40-1->ping -vpn-instance vpn_112jiankong
PING 56 data bytes, press CTRL_C to break
Request time out
Request time out
100.00% packet loss

Alarm Information


Handling Process

1. The engineer found no problem when checking the configuration. The service flowed normally on the VPN instance, vpn_112jiankong. The new service could be provided easily as long as a VPN interface was added to NE40-2. Therefore, the problem must not be caused by the configuration.
2. The engineer carefully checked the VPN routing table of NE40-1, finding IP address overlapping in the new VPN segment.
#^I         100      0/1296
# I                                        100       0/1296

#^I           100         0/1083
# I                                           100        0/1083
After confirmation, the engineer learned that NE40/NE80 V3.10 2xxx routers did not support IP address overlapping in the VPN segments.
The engineer then solved the problem by modifying the corresponding VPN addresses.

Root Cause

1. Configuration.
2. Equipment. 


NE40/NE80 V3.10 2xxx routers do not support IP address overlapping in the VPN segments.
1. Try to avoid IP address overlapping.
2. Upgrade the version to V5 or V3.10 53XX.