[mpls-linux-general] Re: ldpd doesn't start properly

[Adrian P. <adr...@gm...>]

I have some extra information on this. Attached is a packet capture
when the two LDP neighbours connect (just before one of them dies)

The file is in libpcap format (viewable with tcpdump or with ethereal)

On 3/13/06, Adrian Popa <adr...@gm...> wrote:
> I'm trying to get ldpd to work and I'm having difficulties.
>
> I'm connecting to ldpd using telnet and this is how I configured my LER:
>
> e1:/home/irina.dumitrascu# cat /usr/etc/ldpd.conf
> !
> ! Zebra configuration saved from vty
> !   2006/03/13 16:01:36
> !
> hostname uml-1
> password root
> enable password root
> !
> interface eth0
> !
> interface eth1
>  mpls ip
> !
> interface eth2
> !
> interface eth3
> !
> interface gre0
> !
> interface ip6tnl0
> !
> interface lo
> !
> interface mpls0
> !
> interface sit0
> !
> interface teql0
> !
> !
> mpls ldp
>  egress connected
> !
> line vty
> !
>
> On the LSR I set up both interfaces with mpls ip (eth0 and eth1), but
> when I try to start ldpd on the lsr, it says:
>
> e2:/home/irina.dumitrascu# ldpd -u root -P 6222
> ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion
> `li->iff.index' failed.
> Aborted.
>
> I can start it if I comment out the 'mpls ip' lines from interface
> eth0 and eth1.
>
> After I manage to start LDP on the LSR, and try to run  show ldp I get
> an error message: 'There isn't an active LDP instance.' This happens
> after I have have configured manually the interfaces (mpls ip).
>
> When I have the lsr manually configured (172.16.0.3) and the next ler
> running (172.16.0.2), and on the lsr I issue the command 'mpls ldp'
> this is what happens:
>
> * the ler is constantly sending out LDP Hello packets
> * when I issue mpls ldp on the lsr, the lsr sends a LDP Hello, and
> then freezes (actually only ldpd freezes)
>
> This is the output of tcpdump
>
> 16:18:56.453269 IP 172.16.0.2.646 > 224.0.0.2.646: LDP,
> Label-Space-ID: 192.168.0.2:0, length: 34
> 16:19:01.453496 IP 172.16.0.2.646 > 224.0.0.2.646: LDP,
> Label-Space-ID: 192.168.0.2:0, length: 34
> 16:19:02.924352 IP 172.16.0.3.646 > 224.0.0.2.646: LDP,
> Label-Space-ID: 141.85.43.122:0, length: 34
> 16:19:06.453724 IP 172.16.0.2.646 > 224.0.0.2.646: LDP,
> Label-Space-ID: 192.168.0.2:0, length: 34
> 16:19:11.453952 IP 172.16.0.2.646 > 224.0.0.2.646: LDP,
> Label-Space-ID: 192.168.0.2:0, length: 34
>
>
> Do you have any idea why this doesn't work?
>