Home / Browse / MPLS for Linux / Mail / Archive

MPLS for Linux

Email Archive: mpls-linux-devel (read-only)

2003:	_Jan	_Feb	_Mar	_Apr	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov (7)	_Dec (8)
2004:	_Jan (5)	_Feb (73)	_Mar (22)	_Apr (21)	_May	_Jun	_Jul (3)	_Aug (5)	_Sep (4)	_Oct (4)	_Nov (2)	_Dec (6)
2005:	_Jan (5)	_Feb	_Mar (6)	_Apr (11)	_May (6)	_Jun (5)	_Jul (4)	_Aug (1)	_Sep (1)	_Oct	_Nov (9)	_Dec (15)
2006:	_Jan (11)	_Feb (7)	_Mar (4)	_Apr (1)	_May (2)	_Jun (2)	_Jul (7)	_Aug	_Sep (8)	_Oct (9)	_Nov (10)	_Dec (14)
2007:	_Jan (11)	_Feb (9)	_Mar (39)	_Apr (7)	_May (4)	_Jun (2)	_Jul (5)	_Aug (6)	_Sep (6)	_Oct (1)	_Nov (1)	_Dec (8)
2008:	_Jan	_Feb (13)	_Mar (19)	_Apr (11)	_May (16)	_Jun (6)	_Jul (2)	_Aug (4)	_Sep	_Oct (5)	_Nov	_Dec (16)
2009:	_Jan (13)	_Feb (5)	_Mar	_Apr	_May (11)	_Jun (7)	_Jul (3)	_Aug	_Sep (2)	_Oct (8)	_Nov (16)	_Dec (15)
2010:	_Jan (6)	_Feb (5)	_Mar (1)	_Apr (14)	_May (42)	_Jun (4)	_Jul (1)	_Aug (1)	_Sep	_Oct	_Nov (4)	_Dec (1)
2011:	_Jan (3)	_Feb	_Mar	_Apr (7)	_May (1)	_Jun (2)	_Jul (4)	_Aug (19)	_Sep (9)	_Oct (13)	_Nov (4)	_Dec (3)
2012:	_Jan (2)	_Feb (3)	_Mar	_Apr	_May	_Jun (11)	_Jul	_Aug (1)	_Sep	_Oct	_Nov (3)	_Dec (2)
2013:	_Jan (4)	_Feb	_Mar	_Apr (1)	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec

[mpls-linux-devel] LDP problems

From: <gsr16959@al...> - 2007-03-19 09:24

Hello everybody:

I've migrated my PCs from FC4 to FC5 with all the RPMs for the 1.955 =
version. The problem must be that I'm forgetting something or doing =
something wrong cause I've notice that Julien or Marco were at the same =
situacion and they both are able to run LDP.

This is what I do, it's a simple scenario with two LSRs:

1. First of all I load "mpls4" and activate ip forwarding.
2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
   Without specifying the config files (though I tried it also with the =
.conf files and even=20
   starting them as services ("service ... start")).
3. Then I entered vtysh to type by here ALL the config.
   -First, the OSPF networks: router ospf, network ... area 0.
   -I wait to the new routes to be discovered and then I configured ldp.
   -mpls ldp, and in the corresponding interface of each LSR to the MPLS =
link:=20
    mpls ip and mpls labelspace 0.

The OSPF routes are discovered correctly, and the NHLFE and ILM entries, =
created properly, but I'm not able to send labelled packets through the =
mpls link I'm trying to set up.

If someone working with FC5 and LDP running could tell me his method =
should be very useful.

Thanks in advance,
Gonzalo.

Re: [mpls-linux-devel] LDP problems

From: Marco Schmidt <marco.schmidt@s2...> - 2007-03-19 12:03

Here is what I got so far...

I'm experiencing the same problems. Some connections are labeled, most
of them are not - that differs from friday, where only one PC didn't
work properly.
In the non-working-case, LDPd finds the pending NHLFEs, but does nothing mo=
re.

...
2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
whole log can be found here:
http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.log


Different reaction where the binding works properly:

...
>2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen type (29=
), seq=3D1, pid=3D4294963188
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet co=
mes from mpls-netlink-listen
2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_DELR=
OUTE 172.16.30.0/24, type IPv4=20
2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nexthop =
via 10.0.5.1 if 2
2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(25),=
 seq=3D7
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRTM_=
DELROUTE(25), seq=3D7, pid=3D0
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_DELR=
OUTE(25), seq=3D7, pid=3D4294963190
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes fro=
m netlink-listen
2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_NEWR=
OUTE 172.16.30.0/24, type IPv4=20
2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nexthop =
via 10.0.5.1 if 2
2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): MPLS inf=
o 00000009
2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24),=
 seq=3D8
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRTM_=
NEWROUTE(24), seq=3D8, pid=3D0
>2007/03/19 12:07:44 LDP: route 172.16.30.0/24
>2007/03/19 12:07:44 LDP:        num nexthop 0
>2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
>2007/03/19 12:07:44 LDP:        add
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWR=
OUTE(24), seq=3D8, pid=3D4294963190
2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes fro=
m netlink-listen

Here, the label binding appears unter "ip route show" command.
whole log: http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label_bind=
ing_and_zebra_crash121437.log

The marked operations never happen at the non-working links.

LDPd sometimes closes because of I/O errors, but there are no messages
in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
message (can be found two times in the above logfile)

2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); aborti=
ng...
Program counter: /usr/sbin/zebra[0x80537b1]

My conf-files can also be found in die MPLS directory http://www-user.tu-ch=
emnitz.de/~smarco/MPLS/

Regards,
Marco



> Hello everybody:

> I've migrated my PCs from FC4 to FC5 with all the RPMs for the
> 1.955 version. The problem must be that I'm forgetting something or
> doing something wrong cause I've notice that Julien or Marco were at
> the same situacion and they both are able to run LDP.

> This is what I do, it's a simple scenario with two LSRs:

> 1. First of all I load "mpls4" and activate ip forwarding.
> 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
>    Without specifying the config files (though I tried it also with the .=
conf files and even
>    starting them as services ("service ... start")).
> 3. Then I entered vtysh to type by here ALL the config.
>    -First, the OSPF networks: router ospf, network ... area 0.
>    -I wait to the new routes to be discovered and then I configured ldp.
>    -mpls ldp, and in the corresponding interface of each LSR to the MPLS =
link:
>     mpls ip and mpls labelspace 0.

> The OSPF routes are discovered correctly, and the NHLFE and ILM
> entries, created properly, but I'm not able to send labelled packets
> through the mpls link I'm trying to set up.

> If someone working with FC5 and LDP running could tell me his method shou=
ld be very useful.

> Thanks in advance,
> Gonzalo.




> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

Re: [mpls-linux-devel] LDP problems

From: James R. Leu <jleu@mi...> - 2007-03-19 18:07

Attachments: Message as HTML

I am looking into this issue.  I will post a instrumented FC5 quagga-mpls
RPM that will hopefully provide more details about what is happening.
I will be building the RPM this evening and posting a URL to pick it
up from shortly thereafter.

On Mon, Mar 19, 2007 at 01:03:04PM +0100, Marco Schmidt wrote:
> Here is what I got so far...
>=20
> I'm experiencing the same problems. Some connections are labeled, most
> of them are not - that differs from friday, where only one PC didn't
> work properly.
> In the non-working-case, LDPd finds the pending NHLFEs, but does nothing =
more.
>=20
> ...
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> whole log can be found here:
> http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.log
>=20
>=20
> Different reaction where the binding works properly:
>=20
> ...
> >2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen type (=
29), seq=3D1, pid=3D4294963188
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet =
comes from mpls-netlink-listen
> 2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
> 2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_DE=
LROUTE 172.16.30.0/24, type IPv4=20
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nextho=
p via 10.0.5.1 if 2
> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(25=
), seq=3D7
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT=
M_DELROUTE(25), seq=3D7, pid=3D0
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_DE=
LROUTE(25), seq=3D7, pid=3D4294963190
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes f=
rom netlink-listen
> 2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_NE=
WROUTE 172.16.30.0/24, type IPv4=20
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nextho=
p via 10.0.5.1 if 2
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): MPLS i=
nfo 00000009
> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24=
), seq=3D8
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT=
M_NEWROUTE(24), seq=3D8, pid=3D0
> >2007/03/19 12:07:44 LDP: route 172.16.30.0/24
> >2007/03/19 12:07:44 LDP:        num nexthop 0
> >2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
> >2007/03/19 12:07:44 LDP:        add
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_NE=
WROUTE(24), seq=3D8, pid=3D4294963190
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes f=
rom netlink-listen
>=20
> Here, the label binding appears unter "ip route show" command.
> whole log: http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label_bi=
nding_and_zebra_crash121437.log
>=20
> The marked operations never happen at the non-working links.
>=20
> LDPd sometimes closes because of I/O errors, but there are no messages
> in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
> message (can be found two times in the above logfile)
>=20
> 2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
> ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); abor=
ting...
> Program counter: /usr/sbin/zebra[0x80537b1]
>=20
> My conf-files can also be found in die MPLS directory http://www-user.tu-=
chemnitz.de/~smarco/MPLS/
>=20
> Regards,
> Marco
>=20
>=20
>=20
> > Hello everybody:
>=20
> > I've migrated my PCs from FC4 to FC5 with all the RPMs for the
> > 1.955 version. The problem must be that I'm forgetting something or
> > doing something wrong cause I've notice that Julien or Marco were at
> > the same situacion and they both are able to run LDP.
>=20
> > This is what I do, it's a simple scenario with two LSRs:
>=20
> > 1. First of all I load "mpls4" and activate ip forwarding.
> > 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
> >    Without specifying the config files (though I tried it also with the=
 .conf files and even
> >    starting them as services ("service ... start")).
> > 3. Then I entered vtysh to type by here ALL the config.
> >    -First, the OSPF networks: router ospf, network ... area 0.
> >    -I wait to the new routes to be discovered and then I configured ldp.
> >    -mpls ldp, and in the corresponding interface of each LSR to the MPL=
S link:
> >     mpls ip and mpls labelspace 0.
>=20
> > The OSPF routes are discovered correctly, and the NHLFE and ILM
> > entries, created properly, but I'm not able to send labelled packets
> > through the mpls link I'm trying to set up.
>=20
> > If someone working with FC5 and LDP running could tell me his method sh=
ould be very useful.
>=20
> > Thanks in advance,
> > Gonzalo.
>=20
>=20
>=20
>=20
> > -----------------------------------------------------------------------=
--
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share=
 your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpls-linux-devel@...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jleu@...

Re: [mpls-linux-devel] LDP problems

From: James R. Leu <jleu@mi...> - 2007-03-20 03:11

Attachments: Message as HTML

I've added some additional debugging.  In the process I was able to reprodu=
ce
a similar failure multiple times and I found a couple place were I was
using uninitialized structures.  By correctly zeroing these structures
I was able to fix the failure I was seeing.  I do not presume this will
fix the failures you both are seeing, but the debugging should help
us figure what is happening.

Please download version 1.955d of quagga from sf.net

    http://sourceforge.net/project/showfiles.php?group_id=3D15443&package_i=
d=3D12482


On Mon, Mar 19, 2007 at 01:03:04PM +0100, Marco Schmidt wrote:
> Here is what I got so far...
>=20
> I'm experiencing the same problems. Some connections are labeled, most
> of them are not - that differs from friday, where only one PC didn't
> work properly.
> In the non-working-case, LDPd finds the pending NHLFEs, but does nothing =
more.
>=20
> ...
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> whole log can be found here:
> http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.log
>=20
>=20
> Different reaction where the binding works properly:
>=20
> ...
> >2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen type (=
29), seq=3D1, pid=3D4294963188
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet =
comes from mpls-netlink-listen
> 2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
> 2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_DE=
LROUTE 172.16.30.0/24, type IPv4=20
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nextho=
p via 10.0.5.1 if 2
> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(25=
), seq=3D7
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT=
M_DELROUTE(25), seq=3D7, pid=3D0
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_DE=
LROUTE(25), seq=3D7, pid=3D4294963190
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes f=
rom netlink-listen
> 2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_NE=
WROUTE 172.16.30.0/24, type IPv4=20
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nextho=
p via 10.0.5.1 if 2
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): MPLS i=
nfo 00000009
> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24=
), seq=3D8
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT=
M_NEWROUTE(24), seq=3D8, pid=3D0
> >2007/03/19 12:07:44 LDP: route 172.16.30.0/24
> >2007/03/19 12:07:44 LDP:        num nexthop 0
> >2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
> >2007/03/19 12:07:44 LDP:        add
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_NE=
WROUTE(24), seq=3D8, pid=3D4294963190
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes f=
rom netlink-listen
>=20
> Here, the label binding appears unter "ip route show" command.
> whole log: http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label_bi=
nding_and_zebra_crash121437.log
>=20
> The marked operations never happen at the non-working links.
>=20
> LDPd sometimes closes because of I/O errors, but there are no messages
> in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
> message (can be found two times in the above logfile)
>=20
> 2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
> ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); abor=
ting...
> Program counter: /usr/sbin/zebra[0x80537b1]
>=20
> My conf-files can also be found in die MPLS directory http://www-user.tu-=
chemnitz.de/~smarco/MPLS/
>=20
> Regards,
> Marco
>=20
>=20
>=20
> > Hello everybody:
>=20
> > I've migrated my PCs from FC4 to FC5 with all the RPMs for the
> > 1.955 version. The problem must be that I'm forgetting something or
> > doing something wrong cause I've notice that Julien or Marco were at
> > the same situacion and they both are able to run LDP.
>=20
> > This is what I do, it's a simple scenario with two LSRs:
>=20
> > 1. First of all I load "mpls4" and activate ip forwarding.
> > 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
> >    Without specifying the config files (though I tried it also with the=
 .conf files and even
> >    starting them as services ("service ... start")).
> > 3. Then I entered vtysh to type by here ALL the config.
> >    -First, the OSPF networks: router ospf, network ... area 0.
> >    -I wait to the new routes to be discovered and then I configured ldp.
> >    -mpls ldp, and in the corresponding interface of each LSR to the MPL=
S link:
> >     mpls ip and mpls labelspace 0.
>=20
> > The OSPF routes are discovered correctly, and the NHLFE and ILM
> > entries, created properly, but I'm not able to send labelled packets
> > through the mpls link I'm trying to set up.
>=20
> > If someone working with FC5 and LDP running could tell me his method sh=
ould be very useful.
>=20
> > Thanks in advance,
> > Gonzalo.
>=20
>=20
>=20
>=20
> > -----------------------------------------------------------------------=
--
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share=
 your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpls-linux-devel@...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jleu@...

Re: [mpls-linux-devel] LDP problems

From: <gsr16959@al...> - 2007-03-20 09:59

Hi:

I've downloaded your revised quagga RPM for FC5 and I tried this =
scenario:

                  eth0   eth1             eth1   eth0
       12.0.0.1-------PE1---------------------PE2-------13.0.0.1
                         .1  10.0.0.0/24    .2

I enclose the configuration and commands related to MPLS and LDP at PE2 =
and the log file created debugging zebra.

At the bottom of the log file there's: "unable to find FEC 10.0.0.0/24", =
furthermore, the output of "sh mpls forwarding" shows the labelspace as =
inactive.

Please take a look, I hope it could be helpful to figure out what's =
happening.

Thanks in advance,

Gonzalo.

PE3 config
------------------------------------------------------------------------

Current configuration:
!
hostname PE3
log file /var/log/quagga/1955d.log
!
debug zebra events
debug zebra packet
debug zebra kernel
debug zebra rib
!
interface eth0
 ipv6 nd suppress-ra
!
interface eth1
 ipv6 nd suppress-ra
 mpls ip
 mpls labelspace 0
!
interface lo
!
interface mpls0
 ipv6 nd suppress-ra
!
interface sit0
 ipv6 nd suppress-ra
!
mpls ldp
 egress connected
!
router ospf
 network 10.0.0.0/24 area 0.0.0.0
 network 13.0.0.0/24 area 0.0.0.0
!
ip forwarding
!
line vty
!

PE3# sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       I - ISIS, B - BGP, > - selected route, * - FIB route

O   10.0.0.0/24 [110/10] is directly connected, eth1, 00:02:49
C>* 10.0.0.0/24 is directly connected, eth1
O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:01:37
O   13.0.0.0/24 [110/10] is dPE3# sh ldp neig
Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
        TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
        State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
        Up time: 00:04:08
        LDP discovery sources:
          eth1
        Addresses bound to peer:
          10.0.0.1      12.0.0.1
irectly connected, eth0, 00:02:43
C>* 13.0.0.0/24 is directly connected, eth0
C>* 127.0.0.0/8 is directly connected, lo

PE3# sh mpls for
Insegments:
  Lbl Spc  Label Owner
    0      10000 ldp    (inactive)
Total 1

Outsegments:
  Interface          Label Next Hop        Owner
  eth1               10000 10.0.0.1        ldp
Total 1

Cross Connects:

Total 0

PE3# sh ldp ses
2  9.151.111.152 45  OPERATIONAL
        10.0.0.1
        12.0.0.1

PE3# sh ldp disc

Local LSR Identifier: 13.0.0.1

Interface Discovery Sources:
        eth1: xmit/recv
            LDP Id: 12.0.0.1:0

Targeted Discovery Sources:
        No configured peers

PE3# sh ldp neig
Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
        TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
        State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
        Up time: 00:04:08
        LDP discovery sources:
          eth1
        Addresses bound to peer:
          10.0.0.1      12.0.0.1

[root@... ~]# mpls ilm
ILM entry label gen 10000 labelspace 0 proto ipv4
        pop peek  (0 bytes, 0 pkts)

[root@... ~]# mpls nhlfe
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
        push gen 10000 set eth1 ipv4 10.0.0.1  (0 bytes, 0 pkts)

[root@... ~]# ip route
10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.2
12.0.0.0/24 via 10.0.0.1 dev eth1  proto zebra  metric 20
13.0.0.0/24 dev eth0  proto kernel  scope link  src 13.0.0.1

[root@... ~]# rpm -q quagga
quagga-0.99.6-01.fc5.mpls.1.955d

/var/log/quagga/1955d.log
------------------------------------------------------------------------

2007/03/20 10:30:40 OSPF: interface 10.0.0.2 [3] join AllSPFRouters =
Multicast group.
2007/03/20 10:30:40 ZEBRA: zebra message comes from socket [14]
2007/03/20 10:30:40 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
2007/03/20 10:30:40 ZEBRA: rib_link: rn 0x8efcf48, rib 0x8f02c70
2007/03/20 10:30:40 ZEBRA: rib_link: new head, rn_status copied over
2007/03/20 10:30:41 ZEBRA: rib_process: Updating existing route, select =
0x8efcf88, fib 0x8efcf88
2007/03/20 10:30:43 OSPF: interface 13.0.0.1 [4] join AllSPFRouters =
Multicast group.
2007/03/20 10:30:46 ZEBRA: zebra message comes from socket [14]
2007/03/20 10:30:46 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
2007/03/20 10:30:46 ZEBRA: rib_link: rn 0x8efd150, rib 0x8f03158
2007/03/20 10:30:46 ZEBRA: rib_link: new head, rn_status copied over
2007/03/20 10:30:46 ZEBRA: rib_process: Updating existing route, select =
0x8efd190, fib 0x8efd190
2007/03/20 10:31:05 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now =
Init/DROther
2007/03/20 10:31:20 OSPF: DR-Election[1st]: Backup 10.0.0.2
2007/03/20 10:31:20 OSPF: DR-Election[1st]: DR     10.0.0.2
2007/03/20 10:31:20 OSPF: DR-Election[2nd]: Backup 10.0.0.1
2007/03/20 10:31:20 OSPF: DR-Election[2nd]: DR     10.0.0.2
2007/03/20 10:31:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now =
DR
2007/03/20 10:31:20 OSPF: interface 10.0.0.2 [3] join AllDRouters =
Multicast group.
2007/03/20 10:31:23 OSPF: DR-Election[1st]: Backup 13.0.0.1
2007/03/20 10:31:23 OSPF: DR-Election[1st]: DR     13.0.0.1
2007/03/20 10:31:23 OSPF: DR-Election[2nd]: Backup 0.0.0.0
2007/03/20 10:31:23 OSPF: DR-Election[2nd]: DR     13.0.0.1
2007/03/20 10:31:23 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now =
DR
2007/03/20 10:31:23 OSPF: interface 13.0.0.1 [4] join AllDRouters =
Multicast group.
2007/03/20 10:31:45 OSPF: Packet[DD]: Neighbor 12.0.0.1: Initial DBD =
from Slave, ignoring.
2007/03/20 10:31:45 OSPF: DR-Election[1st]: Backup 10.0.0.1
2007/03/20 10:31:45 OSPF: DR-Election[1st]: DR     10.0.0.2
2007/03/20 10:31:50 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done =
(Master).
2007/03/20 10:31:50 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now =
Loading/Backup
2007/03/20 10:31:50 OSPF: nsm_change_state(12.0.0.1, Loading -> Full): =
scheduling new router-LSA origination
2007/03/20 10:31:52 ZEBRA: zebra message comes from socket [14]
2007/03/20 10:31:52 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
2007/03/20 10:31:52 ZEBRA: rib_link: rn 0x8f032a8, rib 0x8f031e0
2007/03/20 10:31:52 ZEBRA: rib_process: Adding route, select 0x8f031e0
2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop): =
RTM_NEWROUTE 12.0.0.0/24, type IPv4=20
2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop): =
nexthop via 10.0.0.1 if 3
2007/03/20 10:31:52 ZEBRA: netlink_talk: netlink-cmd type =
RTM_NEWROUTE(24), seq=3D6
2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd ACK: =
type=3DRTM_NEWROUTE(24), seq=3D6, pid=3D0
2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-listen type =
RTM_NEWROUTE(24), seq=3D6, pid=3D4294963198
2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd packet comes =
from netlink-listen
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 LDP: route 10.0.0.0/24
2007/03/20 10:32:09 LDP: 	num ifindex 0
2007/03/20 10:32:09 LDP: 	attached
2007/03/20 10:32:09 LDP: 	ifindex 3
2007/03/20 10:32:09 LDP: 	add
2007/03/20 10:32:09 LDP: route 13.0.0.0/24
2007/03/20 10:32:09 LDP: 	num ifindex 0
2007/03/20 10:32:09 LDP: 	attached
2007/03/20 10:32:09 LDP: 	ifindex 4
2007/03/20 10:32:09 LDP: 	add
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 LDP: route 12.0.0.0/24
2007/03/20 10:32:09 LDP: 	num nexthop 0
2007/03/20 10:32:09 LDP: 	nexthop 10.0.0.1
2007/03/20 10:32:09 LDP: 	add
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:09 ZEBRA: zebra message received =
[ZEBRA_REDISTRIBUTE_ADD] 1
2007/03/20 10:32:15 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), =
seq=3D1
2007/03/20 10:32:15 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: =
type=3D(29), seq=3D1, pid=3D0
2007/03/20 10:32:52 LDP: OUT: ldp_session_attempt_setup: =
MPLS_NON_BLOCKING
2007/03/20 10:32:52 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO:
2007/03/20 10:32:57 LDP: OUT: ldp_session_attempt_setup: =
MPLS_NON_BLOCKING
2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:59 ZEBRA: zebra message received =
[ZEBRA_MPLS_IN_SEGMENT_ADD] 10
2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), =
seq=3D2
2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: =
type=3D(29), seq=3D2, pid=3D0
2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type =
(29), seq=3D0, pid=3D0
2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:59 ZEBRA: zebra message received =
[ZEBRA_MPLS_OUT_SEGMENT_ADD] 39
2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), =
seq=3D1
2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type =
(29), seq=3D1, pid=3D4294963196
2007/03/20 10:32:59 ZEBRA: netlink_talk: ignoring message type 0x001d
2007/03/20 10:32:59 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000002
2007/03/20 10:32:59 LDP: found pending NHLFE: 0x997e9a8
2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type =
(29), seq=3D1, pid=3D4294963196
2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet =
comes from mpls-netlink-listen
2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
2007/03/20 10:32:59 ZEBRA: mpls_ftn_register: unable to find FEC =
10.0.0.0/24


-----Mensaje original-----
De: James R. Leu [mailto:jleu@...]
Enviado el: mar 20/03/2007 4:11
Para: Marco Schmidt
CC: Sienes Rodr=EDguez Gonzalo; mpls-linux-devel@...
Asunto: Re: [mpls-linux-devel] LDP problems
=20
I've added some additional debugging.  In the process I was able to =
reproduce
a similar failure multiple times and I found a couple place were I was
using uninitialized structures.  By correctly zeroing these structures
I was able to fix the failure I was seeing.  I do not presume this will
fix the failures you both are seeing, but the debugging should help
us figure what is happening.

Please download version 1.955d of quagga from sf.net

    =
http://sourceforge.net/project/showfiles.php?group_id=3D15443&package_id=3D=
12482


On Mon, Mar 19, 2007 at 01:03:04PM +0100, Marco Schmidt wrote:
> Here is what I got so far...
>=20
> I'm experiencing the same problems. Some connections are labeled, most
> of them are not - that differs from friday, where only one PC didn't
> work properly.
> In the non-working-case, LDPd finds the pending NHLFEs, but does =
nothing more.
>=20
> ...
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> whole log can be found here:
> =
http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.log=

>=20
>=20
> Different reaction where the binding works properly:
>=20
> ...
> >2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen =
type (29), seq=3D1, pid=3D4294963188
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe =
packet comes from mpls-netlink-listen
> 2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
> 2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): =
RTM_DELROUTE 172.16.30.0/24, type IPv4=20
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): =
nexthop via 10.0.5.1 if 2
> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type =
RTM_DELROUTE(25), seq=3D7
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: =
type=3DRTM_DELROUTE(25), seq=3D7, pid=3D0
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type =
RTM_DELROUTE(25), seq=3D7, pid=3D4294963190
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet =
comes from netlink-listen
> 2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): =
RTM_NEWROUTE 172.16.30.0/24, type IPv4=20
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): =
nexthop via 10.0.5.1 if 2
> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): =
MPLS info 00000009
> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type =
RTM_NEWROUTE(24), seq=3D8
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: =
type=3DRTM_NEWROUTE(24), seq=3D8, pid=3D0
> >2007/03/19 12:07:44 LDP: route 172.16.30.0/24
> >2007/03/19 12:07:44 LDP:        num nexthop 0
> >2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
> >2007/03/19 12:07:44 LDP:        add
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type =
RTM_NEWROUTE(24), seq=3D8, pid=3D4294963190
> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet =
comes from netlink-listen
>=20
> Here, the label binding appears unter "ip route show" command.
> whole log: =
http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label_binding_and_z=
ebra_crash121437.log
>=20
> The marked operations never happen at the non-working links.
>=20
> LDPd sometimes closes because of I/O errors, but there are no messages
> in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
> message (can be found two times in the above logfile)
>=20
> 2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] =
11
> ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); =
aborting...
> Program counter: /usr/sbin/zebra[0x80537b1]
>=20
> My conf-files can also be found in die MPLS directory =
http://www-user.tu-chemnitz.de/~smarco/MPLS/
>=20
> Regards,
> Marco
>=20
>=20
>=20
> > Hello everybody:
>=20
> > I've migrated my PCs from FC4 to FC5 with all the RPMs for the
> > 1.955 version. The problem must be that I'm forgetting something or
> > doing something wrong cause I've notice that Julien or Marco were at
> > the same situacion and they both are able to run LDP.
>=20
> > This is what I do, it's a simple scenario with two LSRs:
>=20
> > 1. First of all I load "mpls4" and activate ip forwarding.
> > 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
> >    Without specifying the config files (though I tried it also with =
the .conf files and even
> >    starting them as services ("service ... start")).
> > 3. Then I entered vtysh to type by here ALL the config.
> >    -First, the OSPF networks: router ospf, network ... area 0.
> >    -I wait to the new routes to be discovered and then I configured =
ldp.
> >    -mpls ldp, and in the corresponding interface of each LSR to the =
MPLS link:
> >     mpls ip and mpls labelspace 0.
>=20
> > The OSPF routes are discovered correctly, and the NHLFE and ILM
> > entries, created properly, but I'm not able to send labelled packets
> > through the mpls link I'm trying to set up.
>=20
> > If someone working with FC5 and LDP running could tell me his method =
should be very useful.
>=20
> > Thanks in advance,
> > Gonzalo.
>=20
>=20
>=20
>=20
> > =
-------------------------------------------------------------------------=

> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to =
share your
> > opinions on IT & business topics through brief surveys-and earn cash
> > =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpls-linux-devel@...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>=20
>=20
>=20
>=20
>=20
> =
-------------------------------------------------------------------------=

> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share your
> opinions on IT & business topics through brief surveys-and earn cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jleu@...

Re: [mpls-linux-devel] LDP problems

From: Marco Schmidt <marco.schmidt@s2...> - 2007-03-20 16:07

Hello James,

the Labeling is working better now, thank you for the debugging.
But as you expected, the problems aren't completely solved.
I think there is a problem with networks where loops are possible...

The labelspaces and crossconnects are also marked inactive on my
systems, but it is possible to send labeled packets through the
network.

It is! working at the moment, but I had to remove the link between E4
and E3. (one, that made redundant paths possible)
Zebra/Ldpd doesn't seem to be able to manage redundant paths with the
same destination.
It crashed after enabling the link again. Have a look at the logfiles:
http://www-user.tu-chemnitz.de/~smarco/MPLS/20070320_v2/E3_with_crash_after=
_linkupdate.log
There are a few more logs from today in the MPLS directory.

Right now, I found the same error as Gonzalo (at the bottom of the
file):
2007/03/20 16:08:01 LDP: found pending NHLFE: 0x9782308
2007/03/20 16:08:01 ZEBRA: zebra message comes from socket [17]
2007/03/20 16:08:01 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
2007/03/20 16:08:01 ZEBRA: IPV41 mismatch
>>2007/03/20 16:08:01 ZEBRA: mpls_ftn_register: unable to find FEC 172.16.2=
0.0/24
2007/03/20 16:08:01 ZEBRA: zebra message comes from socket [17]
2007/03/20 16:08:01 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
ZEBRA: Received signal 11 at 1174403281 (si_addr 0xe, PC 0x80539cf); aborti=
ng...
Program counter: /usr/sbin/zebra[0x80539cf]

Regards,
Marco



> Hi:

> I've downloaded your revised quagga RPM for FC5 and I tried this scenario:

>                   eth0   eth1             eth1   eth0
>        12.0.0.1-------PE1---------------------PE2-------13.0.0.1
>                          .1  10.0.0.0/24    .2

> I enclose the configuration and commands related to MPLS and LDP at
> PE2 and the log file created debugging zebra.

> At the bottom of the log file there's: "unable to find FEC
> 10.0.0.0/24", furthermore, the output of "sh mpls forwarding" shows the l=
abelspace as inactive.

> Please take a look, I hope it could be helpful to figure out what's happe=
ning.

> Thanks in advance,

> Gonzalo.

> PE3 config
> ------------------------------------------------------------------------

> Current configuration:
> !
> hostname PE3
> log file /var/log/quagga/1955d.log
> !
> debug zebra events
> debug zebra packet
> debug zebra kernel
> debug zebra rib
> !
> interface eth0
>  ipv6 nd suppress-ra
> !
> interface eth1
>  ipv6 nd suppress-ra
>  mpls ip
>  mpls labelspace 0
> !
> interface lo
> !
> interface mpls0
>  ipv6 nd suppress-ra
> !
> interface sit0
>  ipv6 nd suppress-ra
> !
> mpls ldp
>  egress connected
> !
> router ospf
>  network 10.0.0.0/24 area 0.0.0.0
>  network 13.0.0.0/24 area 0.0.0.0
> !
> ip forwarding
> !
> line vty
> !

> PE3# sh ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
>        I - ISIS, B - BGP, > - selected route, * - FIB route

> O   10.0.0.0/24 [110/10] is directly connected, eth1, 00:02:49
C>>* 10.0.0.0/24 is directly connected, eth1
O>>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:01:37
> O   13.0.0.0/24 [110/10] is dPE3# sh ldp neig
> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
>         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
>         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
>         Up time: 00:04:08
>         LDP discovery sources:
>           eth1
>         Addresses bound to peer:
>           10.0.0.1      12.0.0.1
> irectly connected, eth0, 00:02:43
C>>* 13.0.0.0/24 is directly connected, eth0
C>>* 127.0.0.0/8 is directly connected, lo

> PE3# sh mpls for
> Insegments:
>   Lbl Spc  Label Owner
>     0      10000 ldp    (inactive)
> Total 1

> Outsegments:
>   Interface          Label Next Hop        Owner
>   eth1               10000 10.0.0.1        ldp
> Total 1

> Cross Connects:

> Total 0

> PE3# sh ldp ses
> 2  9.151.111.152 45  OPERATIONAL
>         10.0.0.1
>         12.0.0.1

> PE3# sh ldp disc

> Local LSR Identifier: 13.0.0.1

> Interface Discovery Sources:
>         eth1: xmit/recv
>             LDP Id: 12.0.0.1:0

> Targeted Discovery Sources:
>         No configured peers

> PE3# sh ldp neig
> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
>         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
>         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
>         Up time: 00:04:08
>         LDP discovery sources:
>           eth1
>         Addresses bound to peer:
>           10.0.0.1      12.0.0.1

> [root@... ~]# mpls ilm
> ILM entry label gen 10000 labelspace 0 proto ipv4
>         pop peek  (0 bytes, 0 pkts)

> [root@... ~]# mpls nhlfe
> NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
>         push gen 10000 set eth1 ipv4 10.0.0.1  (0 bytes, 0 pkts)

> [root@... ~]# ip route
> 10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.2
> 12.0.0.0/24 via 10.0.0.1 dev eth1  proto zebra  metric 20
> 13.0.0.0/24 dev eth0  proto kernel  scope link  src 13.0.0.1

> [root@... ~]# rpm -q quagga
> quagga-0.99.6-01.fc5.mpls.1.955d

> /var/log/quagga/1955d.log
> ------------------------------------------------------------------------

> 2007/03/20 10:30:40 OSPF: interface 10.0.0.2 [3] join AllSPFRouters Multi=
cast group.
> 2007/03/20 10:30:40 ZEBRA: zebra message comes from socket [14]
> 2007/03/20 10:30:40 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
> 2007/03/20 10:30:40 ZEBRA: rib_link: rn 0x8efcf48, rib 0x8f02c70
> 2007/03/20 10:30:40 ZEBRA: rib_link: new head, rn_status copied over
> 2007/03/20 10:30:41 ZEBRA: rib_process: Updating existing route, select 0=
x8efcf88, fib 0x8efcf88
> 2007/03/20 10:30:43 OSPF: interface 13.0.0.1 [4] join AllSPFRouters Multi=
cast group.
> 2007/03/20 10:30:46 ZEBRA: zebra message comes from socket [14]
> 2007/03/20 10:30:46 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
> 2007/03/20 10:30:46 ZEBRA: rib_link: rn 0x8efd150, rib 0x8f03158
> 2007/03/20 10:30:46 ZEBRA: rib_link: new head, rn_status copied over
> 2007/03/20 10:30:46 ZEBRA: rib_process: Updating existing route, select 0=
x8efd190, fib 0x8efd190
> 2007/03/20 10:31:05 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now =
Init/DROther
> 2007/03/20 10:31:20 OSPF: DR-Election[1st]: Backup 10.0.0.2
> 2007/03/20 10:31:20 OSPF: DR-Election[1st]: DR     10.0.0.2
> 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: Backup 10.0.0.1
> 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: DR     10.0.0.2
> 2007/03/20 10:31:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now DR
> 2007/03/20 10:31:20 OSPF: interface 10.0.0.2 [3] join AllDRouters Multica=
st group.
> 2007/03/20 10:31:23 OSPF: DR-Election[1st]: Backup 13.0.0.1
> 2007/03/20 10:31:23 OSPF: DR-Election[1st]: DR     13.0.0.1
> 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: Backup 0.0.0.0
> 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: DR     13.0.0.1
> 2007/03/20 10:31:23 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now DR
> 2007/03/20 10:31:23 OSPF: interface 13.0.0.1 [4] join AllDRouters Multica=
st group.
> 2007/03/20 10:31:45 OSPF: Packet[DD]: Neighbor 12.0.0.1: Initial DBD from=
 Slave, ignoring.
> 2007/03/20 10:31:45 OSPF: DR-Election[1st]: Backup 10.0.0.1
> 2007/03/20 10:31:45 OSPF: DR-Election[1st]: DR     10.0.0.2
> 2007/03/20 10:31:50 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done =
(Master).
> 2007/03/20 10:31:50 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now =
Loading/Backup
> 2007/03/20 10:31:50 OSPF: nsm_change_state(12.0.0.1, Loading ->
> Full): scheduling new router-LSA origination
> 2007/03/20 10:31:52 ZEBRA: zebra message comes from socket [14]
> 2007/03/20 10:31:52 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
> 2007/03/20 10:31:52 ZEBRA: rib_link: rn 0x8f032a8, rib 0x8f031e0
> 2007/03/20 10:31:52 ZEBRA: rib_process: Adding route, select 0x8f031e0
> 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop):
> RTM_NEWROUTE 12.0.0.0/24, type IPv4=20
> 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop): nextho=
p via 10.0.0.1 if 3
> 2007/03/20 10:31:52 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24=
), seq=3D6
> 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd ACK:
> type=3DRTM_NEWROUTE(24), seq=3D6, pid=3D0
> 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-listen type
> RTM_NEWROUTE(24), seq=3D6, pid=3D4294963198
> 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd packet comes f=
rom netlink-listen
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 LDP: route 10.0.0.0/24
> 2007/03/20 10:32:09 LDP:        num ifindex 0
> 2007/03/20 10:32:09 LDP:        attached
> 2007/03/20 10:32:09 LDP:        ifindex 3
> 2007/03/20 10:32:09 LDP:        add
> 2007/03/20 10:32:09 LDP: route 13.0.0.0/24
> 2007/03/20 10:32:09 LDP:        num ifindex 0
> 2007/03/20 10:32:09 LDP:        attached
> 2007/03/20 10:32:09 LDP:        ifindex 4
> 2007/03/20 10:32:09 LDP:        add
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 LDP: route 12.0.0.0/24
> 2007/03/20 10:32:09 LDP:        num nexthop 0
> 2007/03/20 10:32:09 LDP:        nexthop 10.0.0.1
> 2007/03/20 10:32:09 LDP:        add
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:15 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq=
=3D1
> 2007/03/20 10:32:15 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type=
=3D(29), seq=3D1, pid=3D0
> 2007/03/20 10:32:52 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING
> 2007/03/20 10:32:52 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO:
> 2007/03/20 10:32:57 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING
> 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_IN_SEGMENT_=
ADD] 10
> 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq=
=3D2
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type=
=3D(29), seq=3D2, pid=3D0
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type (=
29), seq=3D0, pid=3D0
> 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_OUT_SEGMENT=
_ADD] 39
> 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), se=
q=3D1
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type (2=
9), seq=3D1, pid=3D4294963196
> 2007/03/20 10:32:59 ZEBRA: netlink_talk: ignoring message type 0x001d
> 2007/03/20 10:32:59 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000002
> 2007/03/20 10:32:59 LDP: found pending NHLFE: 0x997e9a8
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type (=
29), seq=3D1, pid=3D4294963196
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe
> packet comes from mpls-netlink-listen
> 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
> 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
> 2007/03/20 10:32:59 ZEBRA: mpls_ftn_register: unable to find FEC 10.0.0.0=
/24


> -----Mensaje original-----
> De: James R. Leu [mailto:jleu@...]
> Enviado el: mar 20/03/2007 4:11
> Para: Marco Schmidt
> CC: Sienes Rodr=EDguez Gonzalo; mpls-linux-devel@...
> Asunto: Re: [mpls-linux-devel] LDP problems
> =20
> I've added some additional debugging.  In the process I was able to repro=
duce
> a similar failure multiple times and I found a couple place were I was
> using uninitialized structures.  By correctly zeroing these structures
> I was able to fix the failure I was seeing.  I do not presume this will
> fix the failures you both are seeing, but the debugging should help
> us figure what is happening.

> Please download version 1.955d of quagga from sf.net

>   =20
> http://sourceforge.net/project/showfiles.php?group_id=3D15443&package_id=
=3D12482


> On Mon, Mar 19, 2007 at 01:03:04PM +0100, Marco Schmidt wrote:
>> Here is what I got so far...
>>=20
>> I'm experiencing the same problems. Some connections are labeled, most
>> of them are not - that differs from friday, where only one PC didn't
>> work properly.
>> In the non-working-case, LDPd finds the pending NHLFEs, but does nothing=
 more.
>>=20
>> ...
>> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
>> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
>> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
>> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
>> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
>> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
>> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> whole log can be found here:
>> http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.log
>>=20
>>=20
>> Different reaction where the binding works properly:
>>=20
>> ...
>> >2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen type =
(29), seq=3D1, pid=3D4294963188
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet=
 comes from mpls-netlink-listen
>> 2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
>> 2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_D=
ELROUTE 172.16.30.0/24, type IPv4=20
>> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nexth=
op via 10.0.5.1 if 2
>> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(2=
5), seq=3D7
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DR=
TM_DELROUTE(25), seq=3D7, pid=3D0
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_D=
ELROUTE(25), seq=3D7, pid=3D4294963190
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes =
from netlink-listen
>> 2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
>> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_N=
EWROUTE 172.16.30.0/24, type IPv4=20
>> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nexth=
op via 10.0.5.1 if 2
>> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): MPLS =
info 00000009
>> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(2=
4), seq=3D8
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DR=
TM_NEWROUTE(24), seq=3D8, pid=3D0
>> >2007/03/19 12:07:44 LDP: route 172.16.30.0/24
>> >2007/03/19 12:07:44 LDP:        num nexthop 0
>> >2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
>> >2007/03/19 12:07:44 LDP:        add
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_N=
EWROUTE(24), seq=3D8, pid=3D4294963190
>> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes =
from netlink-listen
>>=20
>> Here, the label binding appears unter "ip route show" command.
>> whole log: http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label_b=
inding_and_zebra_crash121437.log
>>=20
>> The marked operations never happen at the non-working links.
>>=20
>> LDPd sometimes closes because of I/O errors, but there are no messages
>> in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
>> message (can be found two times in the above logfile)
>>=20
>> 2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
>> ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); abo=
rting...
>> Program counter: /usr/sbin/zebra[0x80537b1]
>>=20
>> My conf-files can also be found in die MPLS directory http://www-user.tu=
-chemnitz.de/~smarco/MPLS/
>>=20
>> Regards,
>> Marco
>>=20
>>=20
>>=20
>> > Hello everybody:
>>=20
>> > I've migrated my PCs from FC4 to FC5 with all the RPMs for the
>> > 1.955 version. The problem must be that I'm forgetting something or
>> > doing something wrong cause I've notice that Julien or Marco were at
>> > the same situacion and they both are able to run LDP.
>>=20
>> > This is what I do, it's a simple scenario with two LSRs:
>>=20
>> > 1. First of all I load "mpls4" and activate ip forwarding.
>> > 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
>> >    Without specifying the config files (though I tried it also with th=
e .conf files and even
>> >    starting them as services ("service ... start")).
>> > 3. Then I entered vtysh to type by here ALL the config.
>> >    -First, the OSPF networks: router ospf, network ... area 0.
>> >    -I wait to the new routes to be discovered and then I configured ld=
p.
>> >    -mpls ldp, and in the corresponding interface of each LSR to the MP=
LS link:
>> >     mpls ip and mpls labelspace 0.
>>=20
>> > The OSPF routes are discovered correctly, and the NHLFE and ILM
>> > entries, created properly, but I'm not able to send labelled packets
>> > through the mpls link I'm trying to set up.
>>=20
>> > If someone working with FC5 and LDP running could tell me his method s=
hould be very useful.
>>=20
>> > Thanks in advance,
>> > Gonzalo.
>>=20
>>=20
>>=20
>>=20
>> > ----------------------------------------------------------------------=
---
>> > Take Surveys. Earn Cash. Influence the Future of IT
>> > Join SourceForge.net's Techsay panel and you'll get the chance to shar=
e your
>> > opinions on IT & business topics through brief surveys-and earn cash
>> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
>> > _______________________________________________
>> > mpls-linux-devel mailing list
>> > mpls-linux-devel@...
>> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>>=20
>>=20
>>=20
>>=20
>>=20
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
>> _______________________________________________
>> mpls-linux-devel mailing list
>> mpls-linux-devel@...
>> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

Re: [mpls-linux-devel] LDP problems

From: James R. Leu <jleu@mi...> - 2007-03-20 16:25

Attachments: Message as HTML

Thank you for your report.  ECMP is currently not supported via
ldp-portable.  It is something I hope to support in the next release.
For now can you change the OSPF cost on that link to see if it works
with the link connected?

As for the "unable to find FEC" that is part of the debugging I added.
It is not necessarily an error.  It just means that a label mapping came
in and we were not able to find an exact match (ie prefix AND nexthop have
to match).  In this case I believe is it the prefix of the transit
subnet (which should come back as not matching ... the nexthop does not mat=
ch).

Besides the crash related to ECMP is everything else working ok for you?

On Tue, Mar 20, 2007 at 05:07:21PM +0100, Marco Schmidt wrote:
> Hello James,
>=20
> the Labeling is working better now, thank you for the debugging.
> But as you expected, the problems aren't completely solved.
> I think there is a problem with networks where loops are possible...
>=20
> The labelspaces and crossconnects are also marked inactive on my
> systems, but it is possible to send labeled packets through the
> network.
>=20
> It is! working at the moment, but I had to remove the link between E4
> and E3. (one, that made redundant paths possible)
> Zebra/Ldpd doesn't seem to be able to manage redundant paths with the
> same destination.
> It crashed after enabling the link again. Have a look at the logfiles:
> http://www-user.tu-chemnitz.de/~smarco/MPLS/20070320_v2/E3_with_crash_aft=
er_linkupdate.log
> There are a few more logs from today in the MPLS directory.
>=20
> Right now, I found the same error as Gonzalo (at the bottom of the
> file):
> 2007/03/20 16:08:01 LDP: found pending NHLFE: 0x9782308
> 2007/03/20 16:08:01 ZEBRA: zebra message comes from socket [17]
> 2007/03/20 16:08:01 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/20 16:08:01 ZEBRA: IPV41 mismatch
> >>2007/03/20 16:08:01 ZEBRA: mpls_ftn_register: unable to find FEC 172.16=
.20.0/24
> 2007/03/20 16:08:01 ZEBRA: zebra message comes from socket [17]
> 2007/03/20 16:08:01 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
> ZEBRA: Received signal 11 at 1174403281 (si_addr 0xe, PC 0x80539cf); abor=
ting...
> Program counter: /usr/sbin/zebra[0x80539cf]
>=20
> Regards,
> Marco
>=20
>=20
>=20
> > Hi:
>=20
> > I've downloaded your revised quagga RPM for FC5 and I tried this scenar=
io:
>=20
> >                   eth0   eth1             eth1   eth0
> >        12.0.0.1-------PE1---------------------PE2-------13.0.0.1
> >                          .1  10.0.0.0/24    .2
>=20
> > I enclose the configuration and commands related to MPLS and LDP at
> > PE2 and the log file created debugging zebra.
>=20
> > At the bottom of the log file there's: "unable to find FEC
> > 10.0.0.0/24", furthermore, the output of "sh mpls forwarding" shows the=
 labelspace as inactive.
>=20
> > Please take a look, I hope it could be helpful to figure out what's hap=
pening.
>=20
> > Thanks in advance,
>=20
> > Gonzalo.
>=20
> > PE3 config
> > ------------------------------------------------------------------------
>=20
> > Current configuration:
> > !
> > hostname PE3
> > log file /var/log/quagga/1955d.log
> > !
> > debug zebra events
> > debug zebra packet
> > debug zebra kernel
> > debug zebra rib
> > !
> > interface eth0
> >  ipv6 nd suppress-ra
> > !
> > interface eth1
> >  ipv6 nd suppress-ra
> >  mpls ip
> >  mpls labelspace 0
> > !
> > interface lo
> > !
> > interface mpls0
> >  ipv6 nd suppress-ra
> > !
> > interface sit0
> >  ipv6 nd suppress-ra
> > !
> > mpls ldp
> >  egress connected
> > !
> > router ospf
> >  network 10.0.0.0/24 area 0.0.0.0
> >  network 13.0.0.0/24 area 0.0.0.0
> > !
> > ip forwarding
> > !
> > line vty
> > !
>=20
> > PE3# sh ip route
> > Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
> >        I - ISIS, B - BGP, > - selected route, * - FIB route
>=20
> > O   10.0.0.0/24 [110/10] is directly connected, eth1, 00:02:49
> C>>* 10.0.0.0/24 is directly connected, eth1
> O>>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:01:37
> > O   13.0.0.0/24 [110/10] is dPE3# sh ldp neig
> > Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
> >         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
> >         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
> >         Up time: 00:04:08
> >         LDP discovery sources:
> >           eth1
> >         Addresses bound to peer:
> >           10.0.0.1      12.0.0.1
> > irectly connected, eth0, 00:02:43
> C>>* 13.0.0.0/24 is directly connected, eth0
> C>>* 127.0.0.0/8 is directly connected, lo
>=20
> > PE3# sh mpls for
> > Insegments:
> >   Lbl Spc  Label Owner
> >     0      10000 ldp    (inactive)
> > Total 1
>=20
> > Outsegments:
> >   Interface          Label Next Hop        Owner
> >   eth1               10000 10.0.0.1        ldp
> > Total 1
>=20
> > Cross Connects:
>=20
> > Total 0
>=20
> > PE3# sh ldp ses
> > 2  9.151.111.152 45  OPERATIONAL
> >         10.0.0.1
> >         12.0.0.1
>=20
> > PE3# sh ldp disc
>=20
> > Local LSR Identifier: 13.0.0.1
>=20
> > Interface Discovery Sources:
> >         eth1: xmit/recv
> >             LDP Id: 12.0.0.1:0
>=20
> > Targeted Discovery Sources:
> >         No configured peers
>=20
> > PE3# sh ldp neig
> > Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
> >         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
> >         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
> >         Up time: 00:04:08
> >         LDP discovery sources:
> >           eth1
> >         Addresses bound to peer:
> >           10.0.0.1      12.0.0.1
>=20
> > [root@... ~]# mpls ilm
> > ILM entry label gen 10000 labelspace 0 proto ipv4
> >         pop peek  (0 bytes, 0 pkts)
>=20
> > [root@... ~]# mpls nhlfe
> > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
> >         push gen 10000 set eth1 ipv4 10.0.0.1  (0 bytes, 0 pkts)
>=20
> > [root@... ~]# ip route
> > 10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.2
> > 12.0.0.0/24 via 10.0.0.1 dev eth1  proto zebra  metric 20
> > 13.0.0.0/24 dev eth0  proto kernel  scope link  src 13.0.0.1
>=20
> > [root@... ~]# rpm -q quagga
> > quagga-0.99.6-01.fc5.mpls.1.955d
>=20
> > /var/log/quagga/1955d.log
> > ------------------------------------------------------------------------
>=20
> > 2007/03/20 10:30:40 OSPF: interface 10.0.0.2 [3] join AllSPFRouters Mul=
ticast group.
> > 2007/03/20 10:30:40 ZEBRA: zebra message comes from socket [14]
> > 2007/03/20 10:30:40 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD=
] 17
> > 2007/03/20 10:30:40 ZEBRA: rib_link: rn 0x8efcf48, rib 0x8f02c70
> > 2007/03/20 10:30:40 ZEBRA: rib_link: new head, rn_status copied over
> > 2007/03/20 10:30:41 ZEBRA: rib_process: Updating existing route, select=
 0x8efcf88, fib 0x8efcf88
> > 2007/03/20 10:30:43 OSPF: interface 13.0.0.1 [4] join AllSPFRouters Mul=
ticast group.
> > 2007/03/20 10:30:46 ZEBRA: zebra message comes from socket [14]
> > 2007/03/20 10:30:46 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD=
] 17
> > 2007/03/20 10:30:46 ZEBRA: rib_link: rn 0x8efd150, rib 0x8f03158
> > 2007/03/20 10:30:46 ZEBRA: rib_link: new head, rn_status copied over
> > 2007/03/20 10:30:46 ZEBRA: rib_process: Updating existing route, select=
 0x8efd190, fib 0x8efd190
> > 2007/03/20 10:31:05 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 no=
w Init/DROther
> > 2007/03/20 10:31:20 OSPF: DR-Election[1st]: Backup 10.0.0.2
> > 2007/03/20 10:31:20 OSPF: DR-Election[1st]: DR     10.0.0.2
> > 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: Backup 10.0.0.1
> > 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: DR     10.0.0.2
> > 2007/03/20 10:31:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now=
 DR
> > 2007/03/20 10:31:20 OSPF: interface 10.0.0.2 [3] join AllDRouters Multi=
cast group.
> > 2007/03/20 10:31:23 OSPF: DR-Election[1st]: Backup 13.0.0.1
> > 2007/03/20 10:31:23 OSPF: DR-Election[1st]: DR     13.0.0.1
> > 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: Backup 0.0.0.0
> > 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: DR     13.0.0.1
> > 2007/03/20 10:31:23 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now=
 DR
> > 2007/03/20 10:31:23 OSPF: interface 13.0.0.1 [4] join AllDRouters Multi=
cast group.
> > 2007/03/20 10:31:45 OSPF: Packet[DD]: Neighbor 12.0.0.1: Initial DBD fr=
om Slave, ignoring.
> > 2007/03/20 10:31:45 OSPF: DR-Election[1st]: Backup 10.0.0.1
> > 2007/03/20 10:31:45 OSPF: DR-Election[1st]: DR     10.0.0.2
> > 2007/03/20 10:31:50 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation don=
e (Master).
> > 2007/03/20 10:31:50 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 no=
w Loading/Backup
> > 2007/03/20 10:31:50 OSPF: nsm_change_state(12.0.0.1, Loading ->
> > Full): scheduling new router-LSA origination
> > 2007/03/20 10:31:52 ZEBRA: zebra message comes from socket [14]
> > 2007/03/20 10:31:52 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD=
] 17
> > 2007/03/20 10:31:52 ZEBRA: rib_link: rn 0x8f032a8, rib 0x8f031e0
> > 2007/03/20 10:31:52 ZEBRA: rib_process: Adding route, select 0x8f031e0
> > 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop):
> > RTM_NEWROUTE 12.0.0.0/24, type IPv4=20
> > 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop): next=
hop via 10.0.0.1 if 3
> > 2007/03/20 10:31:52 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(=
24), seq=3D6
> > 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd ACK:
> > type=3DRTM_NEWROUTE(24), seq=3D6, pid=3D0
> > 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-listen type
> > RTM_NEWROUTE(24), seq=3D6, pid=3D4294963198
> > 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd packet comes=
 from netlink-listen
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 LDP: route 10.0.0.0/24
> > 2007/03/20 10:32:09 LDP:        num ifindex 0
> > 2007/03/20 10:32:09 LDP:        attached
> > 2007/03/20 10:32:09 LDP:        ifindex 3
> > 2007/03/20 10:32:09 LDP:        add
> > 2007/03/20 10:32:09 LDP: route 13.0.0.0/24
> > 2007/03/20 10:32:09 LDP:        num ifindex 0
> > 2007/03/20 10:32:09 LDP:        attached
> > 2007/03/20 10:32:09 LDP:        ifindex 4
> > 2007/03/20 10:32:09 LDP:        add
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 LDP: route 12.0.0.0/24
> > 2007/03/20 10:32:09 LDP:        num nexthop 0
> > 2007/03/20 10:32:09 LDP:        nexthop 10.0.0.1
> > 2007/03/20 10:32:09 LDP:        add
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_A=
DD] 1
> > 2007/03/20 10:32:15 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), se=
q=3D1
> > 2007/03/20 10:32:15 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: ty=
pe=3D(29), seq=3D1, pid=3D0
> > 2007/03/20 10:32:52 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCK=
ING
> > 2007/03/20 10:32:52 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO:
> > 2007/03/20 10:32:57 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCK=
ING
> > 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_IN_SEGMEN=
T_ADD] 10
> > 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), se=
q=3D2
> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: ty=
pe=3D(29), seq=3D2, pid=3D0
> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type=
 (29), seq=3D0, pid=3D0
> > 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_OUT_SEGME=
NT_ADD] 39
> > 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), =
seq=3D1
> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type =
(29), seq=3D1, pid=3D4294963196
> > 2007/03/20 10:32:59 ZEBRA: netlink_talk: ignoring message type 0x001d
> > 2007/03/20 10:32:59 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000002
> > 2007/03/20 10:32:59 LDP: found pending NHLFE: 0x997e9a8
> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type=
 (29), seq=3D1, pid=3D4294963196
> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe
> > packet comes from mpls-netlink-listen
> > 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> > 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> > 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
> > 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
> > 2007/03/20 10:32:59 ZEBRA: mpls_ftn_register: unable to find FEC 10.0.0=
.0/24
>=20
>=20
> > -----Mensaje original-----
> > De: James R. Leu [mailto:jleu@...]
> > Enviado el: mar 20/03/2007 4:11
> > Para: Marco Schmidt
> > CC: Sienes Rodr?guez Gonzalo; mpls-linux-devel@...
> > Asunto: Re: [mpls-linux-devel] LDP problems
> > =20
> > I've added some additional debugging.  In the process I was able to rep=
roduce
> > a similar failure multiple times and I found a couple place were I was
> > using uninitialized structures.  By correctly zeroing these structures
> > I was able to fix the failure I was seeing.  I do not presume this will
> > fix the failures you both are seeing, but the debugging should help
> > us figure what is happening.
>=20
> > Please download version 1.955d of quagga from sf.net
>=20
> >   =20
> > http://sourceforge.net/project/showfiles.php?group_id=3D15443&package_i=
d=3D12482
>=20
>=20
> > On Mon, Mar 19, 2007 at 01:03:04PM +0100, Marco Schmidt wrote:
> >> Here is what I got so far...
> >>=20
> >> I'm experiencing the same problems. Some connections are labeled, most
> >> of them are not - that differs from friday, where only one PC didn't
> >> work properly.
> >> In the non-working-case, LDPd finds the pending NHLFEs, but does nothi=
ng more.
> >>=20
> >> ...
> >> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
> >> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
> >> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
> >> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> >> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD]=
 11
> >> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> >> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD]=
 11
> >> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> >> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD]=
 11
> >> whole log can be found here:
> >> http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.=
log
> >>=20
> >>=20
> >> Different reaction where the binding works properly:
> >>=20
> >> ...
> >> >2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen typ=
e (29), seq=3D1, pid=3D4294963188
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe pack=
et comes from mpls-netlink-listen
> >> 2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
> >> 2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD]=
 11
> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM=
_DELROUTE 172.16.30.0/24, type IPv4=20
> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nex=
thop via 10.0.5.1 if 2
> >> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE=
(25), seq=3D7
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=
=3DRTM_DELROUTE(25), seq=3D7, pid=3D0
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM=
_DELROUTE(25), seq=3D7, pid=3D4294963190
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet come=
s from netlink-listen
> >> 2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM=
_NEWROUTE 172.16.30.0/24, type IPv4=20
> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nex=
thop via 10.0.5.1 if 2
> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): MPL=
S info 00000009
> >> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE=
(24), seq=3D8
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=
=3DRTM_NEWROUTE(24), seq=3D8, pid=3D0
> >> >2007/03/19 12:07:44 LDP: route 172.16.30.0/24
> >> >2007/03/19 12:07:44 LDP:        num nexthop 0
> >> >2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
> >> >2007/03/19 12:07:44 LDP:        add
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM=
_NEWROUTE(24), seq=3D8, pid=3D4294963190
> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet come=
s from netlink-listen
> >>=20
> >> Here, the label binding appears unter "ip route show" command.
> >> whole log: http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label=
_binding_and_zebra_crash121437.log
> >>=20
> >> The marked operations never happen at the non-working links.
> >>=20
> >> LDPd sometimes closes because of I/O errors, but there are no messages
> >> in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
> >> message (can be found two times in the above logfile)
> >>=20
> >> 2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] =
11
> >> ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); a=
borting...
> >> Program counter: /usr/sbin/zebra[0x80537b1]
> >>=20
> >> My conf-files can also be found in die MPLS directory http://www-user.=
tu-chemnitz.de/~smarco/MPLS/
> >>=20
> >> Regards,
> >> Marco
> >>=20
> >>=20
> >>=20
> >> > Hello everybody:
> >>=20
> >> > I've migrated my PCs from FC4 to FC5 with all the RPMs for the
> >> > 1.955 version. The problem must be that I'm forgetting something or
> >> > doing something wrong cause I've notice that Julien or Marco were at
> >> > the same situacion and they both are able to run LDP.
> >>=20
> >> > This is what I do, it's a simple scenario with two LSRs:
> >>=20
> >> > 1. First of all I load "mpls4" and activate ip forwarding.
> >> > 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
> >> >    Without specifying the config files (though I tried it also with =
the .conf files and even
> >> >    starting them as services ("service ... start")).
> >> > 3. Then I entered vtysh to type by here ALL the config.
> >> >    -First, the OSPF networks: router ospf, network ... area 0.
> >> >    -I wait to the new routes to be discovered and then I configured =
ldp.
> >> >    -mpls ldp, and in the corresponding interface of each LSR to the =
MPLS link:
> >> >     mpls ip and mpls labelspace 0.
> >>=20
> >> > The OSPF routes are discovered correctly, and the NHLFE and ILM
> >> > entries, created properly, but I'm not able to send labelled packets
> >> > through the mpls link I'm trying to set up.
> >>=20
> >> > If someone working with FC5 and LDP running could tell me his method=
 should be very useful.
> >>=20
> >> > Thanks in advance,
> >> > Gonzalo.
> >>=20
> >>=20
> >>=20
> >>=20
> >> > --------------------------------------------------------------------=
-----
> >> > Take Surveys. Earn Cash. Influence the Future of IT
> >> > Join SourceForge.net's Techsay panel and you'll get the chance to sh=
are your
> >> > opinions on IT & business topics through brief surveys-and earn cash
> >> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&C=
ID=3DDEVDEV
> >> > _______________________________________________
> >> > mpls-linux-devel mailing list
> >> > mpls-linux-devel@...
> >> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
> >>=20
> >>=20
> >>=20
> >>=20
> >>=20
> >> ----------------------------------------------------------------------=
---
> >> Take Surveys. Earn Cash. Influence the Future of IT
> >> Join SourceForge.net's Techsay panel and you'll get the chance to shar=
e your
> >> opinions on IT & business topics through brief surveys-and earn cash
> >> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> >> _______________________________________________
> >> mpls-linux-devel mailing list
> >> mpls-linux-devel@...
> >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>=20
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jleu@...

Re: [mpls-linux-devel] LDP problems

From: Marco Schmidt <marco.schmidt@s2...> - 2007-03-21 10:26

Well, I'm glad to say that everything seems to work properly.

Just raising the cost on one link, so that there are no more ECMPs,
done.
Dynamical updates now work on "link failures", OSPF updates the routing
tables and LDP reacts as it should.

I'll do some testing with other modes than the default ones.

Regards, Marco


> Thank you for your report.  ECMP is currently not supported via
> ldp-portable.  It is something I hope to support in the next release.
> For now can you change the OSPF cost on that link to see if it works
> with the link connected?

> As for the "unable to find FEC" that is part of the debugging I added.
> It is not necessarily an error.  It just means that a label mapping came
> in and we were not able to find an exact match (ie prefix AND nexthop have
> to match).  In this case I believe is it the prefix of the transit
> subnet (which should come back as not matching ... the nexthop does not match).

> Besides the crash related to ECMP is everything else working ok for you?

> On Tue, Mar 20, 2007 at 05:07:21PM +0100, Marco Schmidt wrote:
>> Hello James,
>> 
>> the Labeling is working better now, thank you for the debugging.
>> But as you expected, the problems aren't completely solved.
>> I think there is a problem with networks where loops are possible...
>> 
>> The labelspaces and crossconnects are also marked inactive on my
>> systems, but it is possible to send labeled packets through the
>> network.
>> 
>> It is! working at the moment, but I had to remove the link between E4
>> and E3. (one, that made redundant paths possible)
>> Zebra/Ldpd doesn't seem to be able to manage redundant paths with the
>> same destination.
>> It crashed after enabling the link again. Have a look at the logfiles:
>> http://www-user.tu-chemnitz.de/~smarco/MPLS/20070320_v2/E3_with_crash_after_linkupdate.log
>> There are a few more logs from today in the MPLS directory.
>> 
>> Right now, I found the same error as Gonzalo (at the bottom of the
>> file):
>> 2007/03/20 16:08:01 LDP: found pending NHLFE: 0x9782308
>> 2007/03/20 16:08:01 ZEBRA: zebra message comes from socket [17]
>> 2007/03/20 16:08:01 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> 2007/03/20 16:08:01 ZEBRA: IPV41 mismatch
>> >>2007/03/20 16:08:01 ZEBRA: mpls_ftn_register: unable to find FEC 172.16.20.0/24
>> 2007/03/20 16:08:01 ZEBRA: zebra message comes from socket [17]
>> 2007/03/20 16:08:01 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
>> ZEBRA: Received signal 11 at 1174403281 (si_addr 0xe, PC 0x80539cf); aborting...
>> Program counter: /usr/sbin/zebra[0x80539cf]
>> 
>> Regards,
>> Marco
>> 
>> 
>> 
>> > Hi:
>> 
>> > I've downloaded your revised quagga RPM for FC5 and I tried this scenario:
>> 
>> >                   eth0   eth1             eth1   eth0
>> >        12.0.0.1-------PE1---------------------PE2-------13.0.0.1
>> >                          .1  10.0.0.0/24    .2
>> 
>> > I enclose the configuration and commands related to MPLS and LDP at
>> > PE2 and the log file created debugging zebra.
>> 
>> > At the bottom of the log file there's: "unable to find FEC
>> > 10.0.0.0/24", furthermore, the output of "sh mpls forwarding" shows the labelspace as inactive.
>> 
>> > Please take a look, I hope it could be helpful to figure out what's happening.
>> 
>> > Thanks in advance,
>> 
>> > Gonzalo.
>> 
>> > PE3 config
>> > ------------------------------------------------------------------------
>> 
>> > Current configuration:
>> > !
>> > hostname PE3
>> > log file /var/log/quagga/1955d.log
>> > !
>> > debug zebra events
>> > debug zebra packet
>> > debug zebra kernel
>> > debug zebra rib
>> > !
>> > interface eth0
>> >  ipv6 nd suppress-ra
>> > !
>> > interface eth1
>> >  ipv6 nd suppress-ra
>> >  mpls ip
>> >  mpls labelspace 0
>> > !
>> > interface lo
>> > !
>> > interface mpls0
>> >  ipv6 nd suppress-ra
>> > !
>> > interface sit0
>> >  ipv6 nd suppress-ra
>> > !
>> > mpls ldp
>> >  egress connected
>> > !
>> > router ospf
>> >  network 10.0.0.0/24 area 0.0.0.0
>> >  network 13.0.0.0/24 area 0.0.0.0
>> > !
>> > ip forwarding
>> > !
>> > line vty
>> > !
>> 
>> > PE3# sh ip route
>> > Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
>> >        I - ISIS, B - BGP, > - selected route, * - FIB route
>> 
>> > O   10.0.0.0/24 [110/10] is directly connected, eth1, 00:02:49
>> C>>* 10.0.0.0/24 is directly connected, eth1
>> O>>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:01:37
>> > O   13.0.0.0/24 [110/10] is dPE3# sh ldp neig
>> > Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
>> >         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
>> >         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
>> >         Up time: 00:04:08
>> >         LDP discovery sources:
>> >           eth1
>> >         Addresses bound to peer:
>> >           10.0.0.1      12.0.0.1
>> > irectly connected, eth0, 00:02:43
>> C>>* 13.0.0.0/24 is directly connected, eth0
>> C>>* 127.0.0.0/8 is directly connected, lo
>> 
>> > PE3# sh mpls for
>> > Insegments:
>> >   Lbl Spc  Label Owner
>> >     0      10000 ldp    (inactive)
>> > Total 1
>> 
>> > Outsegments:
>> >   Interface          Label Next Hop        Owner
>> >   eth1               10000 10.0.0.1        ldp
>> > Total 1
>> 
>> > Cross Connects:
>> 
>> > Total 0
>> 
>> > PE3# sh ldp ses
>> > 2  9.151.111.152 45  OPERATIONAL
>> >         10.0.0.1
>> >         12.0.0.1
>> 
>> > PE3# sh ldp disc
>> 
>> > Local LSR Identifier: 13.0.0.1
>> 
>> > Interface Discovery Sources:
>> >         eth1: xmit/recv
>> >             LDP Id: 12.0.0.1:0
>> 
>> > Targeted Discovery Sources:
>> >         No configured peers
>> 
>> > PE3# sh ldp neig
>> > Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
>> >         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
>> >         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
>> >         Up time: 00:04:08
>> >         LDP discovery sources:
>> >           eth1
>> >         Addresses bound to peer:
>> >           10.0.0.1      12.0.0.1
>> 
>> > [root@... ~]# mpls ilm
>> > ILM entry label gen 10000 labelspace 0 proto ipv4
>> >         pop peek  (0 bytes, 0 pkts)
>> 
>> > [root@... ~]# mpls nhlfe
>> > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
>> >         push gen 10000 set eth1 ipv4 10.0.0.1  (0 bytes, 0 pkts)
>> 
>> > [root@... ~]# ip route
>> > 10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.2
>> > 12.0.0.0/24 via 10.0.0.1 dev eth1  proto zebra  metric 20
>> > 13.0.0.0/24 dev eth0  proto kernel  scope link  src 13.0.0.1
>> 
>> > [root@... ~]# rpm -q quagga
>> > quagga-0.99.6-01.fc5.mpls.1.955d
>> 
>> > /var/log/quagga/1955d.log
>> > ------------------------------------------------------------------------
>> 
>> > 2007/03/20 10:30:40 OSPF: interface 10.0.0.2 [3] join AllSPFRouters Multicast group.
>> > 2007/03/20 10:30:40 ZEBRA: zebra message comes from socket [14]
>> > 2007/03/20 10:30:40 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] 17
>> > 2007/03/20 10:30:40 ZEBRA: rib_link: rn 0x8efcf48, rib 0x8f02c70
>> > 2007/03/20 10:30:40 ZEBRA: rib_link: new head, rn_status copied over
>> > 2007/03/20 10:30:41 ZEBRA: rib_process: Updating existing route, select 0x8efcf88, fib 0x8efcf88
>> > 2007/03/20 10:30:43 OSPF: interface 13.0.0.1 [4] join AllSPFRouters Multicast group.
>> > 2007/03/20 10:30:46 ZEBRA: zebra message comes from socket [14]
>> > 2007/03/20 10:30:46 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] 17
>> > 2007/03/20 10:30:46 ZEBRA: rib_link: rn 0x8efd150, rib 0x8f03158
>> > 2007/03/20 10:30:46 ZEBRA: rib_link: new head, rn_status copied over
>> > 2007/03/20 10:30:46 ZEBRA: rib_process: Updating existing route, select 0x8efd190, fib 0x8efd190
>> > 2007/03/20 10:31:05 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now Init/DROther
>> > 2007/03/20 10:31:20 OSPF: DR-Election[1st]: Backup 10.0.0.2
>> > 2007/03/20 10:31:20 OSPF: DR-Election[1st]: DR     10.0.0.2
>> > 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: Backup 10.0.0.1
>> > 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: DR     10.0.0.2
>> > 2007/03/20 10:31:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now DR
>> > 2007/03/20 10:31:20 OSPF: interface 10.0.0.2 [3] join AllDRouters Multicast group.
>> > 2007/03/20 10:31:23 OSPF: DR-Election[1st]: Backup 13.0.0.1
>> > 2007/03/20 10:31:23 OSPF: DR-Election[1st]: DR     13.0.0.1
>> > 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: Backup 0.0.0.0
>> > 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: DR     13.0.0.1
>> > 2007/03/20 10:31:23 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now DR
>> > 2007/03/20 10:31:23 OSPF: interface 13.0.0.1 [4] join AllDRouters Multicast group.
>> > 2007/03/20 10:31:45 OSPF: Packet[DD]: Neighbor 12.0.0.1: Initial DBD from Slave, ignoring.
>> > 2007/03/20 10:31:45 OSPF: DR-Election[1st]: Backup 10.0.0.1
>> > 2007/03/20 10:31:45 OSPF: DR-Election[1st]: DR     10.0.0.2
>> > 2007/03/20 10:31:50 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done (Master).
>> > 2007/03/20 10:31:50 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now Loading/Backup
>> > 2007/03/20 10:31:50 OSPF: nsm_change_state(12.0.0.1, Loading ->
>> > Full): scheduling new router-LSA origination
>> > 2007/03/20 10:31:52 ZEBRA: zebra message comes from socket [14]
>> > 2007/03/20 10:31:52 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] 17
>> > 2007/03/20 10:31:52 ZEBRA: rib_link: rn 0x8f032a8, rib 0x8f031e0
>> > 2007/03/20 10:31:52 ZEBRA: rib_process: Adding route, select 0x8f031e0
>> > 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop):
>> > RTM_NEWROUTE 12.0.0.0/24, type IPv4 
>> > 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop): nexthop via 10.0.0.1 if 3
>> > 2007/03/20 10:31:52 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24), seq=6
>> > 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd ACK:
>> > type=RTM_NEWROUTE(24), seq=6, pid=0
>> > 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-listen type
>> > RTM_NEWROUTE(24), seq=6, pid=4294963198
>> > 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd packet comes from netlink-listen
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 LDP: route 10.0.0.0/24
>> > 2007/03/20 10:32:09 LDP:        num ifindex 0
>> > 2007/03/20 10:32:09 LDP:        attached
>> > 2007/03/20 10:32:09 LDP:        ifindex 3
>> > 2007/03/20 10:32:09 LDP:        add
>> > 2007/03/20 10:32:09 LDP: route 13.0.0.0/24
>> > 2007/03/20 10:32:09 LDP:        num ifindex 0
>> > 2007/03/20 10:32:09 LDP:        attached
>> > 2007/03/20 10:32:09 LDP:        ifindex 4
>> > 2007/03/20 10:32:09 LDP:        add
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 LDP: route 12.0.0.0/24
>> > 2007/03/20 10:32:09 LDP:        num nexthop 0
>> > 2007/03/20 10:32:09 LDP:        nexthop 10.0.0.1
>> > 2007/03/20 10:32:09 LDP:        add
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD] 1
>> > 2007/03/20 10:32:15 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq=1
>> > 2007/03/20 10:32:15 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type=(29), seq=1, pid=0
>> > 2007/03/20 10:32:52 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING
>> > 2007/03/20 10:32:52 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO:
>> > 2007/03/20 10:32:57 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING
>> > 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_IN_SEGMENT_ADD] 10
>> > 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq=2
>> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type=(29), seq=2, pid=0
>> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type (29), seq=0, pid=0
>> > 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_OUT_SEGMENT_ADD] 39
>> > 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), seq=1
>> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type (29), seq=1, pid=4294963196
>> > 2007/03/20 10:32:59 ZEBRA: netlink_talk: ignoring message type 0x001d
>> > 2007/03/20 10:32:59 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000002
>> > 2007/03/20 10:32:59 LDP: found pending NHLFE: 0x997e9a8
>> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type (29), seq=1, pid=4294963196
>> > 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe
>> > packet comes from mpls-netlink-listen
>> > 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
>> > 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> > 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
>> > 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
>> > 2007/03/20 10:32:59 ZEBRA: mpls_ftn_register: unable to find FEC 10.0.0.0/24
>> 
>> 
>> > -----Mensaje original-----
>> > De: James R. Leu [mailto:jleu@...]
>> > Enviado el: mar 20/03/2007 4:11
>> > Para: Marco Schmidt
>> > CC: Sienes Rodr?guez Gonzalo; mpls-linux-devel@...
>> > Asunto: Re: [mpls-linux-devel] LDP problems
>> >  
>> > I've added some additional debugging.  In the process I was able to reproduce
>> > a similar failure multiple times and I found a couple place were I was
>> > using uninitialized structures.  By correctly zeroing these structures
>> > I was able to fix the failure I was seeing.  I do not presume this will
>> > fix the failures you both are seeing, but the debugging should help
>> > us figure what is happening.
>> 
>> > Please download version 1.955d of quagga from sf.net
>> 
>> >    
>> > http://sourceforge.net/project/showfiles.php?group_id=15443&package_id=12482
>> 
>> 
>> > On Mon, Mar 19, 2007 at 01:03:04PM +0100, Marco Schmidt wrote:
>> >> Here is what I got so far...
>> >> 
>> >> I'm experiencing the same problems. Some connections are labeled, most
>> >> of them are not - that differs from friday, where only one PC didn't
>> >> work properly.
>> >> In the non-working-case, LDPd finds the pending NHLFEs, but does nothing more.
>> >> 
>> >> ...
>> >> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
>> >> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
>> >> 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
>> >> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
>> >> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> >> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
>> >> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> >> 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
>> >> 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> >> whole log can be found here:
>> >> http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.log
>> >> 
>> >> 
>> >> Different reaction where the binding works properly:
>> >> 
>> >> ...
>> >> >2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen type (29), seq=1, pid=4294963188
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet comes from mpls-netlink-listen
>> >> 2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
>> >> 2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_DELROUTE 172.16.30.0/24, type IPv4 
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nexthop via 10.0.5.1 if 2
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(25), seq=7
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=RTM_DELROUTE(25), seq=7, pid=0
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_DELROUTE(25), seq=7, pid=4294963190
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes from netlink-listen
>> >> 2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_NEWROUTE 172.16.30.0/24, type IPv4 
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): nexthop via 10.0.5.1 if 2
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): MPLS info 00000009
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24), seq=8
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=RTM_NEWROUTE(24), seq=8, pid=0
>> >> >2007/03/19 12:07:44 LDP: route 172.16.30.0/24
>> >> >2007/03/19 12:07:44 LDP:        num nexthop 0
>> >> >2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
>> >> >2007/03/19 12:07:44 LDP:        add
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWROUTE(24), seq=8, pid=4294963190
>> >> 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes from netlink-listen
>> >> 
>> >> Here, the label binding appears unter "ip route show" command.
>> >> whole log: http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label_binding_and_zebra_crash121437.log
>> >> 
>> >> The marked operations never happen at the non-working links.
>> >> 
>> >> LDPd sometimes closes because of I/O errors, but there are no messages
>> >> in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
>> >> message (can be found two times in the above logfile)
>> >> 
>> >> 2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
>> >> ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); aborting...
>> >> Program counter: /usr/sbin/zebra[0x80537b1]
>> >> 
>> >> My conf-files can also be found in die MPLS directory http://www-user.tu-chemnitz.de/~smarco/MPLS/
>> >> 
>> >> Regards,
>> >> Marco
>> >> 
>> >> 
>> >> 
>> >> > Hello everybody:
>> >> 
>> >> > I've migrated my PCs from FC4 to FC5 with all the RPMs for the
>> >> > 1.955 version. The problem must be that I'm forgetting something or
>> >> > doing something wrong cause I've notice that Julien or Marco were at
>> >> > the same situacion and they both are able to run LDP.
>> >> 
>> >> > This is what I do, it's a simple scenario with two LSRs:
>> >> 
>> >> > 1. First of all I load "mpls4" and activate ip forwarding.
>> >> > 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
>> >> >    Without specifying the config files (though I tried it also with the .conf files and even
>> >> >    starting them as services ("service ... start")).
>> >> > 3. Then I entered vtysh to type by here ALL the config.
>> >> >    -First, the OSPF networks: router ospf, network ... area 0.
>> >> >    -I wait to the new routes to be discovered and then I configured ldp.
>> >> >    -mpls ldp, and in the corresponding interface of each LSR to the MPLS link:
>> >> >     mpls ip and mpls labelspace 0.
>> >> 
>> >> > The OSPF routes are discovered correctly, and the NHLFE and ILM
>> >> > entries, created properly, but I'm not able to send labelled packets
>> >> > through the mpls link I'm trying to set up.
>> >> 
>> >> > If someone working with FC5 and LDP running could tell me his method should be very useful.
>> >> 
>> >> > Thanks in advance,
>> >> > Gonzalo.
>> >> 
>> >> 
>> >> 
>> >> 
>> >> > -------------------------------------------------------------------------
>> >> > Take Surveys. Earn Cash. Influence the Future of IT
>> >> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> >> > opinions on IT & business topics through brief surveys-and earn cash
>> >> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> >> > _______________________________________________
>> >> > mpls-linux-devel mailing list
>> >> > mpls-linux-devel@...
>> >> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>> >> 
>> >> 
>> >> 
>> >> 
>> >> 
>> >> -------------------------------------------------------------------------
>> >> Take Surveys. Earn Cash. Influence the Future of IT
>> >> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> >> opinions on IT & business topics through brief surveys-and earn cash
>> >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> >> _______________________________________________
>> >> mpls-linux-devel mailing list
>> >> mpls-linux-devel@...
>> >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>> 
>> 
>> 
>> 
>> 
>> 
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> mpls-linux-devel mailing list
>> mpls-linux-devel@...
>> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

Re: [mpls-linux-devel] LDP problems

From: James R. Leu <jleu@mi...> - 2007-03-22 05:01

Attachments: Message as HTML

Hello Gonzalo,

Can you compare your configuration and setup with what Marco
has done?  He has posted his configs at:

    http://www-user.tu-chemnitz.de/~smarco/MPLS/

I would like to figure out what is different in your setup
and fix any associated bugs.

On Tue, Mar 20, 2007 at 10:55:39AM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi:
>=20
> I've downloaded your revised quagga RPM for FC5 and I tried this scenario:
>=20
>                   eth0   eth1             eth1   eth0
>        12.0.0.1-------PE1---------------------PE2-------13.0.0.1
>                          .1  10.0.0.0/24    .2
>=20
> I enclose the configuration and commands related to MPLS and LDP at PE2 a=
nd the log file created debugging zebra.
>=20
> At the bottom of the log file there's: "unable to find FEC 10.0.0.0/24", =
furthermore, the output of "sh mpls forwarding" shows the labelspace as ina=
ctive.
>=20
> Please take a look, I hope it could be helpful to figure out what's happe=
ning.
>=20
> Thanks in advance,
>=20
> Gonzalo.
>=20
> PE3 config
> ------------------------------------------------------------------------
>=20
> Current configuration:
> !
> hostname PE3
> log file /var/log/quagga/1955d.log
> !
> debug zebra events
> debug zebra packet
> debug zebra kernel
> debug zebra rib
> !
> interface eth0
>  ipv6 nd suppress-ra
> !
> interface eth1
>  ipv6 nd suppress-ra
>  mpls ip
>  mpls labelspace 0
> !
> interface lo
> !
> interface mpls0
>  ipv6 nd suppress-ra
> !
> interface sit0
>  ipv6 nd suppress-ra
> !
> mpls ldp
>  egress connected
> !
> router ospf
>  network 10.0.0.0/24 area 0.0.0.0
>  network 13.0.0.0/24 area 0.0.0.0
> !
> ip forwarding
> !
> line vty
> !
>=20
> PE3# sh ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
>        I - ISIS, B - BGP, > - selected route, * - FIB route
>=20
> O   10.0.0.0/24 [110/10] is directly connected, eth1, 00:02:49
> C>* 10.0.0.0/24 is directly connected, eth1
> O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:01:37
> O   13.0.0.0/24 [110/10] is dPE3# sh ldp neig
> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
>         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
>         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
>         Up time: 00:04:08
>         LDP discovery sources:
>           eth1
>         Addresses bound to peer:
>           10.0.0.1      12.0.0.1
> irectly connected, eth0, 00:02:43
> C>* 13.0.0.0/24 is directly connected, eth0
> C>* 127.0.0.0/8 is directly connected, lo
>=20
> PE3# sh mpls for
> Insegments:
>   Lbl Spc  Label Owner
>     0      10000 ldp    (inactive)
> Total 1
>=20
> Outsegments:
>   Interface          Label Next Hop        Owner
>   eth1               10000 10.0.0.1        ldp
> Total 1
>=20
> Cross Connects:
>=20
> Total 0
>=20
> PE3# sh ldp ses
> 2  9.151.111.152 45  OPERATIONAL
>         10.0.0.1
>         12.0.0.1
>=20
> PE3# sh ldp disc
>=20
> Local LSR Identifier: 13.0.0.1
>=20
> Interface Discovery Sources:
>         eth1: xmit/recv
>             LDP Id: 12.0.0.1:0
>=20
> Targeted Discovery Sources:
>         No configured peers
>=20
> PE3# sh ldp neig
> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 13.0.0.1:0
>         TCP connection: 10.0.0.2.45483 - 10.0.0.1.646
>         State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
>         Up time: 00:04:08
>         LDP discovery sources:
>           eth1
>         Addresses bound to peer:
>           10.0.0.1      12.0.0.1
>=20
> [root@... ~]# mpls ilm
> ILM entry label gen 10000 labelspace 0 proto ipv4
>         pop peek  (0 bytes, 0 pkts)
>=20
> [root@... ~]# mpls nhlfe
> NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
>         push gen 10000 set eth1 ipv4 10.0.0.1  (0 bytes, 0 pkts)
>=20
> [root@... ~]# ip route
> 10.0.0.0/24 dev eth1  proto kernel  scope link  src 10.0.0.2
> 12.0.0.0/24 via 10.0.0.1 dev eth1  proto zebra  metric 20
> 13.0.0.0/24 dev eth0  proto kernel  scope link  src 13.0.0.1
>=20
> [root@... ~]# rpm -q quagga
> quagga-0.99.6-01.fc5.mpls.1.955d
>=20
> /var/log/quagga/1955d.log
> ------------------------------------------------------------------------
>=20
> 2007/03/20 10:30:40 OSPF: interface 10.0.0.2 [3] join AllSPFRouters Multi=
cast group.
> 2007/03/20 10:30:40 ZEBRA: zebra message comes from socket [14]
> 2007/03/20 10:30:40 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
> 2007/03/20 10:30:40 ZEBRA: rib_link: rn 0x8efcf48, rib 0x8f02c70
> 2007/03/20 10:30:40 ZEBRA: rib_link: new head, rn_status copied over
> 2007/03/20 10:30:41 ZEBRA: rib_process: Updating existing route, select 0=
x8efcf88, fib 0x8efcf88
> 2007/03/20 10:30:43 OSPF: interface 13.0.0.1 [4] join AllSPFRouters Multi=
cast group.
> 2007/03/20 10:30:46 ZEBRA: zebra message comes from socket [14]
> 2007/03/20 10:30:46 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
> 2007/03/20 10:30:46 ZEBRA: rib_link: rn 0x8efd150, rib 0x8f03158
> 2007/03/20 10:30:46 ZEBRA: rib_link: new head, rn_status copied over
> 2007/03/20 10:30:46 ZEBRA: rib_process: Updating existing route, select 0=
x8efd190, fib 0x8efd190
> 2007/03/20 10:31:05 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now =
Init/DROther
> 2007/03/20 10:31:20 OSPF: DR-Election[1st]: Backup 10.0.0.2
> 2007/03/20 10:31:20 OSPF: DR-Election[1st]: DR     10.0.0.2
> 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: Backup 10.0.0.1
> 2007/03/20 10:31:20 OSPF: DR-Election[2nd]: DR     10.0.0.2
> 2007/03/20 10:31:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now DR
> 2007/03/20 10:31:20 OSPF: interface 10.0.0.2 [3] join AllDRouters Multica=
st group.
> 2007/03/20 10:31:23 OSPF: DR-Election[1st]: Backup 13.0.0.1
> 2007/03/20 10:31:23 OSPF: DR-Election[1st]: DR     13.0.0.1
> 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: Backup 0.0.0.0
> 2007/03/20 10:31:23 OSPF: DR-Election[2nd]: DR     13.0.0.1
> 2007/03/20 10:31:23 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now DR
> 2007/03/20 10:31:23 OSPF: interface 13.0.0.1 [4] join AllDRouters Multica=
st group.
> 2007/03/20 10:31:45 OSPF: Packet[DD]: Neighbor 12.0.0.1: Initial DBD from=
 Slave, ignoring.
> 2007/03/20 10:31:45 OSPF: DR-Election[1st]: Backup 10.0.0.1
> 2007/03/20 10:31:45 OSPF: DR-Election[1st]: DR     10.0.0.2
> 2007/03/20 10:31:50 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done =
(Master).
> 2007/03/20 10:31:50 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now =
Loading/Backup
> 2007/03/20 10:31:50 OSPF: nsm_change_state(12.0.0.1, Loading -> Full): sc=
heduling new router-LSA origination
> 2007/03/20 10:31:52 ZEBRA: zebra message comes from socket [14]
> 2007/03/20 10:31:52 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] =
17
> 2007/03/20 10:31:52 ZEBRA: rib_link: rn 0x8f032a8, rib 0x8f031e0
> 2007/03/20 10:31:52 ZEBRA: rib_process: Adding route, select 0x8f031e0
> 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop): RTM_NE=
WROUTE 12.0.0.0/24, type IPv4=20
> 2007/03/20 10:31:52 ZEBRA: netlink_route_multipath() (single hop): nextho=
p via 10.0.0.1 if 3
> 2007/03/20 10:31:52 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24=
), seq=3D6
> 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT=
M_NEWROUTE(24), seq=3D6, pid=3D0
> 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-listen type RTM_NE=
WROUTE(24), seq=3D6, pid=3D4294963198
> 2007/03/20 10:31:52 ZEBRA: netlink_parse_info: netlink-cmd packet comes f=
rom netlink-listen
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 LDP: route 10.0.0.0/24
> 2007/03/20 10:32:09 LDP: 	num ifindex 0
> 2007/03/20 10:32:09 LDP: 	attached
> 2007/03/20 10:32:09 LDP: 	ifindex 3
> 2007/03/20 10:32:09 LDP: 	add
> 2007/03/20 10:32:09 LDP: route 13.0.0.0/24
> 2007/03/20 10:32:09 LDP: 	num ifindex 0
> 2007/03/20 10:32:09 LDP: 	attached
> 2007/03/20 10:32:09 LDP: 	ifindex 4
> 2007/03/20 10:32:09 LDP: 	add
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 LDP: route 12.0.0.0/24
> 2007/03/20 10:32:09 LDP: 	num nexthop 0
> 2007/03/20 10:32:09 LDP: 	nexthop 10.0.0.1
> 2007/03/20 10:32:09 LDP: 	add
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:09 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:09 ZEBRA: zebra message received [ZEBRA_REDISTRIBUTE_ADD=
] 1
> 2007/03/20 10:32:15 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq=
=3D1
> 2007/03/20 10:32:15 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type=
=3D(29), seq=3D1, pid=3D0
> 2007/03/20 10:32:52 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING
> 2007/03/20 10:32:52 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO:
> 2007/03/20 10:32:57 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING
> 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_IN_SEGMENT_=
ADD] 10
> 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq=
=3D2
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type=
=3D(29), seq=3D2, pid=3D0
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type (=
29), seq=3D0, pid=3D0
> 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_OUT_SEGMENT=
_ADD] 39
> 2007/03/20 10:32:59 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), se=
q=3D1
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type (2=
9), seq=3D1, pid=3D4294963196
> 2007/03/20 10:32:59 ZEBRA: netlink_talk: ignoring message type 0x001d
> 2007/03/20 10:32:59 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000002
> 2007/03/20 10:32:59 LDP: found pending NHLFE: 0x997e9a8
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-listen type (=
29), seq=3D1, pid=3D4294963196
> 2007/03/20 10:32:59 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet =
comes from mpls-netlink-listen
> 2007/03/20 10:32:59 ZEBRA: zebra message comes from socket [15]
> 2007/03/20 10:32:59 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] 11
> 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
> 2007/03/20 10:32:59 ZEBRA: IPV42 mismatch
> 2007/03/20 10:32:59 ZEBRA: mpls_ftn_register: unable to find FEC 10.0.0.0=
/24
>=20
>=20
> -----Mensaje original-----
> De: James R. Leu [mailto:jleu@...]
> Enviado el: mar 20/03/2007 4:11
> Para: Marco Schmidt
> CC: Sienes Rodr?guez Gonzalo; mpls-linux-devel@...
> Asunto: Re: [mpls-linux-devel] LDP problems
> =20
> I've added some additional debugging.  In the process I was able to repro=
duce
> a similar failure multiple times and I found a couple place were I was
> using uninitialized structures.  By correctly zeroing these structures
> I was able to fix the failure I was seeing.  I do not presume this will
> fix the failures you both are seeing, but the debugging should help
> us figure what is happening.
>=20
> Please download version 1.955d of quagga from sf.net
>=20
>     http://sourceforge.net/project/showfiles.php?group_id=3D15443&package=
_id=3D12482
>=20
>=20
> On Mon, Mar 19, 2007 at 01:03:04PM +0100, Marco Schmidt wrote:
> > Here is what I got so far...
> >=20
> > I'm experiencing the same problems. Some connections are labeled, most
> > of them are not - that differs from friday, where only one PC didn't
> > work properly.
> > In the non-working-case, LDPd finds the pending NHLFEs, but does nothin=
g more.
> >=20
> > ...
> > 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a856d8
> > 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a869a0
> > 2007/03/19 12:18:14 LDP: found pending NHLFE: 0x8a87c68
> > 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> > 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> > 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> > 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> > 2007/03/19 12:18:14 ZEBRA: zebra message comes from socket [17]
> > 2007/03/19 12:18:14 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> > whole log can be found here:
> > http://www-user.tu-chemnitz.de/~smarco/MPLS/E2_no_label_binding121814.l=
og
> >=20
> >=20
> > Different reaction where the binding works properly:
> >=20
> > ...
> > >2007/03/19 12:07:44 LDP: found pending NHLFE: 0x9ccb2e8
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-listen type=
 (29), seq=3D1, pid=3D4294963188
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packe=
t comes from mpls-netlink-listen
> > 2007/03/19 12:07:44 ZEBRA: zebra message comes from socket [18]
> > 2007/03/19 12:07:44 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] =
11
> > 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_=
DELROUTE 172.16.30.0/24, type IPv4=20
> > 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): next=
hop via 10.0.5.1 if 2
> > 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(=
25), seq=3D7
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3D=
RTM_DELROUTE(25), seq=3D7, pid=3D0
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_=
DELROUTE(25), seq=3D7, pid=3D4294963190
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes=
 from netlink-listen
> > 2007/03/19 12:07:44 ZEBRA: rib_process: Adding route, select 0x9763798
> > 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): RTM_=
NEWROUTE 172.16.30.0/24, type IPv4=20
> > 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): next=
hop via 10.0.5.1 if 2
> > 2007/03/19 12:07:44 ZEBRA: netlink_route_multipath() (single hop): MPLS=
 info 00000009
> > 2007/03/19 12:07:44 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(=
24), seq=3D8
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3D=
RTM_NEWROUTE(24), seq=3D8, pid=3D0
> > >2007/03/19 12:07:44 LDP: route 172.16.30.0/24
> > >2007/03/19 12:07:44 LDP:        num nexthop 0
> > >2007/03/19 12:07:44 LDP:        nexthop 10.0.5.1
> > >2007/03/19 12:07:44 LDP:        add
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-listen type RTM_=
NEWROUTE(24), seq=3D8, pid=3D4294963190
> > 2007/03/19 12:07:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes=
 from netlink-listen
> >=20
> > Here, the label binding appears unter "ip route show" command.
> > whole log: http://www-user.tu-chemnitz.de/~smarco/MPLS/E3_120744_label_=
binding_and_zebra_crash121437.log
> >=20
> > The marked operations never happen at the non-working links.
> >=20
> > LDPd sometimes closes because of I/O errors, but there are no messages
> > in the logfile. Zebra crashes when recieving a zebra_mpls_xc_add
> > message (can be found two times in the above logfile)
> >=20
> > 2007/03/19 12:14:37 ZEBRA: zebra message received [ZEBRA_MPLS_XC_ADD] 11
> > ZEBRA: Received signal 11 at 1174302877 (si_addr 0xe, PC 0x80537b1); ab=
orting...
> > Program counter: /usr/sbin/zebra[0x80537b1]
> >=20
> > My conf-files can also be found in die MPLS directory http://www-user.t=
u-chemnitz.de/~smarco/MPLS/
> >=20
> > Regards,
> > Marco
> >=20
> >=20
> >=20
> > > Hello everybody:
> >=20
> > > I've migrated my PCs from FC4 to FC5 with all the RPMs for the
> > > 1.955 version. The problem must be that I'm forgetting something or
> > > doing something wrong cause I've notice that Julien or Marco were at
> > > the same situacion and they both are able to run LDP.
> >=20
> > > This is what I do, it's a simple scenario with two LSRs:
> >=20
> > > 1. First of all I load "mpls4" and activate ip forwarding.
> > > 2. I launch the daemonds by "zebra/ospfd/ldpd -d -A 127.0.0.1".
> > >    Without specifying the config files (though I tried it also with t=
he .conf files and even
> > >    starting them as services ("service ... start")).
> > > 3. Then I entered vtysh to type by here ALL the config.
> > >    -First, the OSPF networks: router ospf, network ... area 0.
> > >    -I wait to the new routes to be discovered and then I configured l=
dp.
> > >    -mpls ldp, and in the corresponding interface of each LSR to the M=
PLS link:
> > >     mpls ip and mpls labelspace 0.
> >=20
> > > The OSPF routes are discovered correctly, and the NHLFE and ILM
> > > entries, created properly, but I'm not able to send labelled packets
> > > through the mpls link I'm trying to set up.
> >=20
> > > If someone working with FC5 and LDP running could tell me his method =
should be very useful.
> >=20
> > > Thanks in advance,
> > > Gonzalo.
> >=20
> >=20
> >=20
> >=20
> > > ---------------------------------------------------------------------=
----
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to sha=
re your
> > > opinions on IT & business topics through brief surveys-and earn cash
> > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CI=
D=3DDEVDEV
> > > _______________________________________________
> > > mpls-linux-devel mailing list
> > > mpls-linux-devel@...
> > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
> >=20
> >=20
> >=20
> >=20
> >=20
> > -----------------------------------------------------------------------=
--
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share=
 your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpls-linux-devel@...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>=20
> --=20
> James R. Leu
> jleu@...
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jleu@...

Re: [mpls-linux-devel] LDP problems

From: <gsr16959@al...> - 2007-03-22 10:35

Hi:

For you, Marco this is the config I made for the following simple =
scenario:      =20

                  eth0   eth1             eth1   eth0
       12.0.0.1-------PE1---------------------PE2-------13.0.0.1
                         .1  10.0.0.0/24    .2

I keep the config files for zebra, ospfd and ldpd empty (only log file =
and hostname) and I configure everything via vtysh:

PE1
-------------------------------------------------------------------------=
-

router ospf
	network 10.0.0.0/24 area 0
	network 12.0.0.0/24 area 0

mpls ldp

int eth1
	mpls labelspace 0
	mpls ip

PE2
-------------------------------------------------------------------------=
-

router ospf
	network 10.0.0.0/24 area 0
	network 13.0.0.0/24 area 0

mpls ldp

int eth1
	mpls labelspace 0
	mpls ip=09

At first I only type in the ospf commands and wait until new routes are =
learned to configure LDP. The label 10000 is distributed properly, the =
NHLFE and ILM entries are created but the problem is that it's not =
possible to associate the label with the route learned via ospf.

I tried your configuration files in my scenario, adding a dummy =
interface in each PE.

                  eth0   eth1             eth1   eth0
       12.0.0.1-------PE1---------------------PE2-------13.0.0.1
                       | .1   10.0.0.0/24   .2 |
                       |                       |
                       |dummy0                 |dummy0
                 192.168.0.1/32          192.168.0.2/32

Now I include at zebra.conf the directions of each interface and at =
ospf.conf, the whole config with eth0 and dummy0 as passive-interfaces =
and the dummy0 as the ID of the OSPF router.

After this I configure via vtysh the LDP commands for eth1.

The labels are distributed and I'm even able to send labeled packets =
from each PE to the dummy interface of the other.

But for the eth0 interfaces, the problem is the same as before, the =
label isn't bound to the corresponding route.

Regards,
Gonzalo.

Re: [mpls-linux-devel] LDP problems

From: Marco Schmidt <marco.schmidt@s2...> - 2007-03-22 13:05

Direct connected links are not labeled. LDPd does a local binding
(for 10.0.0.0/24 in yout case), but this isn't distributed.
From=20PE1 there should only be a label to the 13.0.0.0/xx net.
Would be unnecessary for direct neighbours to send labeled packets...

Strange that you are able to send packets to those dummy interfaces.
They neither show up via ifconfig nor via ip route show. The routes
are not distributed on my systems.

You did not use dummy interfaces before, did you? All I know is that
they have to be there ;-)

Regards,
Marco

> Hi:

> For you, Marco this is the config I made for the following simple scenari=
o:

>                   eth0   eth1             eth1   eth0
>        12.0.0.1-------PE1---------------------PE2-------13.0.0.1
>                          .1  10.0.0.0/24    .2

> I keep the config files for zebra, ospfd and ldpd empty (only log
> file and hostname) and I configure everything via vtysh:

> PE1
> --------------------------------------------------------------------------

> router ospf
>         network 10.0.0.0/24 area 0
>         network 12.0.0.0/24 area 0

> mpls ldp

> int eth1
>         mpls labelspace 0
>         mpls ip

> PE2
> --------------------------------------------------------------------------

> router ospf
>         network 10.0.0.0/24 area 0
>         network 13.0.0.0/24 area 0

> mpls ldp

> int eth1
>         mpls labelspace 0
>         mpls ip=20

> At first I only type in the ospf commands and wait until new routes
> are learned to configure LDP. The label 10000 is distributed
> properly, the NHLFE and ILM entries are created but the problem is
> that it's not possible to associate the label with the route learned via =
ospf.

> I tried your configuration files in my scenario, adding a dummy interface=
 in each PE.

>                   eth0   eth1             eth1   eth0
>        12.0.0.1-------PE1---------------------PE2-------13.0.0.1
>                        | .1   10.0.0.0/24   .2 |
>                        |                       |
>                        |dummy0                 |dummy0
>                  192.168.0.1/32          192.168.0.2/32

> Now I include at zebra.conf the directions of each interface and at
> ospf.conf, the whole config with eth0 and dummy0 as
> passive-interfaces and the dummy0 as the ID of the OSPF router.

> After this I configure via vtysh the LDP commands for eth1.

> The labels are distributed and I'm even able to send labeled
> packets from each PE to the dummy interface of the other.

> But for the eth0 interfaces, the problem is the same as before, the
> label isn't bound to the corresponding route.

> Regards,
> Gonzalo.



> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

[mpls-linux-devel] LDP problems solved

From: <gsr16959@al...> - 2007-04-02 08:07

Hi:

I've had some problems with the mail server so till now I couldn't =
report my last results. I tried a new config with 3 LSRs making a =
triangle, and typing all the config commands, but LDP configuration, by =
the .conf files of ZEBRA and OSPF; and it just work fine. Each LSR has 3 =
interfaces, eth0 and eth1 shared with other LSR and eth2 as a passive =
interface able to hang a non MPLS final equipment. Here it's the =
"running-config" of one of them. However, I'll provide the network =
diagram and all the config files and the process I followed in a web =
page.

Regards,
Gonzalo.

PE3# sh run
Building configuration...

Current configuration:
!
hostname PE3
log file /var/log/quagga/zebra_PE3.log
log file /var/log/quagga/ospfd_PE3.log
log file /var/log/quagga/ldpd_PE3.log
!
service advanced-vty
!
debug zebra events
debug zebra packet
debug zebra kernel
debug zebra rib
!
password root
enable password root
!
interface eth0
 ip address 10.1.3.2/24
 ipv6 nd suppress-ra
 mpls ip
 mpls labelspace 0
!
interface eth1
 ip address 10.2.3.2/24
 ipv6 nd suppress-ra
 mpls ip
 mpls labelspace 0
!
interface eth2
 ip address 10.3.3.1/24
 ipv6 nd suppress-ra
!
interface lo
 description Loopback
!
interface mpls0
 ipv6 nd suppress-ra
!
interface sit0
 ipv6 nd suppress-ra
!
mpls ldp
 egress connected
!
router ospf
 ospf router-id 192.168.0.3
 passive-interface eth2
 network 10.1.3.0/24 area 0.0.0.0
 network 10.2.3.0/24 area 0.0.0.0
 network 10.3.3.0/24 area 0.0.0.0
!
ip forwarding
!
line vty
 exec-timeout 0 0
!

[mpls-linux-devel] LDP recovery after link fall

From: <gsr16959@al...> - 2007-04-16 08:23

Hi James:

About three weeks ago I got LDP to work in a 3 LSRs scenario. Each =
router has three interfaces, two of them are used to configure a =
triangle between the routers (each one connected to the other 2) and the =
last interface isn't configure as MPLS so it could hang non MPLS =
networks.=20

Now the problem is that when a MPLS link falls, LDP daemon ,at the two =
LSRs wich share that link, stop running. So it's impossible the recovery =
of the LINK without a reconfiguration of those LSRs.

Have you tested this?

Thanks in advance,
Gonzalo.

Re: [mpls-linux-devel] LDP recovery after link fall

From: James R. Leu <jleu@mi...> - 2007-04-17 01:28

Attachments: Message as HTML

Hello,

On Mon, Apr 16, 2007 at 10:23:23AM +0200, Sienes Rodr?guez Gonzalo wrote:
> Hi James:
>=20
> About three weeks ago I got LDP to work in a 3 LSRs scenario. Each router=
 has three interfaces, two of them are used to configure a triangle between=
 the routers (each one connected to the other 2) and the last interface isn=
't configure as MPLS so it could hang non MPLS networks.=20
>=20
> Now the problem is that when a MPLS link falls, LDP daemon ,at the two LS=
Rs wich share that link, stop running. So it's impossible the recovery of t=
he LINK without a reconfiguration of those LSRs.
>=20
> Have you tested this?

Nope.  Please provide details such as any back-traces (translated against y=
our
debug RPM) log file output, diagram of your network, and steps to reproduce.
Hopefully, that will be enough for me to reproduce.  If not, I'll need
additional details, but lets start with this.

In the meantime I'll setup my testbed for link up/down testing and see what=
 I
can find.

> Thanks in advance,
> Gonzalo.
>=20
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> mpls-linux-devel mailing list
> mpls-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jleu@...

Re: [mpls-linux-devel] Looking for testers

From: <gsr16959@al...> - 2007-05-14 09:47

Hi James:

It's good news that you've provided another release for MPLS-Linux. I =
would like to help you testing it but unfortunatelly I won't have time =
for it until September. However, I'll follow the mailing list to be =
updated with the progress you'll make.

Good luck,
Gonzalo.