Re: Missing labels in T-LDP

Hi,

I would also like to see the config and the topo.

Thanks,

-- 
Regards,
Iwan Hoogendoorn
CCIE #13084 (R&S / Security / SP)
Sr. Support Engineer  IPexpert, Inc.
URL: http://www.IPexpert.com
On Thu, Oct 8, 2009 at 2:13 AM, Marcel Lammerse <m.lammerse_at_mac.com> wrote:
> Experts,
>
> here I have a load-balanced path between directly connected ldp speakers :
>
> PE4#sh mpls forwarding-table 192.168.2.0
> Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
> Label  Label or VC   or Tunnel Id      Switched      interface
> 22     25            192.168.2.0/24    0             Fa1/0      172.16.14.1
>       23            192.168.2.0/24    0             Fa3/0      172.16.34.3
> PE4#
>
> PE4#sh mpls ldp bindings 192.168.2.0 24 detail
>  lib entry: 192.168.2.0/24, rev 22, chkpt: none
>        local binding:  label: 22 (owner LDP)
>          Advertised to:
>          1.1.1.1:0              3.3.3.3:0
>        remote binding: lsr: 1.1.1.1:0, label: 25
>        remote binding: lsr: 3.3.3.3:0, label: 23
>        route information: state: none, table: default,
>          next-hop: 172.16.14.1, remote label: 25
>        route information: state: none, table: default,
>          next-hop: 172.16.34.3, remote label: 23
>
> If I change the ldp sessions to t-ldp, and keep everything else the same, the labels seem to disappear and traffic appears to go out untagged :
>
> PE4#sh mpls forwarding-table 192.168.2.0
> Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
> Label  Label or VC   or Tunnel Id      Switched      interface
> 22     No Label      192.168.2.0/24    0             Fa1/0      172.16.14.1
>       No Label      192.168.2.0/24    0             Fa3/0      172.16.34.3
> PE4#
>
> PE4#sh mpls ldp bindings 192.168.2.0 24 detail
>  lib entry: 192.168.2.0/24, rev 22, chkpt: none
>        local binding:  label: 22 (owner LDP)
>          Advertised to:
>          3.3.3.3:0              1.1.1.1:0
>        remote binding: lsr: 3.3.3.3:0, label: 23
>        remote binding: lsr: 1.1.1.1:0, label: 25
>        route information: state: none, table: default,
>          next-hop: 172.16.14.1, remote label: <----- no label
>        route information: state: none, table: default,
>          next-hop: 172.16.34.3, remote label: <----- no label
> PE4#
>
> I'm a bit confused by this. I would have expected the traffic to continue to be labeled and the labels to remain the same.
>
> Can anyone shed some light on why this happens?
>
> Thanks,
> Marcel
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- 
Regards,
Iwan Hoogendoorn
CCIE #13084 (R&S / Security / SP)
Sr. Support Engineer  IPexpert, Inc.
URL: http://www.IPexpert.com
Blogs and organic groups at http://www.ccie.net