The MPLS-OPS Archive

["zvika Gazit" <zvika@xpert.com>]

How is the 7200 and the provider connected peer knows each other ?

-----Original Message-----
From: Ran Liebermann [mailto:wan@inter.net.il] 
Sent: Thursday, September 11, 2003 1:44 PM
To: mpls-ops@mplsrc.com
Subject: RE: [MPLS-OPS]: mpls traceroute problems


Hello everybody,

I work with Amos.

I saw that his ASCII drawing got a little gibrished, so you can see the
network diagram here: http://www.karins.co.il/mpls/inter-as-mpls.gif

Thanks,
--
Ran.


> -----Original Message-----
> From: Amos Rosenboim
> Sent: Thursday, September 11, 2003 02:47
> To: mpls-ops@mplsrc.com
> Subject: [MPLS-OPS]: mpls traceroute problems
>
>
> Hi,
>
> I have a problem with mpls tracerote.
>
> My topology is:
>
>
> Pe (cisco 
> 7200)--------fastethernet----?P(cisco7400)------Oc3POS-------?
> ASBR(cisco12008)---------Oc3POS---?upstream provider (inter-as mpls 
> vpn). 213.8.43.8/30
> 213.8.45.220/30
> 63.218.13.12/30
>
> The problem is that when I trace from the PE router to the upstream 
> provider connected ip address ( 63.218.13.13) I get the following 
> output:
>
>
> PNV4#traceroute 63.218.13.13
>
> Type escape sequence to abort.
> Tracing the route to 63.218.13.13
>
> 1 * * *
> 2 * * *
> 3 63.218.13.13 148 msec * 148 msec
> VPNV4#
> Note: this address routing is in a /32 because of a bgp created host 
> route in the gsr.
>
> When tracing to other addresses which I have igp routing to, there is 
> no problem and the traceroute looks just fine:
>
> VPNV4#traceroute 192.116.202.99
>
> Type escape sequence to abort.
> Tracing the route to 192.116.202.99
>
> 1 213.8.43.10 [MPLS: Label 340 Exp 0] 4 msec 0 msec 0 msec
> 2 213.8.45.221 [MPLS: Label 14963 Exp 0] 328 msec 4 msec 0 msec 3 
> 192.117.180.9 200 msec 0 msec 4 msec 4 192.116.202.99 0 msec 0 msec 0 
> msec VPNV4#
>
>
> Routing and mpls label information looks ok to me.
>
> 7200 PE label info:
> VPNV4#sh mpls forwarding-table 63.218.13.13
> Local Outgoing Prefix Bytes tag Outgoing
> Next Hop
> tag tag or VC or Tunnel Id switched interface
>
> 3705 3700 63.218.13.13/32 0 Fa0/0
> 213.8.43.10
> VPNV4#
>
> 7400 P label info:
> PXF#sh mpls forwarding-table 63.218.13.13
> Local Outgoing Prefix Bytes tag Outgoing
> Next Hop
> tag tag or VC or Tunnel Id switched interface
>
> 3700 15331 63.218.13.13/32 600 PO1/0
> point2point
> PXF#
>
> 12008 ASBR label info:
> Eden#sh mpls forwarding-table 63.218.13.13
> Local Outgoing Prefix Bytes tag Outgoing
> Next Hop
> tag tag or VC or Tunnel Id switched interface
>
> 15331 Pop tag 63.218.13.13/32 1692 PO0/3
> point2point
> Eden#
>
>
> What makes it even stranger to me is that if I traceroute inside the 
> vrf, it seems ok: VPNV4#traceroute vrf PCCW-TEST 10.1.1.3
>
> Type escape sequence to abort.
> Tracing the route to 10.1.1.3
>
> 1 213.8.43.10 [MPLS: Labels 3700/536 Exp 0] 156 msec 156
> msec 156 msec
> 2 213.8.45.221 [MPLS: Labels 15331/536 Exp 0] 156 msec 156 msec 156 
> msec 3 63.218.13.13 [MPLS: Label 536 Exp 0] 156 msec 156 msec 152 msec
> 4 63.218.12.89 [MPLS: Labels 185/1055 Exp 0] 156 msec 156
> msec 156 msec
> 5 63.218.12.38 [MPLS: Labels 12675/1055 Exp 0] 156 msec 156
> msec 160 msec
> 6 63.216.0.29 [MPLS: Labels 13233/1055 Exp 0] 156 msec 156
> msec 156 msec
> 7 10.1.1.14 [MPLS: Label 1055 Exp 0] 148 msec 148 msec 148 msec
> 8 10.1.1.13 152 msec * 152 msec
> VPNV4#
>
>
> Any suggestions and explanations will be appreciated.
>
> Regards
> Amos Rosenboim
>
>
> -------
> 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

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.516 / Virus Database: 313 - Release Date: 01/09/2003
 


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