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>

Reminder

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

upgrade

NE40 as the PE Cannot Successfully Ping the Peer VPN Gateway

Publication Date:  2012-07-27 Views:  61 Downloads:  0
Issue Description
The networking diagram is as follows:
NE40-1(PE1)---------P------NE40-2(PE2)
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 172.16.1.129 255.255.255.248" 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 172.16.1.128/29          60.222.0.17            100         0/1083
# I                                         60.222.0.17             100         0/1083
However, the gateway of this VPN segment cannot be pinged on NE40-1.
<ne40-1->ping -vpn-instance vpn_112jiankong 172.16.1.129
PING 172.16.1.129: 56 data bytes, press CTRL_C to break
Request time out
Request time out
100.00% packet loss 
 
Alarm Information
Null
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.
Route Distinguisher:218.26.135.54:138
#^I 172.16.1.128/29          60.222.0.241         100      0/1296
# I                                         60.222.0.241         100       0/1296

Route Distinguisher:218.26.135.6:129
#^I 172.16.1.128/29            60.222.0.17         100         0/1083
# I                                            60.222.0.17         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. 
 
Suggestions
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. 
 

END