The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Mar> msg00063



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

RE: Cisco *ing out in traceroute

  • From: "Ohnmacht, Steve, WCS" <ohnmacht@att.com>
  • Date: Wed, 17 Mar 2004 11:00:25 -0500
  • Cc: <mpls-ops@mplsrc.com>
  • Resent-Date: Wed, 17 Mar 2004 11:39:17 -0500
  • Thread-Index: AcQKqp7EBVpyaF43QLWXGhx1xd595QBjMDNg
  • Thread-Topic: [MPLS-OPS]: Cisco *ing out in traceroute
  • To: "Luc De Ghein" <ldeghein@cisco.com>
  • X-MIME-Autoconverted: from quoted-printable to 8bit by host.secure4-hosting.net id i2HG0eKW003115

Nope...The junipers are going to be upgraded to 6.1 whatever, so the
anomaly with juniper's should disapear. I'm also guessing that the cisco
anomaly will as well, maybe not. Still would like to understand why the
cisco is *ing out. I haven't delved into this for a few days now, maybe
I'll keep digging and hopefully come up with something (will post
findings). Still will appreciate any assistance/insight you guys can
provide.

thanks!
-so




-----Original Message-----
From: Luc De Ghein [mailto:ldeghein@cisco.com]
Sent: Monday, March 15, 2004 9:28 AM
To: Ohnmacht, Steve, WCS
Cc: mpls-ops@mplsrc.com
Subject: Re: [MPLS-OPS]: Cisco *ing out in traceroute



Do you have 'ip verify unicast ...' on that PE?


Luc

> Hello -
> 
> I understand why the Juniper's are *ing out, but can anyone provide me
some insight as to why Hop 12 (PE-Cisco) is *ing out? Below are some
sample traces (the traces traverse 2 ASs). I hope this is clear ;-)..
> 
> Forward Trace:
> 
> CE-Router>traceroute x.x.x.x
> 
>   1 x.x.x.x 80 msec 208 msec 116 msec <==== PE
>   2 x.x.x.x [MPLS: Labels 477/14694 Exp 0] 132 msec 128 msec 132 msec
>   3 x.x.x.x [MPLS: Labels 32767/14694 Exp 0] 128 msec 136 msec 128
msec
>   4 x.x.x.x [MPLS: Labels 32762/14694 Exp 0] 132 msec 128 msec 132
msec
>   5 x.x.x.x [MPLS: Labels 32755/14694 Exp 0] 128 msec 128 msec 128
msec 
>   6 x.x.x.x [MPLS: Labels 32726/14694 Exp 0] 128 msec 132 msec 132
msec <==== pop BB label
>   7 x.x.x.x [MPLS: Label 14694 Exp 0] 128 msec 128 msec 128 msec <====
leaving local AS - pop VPN label
>   8 x.x.x.x [MPLS: Label 13169 Exp 0] 128 msec 128 msec 128 msec <====
entering remote AS
>   9  *  *  * <==== JUNIPER
>  10  *  *  *  <==== JUNIPER
>  11  *  *  *  <==== JUNIPER <===== pop BB label
>  12  *  *  * <==== PE-CISCO - why is the cisco *ing out????
>  13 x.x.x.x [AS XXX] 128 msec *  132 msec <==== remote CE
> 
> 
> 
> Reverse Trace:
> 
> 
> CE-Router>traceroute x.x.x.x
> 
>   1 x.x.x.x 4 msec 0 msec 0 msec <==== PE
>   2  *  *  *  <===== JUNIPER
>   3 x.x.x.x [MPLS: Labels 12616/13379 Exp 0] 132 msec 132 msec 132
msec <=== This "P" router -Cisco is not exhibiting behavior
>   4 x.x.x.x [MPLS: Label 13379 Exp 0] 128 msec 132 msec 128 msec
>   5 x.x.x.x [MPLS: Label 15097 Exp 0] 132 msec 132 msec 128 msec
>   6 x.x.x.x [MPLS: Labels 32651/2428 Exp 0] 132 msec 132 msec 132 msec
>   7 x.x.x.x [MPLS: Labels 32695/2428 Exp 0] 128 msec 132 msec 132 msec
>   8 x.x.x.x [MPLS: Labels 32497/2428 Exp 0] 128 msec 132 msec 132 msec
>   9 x.x.x.x [MPLS: Labels 32486/2428 Exp 0] 132 msec 132 msec 132 msec
>  10 x.x.x.x [MPLS: Labels 32577/2428 Exp 0] 132 msec 128 msec 132 msec
>  11 x.x.x.x [MPLS: Labels 404/2428 Exp 0] 132 msec 132 msec 132 msec 
>  12 x.x.x.x [AS XXX] [MPLS: Label 2428 Exp 0] 128 msec 128 msec 128
msec <==== PE
>  13 x.x.x.x [AS XXX] 128 msec *  128 msec <==== CE
> 
> 
> Thanks!
> -so
> 
> 
> 
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml