Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5
|
From: James R. L. <jl...@mi...> - 2007-03-16 05:56:07
|
This doesn't seem to be enough debugging. Try adding: debug zebra rib debug zebra packet On Wed, Mar 14, 2007 at 12:46:57PM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: >=20 > This is what I get in the log file at PE2, maybe these could be helpful t= o understand what's happening: >=20 > As always the NHLFE and ILM entries are created and IP routes learned by = OSPF. >=20 > 2007/03/14 12:04:37 LDP: Terminating on signal > 2007/03/14 12:04:37 ZEBRA: Terminating on signal > 2007/03/14 12:04:37 ZEBRA: netlink_route_multipath() (single hop): RTM_DE= LROUTE 12.0.0.0/24, type IPv4=20 > 2007/03/14 12:04:37 ZEBRA: netlink_route_multipath() (single hop): nextho= p via 10.0.0.1 if 4 > 2007/03/14 12:04:37 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(25= ), seq=3D7 > 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT= M_DELROUTE(25), seq=3D7, pid=3D0 > 2007/03/14 12:04:37 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D3 > 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D3, pid=3D0 > 2007/03/14 12:04:37 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D4 > 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D4, pid=3D0 > 2007/03/14 12:04:37 ZEBRA: IRDP: Received shutdown notification. > 2007/03/14 12:06:02 OSPF: interface 13.0.0.1 [3] join AllSPFRouters Multi= cast group. > 2007/03/14 12:06:22 OSPF: interface 10.0.0.2 [4] join AllSPFRouters Multi= cast group. > 2007/03/14 12:06:40 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now = Init/DROther > 2007/03/14 12:06:42 OSPF: DR-Election[1st]: Backup 13.0.0.1 > 2007/03/14 12:06:42 OSPF: DR-Election[1st]: DR 13.0.0.1 > 2007/03/14 12:06:42 OSPF: DR-Election[2nd]: Backup 0.0.0.0 > 2007/03/14 12:06:42 OSPF: DR-Election[2nd]: DR 13.0.0.1 > 2007/03/14 12:06:42 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now DR > 2007/03/14 12:06:42 OSPF: interface 13.0.0.1 [3] join AllDRouters Multica= st group. > 2007/03/14 12:07:02 OSPF: DR-Election[1st]: Backup 10.0.0.1 > 2007/03/14 12:07:02 OSPF: DR-Election[1st]: DR 10.0.0.1 > 2007/03/14 12:07:02 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now D= ROther > 2007/03/14 12:07:20 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done = (Slave). > 2007/03/14 12:07:20 OSPF: nsm_change_state(12.0.0.1, Loading -> Full): sc= heduling new router-LSA origination > 2007/03/14 12:07:20 OSPF: DR-Election[1st]: Backup 10.0.0.2 > 2007/03/14 12:07:20 OSPF: DR-Election[1st]: DR 10.0.0.1 > 2007/03/14 12:07:20 OSPF: DR-Election[2nd]: Backup 10.0.0.2 > 2007/03/14 12:07:20 OSPF: DR-Election[2nd]: DR 10.0.0.1 > 2007/03/14 12:07:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now B= ackup > 2007/03/14 12:07:20 OSPF: interface 10.0.0.2 [4] join AllDRouters Multica= st group. > 2007/03/14 12:07:25 ZEBRA: netlink_route_multipath() (single hop): RTM_NE= WROUTE 12.0.0.0/24, type IPv4=20 > 2007/03/14 12:07:25 ZEBRA: netlink_route_multipath() (single hop): nextho= p via 10.0.0.1 if 4 > 2007/03/14 12:07:25 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24= ), seq=3D6 > 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT= M_NEWROUTE(24), seq=3D6, pid=3D0 > 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-listen type RTM_NE= WROUTE(24), seq=3D6, pid=3D4294963184 > 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-cmd packet comes f= rom netlink-listen > 2007/03/14 12:07:34 LDP: route 169.254.0.0/16 > 2007/03/14 12:07:34 LDP: num ifindex 0 > 2007/03/14 12:07:34 LDP: ifindex 4 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:34 LDP: route 10.0.0.0/24 > 2007/03/14 12:07:34 LDP: num ifindex 0 > 2007/03/14 12:07:34 LDP: attached > 2007/03/14 12:07:34 LDP: ifindex 4 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:34 LDP: route 13.0.0.0/24 > 2007/03/14 12:07:34 LDP: num ifindex 0 > 2007/03/14 12:07:34 LDP: attached > 2007/03/14 12:07:34 LDP: ifindex 3 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:34 LDP: route 12.0.0.0/24 > 2007/03/14 12:07:34 LDP: num nexthop 0 > 2007/03/14 12:07:34 LDP: nexthop 10.0.0.1 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:44 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D1 > 2007/03/14 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D1, pid=3D0 > 2007/03/14 12:07:59 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING > 2007/03/14 12:07:59 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO: > 2007/03/14 12:08:03 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING > 2007/03/14 12:08:03 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO: > 2007/03/14 12:08:08 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING > 2007/03/14 12:08:10 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D2 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D2, pid=3D0 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-listen type (= 29), seq=3D0, pid=3D0 > 2007/03/14 12:08:10 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), se= q=3D1 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type (2= 9), seq=3D1, pid=3D4294963182 > 2007/03/14 12:08:10 ZEBRA: netlink_talk: ignoring message type 0x001d > 2007/03/14 12:08:10 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000003 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-listen type (= 29), seq=3D1, pid=3D4294963182 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet = comes from mpls-netlink-listen > 2007/03/14 12:08:10 LDP: found pending NHLFE: 0x916d858 >=20 > Thanks in advance, > Gonzalo. >=20 >=20 >=20 > -----Mensaje original----- > De: James R. Leu [mailto:jl...@mi...] > Enviado el: mar 13/03/2007 14:11 > Para: Sienes Rodr?guez Gonzalo > CC: mpl...@li... > Asunto: Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5 > =20 > I see some difference with my testing setup. First, I create all > my routes via vtysh with LDP running at that time, in otherwords: >=20 > I start zebra, ospfd, and ldpd, then start my configuration via vtysh. > I configure EVERYTHING via vtysh. The only interface on the box that is > not configure via vtysh is the managment interface which does not > participate in routing. >=20 > Is there a reason you do not use the system scripts to start zebra ospfd > and ldpd? (ie service zebra start; service ospfd start; service ldpd sta= rt) >=20 > Have you tried turning on zebra debugging? (in vtysh: debug zebra kernel) > You will need to have logging configured for this to produce anything > useful. >=20 > I've run your exact configuration on my network at home at it works just = fine. > There must be something with the order of events that is causing an issue. > Obviously I'd like to fix this issue, but I need to know what "mis-orderi= ng" > is causing it and be able to reproduce it before I can fix it. >=20 > At this point I do not believe you have ever gotten LDP to work for you > so forgive me for being sceptical. >=20 > On Tue, Mar 13, 2007 at 09:27:53AM +0100, Sienes Rodr?guez Gonzalo wrote: > > Hi James: > > =20 > > I?m trying two different experiments with the following scenario and th= ese are the results. > > =20 > > eth0 eth1 eth1 eth0 > > 12.0.0.1-------PE1---------------------PE2-------13.0.0.1 > > .1 10.0.0.0/24 .2 > > =20 > >=20 > > 1? - I create static routes from PE1 to 13..0/24 and PE3 to 12..0/24= .=20 > > =20 > > - Then I launch zebra and ldpd typing zebra -d and ldpd -d by th= e command line.=20 > > (I load the mpls4 module since system boots). > > =20 > > - I configure PE1 and PE3 as LSRs by vtysh: > > =20 > > > "mpls ldp" > > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > > =20 > > - Then I hang a host at 12..0/24 to send packets to 13.1 through= 10..0/24. > > =20 > > - RESULTS: > > =20 > > > Those packets can't even arrive to their destination, cause the sta= tic routes that > > I configured DISAPEAR. From vtysh (sh ip route) I see the new route= s with their LABEL,=20 > > but from the command line (ip route) I just see the default routes = at PE1 and PE3. > > =20 > > > The NHLFE and ILM entries for that routes are created properly: > > =20 > > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > > =20 > > ILM entry label gen 10000 labelspace 0 proto ipv4 > > pop peek (0 bytes, 0 pkts) > > =20 > > > So the problem is that with those entries the control component isn= 't able to change=20 > > the kernel routes. > > =20 > > 2? - I launch zebra and ospfd.=20 > > =20 > > - Then I configure ospf by vtysh: "router ospf" -> "network 10.0= .0.0/24 area 0" (PE1 and PE3) > > -> "network 12.0.0.0/24 area 0" (PE3) > > -> "network 13.0.0.0/24 area 0" (PE1) > > =20 > > - After new routes are learned I close vtysh, launch ldpd and con= figure PE1 and PE3 as LSRs by vtysh: > > =20 > > > "mpls ldp" > > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > > =20 > > - Then I hang a host at 12..0/24 to send packets to 13.1 through = 10..0/24. > > =20 > > - RESULTS: > > =20 > > > Those packets arrive to their destination, but without a label.= >From vtysh (sh ip route) I see the new ospf=20 > > routes with their hop count (not any label) and from the comma= nd line (ip route) I see the same routes learned by ospf. > > =20 > > > The NHLFE and ILM entries for that routes are created properly: > > =20 > > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > > =20 > > ILM entry label gen 10000 labelspace 0 proto ipv4 > > pop peek (0 bytes, 0 pkts) > > =20 > > > So the problem, again, is that with those entries the control co= mponent isn't able to change=20 > > the kernel routes. > > =20 > > Any idea of what's happening? As I told you, if you could provide me so= me documentation for understanding how the code is organized, maybe I could= help. > > =20 > > Thanks for your time, > > Gonzalo. > >=20 >=20 >=20 >=20 > --=20 > James R. Leu > jl...@mi... >=20 --=20 James R. Leu jl...@mi... |
