The MPLS-OPS Archive

[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index][Thread Index][Author Index][Subject Index]

REG: Traceroute problems on MPLS cores

From: "Vinod Anthony Joseph Cherunni" <vac@antarix.biz>
Date: Thu, 28 Mar 2002 17:49:30 +0530
Resent-Date: Thu, 28 Mar 2002 08:09:46 -0500
To: mpls-ops@mplsrc.com
X-MIMETrack: Serialize by Router on MEGREZ/DSQworld(Release 5.0.8 |June 18, 2001) at 03/28/200205:49:35 PM,Serialize complete at 03/28/2002 05:49:35 PM

Dear All,

I had made a few observations.

From a PE router (say PE1) , when i trace route to the loopback interface of another PE router (say PE3), I get the following output -

PE1#trace 211.8.1.12

Type escape sequence to abort.
Tracing the route to (211.8.1.12)

1 * * *
2 * * *
3 211.8.99.133 28 msec * 28 msec

(In this scenario, there are two P routers (P1, & P2) connecting PE 1 & PE3

PE1#sh ip cef 211.8.1.12
211.8.1.12/32, version 7573, cached adjacency to Serial2/0:1
0 packets, 0 bytes
tag information set
local tag: 28
fast tag rewrite with Se2/0:1, point2point, tags imposed: {51}
via 211.8.2.5, Serial2/0:1, 0 dependencies
next hop 211.8.2.5, Serial2/0:1
valid cached adjacency
tag rewrite with Se2/0:1, point2point, tags imposed: {51}

PE1#trace 211.8.1.3

Type escape sequence to abort.
Tracing the route to (210.4.0.3)

1 211.6.3.5 [MPLS: Label 58 Exp 0] 312 msec 32 4 msec 312 msec
2 211.6.3.2 304 msec * 304 msec

(In this scenario, P router P1 connects the two Provider Edge routers PE1, & PE2.)

PE1#sh ip cef 211.8.1.3
211.8.1.3/32, version 7567, cached adjacency to Serial2/0:1
0 packets, 0 bytes
tag information set, shared
local tag: 22
fast tag rewrite with Se2/0:1, point2point, tags imposed: {58}
via 211.8.2.5, Serial2/0:1, 17 dependencies
next hop 211.8.2.5, Serial2/0:1
valid cached adjacency
tag rewrite with Se2/0:1, point2point, tags imposed: {58}

What is the significance of the "tag information set / tag information set, shared.

Kindly advise what could be the issue here.

With warm regards,

Vinod.