The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Mar> msg00176



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

Re: REG: Traceroute problems on MPLS cores

  • From: "Krzysztof Szarkowicz" <kszarkowicz@freemail.hu>
  • Date: Tue, 26 Mar 2002 17:20:43 +0100
  • Cc: <mpls-ops@mplsrc.com>
  • Resent-Date: Tue, 26 Mar 2002 12:38:53 -0500
  • To: "Vinod Anthony Joseph Cherunni" <vac@antarix.biz>
  • X-OriginalArrivalTime: 26 Mar 2002 16:20:46.0428 (UTC) FILETIME=[2F4BD1C0:01C1D4E2]
  • X-Originating-IP: [212.222.244.14]

Hi,
 
what is your configuration of TTL propagation on P2?
 
Krzysztof
----- Original Message -----
Sent: Tuesday, March 26, 2002 2:35 PM
Subject: [MPLS-OPS]: REG: Traceroute problems on MPLS cores


Dear All,

I am facing a problem as given below.

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

But when I trace route from PE1 to another PE router PE2, The output is follows -

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.)

All other functions, such as MPLS VPN connectivity seem to be across all the PE routers, but only SMTP applications seem to be fail for (non Label switched traffic flowing from PE1 TO PE3).

Kindly advise, as why  this nature prevails.

With warm regards,

Vinod.