Thursday, December 6, 2018

Traceroute is different from regular ipv4 to mpls ipv4.

Scenario I'm pinging a host outside the MPLS network and I'm getting different result between regular ipv4 trace and mpls ipv4 trace?

Simple topology:

R9(9.9.9.9) --> R1(1.1.1.1) ----> (Partner provider) -----> 192.168.1.1

MPLS TRACE: PE-PE

traceroute mpls ipv4 1.1.1.1/32 source 9.9.9.9 exp 1
 Thu Dec  6 16:40:12.070 GMT
Tracing MPLS Label Switched Path to 
  0 x.x.x.x MRU 9202 [Labels: 34784/implicit-null Exp: 1/1]
L 1 xxxx MRU 9000 [Labels: 34714/implicit-null Exp: 1/1] 4 ms
L 2 xxxx MRU 9202 [Labels: 32607/implicit-null Exp: 1/1] 250 ms
L 3 x.x.x.x MRU 9202 [Labels: implicit-null/implicit-null Exp: 1/1] 266 ms
! 4 1.1.1.1 220 ms

IPV4 TRACE: PE-CE

1 x.x.x.x [MPLS: Labels 34784/22894 Exp 0] 291 msec 289 msec 288 msec

2 x.x.x.x [MPLS: Labels 34714/22894 Exp 0] 288 msec 287 msec 288 msec

3 x.x.x.x [MPLS: Labels 32607/22894 Exp 0] 289 msec 287 msec 288 msec

4 x.x.x.x [MPLS: Label 22894 Exp 0] 286 msec 287 msec 286 msec

5 x.x.x.x [MPLS: Label 21239 Exp 0] 287 msec 286 msec 286 msec

6 x.x.x.x msec 287 msec 286 msec

Comparing the latency, just want to ask that when regular trace, The mpls path will use the destination latency?

Thanks



No comments:

Post a Comment