Quantcast
Channel: Routing topics
Viewing all articles
Browse latest Browse all 2062

MPLS Traceroute [icmp-tunneling]

$
0
0

Hi All,

 

In the attached diagram, I have configured eBGP as a PE-CE routing protocol & MP-BGP is running in the MPLS backbone.

 

R1 & R6 can ping each others loopback interfaces via BGP.

 

But, the end-to-end traceroute is not working in this scenario since I can't see intermediate hops/labels. After some web search, I found that icmp-tunneling would help achieve proper traceroute result, but not really getting how does it work and why doesn't JunOS provide traceroute result with VPN/Transport label values by default.

 

Additionally, I would be thankful if someone can explain use case of "vrf-table-label" command under the VRF instance.

 

Your input will be hightly appreciated.

 

root@R1# run ping 6.6.6.6 source 1.1.1.1 count 5
PING 6.6.6.6 (6.6.6.6): 56 data bytes
64 bytes from 6.6.6.6: icmp_seq=0 ttl=63 time=1.409 ms
64 bytes from 6.6.6.6: icmp_seq=1 ttl=63 time=1.391 ms
64 bytes from 6.6.6.6: icmp_seq=2 ttl=63 time=1.836 ms
64 bytes from 6.6.6.6: icmp_seq=3 ttl=63 time=1.525 ms
64 bytes from 6.6.6.6: icmp_seq=4 ttl=63 time=1.590 ms

--- 6.6.6.6 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.391/1.550/1.836/0.161 ms

[edit]

root@R1# run traceroute 6.6.6.6 source 1.1.1.1
traceroute to 6.6.6.6 (6.6.6.6) from 1.1.1.1, 30 hops max, 40 byte packets
1 10.1.12.2 (10.1.12.2) 0.399 ms 0.452 ms 0.410 ms
2 * * *
3 6.6.6.6 (6.6.6.6) 1.484 ms 1.452 ms 1.073 ms

[edit]
root@R1#

 

Thanks!


Viewing all articles
Browse latest Browse all 2062

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>