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

Reminder

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

upgrade
Knowledge Base

AR46 (PE) Fails to Ping a Remote CE

Publication Date:  2012-07-27  |   Views:  152  |   Downloads:  0  |   Author:  SU1001733364  |   Document ID:  EKB0000485506

Contents

Issue Description

 Network topology: E1/0/1 Et1/0/2
(JG)AR46(PE)--------------- NE40(PE)-bound to vpn1----------Z device CE)
|E1/0/8
|E0/0/1
(PE)AR46(BZS)
Phenomenon
If the AR46 (BZS) uses VPN1 and the IP address of the interface to which VPN1 is bound to ping the remote CE (a Z device), the ping is successful; if the AR46 (BZS) does not use the address of the interface to which VPN1 is bound and pings the remote CE, the ping fails.
<BZS-4620>ping -vpn-instance BGW 10.66.129.166
PING 10.66.129.166: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out
--- 10.66.129.166 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss
<BZS-4620>ping -a 10.66.149.254 -vpn-instance BGW 10.66.129.166
//If the interface to which VPN1 is bound is used as the source address, the device can ping the CE which is also in VPN1.
PING 10.66.129.166: 56 data bytes, press CTRL_C to break
Reply from 10.66.129.166: bytes=56 Sequence=1 ttl=254 time=3 ms
Reply from 10.66.129.166: bytes=56 Sequence=2 ttl=254 time=3 ms
Reply from 10.66.129.166: bytes=56 Sequence=3 ttl=254 time=3 ms
Reply from 10.66.129.166: bytes=56 Sequence=4 ttl=254 time=3 ms
Reply from 10.66.129.166: bytes=56 Sequence=5 ttl=254 time=3 ms
--- 10.66.129.166 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 3/3/3 ms
Another AR46 (PE) can ping the remote CE without using a source address.
<JG-4620>ping -vpn-instance BGW 10.66.129.166
PING 10.66.129.166: 56 data bytes, press CTRL_C to break
Reply from 10.66.129.166: bytes=56 Sequence=1 ttl=254 time=10 ms
Reply from 10.66.129.166: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 10.66.129.166: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 10.66.129.166: bytes=56 Sequence=4 ttl=254 time=1 ms
Reply from 10.66.129.166: bytes=56 Sequence=5 ttl=254 time=1 ms
--- 10.66.129.166 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/2/10 ms 
 

Alarm Information

 Null 

Handling Process

 All AR46s on the existing network are upgraded to VRP3.40202P11. Then, every AR46 (PE) to successfully ping the remote CEs without -a configured and with the bound VPN instance specified. 

Root Cause

 On the existing network with multiple AR46s deployed, only a part of AR46s can ping the remote CE. Based on statistics, AR46s running VRP3.40201 and later versions can ping the remote CE only if they use source addresses; AR46s running VRP3.40109 and VRP3.40017 can ping the remote CE without using source addresses. In addition, if more than one interface is bound to a VPN and the address to be pinged is in a different network segment from the source address, without -a configured, the ping fails. Based on the analysis of captured packets, if -a is not configured, the source address is 0.0.0.0 by default in the ping packets. The fault can be rectified in VRP3.40202P11. 

Suggestions

 Null