Re: unable to reach VPN sites behind TE tunnel?

JR,

Classic problem - you forgot to enable LDP on the MPLS TE tunnel and
therefore R8 sees the exposed VPNv4 label addressed for R9. You need
additional label on the stack so that R8 may transport the packet
further to R9. Dont forget to accept targetted LDP hellos on R8.

Regards,

Petr

2010/5/28 JR Garcia <ttuner_at_gmail.com>:
> did some debugs...packets from R9 to R5 are getting there, but R5 to
> R9 dont seem to be going anywhere.
>
> On 5/28/10, JR Garcia <ttuner_at_gmail.com> wrote:
>> topology:
>>
>> R5------R6-----R8------R9
>>
>> - TE tunnel between R5 and R8 (tunnel is up)
>> - R5 and R9 are vpnv4 neighbors
>>
>> i see the routes in the vrf routing table on both sides, but cant ping.
>> i remove the tunnel and just let the LSP set up over LDP and all is
>> well. what am i missing?
>>
>> tunnel configs:
>>
>> interface Tunnel1
>> ip unnumbered Loopback0
>> tunnel destination 192.168.8.8
>> tunnel mode mpls traffic-eng
>> tunnel mpls traffic-eng autoroute announce
>> tunnel mpls traffic-eng path-option 1 explicit name R8
>>
>>
>> interface Tunnel0
>> ip unnumbered Loopback0
>> tunnel destination 192.168.5.5
>> tunnel mode mpls traffic-eng
>> tunnel mpls traffic-eng autoroute announce
>> tunnel mpls traffic-eng path-option 1 explicit name R5
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri May 28 2010 - 21:01:55 ART