[c-nsp] MPLS is not working

[Peter Rathlev]

Hm... Strange. Can you do an MPLS trace from PE1 to PE2 and the other
way? For example "trace mpls ipv4 10.10.10.101 32" from PE2?

And just to be sure: How does the routing table on the CE-boxes look? I
guess they point towards the PE's (172.16.{1,2}.1), right?

Regards,
Peter


On Fri, 2008-02-29 at 18:42 -0500, Ahmed Mohamed wrote:
> Thanks Peter for the Respond,
>  
> i got your point regarding the MPLS forwarding table, thanks for
> clarification
>  
> i don't have the no form of the command "tag-switching ip
> propagate-ttl" configured
>  
> the network 170.5.1.0 is in CEA-1:
> =========================================================================
> CEA-1#sh ip int brie
> Interface                  IP-Address      OK? Method Status
> Protocol
> FastEthernet0/0            unassigned      YES NVRAM  administratively
> down down
> Serial1/0                  172.16.1.2      YES NVRAM  up
> up
> Serial1/1                  170.1.1.0       YES NVRAM  up
> up
> Serial1/2                  170.5.1.0       YES NVRAM  up
> up
> =========================================================================
> here is the output on it's PE:
>  
> ============================================================================
> PE1-AS1#sh ip cef vrf CustomerA 170.5.0.0 255.255.0.0
> 170.5.0.0/16, version 20, cached adjacency 172.16.1.2
> 0 packets, 0 bytes
>   tag information set
>     local tag: 26
>   via 172.16.1.2, 0 dependencies, recursive
>     next hop 172.16.1.2, Serial1/0 via 172.16.1.2/32
>     valid cached adjacency
>     tag rewrite with Se1/0, 172.16.1.2, tags imposed: {}
> ============================================================================
> and the output on the remote PE :
> ============================================================================
> PE2-AS1#sh ip cef vrf CustomerA 170.5.0.0 255.255.0.0
> 170.5.0.0/16, version 23, cached adjacency to Serial0/0
> 0 packets, 0 bytes
>   tag information set
>     local tag: VPN-route-head
>     fast tag rewrite with Se0/0, point2point, tags imposed: {18 26}
>   via 10.10.10.101, 0 dependencies, recursive
>     next hop 10.10.10.5, Serial0/0 via 10.10.10.101/32
>     valid cached adjacency
>     tag rewrite with Se0/0, point2point, tags imposed: {18 26}
> ============================================================================